# Product Discovery

The work of reducing uncertainty about which customer problems and product solutions are valuable, usable, feasible, and viable before scaling.

- Type: practice
- Domain: Strategy & discovery
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-discovery/>)

## What it means

Product discovery is a collaborative learning process used to decide what to build and why. A cross-functional team studies customers and context, frames opportunities, explores alternatives, and tests critical risks before committing substantial delivery effort, while continuing to learn after release.

## Why it matters

Delivery efficiency is wasteful when a team is confidently building the wrong thing. Discovery improves the quality of product decisions by testing value, usability, feasibility, and business viability early and by keeping evidence close to the people who will design and build the product.

## When to use it

Use discovery for new products, major capabilities, uncertain customer problems, risky business changes, and meaningful redesigns. Scale the effort to the uncertainty and cost of being wrong; small reversible changes should not inherit a heavyweight ceremony.

## How it works

1. Clarify the decision, desired outcome, constraints, and important unknowns.
2. Gather evidence from customers, behavior, markets, operations, and technical systems.
3. Frame and prioritize opportunities rather than beginning with a feature list.
4. Explore multiple solutions with product, design, and engineering perspectives.
5. Test the riskiest assumptions using the smallest credible evidence.
6. Decide whether to proceed, change direction, gather more evidence, or stop.

## A practical example

A logistics platform considers automated delivery estimates. The trio interviews dispatchers, reviews late-shipment data, prototypes confidence ranges, and runs a technical spike on data quality. It learns that exception explanations create more trust than a single precise time and adjusts the concept before delivery.

## Where it breaks

Discovery cannot remove uncertainty, prove future demand, or replace judgment. Poor samples and leading tests create false confidence, while endless research can delay decisions. Discovery also fails when teams lack authority to act on evidence or exclude delivery and operational realities.

## Common mistakes

- Running discovery as a design phase handed off to engineering.
- Seeking validation of a chosen solution rather than comparing options.
- Using research volume as a substitute for a decision and learning threshold.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/product-discovery/#visualization-product-discovery>)

## Sources

1. [Product Discovery](<https://www.svpg.com/product-discovery/>) — Silicon Valley Product Group · Practitioner article
2. [The Origin of Product Discovery](<https://www.svpg.com/the-origin-of-product-discovery/>) — Silicon Valley Product Group · Practitioner history

## Related topics

- [Continuous Discovery](<https://wiki.soroush.uk/topic/continuous-discovery/>)
- [Opportunity Solution Tree](<https://wiki.soroush.uk/topic/opportunity-solution-tree/>)
- [Problem Framing](<https://wiki.soroush.uk/topic/problem-framing/>)
