What is Product Discovery?
Product discovery is the process of determining what to build before engineering starts building it.
Product discovery is the process of determining what to build before engineering starts building it. It answers: Is this a real problem? Does our solution address it? Can we build it? Will they pay for it?
Popularized by Marty Cagan and Teresa Torres, product discovery uses rapid experimentation to validate product ideas before committing engineering resources.
Discovery techniques include: customer interviews, prototype testing, painted door tests (fake feature buttons that measure interest), Wizard of Oz tests, data analysis, and competitive research.
The Continuous Discovery framework (Teresa Torres) recommends weekly touchpoints with customers, opportunity solution trees for mapping hypotheses, and regular assumption testing to de-risk product decisions.
Why It Matters
Product discovery prevents the most costly product error: building features nobody wants. Engineering time is the most expensive resource in most companies — discovery ensures it's invested in validated opportunities.
Frequently Asked Questions
What is product discovery?
Product discovery is the process of validating what to build before engineering starts. It uses customer research, experimentation, and data analysis to de-risk product decisions.
How much time should teams spend on discovery?
Teresa Torres recommends at least 20% of product time on discovery. The best teams maintain continuous discovery habits — weekly customer interviews and regular assumption tests.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →