<?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 David McDougall on Medium]]></title>
        <description><![CDATA[Stories by David McDougall on Medium]]></description>
        <link>https://medium.com/@dmcdougall?source=rss-226e559bdb37------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YoLpjNNCjHc0i9O9J3XjYw@2x.jpeg</url>
            <title>Stories by David McDougall on Medium</title>
            <link>https://medium.com/@dmcdougall?source=rss-226e559bdb37------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:11:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dmcdougall/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[Personal learnings from the 2019 JAM Product Leaders Weekend]]></title>
            <link>https://medium.com/@dmcdougall/personal-learnings-from-the-2019-jam-product-leaders-weekend-e46ddb9ee81f?source=rss-226e559bdb37------2</link>
            <guid isPermaLink="false">https://medium.com/p/e46ddb9ee81f</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[David McDougall]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 14:07:10 GMT</pubDate>
            <atom:updated>2019-04-11T14:09:59.882Z</atom:updated>
            <content:encoded><![CDATA[<p>I spent this past weekend at <a href="https://www.jamlondon.io/events/experiences/jam-product-leaders-weekend-2019">JAM Product Leaders Weekend</a> with 40 amazing and inspiring Product leaders at a <a href="https://www.coldatnight.co.uk/">farmhouse in Wales</a>, discussing our challenges and sharing best practices. (We also found time for some canoeing, foraging, sauna-ing, eating, and making new friends 😊 ) Every speaker and every conversation I had over the course of the weekend taught me something, or challenged me, or reminded me of things that I will focus on going forward. A huge thanks up front to <a href="https://www.linkedin.com/in/mathildeleo/">Mathilde</a>, <a href="https://www.linkedin.com/in/sebastienpowell/">Seb</a>, and <a href="https://www.linkedin.com/in/jessiegiladi/">Jessie</a> for putting it together!</p><p>For my own reference as well as to inspire some conversation, I’ve documented a few insights that resonated especially strongly for me:</p><p><a href="https://www.linkedin.com/in/kevinshanahan1/">Kevin Shanahan</a> from Memrise talked about building effective squads, and placing a ‘Magic Trio’ of Design, Product, and a Tech Lead at the centre of a squad. The Magic Trio should refine ideas before getting the rest of the team involved, with each of them focused on a specific criteria: Desirability should be led by the Designer, Viability by the Product Manager, and Feasibility by the Tech Lead. These are the leaders and decision-makers within the squad.</p><p><a href="https://www.linkedin.com/in/ellenmurula">Ellen MacKay</a> from Monzo framed 5 traps that keep us from building ‘Speed as a Habit’ in our teams. Two antipatterns that resonated for me especially were ‘Lead with vision’ and ‘Build a good relationship with stakeholders.’ To remedy leading with vision, Ellen suggested fast feedback loops and having only 2–6 weeks of backlog in play. I think there may be limits to this approach, but I think our overwhelming bias should be to build this approach in our teams. The more teams can ‘Ship to Learn,’ as they say at Intercom, the more effective we can be in building value for users and the companies in which we work.</p><p>To counteract the ‘Build a good relationship with stakeholders’ trap, Ellen painted a vision of team autonomy based on risk ownership, where owners of the product decisions also own the risks associated with them. When the limits to a team’s authority are defined in advance, they are then empowered to make decisions without needing to reach stakeholder consensus before taking action.</p><p>These were just a few of the insights I took from the formal talks; from other talks and conversations, here are a few few brief notes and reminders that feel worth sharing:</p><ul><li>Storytelling is an important, high-leverage component of effective Product management. (Thanks <a href="https://www.linkedin.com/in/janehoney/">Jane</a>)</li><li>What would you do to set up your team for success if you only had 90 days left in your current role? OK, now go do that. (Thanks <a href="https://www.linkedin.com/in/konradin-breyer-054a1433/">Koin</a>)</li><li>Think about the Task Relevant Maturity of your team members when decided how hands-on or hands-off to be in managing them… also, Andy Grove is the best. (Thanks <a href="https://www.linkedin.com/in/antoinesakho/">Antoine</a>)</li><li>OKRs are also products that we can optimise; you might not get OKRs right the first time, or even the second, but starting is the most important thing. It’s helpful to decide in advance what percentage of the team’s efforts should be devoted to OKRs, and how much to allocate to maintenance and business as usual. (Thanks <a href="https://www.linkedin.com/in/herbigt/">Tim</a>)</li></ul><p>And a few additional notes from our fireside chats:</p><ul><li>Before embarking on any experiment, clarify exactly what you hope to learn, and exactly what actions you will do based on that learning.</li><li>Clear naming rules for data fields can help democratise the use and understanding of data — which leads to more effective decision-making, more evenly distributed, at a faster pace.</li><li>Remove RACI communication overheads, and create trust in others’ autonomy.</li><li>Avoid creating mini-waterfalls — most dependencies aren’t true depencies, and can be eliminated by allowing teams to own their own risk. When there are true dependencies, team members should unblock themselves.</li><li>The lesson that brings together everything we talked about over the weekend: The two focuses on a Product Leader should be to increase your team’s <strong>decision velocity</strong> and their <strong>execution velocity</strong>.</li></ul><p>This was a truly transformative event for me — I’m excited to apply these learnings and to share more of my experiences with this amazing group in the near future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vMH04CcQnh4nf_Mkly_V6g.jpeg" /><figcaption>The official group photo :)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e46ddb9ee81f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>