How to Map Opportunity Solution Trees: A 4-Step Tutorial for User-Centric Product Discovery
Created by product discovery expert Teresa Torres, the Opportunity Solution Tree (OST) is a visual framework that structures product discovery. It ensures your team explores multiple paths to reach an outcome, preventing premature commitments to unverified solutions.
Follow this step-by-step tutorial to map your first Opportunity Solution Tree.
Step 1: Define One Clear Target Outcome
Start at the very top of your tree with a single, measurable metric you need to impact over the next quarter or sprint cycle.
Bad Goal: "Build a better onboarding flow" (This is a solution, not an outcome).
Clear Outcome: "Increase 7-day active user retention from 25% to 35%."
Rule: Focus on one primary business or user engagement outcome per tree to maintain team alignment.
Step 2: Uncover User Opportunities (Not Solution Demands)
Branching down from your outcome, list Opportunities—the specific user needs, pain points, or desires that, if addressed, will drive your target outcome.
How to gather them: Extract opportunities directly from qualitative customer interviews, session recordings, and support tickets.
Example Opportunity: "I don't understand how to set up my workspace during initial signup."
Rule: Frame opportunities from the user's perspective, avoiding any mention of UI elements or features.
Step 3: Ideate Multiple Solutions for Each Opportunity
Branching down from each opportunity, brainstorm 3–5 distinct Solutions.
Why multiple solutions matter: Generating multiple ideas prevents "confirmation bias"—the trap of falling in love with your first idea and forcing it to work.
Example Solutions for the signup pain point:
A guided 3-step interactive onboarding wizard.
A pre-populated workspace template tailored by industry.
A 60-second video walkthrough embedded in the dashboard.
Step 4: Define and Test Hidden Assumptions
At the bottom of the tree, break down each candidate solution into testable Assumptions (Desirability, Usability, Feasibility, Viability).
Example Assumption: "Users prefer interactive setups over static video tutorials."
Action: Design low-cost experiments (clickable prototypes, fake-door tests, or 5-second usability tests) to validate assumptions before committing engineering resources to full production builds.
Key Takeaways
Connect Discovery to Strategy: OSTs ensure every feature idea directly traces back to an overarching business metric.
Focus on Problems First: Mapping opportunities derived from real user research keeps product teams grounded in user needs rather than internal opinions.
De-Risk with Experiments: Testing underlying assumptions at the bottom of the tree saves sprint capacity by filtering out weak solutions early.
CTA
Ready to structure your team's product discovery process? Join Product, UX & Design to download customizable OST templates, review real-world discovery case studies, and refine your UX strategy with seasoned product leaders.
Created by product discovery expert Teresa Torres, the Opportunity Solution Tree (OST) is a visual framework that structures product discovery. It ensures your team explores multiple paths to reach an outcome, preventing premature commitments to unverified solutions.
Follow this step-by-step tutorial to map your first Opportunity Solution Tree.
Step 1: Define One Clear Target Outcome
Start at the very top of your tree with a single, measurable metric you need to impact over the next quarter or sprint cycle.
Bad Goal: "Build a better onboarding flow" (This is a solution, not an outcome).
Clear Outcome: "Increase 7-day active user retention from 25% to 35%."
Rule: Focus on one primary business or user engagement outcome per tree to maintain team alignment.
Step 2: Uncover User Opportunities (Not Solution Demands)
Branching down from your outcome, list Opportunities—the specific user needs, pain points, or desires that, if addressed, will drive your target outcome.
How to gather them: Extract opportunities directly from qualitative customer interviews, session recordings, and support tickets.
Example Opportunity: "I don't understand how to set up my workspace during initial signup."
Rule: Frame opportunities from the user's perspective, avoiding any mention of UI elements or features.
Step 3: Ideate Multiple Solutions for Each Opportunity
Branching down from each opportunity, brainstorm 3–5 distinct Solutions.
Why multiple solutions matter: Generating multiple ideas prevents "confirmation bias"—the trap of falling in love with your first idea and forcing it to work.
Example Solutions for the signup pain point:
A guided 3-step interactive onboarding wizard.
A pre-populated workspace template tailored by industry.
A 60-second video walkthrough embedded in the dashboard.
Step 4: Define and Test Hidden Assumptions
At the bottom of the tree, break down each candidate solution into testable Assumptions (Desirability, Usability, Feasibility, Viability).
Example Assumption: "Users prefer interactive setups over static video tutorials."
Action: Design low-cost experiments (clickable prototypes, fake-door tests, or 5-second usability tests) to validate assumptions before committing engineering resources to full production builds.
Key Takeaways
Connect Discovery to Strategy: OSTs ensure every feature idea directly traces back to an overarching business metric.
Focus on Problems First: Mapping opportunities derived from real user research keeps product teams grounded in user needs rather than internal opinions.
De-Risk with Experiments: Testing underlying assumptions at the bottom of the tree saves sprint capacity by filtering out weak solutions early.
CTA
Ready to structure your team's product discovery process? Join Product, UX & Design to download customizable OST templates, review real-world discovery case studies, and refine your UX strategy with seasoned product leaders.
How to Map Opportunity Solution Trees: A 4-Step Tutorial for User-Centric Product Discovery
Created by product discovery expert Teresa Torres, the Opportunity Solution Tree (OST) is a visual framework that structures product discovery. It ensures your team explores multiple paths to reach an outcome, preventing premature commitments to unverified solutions.
Follow this step-by-step tutorial to map your first Opportunity Solution Tree.
Step 1: Define One Clear Target Outcome
Start at the very top of your tree with a single, measurable metric you need to impact over the next quarter or sprint cycle.
Bad Goal: "Build a better onboarding flow" (This is a solution, not an outcome).
Clear Outcome: "Increase 7-day active user retention from 25% to 35%."
Rule: Focus on one primary business or user engagement outcome per tree to maintain team alignment.
Step 2: Uncover User Opportunities (Not Solution Demands)
Branching down from your outcome, list Opportunities—the specific user needs, pain points, or desires that, if addressed, will drive your target outcome.
How to gather them: Extract opportunities directly from qualitative customer interviews, session recordings, and support tickets.
Example Opportunity: "I don't understand how to set up my workspace during initial signup."
Rule: Frame opportunities from the user's perspective, avoiding any mention of UI elements or features.
Step 3: Ideate Multiple Solutions for Each Opportunity
Branching down from each opportunity, brainstorm 3–5 distinct Solutions.
Why multiple solutions matter: Generating multiple ideas prevents "confirmation bias"—the trap of falling in love with your first idea and forcing it to work.
Example Solutions for the signup pain point:
A guided 3-step interactive onboarding wizard.
A pre-populated workspace template tailored by industry.
A 60-second video walkthrough embedded in the dashboard.
Step 4: Define and Test Hidden Assumptions
At the bottom of the tree, break down each candidate solution into testable Assumptions (Desirability, Usability, Feasibility, Viability).
Example Assumption: "Users prefer interactive setups over static video tutorials."
Action: Design low-cost experiments (clickable prototypes, fake-door tests, or 5-second usability tests) to validate assumptions before committing engineering resources to full production builds.
Key Takeaways
Connect Discovery to Strategy: OSTs ensure every feature idea directly traces back to an overarching business metric.
Focus on Problems First: Mapping opportunities derived from real user research keeps product teams grounded in user needs rather than internal opinions.
De-Risk with Experiments: Testing underlying assumptions at the bottom of the tree saves sprint capacity by filtering out weak solutions early.
CTA
Ready to structure your team's product discovery process? Join Product, UX & Design to download customizable OST templates, review real-world discovery case studies, and refine your UX strategy with seasoned product leaders.
Arabic
French
Spanish
Portuguese
Deutsch
Turkish
Dutch
Italiano
Russian
Romaian
Portuguese (Brazil)
Greek