What Is an Opportunity Solution Tree? How to Use It for Product Discovery
The Opportunity Solution Tree (OST) is a visual framework developed by Teresa Torres that helps product teams organize their product discovery work — connecting their desired outcome to the opportunities they’re exploring and the solutions they’re testing. It creates a structured, visual representation of the relationship between what the team is trying to achieve, the customer problems that stand in the way, and the possible solutions to those problems.
The Opportunity Solution Tree is central to Torres’s continuous discovery methodology, which argues that product teams should be in ongoing contact with customers and continuously identifying and validating opportunities rather than conducting episodic research bursts.
The Structure of an Opportunity Solution Tree
The tree has four layers, flowing from top to bottom:
Layer 1: Desired Outcome
The root of the tree is a specific, measurable business outcome the team is working toward — the metric that the team is trying to move. This might be “increase 30-day retention from 45% to 55%” or “reduce time to first value from 8 days to 3 days.” The outcome is not a feature or solution; it’s the result the team is trying to achieve.
Defining the desired outcome precisely is critical: it focuses all subsequent discovery work on problems that matter for this specific goal rather than generalized improvement.
Layer 2: Opportunities
Opportunities are customer needs, pain points, desires, or problems that, if addressed, would contribute to achieving the desired outcome. These are discovered through user research — interviews, observations, behavioral analysis — and represent the space of problems worth solving.
The opportunity space is deliberately broad: the team identifies and maps many more opportunities than they will ultimately pursue. The tree makes these opportunities visible and allows the team to evaluate which are most promising to explore.
Layer 3: Solutions
Solutions are specific product changes, features, or experiments that could address a specific opportunity. Multiple solutions might exist for any opportunity; the tree maps the relationship between solutions and the opportunities they serve.
Layer 4: Experiments
For each solution, the team designs experiments to test the solution’s assumptions before committing to full development. An experiment might be a prototype test, an A/B test, a fake door test, or a wizard-of-oz experiment.
Why the Opportunity Solution Tree Is Valuable
It Connects Solutions to Outcomes
One of the most common problems in product development is that features get built without clear connection to the outcomes the team is supposed to achieve. The OST forces this connection: every solution on the tree traces back to an opportunity, which traces back to the desired outcome. If a proposed solution doesn’t connect, it’s a signal that it doesn’t belong in the current focus area.
It Prevents Premature Solution Convergence
Teams that jump directly from desired outcome to specific solutions skip the crucial step of thoroughly mapping the opportunity space. This leads to solving the most obvious problems rather than the most impactful ones. The OST requires teams to map the opportunity space broadly before narrowing to solutions.
It Creates Shared Team Context
The visual tree format makes the team’s discovery context explicit and shared — rather than living in individual project managers’ heads. Everyone on the team can see what’s been discovered, what’s being explored, and what’s been validated.
It Supports Continuous Discovery
The OST is a living artifact: it grows and evolves as the team learns. New opportunities are added from research; solutions that fail experiments are removed; the tree becomes a record of the team’s accumulated discovery knowledge.
How to Build an Opportunity Solution Tree
- Define the desired outcome — Specifically and measurably. Use a business metric the team can influence.
- Identify opportunities through research — Conduct user interviews focused on the outcome area. Capture pain points, desires, and needs as opportunity nodes.
- Prioritize opportunities — Evaluate opportunities by their frequency, severity, importance to the target customer, and connection to the desired outcome.
- Generate solutions for prioritized opportunities — For each opportunity worth exploring, brainstorm multiple possible solutions.
- Design experiments — For promising solutions, design the smallest possible test that would validate or invalidate the core assumption.
- Run experiments and update the tree — As experiments produce results, update the tree and adjust priorities.
Key Takeaways
The Opportunity Solution Tree is a powerful tool for structuring product discovery work in a way that keeps the team outcome-focused, customer-grounded, and continuously learning. By making the relationship between outcomes, opportunities, solutions, and experiments explicit and visual, it prevents the common failure mode of jumping to solutions before thoroughly understanding the problem space — and creates a shared, evolving record of what the team knows and is exploring.