Don't turn Continuous Discovery into Dogmatic Discovery​Dear Reader,​ When I recently talked to Vivek Kumar for my work-in-progress book, this insight stood out: "The biggest moat you can always have is how fast you can learn." And a recurring theme in a recent Product Discovery workshop was to hold every decision in Product Discovery against "whether it helps reduce lead-time to actionable insights (aka lead-time until we reduce uncertainty). One of the main reasons I see product teams neglect the importance of that lead time is that they stick to a rigid order of activities at all costs. They get stuck in dogmatic Product Discovery. As your teams become more comfortable with deliberate Product Discovery and learn better practices, they may adopt a rigid, Dogmatic adherence to different “rules” of discovery. This represents a significant step forward from Alibi Discovery because it means teams are actively thinking about and incorporating systematized Product Discovery, but it comes with downsides. Characteristics of this state:
Clear signs you have to move on: Teams feel that the discovery process and act get in their way of creating value. Completing a Discovery task gets more priority than the quality of insights generated and decisions made, and the seemingly irrational volume of work raises questions. Did you enjoy this one or have feedback? Do reply. It's motivating. I'm not a robot; I read and respond to every subscriber email I get (just ask around). If this newsletter isn't for you anymore, you can unsubscribe here. Thank you for Practicing Product, ​Tim​ How to Dive Deeper into Product DiscoveryLearn how I helped companies like Deutsche Telekom and Forto hone their Product Discovery practices. I closely work with product organizations through workshops and coaching to introduce and adapt Product Discovery.
What did you think of this week's newsletter? As a Product Management Coach, I guide Product Teams to measure the progress of their evidence-informed decisions. I identify and share the patterns among better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery. |
1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes. Explore my new book on realprogressbook.com
Product Practice #417 User Outcomes are Positively Flipped User Problems PUBLISHED Jul 17, 2026 READ ON HERBIG.CO Dear Reader, Last week, I mapped how OKRs connect to the layers of an Opportunity Solution Tree. But especially the Outcome layer deserves its own issue: turning a customer problem into a team-level Key Result. I first wrote about it in 2023, before I had a name for it. Since then, the positivity flip has become one of the most-used tools in my OKR and Discovery workshops, so...
Product Practice #416 How to Connect OKRs to OSTs PUBLISHED Jul 10, 2026 READ ON HERBIG.CO Dear Reader, OKRs (Objectives and Key Results) help you measure strategic progress. OSTs (Opportunity Solution Trees) are a visual structure for connecting solution and problem spaces to business goals. Let me break down how the layers of an OST connect to the practices of OKR drafting and execution: Layer 1: The Outcome Teresa differentiates between business outcomes, product outcomes, traction metrics...
Product Practice #415 Accelerated Context and the Validation Sparring Partner PUBLISHED Jul 3, 2026 READ ON HERBIG.CO Dear Reader, Most of the AI conversation in product management right now is either describing doomsday scenarios, exaggerated improvements, or warning about what might go wrong. But I am more interested in what changes for product teams doing real work. When a product team adopts an AI tool, what specifically changes about their day? What benefit do they keep coming back for,...