Teresa Torres’s Opportunity Solution Tree is a single picture that holds an entire discovery effort together. At the top sits one outcome — the result you’re trying to produce. Beneath it branch the opportunities — the customer needs, pains, and desires that, if addressed, would drive that outcome. Beneath each opportunity hang solutions, and beneath each solution, the experiments (or assumption tests) that would tell you whether it works. Built top-down, it turns one big goal into a navigable tree of smaller, testable bets.
The levels enforce discipline at each step. The outcome scopes everything — it decides which opportunities are even relevant. Opportunities are framed from the customer’s point of view (a need, not a feature), which stops solutions from masquerading as problems. Solutions are generated only against a named opportunity. And experiments target the riskiest assumption behind a solution, so you learn before you build.
A solution that doesn’t trace up to a real opportunity is a feature in search of a reason. The tree makes the missing branch obvious.
Read the tree top-down for scope and bottom-up for honesty. Top-down: does every opportunity actually serve the outcome? Bottom-up: does every solution trace to a real customer opportunity, and is each one backed by an experiment rather than conviction? The most valuable finding is usually a beloved solution with no opportunity above it — or an important opportunity with no solutions explored beneath it.
Here’s why the OST is the keystone tool for this whole section: its root outcome is a business objective. Pick one of the twelve — retain customers, acquire customers, increase customer value — and the tree becomes the structured path from that objective down to the experiments that pursue it. Where the objectives framework answers “what are we trying to improve,” the OST answers “through which customer opportunities, by what solutions, tested how.” It is the bridge from the spine to execution.
That bridge is also a guard against the most common product failure: shipping solutions that trace to no opportunity and serve no objective. By forcing every branch to connect outcome → opportunity → solution → experiment, the tree keeps a team’s effort tied to a result it can name. In Business Topologies terms, it’s a coordination structure for discovery — it aligns what gets built with why.
Reach for it when a team is generating solutions faster than reasons, when an objective needs a structured path to execution, or when discovery work has sprawled into disconnected bets. Pair it with the business objectives (which supply the root outcome), Jobs-to-be-Done (which sharpens the opportunity layer), and the Impact / Effort Matrix (to sequence the solutions the tree surfaces).