What Is an Opportunity Solution Tree

What does an opportunity solution tree mean?

An opportunity solution tree, often shortened to OST, is a visual map that connects a single desired outcome to the customer opportunities that drive it, the possible solutions that address those opportunities, and the experiments that test whether each solution actually works. Per Product Talk's glossary, Teresa Torres introduced the concept in 2016 as part of a continuous discovery framework, and the tree's job is to show a team the connection between its business goals, what customers actually need, and the possible solutions it could build. When new information arrives, a failed experiment or a surprising interview finding, a team can trace it directly to the branch it affects instead of reworking the whole plan from scratch.

Why an opportunity solution tree matters for product managers

Builders Camp's Product Strategy certification quiz asks members directly what the tree's primary purpose is, and the correct answer describes it as a tool for mapping all possible opportunities and experimenting with different solutions to find the best one, not a record of failed ideas or a tool for ranking opportunities by cost alone. That distinction keeps teams from treating discovery as a single big decision; instead of picking one solution and betting the quarter on it, the tree makes it normal to test several solutions against the same opportunity before committing engineering time to any of them.

Opportunity solution tree example

A team with a stated outcome of reducing new-user churn in the first week starts by mapping the opportunities customers actually describe in interviews: confusing setup, no clear first win, and unclear pricing. Under the setup opportunity, the team lists two candidate solutions, a guided checklist and a shortened onboarding flow, and designs a small experiment for each rather than building both fully. This is the same structure Jobs to Be Done interviews feed into directly: the opportunities on the tree come from what customers say they are actually trying to accomplish, not from a feature request list, and each candidate solution gets checked against an assumption matrix before it earns real engineering time. When the guided checklist experiment wins, the losing branch stays visible on the tree rather than getting deleted, so the next round of discovery does not waste time re-testing an idea the team already ruled out.

How Builders Camp teaches an opportunity solution tree

Product Strategy, a 2 week bootcamp with 4 live sessions and 8 microlessons taught by Andre Albuquerque, includes the Opportunity Solution Tree template directly in its resource library and tests it in the certification quiz described above. Product Manager Foundations introduces the underlying discovery mindset before students reach this tool. See the Product Strategy bootcamp for the full curriculum.