By Teresa Torres · producttalk.org · @ttorres on X · LinkedIn
Teresa Torres argues that product discovery, the work of deciding what to build, should be a continuous activity rather than a project-based phase at the start of a initiative. She contrasts it with delivery, the work of building and shipping. Because digital products are never finished, teams must stay connected to customers, since builders develop a curse of knowledge that blinds them to how customers experience the product. She proposes a simple structure: start with a measurable outcome, discover opportunities from customer stories, then discover solutions through rapid assumption testing. Discovery is best led by a product trio of product manager, designer, and engineer.
01Key takeaways
- Treat product discovery as a continuous decision-making process, not a one-time research phase at project start.
- Anchor discovery in a clear product outcome that is a leading indicator of a business outcome.
- Interview customers weekly and listen for needs and pain points within specific stories rather than stated wants.
- Test assumptions rapidly across desirability, viability, feasibility, usability, and ethics before building full solutions.
- Have the product manager, designer, and engineer interview customers and run assumption tests together.
02Key sections
- Defining discovery versus delivery
- Discovery is the decision-making work about what to build, while delivery is building, shipping, and maintaining the product. Good discovery keeps customers involved throughout.
- The limits of project-based discovery
- Traditional project thinking frames work as solutions, sets success as shipping, and limits customer research to a single upfront phase. This leaves teams unsure whether the solution solved a real problem.
- Why discovery must be continuous
- Digital products are never done, and competitors catch up if teams stop iterating. Teams suffer from the curse of knowledge, so frequent customer contact closes the gap between internal and customer views.
- The underlying structure: outcomes, opportunities, solutions
- Business outcomes are translated into product outcomes, which are then used to map customer opportunities and generate solutions. Opportunity solution trees help keep this structure visible.
- How discovery is practiced and who does it
- Teams interview customers weekly to uncover opportunities from specific stories and run rapid assumption tests to evaluate solutions. A product trio leads this work together.
03From the post
“Product discovery is becoming a trendy topic in the world of digital products. Why? What is it? And what do you need to know about it? I’ve got you covered. This article will cover the ins and outs of product discovery. What is Product Discovery? We typically define product”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.