Is Continuous Discovery Habits worth reading?

Yes, especially for product managers and product leaders who feel that their teams are shipping features without adequate customer validation. The weekly interview habit is actionable immediately, and the Opportunity Solution Tree is one of the clearest tools for structuring discovery work.

What is the Opportunity Solution Tree?

A visual framework that organizes the relationship between a desired business outcome (the top), the customer opportunities that could achieve it (the middle), and the potential solutions for each opportunity (the bottom). It prevents premature fixation on a single solution and keeps the team's work connected to specific customer problems.

How do you start a weekly interview habit if you've never done customer interviews regularly?

Torres recommends starting with a minimal recurring calendar block and a simple outreach script. The first obstacle is recruitment, not the interview itself. She suggests building a recruitment pool from existing customers and users who have expressed interest in giving feedback.

Does Continuous Discovery Habits apply to B2B products with enterprise buyers?

Yes, with adaptation. B2B products often have a distinction between buyers and users, and both need to be understood. The weekly interview habit may need to focus on different roles at different points in the product lifecycle. Torres addresses this in the book.

What is the relationship between Continuous Discovery Habits and Inspired?

Inspired provides the framework for how strong product teams work. Continuous Discovery Habits provides the specific methodology for one of Inspired's most important practices: ongoing customer discovery. They are highly complementary — CDH is the implementation guide for the discovery practices Inspired describes.

Continuous Discovery Habits by Teresa Torres: Summary & Discussion Questions

Summary

Continuous Discovery Habits is Teresa Torres's practical guide to making product discovery a sustainable, weekly team practice rather than a periodic research event. Torres has coached product teams at companies including Spotify, IBM, and Twilio, and the book synthesizes what she has observed separates teams that consistently build the right things from those that execute efficiently on the wrong things.

The core argument is that product discovery — the work of determining whether a potential solution will create value for customers and the business — needs to happen continuously alongside delivery, not in separate phases. The habit Torres recommends is simple in structure: interview at least one customer per week, as a team. Not a monthly focus group, not an annual user research project — a weekly, ongoing, lightweight touch with real customers. The frequency is the point: it creates a cadence that keeps the team's understanding of customers current rather than stale.

The main analytical tool Torres introduces is the Opportunity Solution Tree — a visual framework that organizes the relationship between a desired business outcome, the customer opportunities that could achieve it, and the solutions being considered for each opportunity. The tree keeps the team focused on outcomes rather than features, makes explicit the assumptions behind each solution, and prevents the common problem of fixating on a single solution without considering the range of opportunities that could address the desired outcome.

Torres also addresses assumption testing and experiment design. She distinguishes between product risks — will customers want this, can we build it, should we build it, and can we grow the business with it — and provides a framework for designing experiments that test the most critical assumptions first with the least investment. The book's practical orientation extends to story mapping, assumption mapping, and a specific cadence for how discovery and delivery work should fit together in a typical sprint cycle.

Key takeaways

1.
Continuous discovery requires a weekly interview habit: at least one customer interview per week, conducted as a team, to keep customer understanding current rather than relying on periodic research.
2.
The Opportunity Solution Tree organizes the relationship between a desired outcome, customer opportunities, and potential solutions, preventing fixation on a single solution before adequately exploring the problem space.
3.
Opportunities are customer needs, pain points, or desires — not solutions. Separating opportunity identification from solution design produces more options and better solutions.
4.
Assumption testing before building: identify the most critical assumptions behind a potential solution, design the cheapest test that could falsify each one, then build only what passes.
5.
The four types of product risk: desirability (will customers want it?), viability (can the business support it?), feasibility (can we build it?), and usability (can customers use it?). Discovery should address all four.
6.
Story mapping helps teams understand the end-to-end customer journey and identify the experiments that will create the most learning before committing to a full build.
7.
Weekly customer interviews require a simple, sustainable recruitment process. The biggest obstacle is not finding customers to talk to — it is building the habit of doing it consistently.
8.
Product discovery is team sport: engineers and designers who participate in discovery make better decisions than those who receive discovery outputs as requirements.

Discussion questions

Use these on your own, with a book club, or as chat starters in Superbook.

1.
Torres recommends weekly customer interviews as the foundation of continuous discovery. What are the practical obstacles to making that a weekly habit, and how would you address them?
2.
What is the difference between a customer opportunity and a customer request? Why does Torres insist on that distinction, and when is it hardest to maintain?
3.
The Opportunity Solution Tree is a visualization tool. What does the tree make visible that isn't visible in a standard product roadmap, and what does that change about how you work?
4.
Torres says discovery is a team sport and that engineers who participate in discovery make better decisions. What makes this hard to implement, and what would you expect to change if you made it work?
5.
How do you prioritize which opportunities to pursue from the opportunity solution tree? What signals indicate that an opportunity is worth investing discovery effort in?
6.
Assumption testing before building: what makes a good test? What makes a test so minimal that it doesn't actually tell you anything, and how do you calibrate the right level of experiment?
7.
What is the relationship between continuous discovery and sprint planning? How do you structure a team's week to accommodate both discovery and delivery without one dominating the other?
8.
Torres is explicit that discovery takes time and that teams often resist it in favor of shipping. How do you build organizational patience for discovery when the pressure to deliver is constant?
9.
How does the continuous discovery framework apply to teams building infrastructure or platform products rather than user-facing products?
10.
What is the difference between discovery that is genuinely continuous and discovery that is periodic but labeled as continuous? What observable behaviors distinguish the two?
11.
Torres's book is aimed at product teams in technology companies. How much of the framework transfers to product teams in non-technology businesses?

Themes

Product management Customer discovery Innovation Research Technology

Frequently asked questions

Is Continuous Discovery Habits worth reading?

Yes, especially for product managers and product leaders who feel that their teams are shipping features without adequate customer validation. The weekly interview habit is actionable immediately, and the Opportunity Solution Tree is one of the clearest tools for structuring discovery work.
What is the Opportunity Solution Tree?

A visual framework that organizes the relationship between a desired business outcome (the top), the customer opportunities that could achieve it (the middle), and the potential solutions for each opportunity (the bottom). It prevents premature fixation on a single solution and keeps the team's work connected to specific customer problems.
How do you start a weekly interview habit if you've never done customer interviews regularly?

Torres recommends starting with a minimal recurring calendar block and a simple outreach script. The first obstacle is recruitment, not the interview itself. She suggests building a recruitment pool from existing customers and users who have expressed interest in giving feedback.
Does Continuous Discovery Habits apply to B2B products with enterprise buyers?

Yes, with adaptation. B2B products often have a distinction between buyers and users, and both need to be understood. The weekly interview habit may need to focus on different roles at different points in the product lifecycle. Torres addresses this in the book.
What is the relationship between Continuous Discovery Habits and Inspired?

Inspired provides the framework for how strong product teams work. Continuous Discovery Habits provides the specific methodology for one of Inspired's most important practices: ongoing customer discovery. They are highly complementary — CDH is the implementation guide for the discovery practices Inspired describes.

About Teresa Torres

Teresa Torres is a product discovery coach who works with product teams at companies including Spotify, IBM, Twilio, and numerous startups. She started her career as a software engineer and has spent more than fifteen years working at the intersection of product management, design, and customer research. She writes at producttalk.org, where her weekly interview habit post became one of the most widely shared pieces in the product management community. Continuous Discovery Habits, published in 2021, is her first book and is based on the framework she has developed and refined coaching hundreds of teams.

More books by Teresa Torres