Why your Product Discovery Feels too Theoretical


Why your Product Discovery
Feels too Theoretical

READ ON

HERBIG.CO

PUBLISHED

Apr 25, 2025

READING TIME

4 min & 17 sec

​Dear Reader,​

Over the past two weeks, I've explored treating Product Strategy and OKRs like products to avoid Alibi Progress. Today, let's tackle the practice that often gets dismissed as "good in theory, impossible in practice" — Product Discovery.

When teams tell me "we don't have time for proper Discovery," they're usually stuck in Alibi Progress — focusing on following lengthy processes rather than reducing uncertainties from wherever they are right now. Discovery doesn't need a 28-phase framework to be valuable.

Let's treat Discovery like a product to make it practical:

For product teams, Product Discovery helps reduce uncertainty about problems and solutions worth pursuing. We know it's valuable when investment decisions are based on reliable evidence rather than assumptions, and teams avoid building features that don't solve validated problems.

Let's unpack this value statement:

For your audience (product teams with high uncertainty)

  • Discovery isn't equally valuable for all teams at all times—its intensity should match your level of uncertainty.
  • Teams with established products in mature markets might need less extensive discovery than those entering new spaces.
  • If stakeholders become the primary audience, Discovery risks becoming a theater of validation rather than genuine learning.

For the problem you're solving (reducing risk through evidence):

For your success measures (evidence-based decisions):

  • Track how many feature ideas were discarded based on Discovery evidence (a healthy Discovery process kills bad ideas).
  • Monitor the adoption of shipped features that went through Discovery versus those that didn't. Putting an Epic into the Done column doesn't mean it had an Impact on customer behavior or business goals.
  • Evaluate how quickly teams reach sufficient confidence to make decisions, not just how many research activities they completed.

Instead of worrying about following discovery theory, I recommend a practical approach: the "one-week test." If you could spend one week reducing uncertainty about your biggest uncertainty, what would you do? This approach forces teams to focus on high-leverage activities rather than comprehensive processes.

Remember: You're not a better product manager because you followed a six-phase Discovery process exactly. You're better when you can confidently explain, based on reliable evidence, which customer problems are worth solving.

Did you enjoy the newsletter? Please forward it. It only takes two clicks. Creating this one took two hours.

Thank you for Practicing Product,

Tim

PS: My inner dialogue whenever I discover a new coffee brewer:

How to Dive Deeper into Product Discovery

Learn 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.

Content I found Practical This Week

Product Discovery with Internal Customers

video preview

We did all this discovery... now how do we decide?

To help us to eliminate (not forever, but for the purpose of making a decision now) I've found one technique very helpful. The trick is to flip things around. Instead of describing the good that will happen by doing an idea, we look at what goes wrong when we don't do it. To make that flip, we can ask two simple questions:

Sample size and confidence: How to get your team to trust qualitative research

The only thing that matters is how confident your team is about the next decision they need to make. You might get that confidence from watching 2 people. You might need to watch 20. You might need to watch 20, then check your hypothesis at a larger scale with a survey or analytics. It all depends on the confidence of your team.

Who is Tim Herbig?

As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.

I focus on better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.

Product Practice Newsletter

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.

Read more from Product Practice Newsletter

Product Practice #363 How to IdentifyHigh-Leverage Impacts READ ON HERBIG.CO PUBLISHED May 16, 2025 READING TIME 5 min & 13 sec Dear Reader, An Impact is a metric that describes the achievement of a company- or department-level priority. It's a lagging indicator that changes as a result of multiple compounding efforts, but is not linkable to one individual feature or activity. Most Impacts fall into one of five categories: Growth Engagement Monetization Satisfaction Process Quality From Vague...

Product Practice #362 The Progress Wheel: My favorite Structure to Connect the Dots READ ON HERBIG.CO PUBLISHED May 9, 2025 READING TIME 4 min & 48 sec Dear Reader, Real Progress happens when you choose methods because they create value for you in your context, and you can use each domain to improve the others. To make Real Progress, teams need to understand and practice two core ideas: Putting the value of a practice before the selection of a method or framework is crucial to avoid getting...

Product Practice #361 Connecting North Star Metricsto Business Models READ ON HERBIG.CO PUBLISHED May 2, 2025 READING TIME 4 min & 45 sec Dear Reader, In many organizations, there's still a disconnect between product and business metrics. Product teams focus on customer-centric outcomes while business teams chase financial targets, with neither side fully trusting how one drives the other. When done right, a North Star Metric (NSM) can establish a middle ground that brings together both...