The first 3 interviews are free · Start free or see the prices

Opportunity Solution Tree Template: From Interviews to Experiments

Use this template to connect a product outcome to what you heard in interviews. Each node type has a rule for what belongs in it, so opportunities do not turn into solutions in disguise.

Analyze a transcript free

Use it for

  • One measurable product outcome that the team owns, such as the share of new accounts that invite a second user.
  • Interview snapshots: a one-page summary of each recent customer interview with quotes and the moments the customer described.
  • The solution ideas the team already has, to place on the tree or reject.

Steps

  1. Set one outcome at the top

    Write one measurable outcome that the team can move. Use a product outcome, such as activation, not a business result, such as revenue. A tree with two outcomes is two trees.

  2. Pull opportunities from the snapshots

    Read each interview snapshot and write the needs, pains and desires the customer showed. Write each one in the customer's view, such as "I do not know if my team saw the update".

  3. Group opportunities into parents and children

    Put related opportunities under a broader parent. A child must be a smaller, more specific part of its parent. If you cannot find a parent, the opportunity can sit directly under the outcome.

  4. Choose one target opportunity

    Compare opportunities at the same level. Consider how many customers have it, how much it hurts them and how much it moves the outcome. Pick one child opportunity to work on.

  5. Add at least three solutions

    Under the target opportunity, write three or more different solutions. Three ideas stop the team from falling in love with the first one.

  6. Find and test the riskiest assumptions

    For each solution, list what must be true for it to work. Mark the assumptions with the most risk and the least evidence. Design a small test for each one before you build.

Codebook

Copy the codebook as a table. It pastes into a spreadsheet with one row for each code.

Outcome

The measurable change in customer behavior that the team wants to cause.

Include
Write one metric that the team can move with product work, with its current value if you know it.
Exclude
Do not write a business result the team cannot move alone, such as revenue, or an output, such as "launch feature X".
Example
“Increase the share of new workspaces that invite a teammate in the first 7 days.”

Parent opportunity

A broad customer need, pain or desire that groups several specific opportunities.

Include
Write a need in the customer's view that at least two child opportunities belong to.
Exclude
Do not write a need that only one interview showed and that has no children. Make it a child opportunity.
Example
“I need my team to see my work without asking me.”

Child opportunity

A specific need, pain or desire that a team can address in one cycle of work.

Include
Write a need that you heard in at least one interview story and that is narrow enough for several solutions.
Exclude
Do not write a need that has only one possible solution. That is a solution in disguise. Rewrite it as the need behind it.
Example
“I do not know if my teammate opened the plan I sent.”

Solution

A product change, feature or experiment that could address one opportunity.

Include
Write a concrete idea that sits under one child opportunity. Write at least three per target opportunity.
Exclude
Do not place a solution directly under the outcome. Every solution must connect to an opportunity.
Example
“Show a "Seen by" line with avatars under each shared plan.”

Assumption

A belief that must be true for a solution to work, which you have not yet proven.

Include
Write one belief about desirability, usability, feasibility or viability, in a form you can prove false.
Exclude
Do not write a fact that you already have evidence for. Link the evidence instead.
Example
“Teammates are fine with the sender seeing that they opened the plan.”

Assumption test

A small, fast activity that shows whether an assumption is true.

Include
Write the test, the people it involves and the result that would count as a pass, before you run it.
Exclude
Do not write a full build of the solution. A test must be much smaller than the solution.
Example
“Show 8 users a mock with read receipts. Pass if at most 2 say they would turn them off.”

Interview snapshot

The evidence from one interview that supports one or more opportunities.

Include
Link the snapshot to each opportunity it supports. Include the specific story, not a summary of opinions.
Exclude
Do not link a snapshot where the customer only agreed with an idea you suggested. That is not evidence of a need.
Example
“I sent the launch plan on Monday and found out on Thursday that nobody had read it. We missed the date.”

Report outline

  1. The outcome, its current value and the target.
  2. The tree: outcome, parent and child opportunities, with the number of interviews behind each one.
  3. The target opportunity and why the team chose it over the others.
  4. Solutions under the target opportunity, and the assumptions for each.
  5. Assumption tests: what was tested, the pass rule and the result.
  6. Next steps: the solution to build, the opportunity to explore next and the interviews to schedule.

Mistakes to avoid

  • Do not write solutions as opportunities. "Customers need a dashboard" is a solution. Ask what need the dashboard would meet.
  • Do not build the tree from a single interview. Opportunities need stories from several customers before you choose one.
  • Do not stop at one solution per opportunity. With one idea, the team cannot compare and the test has nothing to beat.
  • Do not keep the tree frozen. Add new interview snapshots every week and move nodes when the evidence changes.

Guides that use it

Questions

It is a visual map. It links one product outcome to customer opportunities, to solutions and to tests for each solution. Teresa Torres made it popular in her book Continuous Discovery Habits.

An opportunity is a customer need, pain or desire. A solution is something you could build. A good test: an opportunity has many possible solutions.

Start the tree after 4 to 6 interviews. Then keep adding interviews each week. The tree is a living map, not a one-time output.

User Evaluation has an Opportunity areas report template that lays out study report themes with their clips. Use its claims as interview evidence when you place opportunities on your tree.

Ask real people your question

The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.

Start free