# Opportunity Solution Tree

A visual decision map connecting a target outcome to customer opportunities, possible solutions, and the tests used to compare assumptions.

- Type: framework
- Domain: Strategy & discovery
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/opportunity-solution-tree/>)

## What it means

An Opportunity Solution Tree, created by Teresa Torres, organizes product discovery as a branching tree. A desired outcome sits at the root, customer needs and pain points form the opportunity space, possible responses form the solution space, and assumption tests provide evidence about promising branches.

## Why it matters

The tree makes the logic behind product bets inspectable. It helps a team avoid jumping from a business goal to a favorite feature, compare multiple opportunities and solutions, connect research to decisions, and explain why current experiments deserve attention.

## When to use it

Use it when a product trio has a measurable outcome and ongoing access to customer evidence but needs to organize options. It is particularly helpful for aligning stakeholders, reviewing discovery work, and maintaining strategic focus across many ideas.

## How it works

1. Name one clear, measurable product outcome that the team can influence.
2. Synthesize interviews and other evidence into distinct customer opportunities.
3. Structure related opportunities without forcing a perfect taxonomy.
4. Generate multiple solutions for selected opportunities.
5. Identify risky assumptions in promising solutions and run focused tests.
6. Update the tree as evidence changes the team’s understanding and choices.

## A practical example

For an invoicing product aiming to increase successful first invoices, interviews reveal that freelancers fear tax mistakes and do not know what details clients require. The team maps both opportunities, explores templates, guided setup, and review services, then tests the riskiest assumptions before building.

## Where it breaks

A tidy tree can overstate certainty and hide contradictory evidence, dependencies, or market forces. Opportunity wording and hierarchy require judgment, and a large tree can become performative documentation. It supports decisions but does not replace strategy, quantitative analysis, or prioritization.

## Common mistakes

- Putting features in the opportunity space instead of customer needs or pain points.
- Attaching only one solution to each opportunity.
- Treating the tree as a roadmap that must remain stable.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/opportunity-solution-tree/#visualization-opportunity-solution-tree>)

## Sources

1. [Opportunity Solution Tree: Definition and Overview](<https://www.producttalk.org/glossary-discovery-opportunity-solution-tree/>) — Product Talk · Creator-authored glossary
2. [Opportunity Solution Trees: Visualize Your Discovery](<https://www.producttalk.org/opportunity-solution-trees/>) — Product Talk · Creator-authored guide

## Related topics

- [Continuous Discovery](<https://wiki.soroush.uk/topic/continuous-discovery/>)
- [Assumption Mapping](<https://wiki.soroush.uk/topic/assumption-mapping/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
