When building products, it’s easy to jump straight from ideas to execution. But great product teams don’t just ask, “What should we build?”—they ask, “What outcome are we trying to achieve, and what’s the best path to get there?” That’s where the Opportunity Solution Tree comes in.
Popularized by product discovery expert Teresa Torres, the Opportunity Solution Tree is a visual decision-making tool that helps product teams stay outcome-focused, align cross-functionally, and reduce the risk of building the wrong things.
What Is an Opportunity Solution Tree?
The Opportunity Solution Tree (OST) is a simple, yet powerful visual framework that maps the path from a desired product outcome to various opportunities, solutions, and experiments.
It consists of four levels:
- Outcome – The measurable business or product goal you’re trying to achieve.
- Opportunities – Customer needs, pain points, or desires uncovered during research.
- Solutions – Ideas or features that could address those opportunities.
- Experiments – Tests to validate if a solution actually solves the opportunity and moves the outcome.
This structure helps teams avoid feature-driven thinking and instead build solutions that are rooted in real customer problems and tied to meaningful goals.
Why Use an Opportunity Solution Tree?
- It connects outcomes to user needs: You don’t just chase features—you solve real problems aligned with business goals.
- It encourages exploration: By visually branching out opportunities and ideas, you’re more likely to consider multiple paths rather than default to the first solution.
- It helps prioritize: OST makes it easier to identify which solutions are worth testing based on opportunity value and risk.
- It aligns teams: Everyone—designers, engineers, stakeholders—can see how decisions ladder up to outcomes.
Breaking Down the Tree
1. Define Your Outcome
Start at the top. What’s the key result or metric you’re trying to improve?
Examples:
- Increase trial-to-paid conversion by 15%
- Improve daily active users by 20%
- Reduce support ticket volume by 30%
This becomes your anchor. Everything in the tree should help move this outcome.
2. Map Opportunities
Next, identify opportunities based on user research. These are problems or unmet needs that, if solved, could move the outcome.
Sources of opportunities:
- User interviews
- Support tickets
- Usage analytics
- Jobs To Be Done (JTBD)
Example opportunities under “Improve trial-to-paid conversion”:
- Users don’t understand the value before the trial ends
- Users struggle to complete setup
- Users miss out on core features
3. Generate Solutions
Now ideate possible ways to solve each opportunity. Don’t settle on one—generate many.
For “Users don’t understand the value,” possible solutions might be:
- Add a product tour
- Show success stories within the app
- Use emails to highlight key features
4. Design Experiments
Before committing resources, test your solutions. Design small experiments to validate assumptions.
Experiments might include:
- A/B testing a new email sequence
- Usability testing a prototype tour
- Fake door tests for upcoming features
A Quick Example
Outcome: Increase trial-to-paid conversion by 15%
Opportunities:
- Trial users don’t reach the “aha” moment
- Onboarding feels overwhelming
- Users don’t perceive enough value
Solutions:
- Interactive onboarding checklist
- Highlight feature benefits in-app
- Send behavioral-based reminder emails
Experiments:
- A/B test onboarding flow changes
- Survey users post-trial
- Run a 2-week trial with guided setup vs. unguided
This tree helps the team stay focused, test iteratively, and avoid wasting effort on solutions that don’t solve a real problem.
Best Practices
- Always start with a clear outcome
- Base opportunities on actual user research—not assumptions
- Encourage divergent thinking—more options lead to better decisions
- Use small experiments to test quickly and cheaply
- Involve the whole product trio (PM, design, engineering) in discovery and planning
Final Thoughts
The Opportunity Solution Tree is not just a framework—it’s a mindset shift. It helps teams stop reacting to ideas and start reasoning from outcomes and real user needs. It makes your product process more intentional, more customer-centered, and ultimately, more effective.
So next time you’re staring at a backlog of features, pause—and try building a tree. It might just show you the better path forward.
Because in product, the best solutions don’t come from guesswork. They come from clarity.