Why There’s No Single “Right” Way to Do Discovery: Part 3

This final session of a three-part webinar series argues there is no single correct way to run product discovery, and that teams should instead be judged by underlying principles that fit their context. It covers two principles: setting up compare-and-contrast decisions rather than binary whether-or-not choices, and surfacing and testing assumptions. The speakers explain how comparing opportunities and solutions against explicit criteria leads to clearer decisions, and how breaking an idea into testable assumptions allows faster, cheaper learning than building and testing whole features. The practical value is in shifting teams away from debating or building one idea at a time toward structured, evidence-based decision-making.

01Key takeaways

• Frame discovery decisions as comparisons between opportunities or solutions using explicit criteria tied to the desired outcome.
• Most discovery choices are two-way doors, so make fast decisions and verify them with experiments instead of extended debate.
• Break ideas into their underlying assumptions across desirability, usability, viability, feasibility, and ethics, then test the riskiest ones first.
• Design experiments that require real behavior, not stated intent, by simulating only the experience needed to test one assumption.
• Turn vague assumptions into falsifiable hypotheses with pass-fail thresholds, and agree on them with stakeholders before running tests.
• When stakeholders bring strong solutions, map how the idea would work and revisit the outcome and target opportunity together.

02Key sections

Recap of Principles 1-5

The speakers briefly review earlier principles including collaborative trio decision-making, externalizing thinking, outcome focus, discovering opportunities, and prioritizing in the opportunity space.

Compare and Contrast Decisions

Teams tend to fixate on one favorite solution, making whether-or-not choices. Comparing multiple opportunities and solutions against explicit criteria, tied to the desired outcome, produces more decisive and productive choices.

Two-Way-Door Decisions and Opportunity Trees

Most discovery decisions are reversible, so teams should decide quickly and verify through experiments rather than over-deliberate. Interview snapshots and opportunity trees should be maintained at a sensible level of effort, and teams are free to use other externalization tools.

Surfacing and Testing Assumptions

Teams should pull hidden beliefs into the open and sort them into desirability, usability, viability, feasibility, and ethical categories. Testing small, critical assumptions is faster than testing whole ideas and enables many experiments per week.

Simulating Experiences and Hypotheses

Good experiments simulate only the experience needed to test one assumption and measure real action rather than stated intent. Assumptions become useful hypotheses when made specific and falsifiable, starting small and scaling rigor as needed.

03From the post

“A few months ago, fellow Product Talk coach Hope Gurion and I sat down to discuss why there’s no single right way to do discovery. Want to read the previous parts of the series? Find Part 1 here and Part 2 here. In this third and final conversation in”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.