Method guideProduct Discovery

Opportunity Solution Tree

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time1-2 h Setup, laufend

Participants2-6

FormatWorkshop + async

MaturityEstablished

Plan the discovery rhythm

Prerequisite

What needs to be finished first

Complete firstClear outcome

A desired product outcome is defined and has an observable signal.

Without an outcome, opportunity selection becomes arbitrary.

Complete firstCustomer learning

Story-based interviews or observations support opportunity mapping; Product Talk recommends 3–4 interviews before a first tree.

Without customer evidence, team opinions can be mistaken for needs.

Preparation

What needs to be ready before start

Materials

Outcome definition, sourced research notes, opportunity clusters, a shared tree and space for solution hypotheses and experiment cards.

People / roles

A product trio or cross-functional team with product, design/research and engineering; discovery ownership keeps the tree and evidence current.

Pre-read

Gather the outcome, target user and current product or customer evidence. Separate customer statements from interpretation.

Time needed

Not a one-off workshop. Allow about 1–2 hours to frame the first tree; interviews, tests and updates continue across discovery cycles.

Setup

Place the outcome above opportunities, solutions under the selected opportunity and experiments against solution assumptions. Deepen one target opportunity at a time.

Core question

The one question this method answers

Which evidence-grounded paths can achieve the desired outcome through customer needs and tested solutions?

Flow

Phases with goal, actions, output and pitfall

The Opportunity Solution Tree visualizes possible paths to a desired result: outcome, customer opportunities, solutions and tests of their assumptions. The map evolves with new evidence.

Opportunity Solution Tree

Fictional teaching example

The tree levels are outcome, customer opportunities, solution options and tests of critical assumptions. The tree shows hypotheses and learning paths, not a project plan.

Outcome

Which team-controllable result should improve?

Fictional outcome: increase completed loans as a share of all reservation requests in the pilot area from 20% to 35% over eight weeks. All figures are invented.

Customer opportunities

Which needs, pain points or desires from concrete customer situations could influence the outcome?

Fictional research hypothesis: uncertainty about availability complicates planning. No customer evidence yet.

Target opportunity

Which opportunity will guide the next discovery cycle, and why?

Fictional choice: clarity about reservation status because it precedes the planned loan.

Solution options

What different approaches could address this opportunity?

Fictional: firm reservation confirmation · callback · self-service status.

Assumptions and tests

Which risky assumption will each test examine, and what decision follows?

Fictional: a prototype test checks whether people understand the status; real user sessions are still needed.

All entries are fictional. Opportunities should come from discovery; team knowledge alone is not customer evidence.

Source: Teresa Torres, Product Talk

