Opportunity Solution Tree: Chart the Path to an Outcome

Created by Teresa Torres - https://www.producttalk.org/

Overview

The Opportunity Solution Tree (OST) is a product discovery framework created by Teresa Torres, a discovery coach and the author of Continuous Discovery Habits. In her words, "Opportunity solution trees are a simple way of visually representing the paths you might take to reach a desired outcome" (Torres, Opportunity Solution Trees). The tree gives a product team one picture that connects the result it is accountable for, the customer needs it has heard about, the ideas it is considering, and the evidence it is collecting on those ideas.

The tree has four layers. The root is the desired outcome, which Torres describes as "the business need that reflects how your team can create business value." Below it sits the opportunity space: the customer needs, pain points, and desires that, if addressed, would drive the outcome. Below each opportunity sit the solutions the team is exploring, and below each solution sit the assumption tests the team uses to judge which solutions will work (Torres, Opportunity Solution Trees). Each line between two nodes is a claim that the lower node serves the upper one, which is what makes the tree useful for spotting weak reasoning.

Torres introduced the tree on Product Talk in August 2016 with a post that opened, "I've found a visual aid that is profoundly changing the way teams work" (Torres, Why This Opportunity Solution Tree is Changing the Way Product Teams Work). In that post she credits two influences. One was Anders Ericsson's research in Peak on how experts rely on better mental representations than novices. The other was a reframing exercise taught by Bernie Roth of the Stanford d.school, which moves a person from a desired solution to the need behind it and then asks how else that need could be met. She later wrote that the first tree grew out of a coaching engagement: a team at BeachBody told her it did not know what to do next in discovery and relied on her too much, and that conversation inspired her to externalize her thinking in the form that became the first tree (Torres and Gurion, Engaging Stakeholders with Opportunity Solution Trees).

Torres expanded the framework into her book Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value, published by Product Talk LLC on April 14, 2021 (Amazon book listing). In January 2026 she wrote that over 135,000 people had bought the book (Torres, CDH Book Club: Chapters 1-2). Independent glossaries such as ProductPlan's also credit Torres with creating the OST in 2016.

The framework sits inside a larger idea of continuous discovery. Marty Cagan of SVPG was already urging teams in 2012 to replace a discovery phase with continuous product discovery that runs alongside delivery (Cagan, Continuous Discovery). Torres describes the structure underneath that work in one sentence: "Good product discovery has a simple underlying structure: Start with an outcome, discover opportunities, discover solutions" (Torres, Product Discovery Basics). The tree is how a team keeps that structure visible while it interviews customers and tests assumptions week after week.

The tree is built to resolve a tension that product teams live with. Torres points out that "Customer value does not always generate business value," and that the opposite failure, creating business value at the customer's expense, is common too. Her answer is structural: the outcome at the root represents business value, and the opportunity space beneath it keeps the path customer-centric, so every idea has to answer to both (Torres, Opportunity Solution Trees).

The tree belongs to a product trio: a product manager, a designer, and an engineer who share responsibility for deciding what to build (Torres, Product Trios). Torres designed it for one trio working toward one outcome, and she advises against a single company-wide tree. It also works as a communication tool. When a stakeholder arrives with a favorite feature, the team can ask which opportunity it addresses and what evidence supports that link, which moves the conversation from opinion to evidence.

Core Principles

Start from one outcome the team can move

The outcome sets the scope of discovery: it tells the team which opportunities are relevant and which are not. Torres separates business outcomes, product outcomes, and traction metrics, and writes, "As a general rule, I like to see a product outcome at the top of an opportunity solution tree" (Torres, Opportunity Solution Trees). A product outcome measures customer behavior or sentiment that the team can influence directly, while a business outcome such as revenue depends on many teams. She also recommends one outcome per team at a time, because a team cannot build a rich understanding of several opportunity spaces at once.

Opportunities come from customer stories

Opportunities on the tree should be ones the team actually heard. Torres teaches story-based interviewing, where the team asks customers to describe a specific past experience, because needs and pain points emerge naturally from those stories. She warns that generating opportunities off the top of your head brings the team's own biases into the tree. Sales calls, support tickets, and feature requests are useful as prompts for what to explore in the next interviews, but they usually lack the context needed to understand the need (Torres, Opportunity Solution Trees).

Keep opportunities and solutions apart

Torres defines an opportunity as "an unmet customer need, pain point, or desire," and a solution as a product, service, or feature offered to address it. Her test for a solution in disguise is to ask, "Is there more than one way to address this opportunity?" If there is only one way, the statement is a solution and needs to be reframed by asking why the customer wants it (Torres, Opportunity Solution Trees). She uses the word opportunity rather than problem because many products serve desires, such as entertainment, that nobody would call a problem.

Structure turns a backlog into a map

A flat list of opportunities is hard to prioritize because the items come in different sizes and many overlap. The tree uses two relationships: a child opportunity is a subset of its parent, and siblings are similar but distinct enough that each can be addressed without the other (Torres, Opportunity Mapping). Breaking a large, intractable opportunity into smaller children lets the team deliver value on one piece at a time. Torres quotes the cognitive psychologist Barbara Tversky to set expectations: "Structure is complicated. It gets done, undone, and redone."

Work on one target opportunity at a time

Torres encourages teams to pick one small target opportunity and work it before moving on, which she ties to the kanban principle of limiting work in progress. Focusing on one opportunity is what makes room to explore several solutions for it. She also asks teams not to wait for a perfect map: choose a target as soon as there is a rough first draft of the opportunity space, because most of the learning happens once solutions and assumptions are being tested (Torres, Opportunity Solution Trees).

Compare and contrast instead of asking whether or not

