What is an opportunity solution tree?

An opportunity solution tree (OST) is a visual map that links a desired outcome to the customer opportunities that could drive it, the solutions that address each opportunity, and the assumption tests that check each solution. Teresa Torres of Product Talk introduced it in 2016 as a core tool of continuous discovery.

Updated

How does an opportunity solution tree work?

The four levels of an opportunity solution tree
LevelWhat it holdsComes from
Outcome (root)One measurable business or product outcome the team ownsLeadership and the team agree on it
OpportunitiesCustomer needs, pain points and desires that would move the outcome if addressedCustomer interviews and other research
SolutionsIdeas that address a specific opportunity, several per opportunityThe team's ideation
Assumption testsSmall experiments that check whether a solution will workThe riskiest assumptions behind each solution

Large opportunities are broken into smaller child opportunities until each is specific enough to solve. The team then compares opportunities against each other before picking solutions, instead of debating a flat backlog of ideas.

Opportunity solution tree example

  • Outcome: increase the share of new finance teams who close their first month in the product.
  • Opportunity: "I don't trust the totals, so I rebuild them in Excel."
  • Child opportunity: "I can't see which transactions make up a total."
  • Solutions: drill-down from any total; a reconciliation view; an audit trail export.
  • Assumption test for drill-down: a clickable prototype with five finance leads, checking whether they stop exporting.

Opportunity solution tree vs backlog

A backlog is a flat list of solutions. A tree keeps the reason for each solution visible: which customer problem it addresses and which outcome that problem affects. That makes it easier to drop a solution without losing the opportunity, and to see when the team has many ideas for one problem and none for a more important one.

Common mistakes with opportunity solution trees

  • Writing solutions as opportunities. "We need a dashboard" is a solution; the opportunity is the need behind it.
  • Inventing opportunities. Opportunities should come from what customers said and did, ideally with quotes attached.
  • One solution per opportunity. Comparing several solutions is what avoids building the first idea.
  • Never updating the tree. It should change every week as interviews and tests teach you something.

How does Praxiom AI help with opportunity solution trees?

Praxiom AI does not draw opportunity solution trees. It supplies the evidence for the opportunity level: synthesized insights typed as pain points, opportunities and user behaviors, each linked to source quotes. See research synthesis and interview synthesis.

Frequently asked questions

Who created the opportunity solution tree?

Teresa Torres, a product discovery coach and author of Continuous Discovery Habits. She introduced the opportunity solution tree on Product Talk in 2016.

What is the difference between an opportunity and a solution?

An opportunity is a customer need, pain point or desire. A solution is something the team could build to address it. Opportunities come from customers; solutions come from the team.

How often should you update an opportunity solution tree?

Whenever you learn something, which in continuous discovery means most weeks. New interviews add or reshape opportunities; assumption tests prune solutions.

Can an opportunity solution tree replace a roadmap?

Not entirely. The tree shows the options and reasoning for one outcome. A roadmap communicates what the team has committed to and roughly when. Many teams use the tree to decide what goes on the roadmap.

Sources

  1. [1]Product Talk: Opportunity Solution Trees (Teresa Torres) (checked 14 November 2026)

Run your product discovery on autopilot.

Bring your interviews, tickets and surveys. Get scored insights, a PRD and tickets.