A Product Discovery Deck · 2026
A 90-day discipline for early-stage product teams.
Chapter 01
Chapter 01 · The problem
Every team collects customer signals — interviews, tickets, churn calls. Most treat them as confirmation, not as falsifiable input.
Median across 200 teams
63%
of "discovery interviews" end without a written, falsifiable hypothesis.
Chapter 02
Chapter 02 · The Validation Loop
A signal is observation; a hypothesis is a prediction with a fail condition.
Chapter 02 · The Validation Loop
| If you're testing… | Use | Why |
|---|---|---|
| Whether the problem is real and frequent | Discovery interview | Surfaces unprompted language and workarounds |
| Willingness to pay or commit | Pre-sale / LOI | Behavior is the only honest signal; opinions inflate |
| Whether a specific solution is usable | Prototype test | Concrete artifact; reveals where assumptions break |
A discovery cycle that produces no killed hypotheses isn't validating — it's rationalizing the roadmap you already have.
— Notebook, week 4
End · Thank you
That's the whole practice.