A single idea invites the question "Is this idea good?", which is hard to answer because good is relative. Torres recommends setting up a compare-and-contrast decision and asking "Which of these ideas looks best?" instead (Torres, How Compare and Contrast Decisions Lead to Better Product Outcomes). In practice that means generating many ideas for the target opportunity and carrying three forward. She adds that only solutions addressing the same opportunity should be compared, because solutions that serve different opportunities are answering different questions.

Test the assumptions behind each idea

Building a whole idea to find out whether it works is slow and expensive. Torres breaks each idea into its underlying assumptions across five categories (desirability, viability, feasibility, usability, and ethical) and tests only the riskiest ones (Torres, Assumption Testing). She deliberately calls these assumption tests: "Assumption tests are used in discovery when trying to decide between ideas. Experiments are used to measure the impact of what we built."

The tree is a living document

Torres writes that "Creating an opportunity solution tree is not a one-time activity" and recommends revisiting the opportunity space every three to four customer interviews (Torres, Opportunity Solution Trees). The top-level structure should stabilize over time while branches gain detail. A team starts a new tree only when the direction of its outcome changes, and keeps the same tree when only the target number moves.

How the Tree Has Evolved

Torres's original post described four sections: a desired outcome, opportunities from generative research, solutions bounded by an opportunity, and experiments (Torres, 2016 post). Her current guidance keeps that shape and changes several of the rules, and teams reading older write-ups should know which version they are following.

Steps

1. Meet the prerequisites Torres lists three before a first tree: a theory of the target customer and the value proposition, a clearly defined outcome, and three to four story-based customer interviews (Torres, Opportunity Solution Trees). She is blunt that trees are nearly impossible to create without good inputs. If the team has not interviewed anyone yet, it should start interviewing before it starts drawing. The output of this step is a short list of interview stories and an agreed outcome.

2. Put the outcome at the top Write the outcome in the root node, phrased as a direction plus a target where the team can measure it. Prefer a product outcome the trio can influence over a business outcome that depends on many teams. If leadership has assigned several outcomes, Torres suggests the team prioritize them and build a tree for the most important one. Check that the outcome is not a disguised output, such as shipping a particular feature.

3. Map the opportunity space Torres breaks the synthesis into four moves: build an experience map from the interview stories, turn its key moments into top-level opportunities, place each individual opportunity under the moment where it occurred, and then structure each branch one at a time into parent, child, and sibling relationships (Torres, Opportunity Solution Trees). Frame each opportunity in the customer's voice. Expect the first map to sprawl and be messy, and aim for a usable draft.

4. Choose a target opportunity Assess the top-level opportunities first, then move down only the chosen branch, so the team never has to compare every node against every other. Torres assesses opportunities on sizing, market factors, company factors, and customer factors, and leaves effort out because any opportunity can have both easy and hard solutions (Torres, Opportunity Solution Trees). She treats this as a reversible decision, so the team should decide quickly and walk back up the tree if the evidence says it chose poorly. Pick a small opportunity near the bottom of the branch so solutions can be small too.

5. Generate solutions and choose three Generate ideas for the target opportunity only. Torres advises against brainstorming across the whole tree. Aim for many ideas before narrowing, since more ideas tend to produce better ones, then carry three distinct ideas forward so the team can make a compare-and-contrast decision (Torres, How Compare and Contrast Decisions Lead to Better Product Outcomes). Add them to the tree as children of the target opportunity. Any idea that does not connect to an opportunity is set aside for now.

6. Test the riskiest assumptions For each of the three ideas, list the assumptions that must be true for it to work, using story mapping to walk through what the customer would have to do (Torres, Assumption Testing). Map them by how important they are and how much evidence already exists, and test the ones that are critical and poorly supported. Most tests fall into four types: prototype tests, one-question surveys, data mining, and research spikes. Write down what result would count as a pass before running each test.

7. Decide, then revisit the tree Use the test results to throw away ideas, refine the one that is good enough for delivery, or choose a new target opportunity. Keep interviewing weekly, and revise the opportunity space every three to four interviews so it reflects what the team is learning (Torres, Opportunity Solution Trees). Mark which opportunities and solutions have supporting evidence and which have been ruled out. Share the tree with stakeholders at the level of detail each one needs.

When to Use

• A team has an outcome but a backlog full of unconnected ideas. The tree forces each idea to name the opportunity it serves, which exposes ideas that serve none and gives the team a way to set them aside without a political fight.
• A product trio is starting weekly customer interviews. Interviews produce more needs and pain points than anyone can remember, and the tree gives them a place to accumulate and be compared.
• Stakeholders keep bringing solutions. Walking a stakeholder from the outcome through the opportunities to their idea turns a debate about preferences into a discussion about evidence.
• The team keeps arguing about two solutions. The argument is often about different underlying opportunities, and the tree makes that visible so the team can choose the opportunity first.
• A team needs to show discovery progress before results arrive. The tree records which opportunities were explored, which were chosen, and which assumptions were tested, which is visible progress even while the outcome metric is still flat.

When Not to Use

• Nobody can talk to customers. Torres treats customer interviews as a prerequisite, and a tree filled with invented opportunities gives false confidence.
• The scope is fixed and there is no room to choose. One product director featured on Product Talk found it too early to build a tree for a new product whose scope was predefined, leaving no room for opportunities outside it (Product in Practice at Texthelp). Delivery planning is the better use of that time.
• The goal is a company-wide strategy view. Torres advises against one tree for the whole company and suggests a KPI tree or a company-wide experience map for that job (Torres, Opportunity Solution Trees).
• The work is urgent maintenance or a known fix. A bug with an obvious remedy has one solution, so building opportunity branches and comparing ideas adds overhead without adding information.