Glossary

Product discovery

Product discovery is the work of deciding what to build and why, by validating that a proposed solution is valuable, usable, feasible and viable before committing significant engineering effort to it.

Also known as Discovery

What is the difference between discovery and delivery?

Discovery decides what to build and whether it is worth building; delivery builds and ships it. Discovery reduces the risk of delivering the wrong thing, which is the most expensive kind of waste.

What questions does product discovery answer?

Do customers have this problem, and how badly? Will they use and value our solution? Can we build it? Does it work for the business? Marty Cagan frames these as value, usability, feasibility and viability risks.

How does customer evidence fit into discovery?

Discovery runs on evidence. The faster a team can pull relevant customer signal, from past tickets to fresh interviews, the faster it can validate or kill an idea before it reaches the backlog.

Put it into practice

Product discovery, in brief

Product discovery is the work of deciding what to build and why, validating that a solution is valuable, usable, feasible and viable before committing significant engineering effort.

Discovery decides what to build and whether it is worth building; delivery builds and ships it. Discovery exists to avoid the expensive waste of delivering the wrong thing.

Related terms

See what your customers keep telling you

Connect a source or upload a few files. Your first opportunities show up in minutes.