An opportunity solution tree (OST) is a visual framework that connects a desired outcome to the opportunities (customer needs) that drive it, the solutions that address each opportunity, and the experiments that validate each solution. It prevents teams from jumping straight from a business goal to a feature list without understanding the customer problems in between.
The Four Levels
Level 1: Desired outcome. The business or product metric you are trying to move. "Increase 30-day retention from 45% to 60%." This comes from your product strategy. Only one outcome per tree.
Level 2: Opportunities. The customer needs, pain points, or desires that, if addressed, would move the outcome. "Users cannot find relevant content in the first session." "Users do not understand the value until week 2." These come from customer research, not brainstorming.
Level 3: Solutions. Specific product ideas that address each opportunity. Each opportunity can have multiple solution candidates. "Personalized onboarding flow," "curated content feed based on role," "guided product tour." These come from ideation.
Level 4: Experiments. Tests that validate whether each solution will work. "Painted door test for personalized onboarding," "A/B test of curated vs chronological feed." These come from your validation plan.
Build your tree visually using the OST Builder to map the connections between each level.
Why It Works
The OST solves two common product team failures:
Feature-first thinking. Without an OST, teams brainstorm features disconnected from customer needs. The tree forces you to identify the opportunity (customer problem) before proposing solutions.
Opinion-based prioritization. With all opportunities and solutions visible on one tree, you can compare options objectively. Use RICE scoring on the solution level to rank candidates within each opportunity branch.
Building the Tree
Start with the outcome. Get alignment from your leadership team on which metric to target.
Map opportunities from research. Review your user interview notes, support tickets, NPS feedback, and usage data. Each distinct customer need or pain point becomes an opportunity node. The user persona builder helps organize research findings by persona.
Generate solutions per opportunity. Brainstorm 3-5 solution ideas for each top opportunity. Do not evaluate yet. Quantity matters more than quality at this stage.
Design experiments per solution. For each top solution candidate, define the cheapest test that would validate demand or feasibility. Painted door tests, prototype tests, and surveys all work. The assumption mapper helps identify which assumptions each experiment should test.
Common Mistakes
Too many opportunities. If your tree has 20+ opportunities, you have not prioritized. Identify the top 3-5 opportunities that most directly affect the outcome. Park the rest.
Jumping to solutions. If your tree has 2 opportunities and 15 solutions, you spent too little time on research and too much on ideation. Go back to customer interviews.
No experiments. Solutions without experiments are just opinions. Every solution on the tree should have at least one experiment attached before it enters the development backlog.
The prioritization guide explains how OSTs fit into the broader prioritization workflow.