1
Outcome
Define a team-controllable outcome
Goal
The team knows which result it is trying to influence.
Inputs for this step
- Product strategy and target user
- Available metric or observable behavior indicator
Actions
- Phrase the outcome as a result or user behavior, not a feature delivery.
- Clarify its signal, target group and time horizon where evidence allows.
- Mark dependencies outside the team’s influence.
Output
Outcome as the root of the tree
Outcome · target user · signal
Quality check
Can the team influence the outcome through product decisions?
Pitfall
A feature or business metric sits at the top without a link to user behavior. Choose a product outcome within the team’s influence and explain its link to the business goal.
Timing: About 30 minutes.
2
Opportunities
Structure customer opportunities
Goal
The opportunity structure is grounded in customer learning and stays solution-free.
Inputs for this step
- Story-based customer interviews or observations
- Outcome and existing opportunity notes
Actions
- Synthesize concrete situations from interviews and observations.
- Cluster related needs and discuss relationships in the opportunity space.
- Attach sources and mark open interpretations.
Output
Customer opportunities with evidence
Need or obstacle · source · open question
Quality check
Is each opportunity grounded in customer learning? Does it still hide a solution?
Pitfall
Team members invent opportunities during the workshop. Add story-based research; treat support, sales or product data as clues and examine them in customer context.
Timing: Update regularly from new discovery work.
3
Focus
Choose a target opportunity
Goal
Solutions address one clear customer need.
Inputs for this step
- Outcome
- Opportunity map and related customer notes
Actions
- Discuss opportunities in light of user relevance, outcome signal and evidence.
- Select one target opportunity, including assumptions and counterevidence gaps.
- Record the reasoning without inventing precise numeric scores.
Output
Selected target opportunity with rationale
Opportunity · evidence · rationale
Quality check
Is the opportunity relevant and understood well enough to explore ideas?
Pitfall
The team jumps from the outcome to its favorite solution. Complete the opportunity layer before discussing solutions and record the rationale.
Timing: About 20 minutes per selection round.
4
Solutions
Explore multiple solution paths
Goal
Different approaches can be compared and tested for risk.
Inputs for this step
- Target opportunity and outcome signal
- Product, design and technical perspectives
Actions
- Generate different solution approaches before elaborating one.
- Connect each solution visibly to the opportunity.
- Record critical assumptions for promising options.
Output
Solution options with assumptions
Option · opportunity addressed · key assumption
Quality check
Are there different ways to address the opportunity?
Pitfall
A single concept is presented as already selected. Explore multiple credible options and deliberately select which ones to test.
Timing: About 30 minutes, depending on scope.
5
Learn
Test assumptions and update the tree
Goal
Learning leads to a justified next decision.
Inputs for this step
- Solution options and explicit assumptions
- Access to suitable users or data
Actions
- Identify the riskiest assumptions for each serious option.
- Design a suitable, low-cost test with an expected observation and decision threshold.
- Record observations and refine or discard the solution, or change the target opportunity.
Output
Updated tree with tests and decisions
Assumption · test · evidence · decision
Quality check
Does the test examine an important solution assumption? Is the next decision stated before the test?
Pitfall
Experiment count is confused with risk reduction. Document learning and remaining uncertainty; count a test as progress only when it informs a relevant decision.
Timing: Ongoing across discovery cycles.

Artifact

What comes out at the end

Sketch: what the artifact looks like

Opportunity Solution Tree · Outcome to ExperimentOutcome, opportunities, solutions, and experiments as a traceable discovery decision chain

Increase activation

Onboarding is unclear

Value is experienced late

Guided Tour

Prototype Test

A/B Test

Setup Checklist

Fake Door

Cohort Review

Quick Win Flow

Concierge Test

Time-to-Value

Sample Data

Wizard Test

Usage Signal

Form

A versioned discovery tree with outcome, linked sources, opportunity structure, target selection, solution options, assumption tests, findings and follow-up decisions.

Versioning / ownership

Date the outcome and tree version. Log opportunity sources, changed branches, tests and decisions. Do not treat workshop cards as established customer evidence.

Tool alternatives

Digital whiteboard or branching document
Interview notes with stable source references
Test cards with assumption, evidence need, method and decision signal

opportunity-solution-tree-outline.md

Plan the initial setup and ongoing rhythm for outcomes, opportunities, solutions and tests.

Opportunity Solution Tree: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Structure continuous discovery Time: Ongoing practice; no total timebox

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Outcome definition, sourced research notes, opportunity clusters, a shared tree and space for solution hypotheses and experiment cards.
Roles: A product trio or cross-functional team with product, design/research and engineering; discovery ownership keeps the tree and evidence current.
Advance information: Gather the outcome, target user and current product or customer evidence. Separate customer statements from interpretation.
Overall time needed: Not a one-off workshop. Allow about 1–2 hours to frame the first tree; interviews, tests and updates continue across discovery cycles.
Setup: Place the outcome above opportunities, solutions under the selected opportunity and experiments against solution assumptions. Deepen one target opportunity at a time.

Prepare for the work steps

Outcome: Define a team-controllable outcome

Product strategy and target user
Available metric or observable behavior indicator

