<?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 Ejiro Oke on Medium]]></title>
        <description><![CDATA[Stories by Ejiro Oke on Medium]]></description>
        <link>https://medium.com/@ejiroogheneoke?source=rss-493818bef8df------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*B-cyST7WhGl3i0W7d34YTA.jpeg</url>
            <title>Stories by Ejiro Oke on Medium</title>
            <link>https://medium.com/@ejiroogheneoke?source=rss-493818bef8df------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:55:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ejiroogheneoke/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[Building “Fast” Starts with Talking Right: Why ‘Managing Up’ Isn’t Enough]]></title>
            <link>https://medium.com/@ejiroogheneoke/building-fast-starts-with-talking-right-why-managing-up-isn-t-enough-6e3522b12e58?source=rss-493818bef8df------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e3522b12e58</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[stakeholder]]></category>
            <dc:creator><![CDATA[Ejiro Oke]]></dc:creator>
            <pubDate>Sat, 26 Apr 2025 12:39:25 GMT</pubDate>
            <atom:updated>2025-04-26T15:04:48.866Z</atom:updated>
            <content:encoded><![CDATA[<p>&quot;Managing up&quot; and &quot;managing across&quot; are common concepts that professionals across different job functions and industries are familiar with. These principles are about understanding how to effectively communicate with and influence others—whether that&#39;s superiors, peers, or cross-functional teams, they get hammered into PMs, engineers, and ICs across industries. But when the flow of communication flips — when business leads, stakeholders, or executives need to communicate <em>downward or across</em> — there’s often little or no pressure to be clear, structured, or collaborative. And that’s where the real problem lies.</p><p><strong>And that gap? It creates:</strong></p><ul><li>Vague requests</li><li>Messy expectations</li><li>A whole lot of unnecessary thrash</li></ul><p>If you’ve ever sat in a meeting thinking, <em>“What are we even deciding here?”</em> — you know the feeling.</p><h4><strong><em>Why does this happen?</em></strong></h4><p><strong>Power dynamics</strong>: There’s often an implicit assumption that PMs and engineers will adapt to stakeholders’ communication styles and emotional needs, but this expectation doesn’t tend to flow in the opposite direction.</p><p><strong>Lack of cross-functional alignment</strong>: Stakeholders, particularly those from non-technical backgrounds, can sometimes default to simply “telling us what they want” rather than engaging in a meaningful dialogue to ensure the ‘how’ and ‘why’ behind those requests are aligned with the overall strategy. (Not because they’re malicious — it’s just how they’re used to working.)</p><p><strong>So what do PMs &amp; ICs do? </strong>We create frameworks. We prompt for specifics. We triage chaos.</p><p>Sometimes we sound annoying. I recently saw this <a href="https://www.instagram.com/reel/DHmEFcfu9I_/?utm_source=ig_web_copy_link">reel</a> poking fun at PMs constantly interrupting conversations:</p><blockquote><em>“What problem are you solving?”</em><br> <em>“It’s not on the roadmap.”</em><br> <em>“Let’s treat it in </em><strong>Q5</strong><em>.” — </em>I knoww 😂😂<br>Cue: “Hard-stop”</blockquote><p><em>Funny</em>? Sure.<br>The comment sections under that skit? Also full of humorous frustration — not at the questions themselves, but at how communication had already broken down <em>long before</em> the questions started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLDQywiZhRSA4UglZ6hfdA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T3IcI6xPvS9iDX_9JR-V1g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dH4eFy0qWK-UfStGHxi3KQ.jpeg" /></figure><h4>The real tension:</h4><blockquote>One side wants space to “just talk.”<br>The other is under pressure to listen, interpret, prioritize, and <em>ship.</em></blockquote><p>Nobody’s wrong.<br>But without <em>shared standards and expectations</em> around communication, friction becomes the default.</p><h4>The bigger irony</h4><p>It gets messier when stakeholders come from big orgs into startups.<br>They crave and expect speed and flexibility — but resist any semblance of structure as <strong><em>“bureaucracy.”</em></strong> And once <strong><em>the B-word</em></strong> is mentioned, the conversation shifts from a discussion of process to a debate about “slowness” and “red tape.” Emotion takes over, and logic often gets sidelined.</p><p>But here’s the key: <strong><em>Startups move fast because of clarity — not in spite of it.</em></strong> When you cut corners, you don’t accelerate progress. You just burn more time fixing what wasn’t clear the first time around.</p><ul><li>You undermine accountability</li><li>You create decision fatigue</li><li>You slow down the very speed you came for</li></ul><p>Not every framework is red tape.<br>Sometimes it’s the only thing standing between momentum and chaos.</p><h4>Fast ≠ Frantic</h4><p>At #ProductCon last year, Des Mazery shared a powerful insight in his keynote:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7m7o-P3zbbk%3Fstart%3D1303%26feature%3Doembed%26start%3D1303&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7m7o-P3zbbk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7m7o-P3zbbk%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/caee72113d6234f8930a26e778c96d6e/href">https://medium.com/media/caee72113d6234f8930a26e778c96d6e/href</a></iframe><blockquote>“Success in Product-Led Growth (PLG) isn’t solely on product managers — it requires every department to be aligned and accountable for their role in development and growth.”</blockquote><p>This perfectly echoes the point: clear, structured communication and alignment across teams are what make fast movement possible. It’s not just about <em>speed</em>; it’s about getting everyone moving in sync.</p><p><strong>Startups aren’t allergic to structure.</strong><br>They’re allergic to <em>unnecessary</em> structure. There’s a difference between creating clarity and creating bureaucracy.<br>And we owe it to each other — across Product, Sales, Growth, Ops — to know the difference.</p><p>And that kind of alignment?</p><ul><li>It takes structured communication</li><li>Mutual understanding</li><li>Not one-way requests.</li></ul><h4><strong>How to Actually Build “Fast” Through Clear Communication?</strong></h4><p>As Product people — we’re charged with building the foundation for scalable, sustainable speed. Here’s how to take action and push the boundaries of what “fast” means in your team:</p><ol><li><strong>Be the Catalyst for Communication Frameworks</strong>: Don’t wait for clarity to emerge through conversations that go around in circles. Start by defining what a well-structured discussion looks like. Ensure that meetings start with a clear agenda and actionable outcomes, and keep documentation simple but precise for easy reference.</li><li><strong>Institute a “Problem-Solving First” Culture</strong>: Instead of getting lost in the noise of feature requests or random stakeholder input, frame every conversation around solving a problem.</li><li><strong>Enforce Real-Time Prioritization</strong>: Speed doesn’t mean rushing through work — it means aligning priorities swiftly. When stakeholders make requests, challenge them to clarify whether their ask aligns with the current business priority. <em>Use tools like Aha! or Trello to visually prioritize and align tasks, ensuring everyone knows what’s most important and why.</em></li><li><strong>Master the “Collaborative Decision-Making” Process</strong>: One of the quickest ways to create chaos is by leaving decisions to one person. Encourage shared decision-making by setting up cross-functional working sessions where stakeholders from all areas (marketing, engineering, design) can provide input. Decision-making should be a transparent, team-wide activity, not siloed into a single person’s desk. <em>Create shared decision-making spaces — tools like Miro or Google Docs can help teams ideate and make decisions collectively without unnecessary back-and-forth.</em></li><li><strong>Push for Structured Feedback Loops</strong>: It’s easy to get caught in a cycle of sprinting without reflecting on whether we’re headed in the right direction. Make it a point to build in structured retrospectives, even when the pace seems high. After each milestone or key release, get feedback not only from your direct team but from cross-functional stakeholders. This feedback loop allows you to course-correct early and avoid larger missteps later on. Implement tools like Jira for ongoing tracking, and hold brief weekly check-ins for feedback to catch misalignments early and avoid bottlenecks.</li></ol><p>These aren’t just “nice ideas”; they are the mechanisms that allow you to control the pace of work without sacrificing clarity or alignment.</p><p>It’s on Product, to set the standards of how we communicate and drive decision-making.</p><p>We can only move fast when everyone’s working off the same playbook — and that starts with defining, creating, and protecting structured communication every day.</p><p>Let’s make speed a byproduct of clarity — not chaos.<br> PMs and engineers aren’t service desks.<br> We’re partners in building and we can only move fast when everyone’s working off the same playbook — and that starts with defining, creating, and protecting structured communication every day.</p><p><em>And, it’s on Product to lead that work — not wait for it.</em></p><p>Efficiency doesn’t happen by accident. It’s built on purpose, through how we talk, decide, and move together.</p><p><strong>— Good sync.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e3522b12e58" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>