<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Product Discovery on RoadmapOne Blog</title>
    <link>https://roadmap.one/blog/categories/product-discovery/</link>
    <description>Recent content in Product Discovery on RoadmapOne Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Tue, 24 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://roadmap.one/blog/categories/product-discovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Product Discovery in Roadmaps: Why Your Invisible Discovery Work Keeps Getting Cut</title>
      <link>https://roadmap.one/blog/posts/blog9-product-discovery-in-roadmaps/</link>
      <pubDate>Tue, 21 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-product-discovery-in-roadmaps/</guid>
      <description>Discovery work is invisible in most roadmaps—which is why it gets cut first and costs you most. Here&amp;rsquo;s how to make discovery visible, measurable, and defensible when stakeholders ask why you&amp;rsquo;re not shipping faster.</description>
    </item>
    <item>
      <title>Double Diamond: Process Framework, Not Prioritisation—And It Needs a Time-Box</title>
      <link>https://roadmap.one/blog/posts/blog9-11-double-diamond/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-11-double-diamond/</guid>
      <description>The Double Diamond describes how to do discovery—diverge, converge, diverge, converge. It&amp;rsquo;s a process framework, not a prioritisation framework. Without time-boxing, it becomes an excuse for endless exploration.</description>
    </item>
    <item>
      <title>GIST Framework: You Probably Already Have This Under Different Names</title>
      <link>https://roadmap.one/blog/posts/blog9-8-gist-framework/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-8-gist-framework/</guid>
      <description>GIST (Goals, Ideas, Steps, Tasks) offers a layered planning framework from strategy to execution. Learn how it compares to OKRs, when the confidence meter concept is genuinely useful, and why you probably don&amp;rsquo;t need the full framework.</description>
    </item>
    <item>
      <title>Impact Mapping: Always Think About the User (Because Most Roadmaps Don&#39;t)</title>
      <link>https://roadmap.one/blog/posts/blog9-10-impact-mapping/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-10-impact-mapping/</guid>
      <description>Gojko Adzic&amp;rsquo;s Impact Mapping forces the question most roadmaps ignore: who are we building for, and what behaviour change do we need from them? It&amp;rsquo;s the &amp;lsquo;always think about the user&amp;rsquo; framework that architects desperately need.</description>
    </item>
    <item>
      <title>Opportunity Solution Trees: Discovery That Maps to Roadmap Reality</title>
      <link>https://roadmap.one/blog/posts/blog9-9-opportunity-solution-tree/</link>
      <pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-9-opportunity-solution-tree/</guid>
      <description>Teresa Torres&amp;rsquo; Opportunity Solution Tree connects outcomes to opportunities to solutions to experiments. It maps directly to RoadmapOne: Outcomes are Objectives, Opportunities and Solutions become Key Results, and we&amp;rsquo;re always running experiments.</description>
    </item>
    <item>
      <title>From Objectives to Key Results: How Product Managers Lead the Discovery Breakdown</title>
      <link>https://roadmap.one/blog/posts/blog9-7-objectives-to-key-results/</link>
      <pubDate>Mon, 27 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-7-objectives-to-key-results/</guid>
      <description>Leadership allocates objectives. Empowered teams define key results. But how does that actually happen? Discovery is the collaborative workshop where product managers facilitate the breakdown from &amp;lsquo;Increase retention 65% to 75%&amp;rsquo; to specific, validated, measurable key results teams commit to delivering. Master this moment—it&amp;rsquo;s where PM leadership matters most.</description>
    </item>
    <item>
      <title>Time-Boxed Discovery: Why Concentrated Discovery Beats Drip-Drip Validation Every Time</title>
      <link>https://roadmap.one/blog/posts/blog9-6-time-boxed-discovery/</link>
      <pubDate>Mon, 27 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-6-time-boxed-discovery/</guid>
      <description>Most teams let discovery drip along for months, creating context switching and unpredictable capacity drain. Time-boxed discovery sprints produce better validation outcomes while making capacity planning honest. Learn why concentrated discovery beats ongoing research—and how to implement it.</description>
    </item>
    <item>
      <title>7 Common Product Discovery Mistakes (And How to Avoid Them)</title>
      <link>https://roadmap.one/blog/posts/blog9-1-product-discovery-mistakes/</link>
      <pubDate>Tue, 21 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-1-product-discovery-mistakes/</guid>
      <description>Avoid the seven most common product discovery mistakes that cause teams to build the wrong things. Learn how to conduct effective discovery that validates assumptions, engages customers, and delivers business value.</description>
    </item>
    <item>
      <title>Allocating Team Capacity for Product Discovery: How Much Is Enough?</title>
      <link>https://roadmap.one/blog/posts/blog9-4-allocating-discovery-capacity/</link>
      <pubDate>Tue, 21 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-4-allocating-discovery-capacity/</guid>
      <description>Learn how to allocate the right amount of team capacity to product discovery. Practical frameworks for balancing discovery and delivery based on uncertainty, risk, and product lifecycle stage.</description>
    </item>
    <item>
      <title>Product Discovery for Remote and Distributed Teams: Making It Work Across Time Zones</title>
      <link>https://roadmap.one/blog/posts/blog9-2-discovery-remote-teams/</link>
      <pubDate>Tue, 21 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-2-discovery-remote-teams/</guid>
      <description>Master product discovery with remote and distributed teams. Learn practical strategies for running effective customer interviews, synthesis sessions, and collaborative discovery when your team is spread across locations and time zones.</description>
    </item>
    <item>
      <title>Product Discovery Metrics and KPIs: How to Measure Discovery Success</title>
      <link>https://roadmap.one/blog/posts/blog9-3-measuring-discovery-success/</link>
      <pubDate>Tue, 21 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-3-measuring-discovery-success/</guid>
      <description>What are the key metrics for measuring product discovery success? Not interviews conducted or prototypes shipped—those are vanity metrics. Track validated learning rate, assumption-to-evidence cycle time, and outcome velocity. Here are the discovery KPIs that actually predict product success.</description>
    </item>
    <item>
      <title>The Product Manager&#39;s Guide to Leading Discovery: Building Team Ownership and Engagement</title>
      <link>https://roadmap.one/blog/posts/blog9-5-leading-discovery-activities/</link>
      <pubDate>Tue, 21 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog9-5-leading-discovery-activities/</guid>
      <description>Master the product manager&amp;rsquo;s most critical leadership role - guiding teams through discovery to break down objectives into key results, building ownership and enthusiasm for outcomes that matter to the business.</description>
    </item>
  </channel>
</rss>
