Opportunity Solution Tree
Visual map from outcomes to tested solutions
The Opportunity Solution Tree (OST) is a visual framework for connecting a desired business outcome to the opportunities (customer problems and desires) that could help achieve it, the possible solutions for each opportunity, and the assumption tests that validate each solution. It prevents teams from jumping to solutions without understanding the opportunity space and makes the team's thinking transparent.
Developed by Teresa Torres, documented in her book 'Continuous Discovery Habits' (2021) and on her blog productboard.com/resources. Grew from her work coaching product teams at companies including Spotify and Intercom.
Use Opportunity Solution Tree when
- ✓Teams running continuous discovery who need a shared visual model of their opportunity space
- ✓PMs who want to connect their backlog to explicit business outcomes rather than feature lists
- ✓Discovery and delivery teams that need a shared artefact to stay aligned on what they're exploring
- ✓Organisations adopting Teresa Torres's Continuous Discovery Habits framework
Avoid it when
- ✗Teams in pure execution mode with no discovery capacity
- ✗Very early-stage products where the desired outcome is still being defined
- ✗Teams without a regular customer interview practice — the tree requires ongoing qualitative input
Key Concepts
The root of the tree: the specific business outcome the team is trying to move. Should be measurable and time-bound.
A customer need, pain point, or desire that, if addressed, would move the desired outcome. Opportunities are discovered, not invented.
A specific product change, feature, or experiment that addresses an opportunity. Multiple solutions can address the same opportunity.
The fastest, cheapest way to validate a critical assumption underlying a solution before building it.
The full set of opportunities visible in the tree at any time — the team's current understanding of the problem landscape.
A more specific version of a parent opportunity. Breaking down opportunities prevents teams from tackling overly broad problems.
How it works
Agree on one measurable desired outcome the team is trying to achieve this quarter. Connect it to business strategy.
Run weekly customer interviews. Every insight maps to an opportunity on the tree. Interview at least 2 customers per week.
For each prioritised opportunity, generate multiple possible solutions. Avoid committing to one solution before exploring alternatives.
Identify the riskiest assumption for each candidate solution. Run the cheapest test possible to validate it before building.
Tools that support Opportunity Solution Tree
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Browser-based with no installation required — runs on any OS and enables instant sharing via URL, removing friction for cross-functional collaboration with PMs, engineers, and stakeholders
Best-in-class infinite canvas experience — the gold standard for collaborative whiteboarding with real-time multiplayer editing
De facto standard for workplace communication — most PMs will use Slack daily, and it appears constantly in job descriptions
Frequently Asked Questions
After every customer interview. The tree is a living artefact that should reflect current customer understanding. Weekly interview cadence means weekly updates. If the tree hasn't changed in a month, the team isn't doing enough discovery.
A manageable tree has 5–15 opportunities. If you have more, cluster related ones or pick the sub-set most relevant to the current desired outcome. Avoid adding every possible opportunity — focus on what's relevant to the current goal.
You can use it as a one-time planning tool, but it was designed for continuous discovery. Its power comes from how it evolves as you learn. A static OST quickly becomes stale and loses the connection to actual customer understanding.