Summary
Teresa Torres lays out a structured, repeatable system for product discovery — the process of deciding what to build. The central argument is that discovery should not be an occasional activity but a continuous habit, with product teams talking to customers every week and using a structured framework (the opportunity solution tree) to connect business outcomes to customer needs to solutions.
Key Ideas
- The opportunity solution tree. This is the book’s core framework: start with a desired business outcome, map the customer opportunities (needs, pain points, desires) that could drive that outcome, then generate and test solutions for each opportunity. It creates visual clarity on why you are building what you are building.
- Weekly customer interviews, no exceptions. Torres argues that the single most important habit a product team can develop is talking to customers every week — not once a quarter, not during a “research phase,” but continuously as a rhythm embedded in the team’s operating cadence.
- Interview for story, not opinion. The most common mistake in customer research is asking people what they want. Instead, ask them to walk through specific recent experiences. Extract opportunities from stories, not from stated preferences — people are bad at predicting their own behavior.
- Assumption mapping and testing. Every solution carries assumptions. The discipline is to identify the riskiest assumptions (desirability, feasibility, usability, viability), then design the smallest possible test to validate or invalidate each one before committing to building.
- Compare solutions, don’t fall in love with one. Cognitive bias leads teams to commit to the first idea that sounds good. The discipline of generating at least three solutions for any given opportunity and comparing them forces better decision-making.
Standout Quotes
“The best product teams don’t just build what customers ask for. They discover what customers need.”
“If you aren’t talking to customers every week, you aren’t doing continuous discovery — you’re guessing.”
“The goal of an interview is not to validate your idea. It’s to understand your customer’s world.”
Takeaways
- Implement a weekly customer interview cadence as a non-negotiable team habit — even 20-minute conversations compound into deep customer understanding.
- Use the opportunity solution tree to keep teams aligned on why they are building specific features, and to prevent the roadmap from becoming a disconnected feature list.
- Before building anything, explicitly name the riskiest assumption and design a test for it. If you can’t articulate the assumption, you don’t understand the solution well enough.
part of books