Product Discovery
The process of determining what to build by deeply understanding customer needs, validating problem-solution fit, and reducing risk before committing to full development.
Also known as: Dual-Track Discovery, Product Discovery Process
Category: Methods
Tags: product-management, product-discovery, customer-needs, risk-management, methodologies, validation
Explanation
Product Discovery is the set of activities product teams undertake to decide what to build. It answers the fundamental questions: Are we solving a real problem? Will customers use this solution? Can we build it? Does it work for our business?
The term gained prominence through the work of Marty Cagan and the Silicon Valley Product Group, distinguishing between discovery (deciding what to build) and delivery (building it). Most failed products don't fail because they were built poorly — they fail because they solved the wrong problem or solved the right problem in the wrong way.
**The four risks of product discovery:**
1. **Value risk**: Will customers buy or use it?
2. **Usability risk**: Can customers figure out how to use it?
3. **Feasibility risk**: Can we build it with the time, skills, and technology available?
4. **Business viability risk**: Does it work for our business model, brand, and stakeholders?
**Key activities:**
- Customer interviews and observation
- Problem space exploration and opportunity mapping
- Prototyping (from low-fidelity sketches to interactive prototypes)
- Assumption testing and experimentation
- Usability testing
- Data analysis and quantitative research
- Stakeholder alignment
**Discovery vs. delivery:**
In modern product organizations, discovery and delivery happen in parallel, not sequentially. While engineers are building the solutions validated in previous discovery cycles, the product trio is simultaneously discovering what to build next. This dual-track approach prevents the bottleneck of waiting for a complete specification before starting development.
**Common mistakes:**
- Treating discovery as optional or a luxury
- Equating customer requests with customer needs
- Skipping discovery for "obvious" features
- Over-indexing on quantitative data while ignoring qualitative insight
- Confusing output (features shipped) with outcome (customer value created)
Effective product discovery doesn't slow teams down — it prevents them from wasting months building the wrong thing.
Related Concepts
← Back to all concepts