Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value
About This Book
Continuous Discovery Habits by Teresa Torres lays out a practical framework for product teams to consistently make better decisions by maintaining regular contact with customers. The central definition anchors the entire book: continuous discovery is "at a minimum, weekly touchpoints with customers, by the team building the product, where they conduct small research activities, in pursuit of a desired outcome."
Torres argues for a fundamental shift from an output mindset (shipping features) to an outcome mindset (measuring the impact those features have on customers and the business). She distinguishes business outcomes, product outcomes, and traction metrics, and stresses that teams perform best with one outcome at a time.
The book introduces the opportunity solution tree as its signature artifact—a visual map connecting a desired outcome (root) to the opportunity space (customer needs, pain points, desires), then to solutions, then to assumption tests. Torres reframes "problems to solve" as "opportunities" to include desires, not just pain points.
Key habits are woven throughout:
- Interview customers every week, using story-based questions rather than direct questions, since people poorly recall their actual behavior.
- Capture each conversation on an interview snapshot and draw the stories you hear.
- Map and structure the opportunity space into distinct, non-overlapping branches.
- Shift from "whether or not" decisions to a compare-and-contrast mindset, generating many ideas because first ideas are rarely best.
- Identify hidden assumptions, prioritize "leap of faith" assumptions, and test assumptions—not whole ideas—quickly.
The work is framed by six mindsets: outcome-oriented, customer-centric, collaborative, visual, experimental, and continuous. Torres emphasizes that discovery decisions are mostly reversible, so teams should move fast, test, and course-correct. Throughout, she champions the cross-functional product trio (product manager, designer, engineer) making decisions together.
Key Takeaways
- 1.Adopt an outcome mindset—define success by the impact code creates for customers and the business, not by features shipped.
- 2.Reframe customer needs, pain points, and desires as opportunities, and structure them on an opportunity solution tree.
- 3.Make weekly customer interviews a keystone habit; the opportunity space is never finite and continuous contact lets you pivot without starting over.
- 4.Use story-based questions because people cannot reliably report their own behavior through direct questions.
- 5.Replace "whether or not" decisions with a compare-and-contrast mindset—always ask what else you could build.
- 6.Test assumptions, not whole ideas, prioritizing the riskiest "leap of faith" assumptions to learn fast and avoid confirmation bias.
- 7.Treat most discovery decisions as reversible—decide quickly with what you know today, then course-correct as evidence arrives.
Top Highlights
In this book, I’ll refer to customer needs, pain points, and desires collectively as “opportunities”—they represent opportunities to intervene in our customers’ lives in a positive way. Why don’t we call them “problems to solve”? In the product world, we don’t just solve customer problems. The word “problem” implies something needs fixing. However, we have many examples of products or services that don’t fix problems. Disneyland entertains me. Ice cream is delicious. Mountain biking is fun. These products address my desires. I could try to shoehorn these desires into needs—I need something to fill my time, I need nutrients, and I need exercise. However, writing a book, eating spinach, and going to the gym might be more effective ways of addressing those needs. The key difference here is that I enjoy Disneyland, ice cream, and mountain biking. These products were designed to address my desires, not solve my problems. So, to make sure this model is more inclusive of such products, I’ll use opportunities to represent customer needs, pain points, and desires collectively and the opportunity space to represent the problem space as well as the desire space.
Highlighted by 4 people
An outcome communicates uncertainty. It says, We know we need this problem solved, but we don’t know the best way to solve it. It gives the product trio the latitude they need to explore and pivot when needed. If the product trio finds flaws with their initial solution, they can quickly shift to a new idea, often trying several before they ultimately find what will drive the desired outcome.
Highlighted by 4 people
A business outcome measures how well the business is progressing. A product outcome measures how well the product is moving the business forward. A traction metric measures usage of a specific feature or workflow in the product.
Highlighted by 4 people
The implication for product trios is that two of the most important steps for reaching our desired outcome are first, how we map out and structure the opportunity space, and second, how we select which opportunities to pursue. Unfortunately, many product trios skip these steps altogether. They start with an outcome and simply start generating ideas. We do have to get to solutions—shipping code is how we ship value to our customers and create value for our business. But the right problem framing will help to ensure that we explore and ultimately ship better solutions.
Highlighted by 4 people
even bigger
Highlighted by 4 people · 4 left notes
Opportunity solution trees have a number of benefits. They help product trios: Resolve the tension between business needs and customer needs Build and maintain a shared understanding of how they might reach their desired outcome Adopt a continuous mindset Unlock better decision-making Unlock faster learning cycles Build confidence in knowing what to do next Unlock simpler stakeholder management
Highlighted by 3 people
Instead of framing our decisions as “whether or not” decisions, this book will teach you to develop a “compare and contrast” mindset. Instead of asking, “Should we solve this customer need?” we’ll ask, “Which of these customer needs is most important for us to address right now?” We’ll compare and contrast our options. Instead of falling in love with our first idea, we’ll ask, “What else could we build?” or “How else might we address this opportunity?” Visualizing your options on an opportunity solution tree will help you catch when you are asking a “whether or not” question and will encourage you, instead, to shift to a compare-and-contrast question.
Highlighted by 3 people
This research suggests that product trios, when faced with a new outcome, should first start with a learning goal (e.g., discover the opportunities that will drive engagement) before being tasked with a performance goal (e.g., increase engagement by 10%). This approach can be particularly helpful because it’s common to have uncertainty around the best way to measure your outcome. We often need to do some discovery to learn how to best measure a product outcome. For example, when Sonja’s team started investigating retention as an outcome, they had no idea what they would uncover. Rather than spinning their wheels trying to define the perfect, specific, measurable retention metric, her team focused on learning what led to churn and used that knowledge to revise their metric over time.
Highlighted by 3 people
Most teams will have more of an impact by focusing on one outcome at a time.
Highlighted by 3 people
The key is to have a conversation as a team about the scope that gives you room to explore while staying focused on your outcome. Once you’ve defined the scope of your experience map, you are ready to take an inventory of your individual knowledge before working to develop a shared understanding of what you collectively know.
Highlighted by 3 people
AI Review
Based on Glasp's analysis of highlights from 10 readers, this is a highly resonant, practical playbook whose core concepts—the opportunity solution tree, weekly interviewing, and outcome thinking—were repeatedly highlighted, signaling strong consensus on its real-world usefulness.
Pros
- +Clear, actionable framework centered on the opportunity solution tree
- +Strong emphasis on weekly customer interviewing as a sustainable habit
- +Reframes decisions from "whether or not" to compare-and-contrast
- +Grounds advice in research on cognitive bias and creativity
- +Practical tools like interview snapshots, story mapping, and assumption mapping
- +Concrete tips for negotiating outcomes and managing stakeholders
Cons
- −Author acknowledges the supporting research is limited and sometimes conflicting
- −Assumes access to customers and organizational latitude that not all teams have
- −Volume of habits and artifacts can feel demanding to adopt all at once
Glasp AI analysis based on highlights from 10 readers.
Who Should Read This
This book is essential for product managers, designers, and engineers working on digital products—especially those forming a cross-functional product trio. It suits teams stuck in feature-factory or output-driven cultures who want to adopt outcome thinking. Product leaders and stakeholders seeking to coach teams toward modern discovery will also benefit. Some familiarity with Agile, Scrum, or basic product development helps, but Torres explains concepts from the ground up, making it accessible to those new to continuous discovery practices.
Frequently Asked Questions
What is Continuous Discovery Habits about?
Who is the book for?
What are the key lessons?
What is an opportunity solution tree?
Why does the book recommend story-based interview questions?
Is it worth reading?
Why test assumptions instead of whole ideas?
How to Apply What You Read
- 1.Schedule at least one customer interview every week and capture each on an interview snapshot.
- 2.Build an opportunity solution tree for your current outcome, structuring opportunities into distinct, non-overlapping branches.
- 3.Generate 15–20 solution ideas individually first, then dot-vote as a team down to three to compare and contrast.
- 4.Map the hidden assumptions behind your top ideas and test the riskiest ones with quick prototype tests or one-question surveys.
- 5.Show your work to stakeholders by walking them through your tree from outcome to opportunities to solutions, rather than presenting only conclusions.
Discussion Questions
- Q1.Is your team currently driven by outputs or outcomes, and what would it take to shift toward measuring impact?
- Q2.How well do you actually know your customers' real behavior versus what they say they do in interviews?
- Q3.What "whether or not" decisions has your team made recently, and how might a compare-and-contrast framing have changed them?
- Q4.Which of the six mindsets—outcome-oriented, customer-centric, collaborative, visual, experimental, continuous—is weakest on your team, and why?
- Q5.What assumptions are you currently treating as facts in your most important product idea?
- Q6.How does your organization's structure and stakeholder culture help or hinder continuous discovery?
- Q7.Where in your process do you fall in love with a single idea, and how could testing sets of ideas guard against that?
Recommended Books
Revisit Your Highlights, Deepen Your Understanding
Import your Kindle highlights to review, organize, and share the ideas that matter most to you.
Get the free browser extension