How to Build an Opportunity Solution Tree (Step by Step)
An Opportunity Solution Tree connects a measurable outcome to the opportunities and solutions you bet on to reach it. Here’s how to build one from scratch — seven steps, the common mistakes, and how to keep it alive instead of letting it rot in a doc.
Before you start
You need two things in hand: a measurable outcome to anchor the tree, and a little customer research (three or four interviews is enough) to draw real opportunities from. Build without an outcome and you can’t prioritize; build without research and you’re just mapping opinions.
The seven steps
Start with one measurable product outcome — a change in customer behaviour that drives business value (e.g. “increase weekly active teams from 20% to 40%”). Not a feature, not a vanity metric. Everything below the root has to earn its place by moving this number.
From your customer research, list the opportunities — the needs, pains, and desires that, if addressed, would move the outcome. Phrase each as the customer’s need (“I can’t tell which teammates are active”), never as a solution. This is the heart of the tree.
Group related opportunities, merge duplicates, and arrange them parent-to-child from broad to specific. A clean opportunity space is what lets you choose where to focus instead of boiling the ocean.
Pick one target opportunity, then brainstorm several solutions for it — not just the first idea. Multiple solutions per opportunity keep you from marrying your first guess.
Under each solution, make the risky beliefs explicit as assumptions (desirability, usability, feasibility, viability). The riskiest, least-evidenced assumptions are what you’ll test before building.
Rank opportunities by importance and the evidence behind them; size solutions by effort versus impact. Decide with evidence and a confidence score, so the loudest opinion stops winning the roadmap.
A tree built once and filed away is worthless. Keep interviewing, keep testing assumptions, and keep re-sorting — the tree should change every week as you learn. That’s continuous discovery.
Common mistakes
No measurable outcome at the root
A tree that starts at opportunities has nothing to prioritize against. Without a number at the top, every branch looks equally worth doing.
Solutions disguised as opportunities
If a node names a feature (“add a dashboard”), it’s a solution. The opportunity is the need beneath it (“I can’t see activity”). Mixing the layers collapses the tree.
One solution per opportunity
Jumping to a single solution skips the comparison that makes discovery valuable. Generate a few, then let evidence choose.
Build it once, then let it rot
The value is in keeping it current. A static tree is just a diagram; a living one is a decision-making tool.
Build it without the manual upkeep
You can build an OST on a whiteboard — but it drifts. Outcomify keeps the structure honest and the tree alive:
- The hierarchy is enforced — outcomes take opportunities, solutions take assumptions — so the tree can’t quietly become a mess.
- Evidence and a confidence score live on each opportunity, so prioritization is grounded in signal.
- Canopy drafts opportunities from your notes for you to approve — so step 2 isn’t a blank page.
Frequently Asked Questions
Common questions about building an Opportunity Solution Tree
Keep exploring
What is an Opportunity Solution Tree?
The concepts behind the steps — outcomes, opportunities, solutions, assumptions.
Customer Interviews to Opportunities
Where step 2’s opportunities actually come from.
Opportunity Discovery Workshop
Build the first version of your tree with the team in a single session.
Build your first tree in minutes
Outcomify enforces the structure, keeps the evidence, and lets Canopy do the first pass — so your Opportunity Solution Tree stays a living decision tool.