<?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 Tomer Jan on Medium]]></title>
        <description><![CDATA[Stories by Tomer Jan on Medium]]></description>
        <link>https://medium.com/@tomerjan?source=rss-c491e63edb5d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lbrW6VtUrg3w-wgonm2-GA.jpeg</url>
            <title>Stories by Tomer Jan on Medium</title>
            <link>https://medium.com/@tomerjan?source=rss-c491e63edb5d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:03:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tomerjan/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[The Retro Revelation: When Silence Spoke Volumes]]></title>
            <link>https://medium.com/@tomerjan/the-retro-revelation-when-silence-spoke-volumes-3b26d9baf13a?source=rss-c491e63edb5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b26d9baf13a</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Tomer Jan]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 16:01:25 GMT</pubDate>
            <atom:updated>2025-07-10T16:01:25.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_7jhXyXbzjxGZYhVBdUfA.jpeg" /></figure><p>It started like pretty much any other casual sprint retrospective. You know the drill: graphs up on the screen, a quick chat about what went well, and then brainstorming ways to boost our velocity. Then came that familiar lull, the silence that just hangs in the air when nobody wants to speak first. Trying to break the ice, I just blurted out, “So, what do you guys think?”</p><p>More silence. And then, our product manager spoke, a mix of honesty and palpable frustration in his voice: “We’re still taking on too much technical debt and not enough of the valuable product work we actually committed to.” I knew the team was busting their tails, seriously. Production issues, unexpected geopolitical events, shifting priorities - they all played a part. But his words lit a fire, kicking off an open discussion, and a clear sentiment started emerging: the team felt they weren’t working on meaningful product features, the kind that actually moved the needle.</p><p>That hit me like a ton of bricks<em>.</em> Every quarter, we pour hours into detailed planning, intensive prep, and clear focus areas. How could they possibly feel this way? The underlying feedback became painfully clear: “We’re not sure what our value is here,” they said. “We feel we have little contribution to the business. We have one or two big features a quarter, and the rest is just small tasks.”</p><p>As the team’s manager, I immediately went into scramble mode. If the team’s perspective was so profoundly misaligned with mine and the product’s, what on earth had we screwed up? This wasn’t just a tough retro; it was a wake-up call<strong>.</strong> It hammered home a fundamental truth: we always, <em>always</em> need to keep communication with the team crystal clear and transparent.</p><p>It turns out, that uncomfortable silence in the retro was a gift. It forced me to confront a gap in our team’s understanding, a gap created by a lack of consistent, transparent communication. When you open up, share context, and bring your team into the full picture, you’re not just informing them; you’re <strong>empowering</strong> them. You’re building <strong>trust</strong>, showing them that their perspective matters, and that they’re valued contributors to something much larger than just their immediate task list.</p><p>That sense of belonging, of being truly “in the loop” and understanding their impact, is what transforms a group of individuals into a powerful, unified force. Let’s make sure our teams never have to guess their value again.</p><p>If any of this sounds familiar, the silence, the misalignment, the sense that your team is busy but not quite sure they’re building the right things it’s probably a good time to pause and make sure everyone understands the <strong>“why”</strong> behind their work and why it actually matters.</p><p>Ask yourself:</p><ul><li>Do people on your team know why the work matters?</li><li>Are you repeating the goals often enough that they stick?</li><li>Do folks feel like contributors, or just ticket closers?</li></ul><p>That retro was a reminder for me to regularly check in with the team and keep them close to the bigger picture, not just what they’re doing, but <strong>why</strong> they’re doing it.</p><p>Here’s what we started doing differently:<br> Since we’re a small team of four engineers, it was manageable to bring everyone together for a conversation about the upcoming quarter. What we plan to build, what the goals are, and what challenges we expect. Just getting everyone into that room made a difference. You could feel the shift in energy and engagement right after.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b26d9baf13a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>