When are you done with Product Discovery?


When are you done
with Product Discovery?

READ ON

HERBIG.CO

PUBLISHED

Aug 22, 2025

READING TIME

3 min & 45 sec

​Dear Reader,​

One of the standard questions I get in discovery coaching and workshops is, "How do I know I have done enough discovery?" I typically smile, because I can get on one of my favorite soapboxes:
Think of the end of discovery as the exit of a highway you feel confident enough in taking, based on your surroundings and your current understanding of how close you are to your destination, without having a GPS.

Ravi Mehta calls this state informed conviction. But, "unfortunately," there's no formula for reaching it. No amount of scoring or sticking to a fixed number of user interviews before making a decision will unlock this state. Your path to informed conviction is subjective and contextual, varying depending on the product life cycle and other factors. As Teresa Torres reminds product teams around the world through her continuous discovery approach, you're never one insight away from success.

As you gather evidence and move toward informed conviction, you'll reach points where the path forward becomes clear. At these moments, three types of decisions typically emerge:

Keep Moving. When evidence suggests you're on the right track but haven't reached informed conviction yet, keep following your current direction while gathering more evidence along the way. Maybe your problem validation shows promise but needs more specific user segments, or your solution tests indicate potential but need stronger evidence of commitment.

Drop and Pivot. When evidence clearly shows that a problem isn't worth solving or a solution isn't worth building, this isn't failure – it's Discovery working as intended.

Each "no" helps you focus resources on more promising paths. Ant Murphy encourages this as a litmus test for Product Discovery: “How many ideas have you discarded and decided NOT to do?“

Commit to Building. When evidence from both problem and solution spaces align, you've validated a worthy problem and found a solution with strong evidence of desirability, feasibility, and viability. This doesn't mean perfect certainty - it means enough confidence to move forward. And while there’s a rightful amount of criticism about feature factories and an exaggerated focus on Product Delivery, remember this: The most perfectly researched problem and holistically tested idea neither help your users nor your business if they are never executed in high quality and sufficient time.

These aren't one-time, permanent decisions. As you learn more through building and shipping, new evidence might lead to new paths worth exploring. That's the essence of Adaptable Discovery: using evidence to continuously reduce uncertainty about which problems are worth solving and which solutions are worth building.

1 Question For You To Put This Into Practice

If you HAD to choose your Discovery priorities right now, would you decide to Keep Moving, Drop and Pivot, or Commit to Building? Why would you make this choice?

Reply and let me know your answer.

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

Join my In-Person Workshops in Berlin

I'm excited to bring my beloved in-person workshops back to Berlin in January 2026. You can choose between 1-day workshops on Product Strategy, Product OKRs, or Product Discovery, or opt for the full 3-day experience for you or your team.

(reach out for custom team quotes)

Content I found Practical This Week

Build Products That Solve Real Problems With This Lightweight JTBD Framework

A good, crisp JTBD statement captures underlying motivations, triggers and context for the problems your user faces. This statement can be foundational for your entire product and GTM planning, from focusing your PRD or product spec, to identifying your channels and marketing messages. A good statement will help remove bias, build empathy for users and bring alignment across product, marketing and eng teams. When you have a well-crafted (and well-communicated) jobs to be done statement, the many things will start to fall into place.

What to Listen for in a Solution Test Interview

Don't believe users when they say "That's interesting" or “I like that." The user is probably just filling time and trying to give you some response about what they’re seeing. In fact, the user might as well be saying “Meh”. This happens because most users want to be nice to their interviewers (most are getting paid after all). And as interviewers, we don’t push back or dig deeper because we don’t know any better. I’ve seen over 600 user interviews so I can tell the difference between “like” and “love”. Instead, use a couple “Why” questions to learn more. And be ready to accept that users just may not value your solution.

Product Discovery at Netflix

In 2005, during my first week as VP of Product at Netflix, I heard the phrase that product leaders fear most: “CEO Pet Project.” Reed Hastings, Netflix’s CEO, wanted previews on the Netflix site for 80% of the movies and TV shows that members watched. At the time, we were still a DVD by mail service, and Internet video was limited to postage-stamp-sized video. While we had 100,000 DVDs on our site, we had no previews. Previews were also hard to execute. Each week, we received cardboard boxes filled with thousands of previews in various formats. Some previews were on beta tapes, others on VHS, while a handful of studios expected us to “rip” previews from DVDs. Worse, the digital rights for previews were murky. Most previews played songs in the background, and the studios didn’t have the right to play the songs online.

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. Explore my new book on realprogressbook.com

Read more from Product Practice Newsletter

Product Practice #414 Content Highlights of 2026 (so far) PUBLISHED Jun 25, 2026 READ ON HERBIG.CO 🚨 NEW LIVE WORKSHOPS ANNOUNCED (Virtual) August 26: From Staring at KPIs to Prioritizing with OKRs, in 6 Hours Sep 1 - 24: How to Build and Execute a Winning Product Strategy Dear Reader, With the year nearing its halfway point, I wanted to reflect on the ideas that resonated the most with my readers and followers. Which led me to bring you concise summaries of my most popular content of the...

Product Practice #413 Case Study: How to Develop Your Product Vision Collaboratively (Part 3) PUBLISHED Jun 18, 2026 READ ON HERBIG.CO Sign up for free Dear Reader, Go here to check out part 1 of this series, and find part 2 right here. There is rarely a perfect moment to work on your product vision. But there are some clear triggers for initiating that work. The clearest ones are structural: A team reorganization, a strategic pivot, an acquisition, or new ownership of a product area. Any of...

Product Practice #412 Case Study: How to Develop Your Product Vision Collaboratively (Part 2) PUBLISHED Jun 11, 2026 READ ON HERBIG.CO Dear Reader, You can find part 1 of this series from last week here. Where to Collaborate Broadly Inspiring everyone does not mean your vision needs to be decided by committee, and everyone needs to be pleased. For Victoria, walking this line meant inviting contributions from the full team during an in-person team retreat, but creating a smaller core group...