Opportunities: Structure customer opportunities

Story-based customer interviews or observations
Outcome and existing opportunity notes

Focus: Choose a target opportunity

Outcome
Opportunity map and related customer notes

Solutions: Explore multiple solution paths

Target opportunity and outcome signal
Product, design and technical perspectives

Learn: Test assumptions and update the tree

Solution options and explicit assumptions
Access to suitable users or data

Opportunity Solution Tree

Outcome

Which team-controllable result should improve?

...

Customer opportunities

Which needs, pain points or desires from concrete customer situations could influence the outcome?

...

Target opportunity

Which opportunity will guide the next discovery cycle, and why?

...

Solution options

What different approaches could address this opportunity?

...

Assumptions and tests

Which risky assumption will each test examine, and what decision follows?

...

Blank worksheet: choose one outcome, connect opportunities to evidence, select a target opportunity, then record solution hypotheses and tests.

Source: Teresa Torres, Product Talk

Outcome: Define a team-controllable outcome

Expected artifact: Outcome as the root of the tree

Outcome · target user · signal

Entry:

...

Can the team influence the outcome through product decisions?

Opportunities: Structure customer opportunities

Expected artifact: Customer opportunities with evidence

Need or obstacle · source · open question

Entry:

...

Is each opportunity grounded in customer learning?
Does it still hide a solution?

Focus: Choose a target opportunity

Expected artifact: Selected target opportunity with rationale

Opportunity · evidence · rationale

Entry:

...

Is the opportunity relevant and understood well enough to explore ideas?

Solutions: Explore multiple solution paths

Expected artifact: Solution options with assumptions

Option · opportunity addressed · key assumption

Entry:

...

Are there different ways to address the opportunity?

Learn: Test assumptions and update the tree

Expected artifact: Updated tree with tests and decisions

Assumption · test · evidence · decision

Entry:

...

Does the test examine an important solution assumption?
Is the next decision stated before the test?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/opportunity-solution-tree/run-sheet

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

opportunity-solution-tree-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Improve completed tool loans

All people, figures and findings are invented. No interviews or product tests took place.

Outcome: Increase completed loans as a share of all reservation requests in the pilot area from 20% to 35% over eight weeks. The baseline, target and timeframe are fictional.

Opportunity hypotheses: Availability is unclear before travel; return requirements may become visible too late. Both need real customer evidence.

Target opportunity for one learning cycle: Clarity about reservation status.

Solutions: Firm confirmation, callback or status view.

Risky assumption: A digital status view actually reduces uncertainty.

Predeclared prototype signal: In eight moderated sessions, at least six of eight relevant participants can identify reservation status correctly and name the next booking action without help. This tests prototype comprehension, not real demand or the eight-week outcome.

Decision: If the signal is met, prepare a bounded pilot; otherwise revisit the status design and opportunity. The signal is fictional and has not been collected.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Define a team-controllable outcomeA feature or business metric sits at the top without a link to user behavior.View in phase
Structure customer opportunitiesTeam members invent opportunities during the workshop.View in phase
Choose a target opportunityThe team jumps from the outcome to its favorite solution.View in phase
Explore multiple solution pathsA single concept is presented as already selected.View in phase
Test assumptions and update the treeExperiment count is confused with risk reduction.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

No team-controllable outcome: clarify it before building the tree.

Opportunity branches come only from brainstorming: add interviews or other direct customer evidence.

Solution generation spreads across the entire tree: focus on one target opportunity.

Tests generate activity without a decision: record the assumption, expected signal and possible decision beforehand.

Where to go next?

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.

Product Discovery

Assumption Mapping

Breaks the riskiest assumption of a solution option into a test plan.

Product Discovery

Riskiest Assumption Test

Tests the identified assumption with the cheapest fitting test.

View in playbookStart Product DiscoveryMove from a vague product idea to a clear target group, problem hypotheses, and first learning steps.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods