opportunity-solution-tree

Opportunity Solution Tree – A Structured Product Discovery Framework

Skill Overview

The Opportunity Solution Tree (OST) is a visual framework that helps product teams structure continuous product discovery by connecting desired business outcomes to customer opportunities, potential solutions, and validation experiments. It is based on Teresa Torres’s methodology from Continuous Discovery Habits.

Applicable Scenarios

1. Structuring Product Discovery Work

When product teams need to conduct discovery systematically rather than through scattered, ad hoc research, the OST provides a clear four-layer structure: outcome → opportunity → solution → experiment. It is suitable when teams do not know “what to do” or “what to do next,” and helps prevent them from jumping directly to solutions while overlooking problem definition.

2. Mapping Opportunities to Solutions

When teams have identified many user pain points but are uncertain how to prioritize and match them with solutions, the OST helps connect opportunities—customer needs, pain points, and desires—with multiple potential solutions. This ensures that every solution is supported by a clearly defined opportunity and avoids the backward process of “starting with a solution and then looking for a problem.”

3. Deciding What to Build First

When product teams face multiple feature requests and need to prioritize based on customer value rather than subjective opinions, the OST uses opportunity scoring (importance × (1 − satisfaction)) and experimental validation to support data-driven decisions. This ensures that resources are invested in problems that truly matter to customers.

Core Functions

1. Four-Layer Discovery Structure Mapping

Provides a complete top-down product discovery tree structure:

Outcome layer: Define a single, measurable business or product metric, such as “increase 7-day retention to 40%.”

Opportunity layer: Identify needs, pain points, and desires from customer research, expressed from the customer’s perspective, such as “I have difficulty…” or “I wish I could…”

Solution layer: Generate at least three possible solutions for each opportunity through collaborative brainstorming by the product trio (PM + designer + engineer).

Experiment layer: Design quick, inexpensive tests to validate whether a solution truly solves the problem, including assessments of value, usability, feasibility, and feasibility risk.

2. Opportunity Prioritization Assessment

Uses the Opportunity Score formula (Opportunity Score = Importance × (1 − Satisfaction)) to prioritize customer opportunities:

Normalize importance and satisfaction to a range of 0–1.

Problems with high importance and low satisfaction receive the highest scores.

Help teams focus on core pain points that genuinely affect the customer experience.

Base decisions on real customer research data rather than internal team opinions.

3. Experiment Design and Validation

Provides a systematic approach to hypothesis validation:

Define a clear hypothesis statement: “Solution X will help customers achieve Y.”

Select the most appropriate experiment method, such as prototype testing, landing pages, fake doors, or a concierge MVP.

Define success metrics and thresholds.

Prioritize experiments involving “skin in the game” from real users rather than validation based solely on opinions.

Frequently Asked Questions

What Is an Opportunity Solution Tree?

The Opportunity Solution Tree (OST) is a visual framework proposed by product discovery expert Teresa Torres for structuring the product discovery process. Through a four-layer tree structure—desired outcomes, customer opportunities, solutions, and validation experiments—it helps product teams systematically move from problem definition to solution validation. The core value of the OST is preventing teams from jumping to solutions too early and ensuring that every feature is based on real customer needs.

How Do You Use the OST Framework for Product Discovery?

The steps for using the OST for product discovery are:

Define the outcome: Determine a single, measurable business metric as the top of the tree.

Identify opportunities: Through customer interviews, surveys, and feedback analysis, express 3–7 needs or pain points from the customer’s perspective.

Prioritize: Use opportunity scoring (importance × (1 − satisfaction)) to rank them and focus on the top 2–3 opportunities.

Generate solutions: For each priority opportunity, have the product trio collaboratively brainstorm at least three solutions.

Design experiments: Design one or two quick validation experiments for the most promising solutions.

Visualize the tree: Present the complete structure as a tree diagram and update it weekly as new learning emerges.

What Scenarios Is the Opportunity Solution Tree Suitable For?

The OST is best suited to scenarios including:

The early stages of product discovery: When teams need to systematically understand user problems and needs.

Feature prioritization decisions: When multiple needs compete for limited development resources.

Avoiding the feature factory model: When teams focus only on shipping features while neglecting value discovery.

Cross-functional collaboration: When PMs, designers, and engineers need to participate jointly in product decisions.

Continuous discovery processes: When establishing a weekly discovery cadence instead of conducting one-off large-scale research projects.

The OST is not suitable for urgent engineering fixes, technical debt cleanup, or purely infrastructure projects.

How Do You Prioritize Product Opportunities?

Use Opportunity Scoring to quantify and rank opportunities:

Collect importance and satisfaction ratings for each opportunity through customer research.

Normalize the ratings to a range of 0–1 (0 = lowest, 1 = highest).

Calculate the opportunity score = importance × (1 − satisfaction).

Rank the scores. A high score indicates a pain point with high importance and low satisfaction that should be prioritized.

Focus first on the top 2–3 opportunities and avoid trying to address too many at once.

Qualitative assessment can also be used, including urgency, scope of impact, and alignment with product strategy.

How Should Product Experiments Be Designed?

Effective product experiments should follow these principles:

Clear hypotheses: Explicitly state, “If we do X, customers will do Y because Z.”

Appropriate methods: Select methods based on the type of risk being validated. For example, use prototype testing to validate usability, fake-door tests to validate value and willingness, and a concierge MVP to validate demand frequency.

Fast and inexpensive: Prioritize experiments that can be completed within a few days at low cost.

Real commitment: Design experiments that require users to invest time, money, or reputation—their “skin in the game”—rather than relying solely on verbal feedback.

Success criteria: Define metrics and thresholds in advance to avoid post hoc interpretation.

Actionable results: After the experiment, be able to clearly decide whether to continue, modify, or stop pursuing the solution.

What Are Teresa Torres’s Continuous Discovery Habits?

Continuous Discovery Habits is Teresa Torres’s product discovery methodology. Its core ideas include:

Continuous rather than periodic discovery: Product teams should conduct customer interviews and small experiments every week rather than large-scale research projects each quarter.

The product trio: PMs, designers, and engineers jointly participate in discovery and decision-making.

The OST framework: Use the Opportunity Solution Tree to structure discovery work.

Hypothesis-driven development: Every solution should be based on a clear hypothesis and validated through experiments.

Avoiding the feature factory: Balance discovery and delivery to ensure an ongoing understanding of customer needs.

This book and methodology have become standard practices in modern product management.

How Should the Product Trio Collaborate?

The product trio refers to the close collaboration among three roles: the product manager (PM), designer, and engineer.

Joint participation in discovery: The trio participates together in customer interviews, data analysis, and opportunity identification.

Joint brainstorming: When generating solutions, the trio contributes ideas together. Torres points out that “the best ideas often come from engineers.”

Complementary perspectives: PMs focus on business value, designers focus on user experience, and engineers focus on feasibility.

Joint decision-making: The trio reaches consensus on priorities and experiment plans rather than leaving decisions to a single role.

Continuous communication: Establish a weekly cadence to synchronize learning and update the OST.

This collaboration breaks away from the traditional linear process of “the PM submits requirements and the engineer implements them.”

How Can You Avoid Jumping to Product Solutions Too Early?

The OST framework prevents a “solution-first” process through the following mechanisms:

Forcing the process to start with the problem: The top of the tree is the outcome, followed by opportunities. Problems must be defined before solutions can be discussed.

Keeping opportunities separate from features: Opportunities must be expressed from the customer’s perspective, such as “I have difficulty…,” rather than “We need a button.”

Generating multiple solutions: Require at least three solutions for each opportunity to avoid the “first idea trap.”

Comparing options: Evaluate and select among multiple solutions rather than immediately executing the first idea.

Validating through experiments: Selected solutions must be tested through hypotheses rather than decided through internal team voting.

Remember Torres’s principle: “Never let customers design solutions; prioritize solving opportunities (problems) rather than building features.”