A Comprehensive Guide to Teresa Torres' Framework for Building Products Customers Love
Continuous discovery is defined as "at a minimum weekly touchpoints with customers by the team building the product where they conduct small research activities in pursuit of a desired product outcome."
Teresa Torres teaches a structured and sustainable approach to continuous discovery that helps product teams infuse their daily product decisions with customer input. Continuous discovery is the process of conducting small research activities through weekly touchpoints with customers, by the team who's building the product.
Unlike traditional product discovery that happens at the beginning of a project and then stops, continuous discovery recognizes that digital products are never truly finished. Customer needs evolve, markets shift, and new competitors emerge. To stay relevant, product teams must maintain an ongoing connection to their customers throughout the entire product lifecycle.
Product people suffer from the "curse of knowledge" - as we develop expert knowledge about our product, we forget what it was like before we had that knowledge and can't imagine what it's like for our customers.
By continuously engaging with customers and discovering their needs, we are more likely to build features that drive value to users than just relying on the validation mindset.
The opportunity space is always evolving as new competitors enter markets, new technology disrupts what's possible, and even our own code releases cause shifts. Good product discovery teams interview week over week to keep tabs on these constant changes.
A product trio—typically comprised of a product manager, a designer, and a software engineer—leads product discovery. This cross-functional team works together from the very beginning, making collaborative decisions about what to build based on direct customer input.
Defines outcomes, manages stakeholders, and ensures alignment between business goals and customer needs. Orchestrates the discovery process and makes prioritization decisions.
Translates customer insights into tangible solutions through prototypes, wireframes, and visual designs. Leads usability testing and ensures solutions are user-friendly.
Provides technical feasibility assessment, identifies constraints, and contributes solution ideas. Ensures proposed solutions are buildable within technical architecture.
When team members disagree, it's almost always because they're relying on different information. One way to turn your product trio into a bright spot is to interview customers together, building a shared foundation from which you're making decisions.
While the trio is the core team, other specialists can join based on the type of decisions being made. For machine learning projects, include a data scientist. For teams committed to research rigor, embed a user researcher. The key is balancing speed with quality input.
Teresa Torres emphasizes making talking to customers weekly a keystone habit, meaning it's the foundational practice that enables all other continuous discovery activities to succeed. Teresa Torres recommends "weekly touchpoints with customers by the team building the product."
Interviewing customers every week helps to keep your discovery process agile, since you can disprove one opportunity and already begin gathering information on the next within a few days. This rapid learning cycle allows teams to pivot quickly when assumptions prove false, without losing momentum.
The frequency ensures that teams stay continuously connected to the customer reality, preventing the drift that happens when insights become stale or assumptions go unchallenged for too long.
Opportunities emerge from customer stories. We want to listen for needs, pain points, and desires in the context of specific stories. Ask customers to walk you through recent experiences rather than hypothetical scenarios.
Share low-fidelity prototypes, wireframes, or mockups to test solution ideas quickly. Use remote testing tools to gather feedback asynchronously or schedule live sessions to observe behavior.
Deploy one-question surveys at strategic moments in the user journey. Keep them focused and specific to decisions you're making this week, not general satisfaction metrics.
Review product usage data to understand what customers are actually doing. Data mining reveals patterns that complement what customers tell you in interviews.
Review customer support conversations, feature requests, and complaints. These unprompted signals reveal pain points customers care enough about to reach out.
Listen to conversations in social media, forums, and user communities. Customers discuss needs and frustrations openly when they're not talking directly to you.
Automate the recruiting process by building recruitment into your app, enlisting customer-facing colleagues to recruit for you, or creating a customer advisory board where each participant is interviewed once a month.
Schedule recurring time blocks for research activities. Protect this time like any other critical meeting. Make it a non-negotiable part of your weekly rhythm.
Have all members of the product trio participate in each interview, since it keeps you learning together and you each bring your own perspective to bear.
Focus each research activity on one or two specific questions. Small, focused research activities are more sustainable than lengthy comprehensive studies.
Avoid sending long notes or recordings. Instead, share key quotes, surprising insights, and actionable takeaways in bite-sized formats that stakeholders will actually consume.
Relying on one person to recruit and interview participants; digging into who, what, why, how, and when questions instead of story-based questions; interviewing only when you think you need it; sharing what you learned by sending pages of notes.
Opportunity solution trees are a simple way of visually representing the paths you might take to reach a desired outcome. Teresa Torres introduces the concept of opportunity solution tree and experience maps as visualization tools to organize insights gathered through continuous discovery.
The Opportunity Solution Tree consists of four sections: a clear outcome, opportunities that have emerged from research, solutions to target opportunities, and experiments to evaluate solutions and the riskiest assumptions behind them.
The root of the tree is your desired outcome—the business need that reflects how your team can create business value. Business outcomes measure the health of the business and are typically financial metrics. Product outcomes typically measure a customer behavior in the product or customer sentiment.
Opportunities are the customer needs, pain points, and desires that, if addressed, will drive your desired outcome. Conduct three to four story-based customer interviews before starting your first opportunity solution tree.
Torres suggests adopting a "compare and contrast" mindset rather than a "whether or not" mindset when prioritizing a target opportunity. Focus on one opportunity at a time to make progress manageable.
Torres advises team members to generate solutions initially on their own before coming together to map them out. Brainstorm solutions for your target opportunity. Don't brainstorm solutions across your entire tree. The goal is to focus on your target opportunity.
For each solution, identify the riskiest assumptions and design small experiments to test them. Use prototype tests, one-question surveys, data mining, and assumption tests to compare solutions.
One of the key benefits is it helps your team externalize and visualize your thinking, so it's easier to align around what to do when.
They keep the team aligned as they manage the messy cycles of continuous discovery.
OSTs provide a clear framework for organizing ideas and prioritizing them effectively by visualizing relationships between outcomes, opportunities, solutions, and experiments.
By first prioritizing opportunities before prioritizing solutions and ensuring everything links back to your most important desired outcome, an opportunity tree helps create clarity and focus.
Opportunity solution trees force you to break down very large, seemingly unsolvable problems into digestible and manageable chunks. A great product experience is about solving customer problems broken down into specific problems with specific solutions.
The outcome at the top sets the scope for discovery. It helps teams understand which opportunities are relevant and keeps them focused on the right types of solutions.
Opportunity solution trees are nearly impossible to create when you don't have good inputs. Always conduct customer interviews first, and never make up opportunities based on assumptions.
Torres explains that the product trio must cultivate six mindsets to successfully adopt the habits outlined in continuous discovery. These mindsets form the foundation for effective discovery work:
Torres outlines, "Use your desired outcome as the north star." When you begin your journey by defining outcomes, you can explore multiple solutions that help you reach your desired outcome. Outputs (features shipped) matter less than impact on customers and business.
Torres emphasizes the importance of continuous customer interviews to frame a customer-centric approach to product development. Build for real customer needs, not internal assumptions or stakeholder preferences.
Develop the so-called "co-creation mindset" where a customer is actively involved in the product creation process. This doesn't mean letting customers make technology decisions, but listening to their perspectives early and often.
Work as a cross-functional product trio, making decisions together based on shared customer insights. Break down silos between product, design, and engineering from day one.
Avoid "yes/no" thinking when evaluating opportunities and solutions. Instead, compare multiple options against each other to identify the best path forward through rigorous evaluation.
This process enables continuous learning and adaptability. "The beauty of continuous discovery is that we can always course-correct as we learn".
Starting continuous discovery doesn't require perfect conditions or complete organizational buy-in. Everyone is capable of making progress on their continuous discovery journey. It's all about finding the small steps you can take to build these habits.
If you work in a feature factory, you literally can do this today. Whatever you're working on, story map it. Use that story map to generate assumptions. This introduces discovery thinking even in output-focused environments.
When you're in the messy middle, interviewing customers together is the habit to start with. It's not easy to talk to customers every week, but start where you are and gradually increase frequency.
When your organization supports discovery, implement the full framework: weekly customer touchpoints, opportunity solution trees, assumption testing, and outcome tracking. Build sustainable practices into your workflow.
Begin with one customer interview per week. Don't wait for perfect conditions. Use whatever customer access you have, even if it's informal conversations with support or sales contacts.
Identify your closest cross-functional collaborators. Schedule regular working sessions where you review insights together and make decisions as a group.
Work with stakeholders to establish measurable outcomes that balance customer value and business value. Use these outcomes to guide all discovery decisions.
Create your first opportunity solution tree after conducting 3-4 customer interviews. Use it to align your team on target opportunities and solution directions.
Design small experiments to test the riskiest assumptions behind your solutions. Use prototype tests, surveys, and data analysis to gather evidence quickly.
Hold regular retrospectives to reflect on your discovery process. What's working? What's not? Continuously refine your approach based on what you learn.
Teams feel they're too busy shipping features to talk to customers. But this creates a vicious cycle of building the wrong things, which requires more rework and takes more time.
Start with 30-minute customer conversations once per week. Replace one internal meeting with a customer touchpoint. The insights will save you far more time than they cost by preventing wrong turns.
Sales owns customer relationships, or legal restrictions make outreach difficult. Direct customer access feels impossible to secure.
Partner with customer-facing teams. Join sales calls as observers. Analyze support tickets and feature requests. Use social listening in communities where customers discuss problems. Automate recruitment by building it into your product.
Leadership pressure to deliver specific outputs makes discovery feel like it will slow things down or be seen as making excuses.
Frame discovery as de-risking delivery. Use opportunity solution trees to show stakeholders how you'll achieve outcomes they care about. Share customer quotes that validate or challenge assumptions. Demonstrate how discovery prevents expensive failures.
If continuous discovery primarily taps into a specific segment of your customer base, it might introduce bias. If the team frequently communicates with power users or early adopters, their views and needs could become overrepresented.
When setting up a continuous discovery program, ensure customer touchpoints are diverse and representative of your entire user base. Intentionally reach out to different customer segments and employ stratified sampling methods.
How do you know if continuous discovery is working? Look for these indicators:
Are you making measurable progress toward your defined outcomes? Track your key metrics weekly to see if discovery insights are translating into outcome improvements.
Can you disprove assumptions and pivot to new opportunities within days instead of weeks? Rapid learning indicates healthy discovery practices.
Is your product trio making decisions together with less debate? Shared customer insights should reduce opinion battles and speed up decision-making.
Are you catching problems early before investing in full development? Fewer late-stage surprises and rework indicate effective assumption testing.
Are customers responding positively to new features? Higher satisfaction and adoption rates show you're building what customers actually need.
Is your team conducting customer touchpoints every week without fail? Consistency in the habit itself is a leading indicator of long-term success.
Discovery isn't a phase—it's an ongoing practice. Discovery and delivery are continuous processes that should happen in parallel. You're always delivering, and you're always discovering.
In a continuous discovery process, aim to talk to users at least once a week. Weekly user interactions keep your team closely aligned with real needs, challenges, and behaviors.
Opportunity solution trees help teams stay aligned and focused. They transform abstract thinking into concrete paths you can evaluate and compare.
Product managers, designers, and engineers should engage with customers together. Shared learning creates shared understanding and better decisions.
Define clear outcomes that balance customer and business value. Let outcomes guide your opportunity selection and solution prioritization.
It's never impossible, too late, nor any amount of adoption too small to introduce elements of continuous discovery into your current process. Start now and iterate from there.