What is an opportunity solution tree?
An opportunity solution tree is a visual map that starts from a single desired outcome.
It connects that outcome to the customer opportunities that could move it, the candidate solutions for each opportunity, and the experiments that would test those solutions.
The structure has four levels: outcome at the top, opportunities beneath it, solutions beneath those, and experiments at the bottom. Opportunities are unmet needs, pains, and desires expressed by customers, phrased in their words, not as features. Teresa Torres developed the tree as the central artifact of continuous discovery.
Why it matters
It forces two separations. First, between the problem space and the solution space, which teams collapse constantly. Second, between competing solutions to the same opportunity, which is where the option value is. Most teams generate one idea per problem and then defend it.
Example
Outcome: increase weekly active teams. Opportunity: "I can't tell if anyone read my report." Solutions: read receipts, a digest email, an in-app activity feed. Experiments: a fake-door test for each. The opportunity came from interview quotes; the solutions did not.
In UpSight
UpSight does not draw the tree. What it gives you is the opportunity layer with receipts: themes are the needs and pains customers stated, each linked to the quotes and the people behind it, so the middle of your tree comes from evidence rather than a brainstorm. From a theme you can create a task to carry a solution or experiment forward, and the task keeps its link back to the evidence. One naming note: "Opportunities" inside UpSight means sales deals, not tree opportunities.
Related terms
FAQ
- What goes at the top of an opportunity solution tree?
- One measurable outcome. Trees with several outcomes at the top become unmanageable and hide trade-offs.
- What's the difference between an opportunity and a solution?
- An opportunity is a customer need stated in the customer's terms. A solution is something you could build. "I never know if it worked" is an opportunity; "add a dashboard" is a solution.
- How often should the tree be updated?
- Continuously. It is a working artifact, not a deliverable. New interview evidence should change it weekly.