Don't Panic — Product Discovery

Product discovery is the work of deciding what to build before delivery turns a choice into a production product. It replaces a feature-shaped hunch with a trail of customer evidence, alternatives, and tests. Delivery is very good at building, shipping, and maintaining things. It is also wonderfully capable of doing all of that for the wrong thing, with excellent uptime.

A requested feature, a roadmap item, and a backlog entry are not proof of a customer problem. Start with a desired outcome, the change a team is trying to influence, then look at what people actually do. An opportunity is a customer need, pain point, or desire discovered in that evidence. It is not the label on the first feature request that enters the building wearing a confident hat.

The useful map is an opportunity solution tree. An outcome sits at the top, customer opportunities sit below it, several solutions sit below a chosen opportunity, and assumption tests sit below those solutions. This shape keeps the problem separate from the proposed answer. It also gives a team somewhere to put a promising idea without marrying it on the first afternoon.

The surprising part is that no test stamps a solution "validated." A prototype can show whether someone can use an interaction. A story-based interview can reveal a past behavior. Existing data can show a pattern, and a research spike can test technical feasibility. Each result answers one bounded question; usability is not demand, and feasibility is not customer value. That division is annoying only until it prevents a very expensive misunderstanding.

Discovery is not an endless research expedition. The strength of evidence should match the cost and reversibility of the commitment. A cheap, reversible change can move with a smaller safe test. An expensive, hard-to-reverse decision needs stronger evidence, or a constrained release that makes failure observable and recoverable. When the remaining uncertainty is acceptable, delivery takes over and production behavior becomes part of the next loop.

Read the Introduction when you need the full system and its boundaries. Use the Slides for the relationships between outcomes, opportunities, solutions, assumptions, and tests. Keep the Cheatsheet nearby when choosing a method or checking what a result does not establish. The Practice Reference and exercise turn the map into a decision record. The point is not to collect research artifacts. It is to make the next product choice less mysterious and more accountable.

Don't Panic — Product Discovery

Relevant careers