Product Discovery
Overview
Discovery is about learning fast and cheaply. The goal is to find evidence that a problem is worth solving and that a solution is desirable, feasible, and viable — before committing major resources.
When to Use
- Early-stage ideas and opportunities
- Major feature or product bets
- When assumptions about users or value are untested
- Before committing to a full build
Core Activities
- Problem framing and opportunity assessment
- Customer interviews and observational research
- Assumption mapping and riskiest-assumption tests
- Solution sketching and concept testing
- Prototype and experiment design
- Go / no-go or pivot recommendations
Principles
- Fall in love with the problem, not the solution
- Test the riskiest assumptions first
- Prefer evidence over opinions
- Time-box discovery; avoid endless research
- Document what you learned and what remains uncertain
Verification
- Key assumptions are listed and tested or explicitly accepted
- Evidence is tied to a clear recommendation
- Discovery outcomes influence the roadmap or decision