<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anna Luky on Medium]]></title>
        <description><![CDATA[Stories by Anna Luky on Medium]]></description>
        <link>https://medium.com/@anya_lu?source=rss-8c4c56ab4ba0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*l5eqAOYIsh3qqe2lLeomPQ.jpeg</url>
            <title>Stories by Anna Luky on Medium</title>
            <link>https://medium.com/@anya_lu?source=rss-8c4c56ab4ba0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:06:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anya_lu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Creating a lightweight knowledge exchange for our design team]]></title>
            <link>https://medium.com/@anya_lu/creating-a-lightweight-knowledge-exchange-for-our-design-team-5eec3ccf372d?source=rss-8c4c56ab4ba0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5eec3ccf372d</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <dc:creator><![CDATA[Anna Luky]]></dc:creator>
            <pubDate>Wed, 13 May 2026 12:51:42 GMT</pubDate>
            <atom:updated>2026-05-13T12:51:42.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_c1yQRWT7I7FVBkKwzEJA.jpeg" /></figure><p>During one of our design retros, someone mentioned what many of us had already been feeling: we needed more space to learn from each other.</p><p>We had tried knowledge-sharing sessions before, but they never really lasted. Things move fast at our company, and if something doesn’t survive the first few weeks, it usually disappears quietly.</p><p>Still, this felt worth trying again.</p><p>So we approached it differently. We kept it intentionally lightweight, low-pressure, and easy to join. No heavy preparation. No mandatory participation. Just space for the team to exchange ideas and learn from each other.</p><p>A few months later — which feels like a long time in our world — we had run 10 sessions. Almost half the team had hosted at least one. Somehow, this small experiment turned into a ritual that actually stuck.</p><p>I knew the initiative had to feel easy to participate in.</p><p>Nobody wants another process layered on top of their actual work. Preparing or hosting a session needed to stay manageable, both for the presenters and for me as the person organizing it.</p><p>Ideally, the initiative would eventually sustain itself — and over time, that’s exactly what happened.</p><p>A few principles shaped it from the beginning:</p><ul><li>Remote-friendly by default</li><li>Optional participation</li><li>Low preparation effort</li><li>Flexible formats</li></ul><p>Hosting a session was always celebrated, but never expected.</p><h3>Exchange formats</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3s2NpTqH3rwkVha6XsWkpg.png" /></figure><h3><strong>Knowledge roundtable</strong></h3><p>On paper, it’s fun — everyone shares quick takes on one topic.<br>In reality, it didn’t really land, and it is the least used format so far.</p><p>Tip: Watching something together (e.g. conference talks) and then discussing it is a perfect use of this format. We casually watched and discussed <a href="https://www.youtube.com/watch?v=FPpzI7z_U-o">Figma Buzz</a> as our first session while sipping drinks. Very easy entry to the knowledge exchange.</p><h3><strong>Design digest</strong></h3><p>Someone brings an industry topic, article, or trend to the group with a bit of preparation beforehand (usually no more than 20 minutes). The real value comes from the discussion itself.</p><p>It works best when the topic is shared in advance so people have time to gather thoughts or examples. At the same time, it’s important to keep the format open enough that anyone can jump in, even if they didn’t prepare.</p><p>One thing that worked surprisingly well for us was pasting the full article directly into the FigJam board and encouraging people to annotate it live while reading. It made discussions much more dynamic, especially for topics like <a href="https://medium.com/r?url=https%3A%2F%2Fwebflow.com%2Fblog%2Fai-powered-prototyping-design-at-webflow">AI-powered prototyping</a> where everyone had slightly different perspectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I7IB-kZPjDMpa8avyCaqcg.png" /><figcaption>Tip: paste the entire article to the board, and suggest people to markup and annotate as they read to dive even deeper to the source.</figcaption></figure><h3><strong>Show &amp; tell</strong></h3><p>This became one of our most popular formats.</p><p>Someone shares a tool, workflow, lesson, conference takeaway, or small practice that helped them in their work. The key is keeping it focused on learnings the rest of the team can actually use.</p><p>We also learned pretty quickly that shorter presentations work better. We usually aim for roughly a 50/50 split between sharing and discussion, which keeps the energy up and makes the sessions feel collaborative rather than performative.</p><p>Some sessions were practical demos. Others turned into bigger conversations around process, AI, or design decisions. Even quick “tips &amp; tricks” sessions around Figma shortcuts ended up being surprisingly valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*14AvEoscJIZZX6HlRk4SBg.png" /><figcaption>Team’s favorite Figma Shortcuts gather, prepared and shared by one of our designers.</figcaption></figure><p>Besides that we also created a Slack channel to share learnings — any interesting article, or a quick learning nugget, or a reflection could be dropped there.</p><p>For team sessions Design digest and Show &amp; Tell became our anchors. Some sessions sparked endless debates. Some were super short and gave us tangible tips. Some even led to new initiatives.</p><h3>Topics</h3><p>We didn’t restrict the team, and didn’t define the topics. We followed a simple rule: it should benefit the entire group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xTBJPBwTNLg7wK6dbn8KUg.png" /><figcaption>It is important to keep knowledge exchange sessions relevant for everyone.</figcaption></figure><h3>The rules that kept it alive</h3><p>As the initiative became part of the team rhythm, we added a few lightweight principles:</p><ul><li>Work comes first. Delivery, critiques, and project feedback always take priority.</li><li>Keep sessions short. Use the smallest amount of time needed for the topic, while leaving room for discussion.</li><li>Stay organized. Record sessions, document takeaways, and keep scheduling flexible so learning never blocks critical work.</li></ul><p>The structure stayed intentionally light. Just enough to create consistency without turning the initiative into another process.</p><h3>What I learned leading this</h3><p>Not every team initiative needs to be ambitious to matter. Sometimes the important part is simply creating a small, sustainable space for people to connect and learn from each other.</p><p>A few things became clear pretty quickly:</p><ul><li>Not every format works — and that’s fine. Dropping the roundtable format gave us more space for the formats people genuinely enjoyed.</li><li>Consistency mattered more than polish. Ten sessions over four months told me the team valued regular opportunities to exchange ideas, even when sessions were informal.</li><li>Variety kept people engaged. Debates, demos, conference talks, workflows, AI discussions — different formats attracted different people.</li></ul><h3>The impact so far</h3><ul><li>The biggest change was probably how connected the team started to feel.</li><li>During our next retrospective, the initiative came up repeatedly as something people genuinely appreciated. We were learning from each other faster, and in ways that actually stuck.</li><li>The sessions also created space for people to share ideas without pressure or judgment. Some team members hosted sessions for the first time. Others contributed casually during discussions. Both mattered equally.</li><li>Over time, other teams in the organization also became curious about how we ran the exchange, which sparked broader conversations around learning culture and knowledge sharing.</li></ul><h3>Tips if you want to try something similar</h3><ul><li>Don’t aim for perfection: start small and iterate.</li><li>Reduce friction end entry level. Start as simple as watching a conference talk together (we watched one of the Config talks), followed by a casual exchange. Remote or in person, that creates absolutely no pressure and could be a nice low effort start.</li><li>Keep preparation under 20 minutes so no one feels burdened.</li><li>Rotate hosts to share ownership. You can suggest someone to setup a session, but make sure it doesn’t become a chore.</li><li>Be ready to drop what doesn’t work, or turn all the way around.</li></ul><h3>Closing</h3><p>Creating team culture doesn’t always require a big strategy. Sometimes it starts with noticing a need, creating space for it, and giving it enough consistency to grow.</p><p>This initiative started as a small experiment — essentially a “what if we tried this again?” moment — and slowly became part of how our team works together.</p><p>If you want to try something similar, keep it simple, keep it lightweight, and focus on creating the conditions for people to participate naturally.</p><p>That’s usually enough for something meaningful to take root.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5eec3ccf372d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>