Our review
Build an Opportunity Solution Tree (OST) to structure product discovery by linking a desired outcome to customer opportunities, potential solutions, and validation experiments.
Strengths
- Clear visual framework connecting outcome, customer problems, and solutions
- Encourages generating multiple solutions before committing to one
- Grounds prioritization in user research data
- Supports continuous, iterative discovery rather than one-off planning
Limitations
- Requires solid user research to identify genuine opportunities
- Can become unwieldy if scope is too broad or branches too many
- Opportunity scoring may be subjective without reliable quantitative data
Use this tree when you need to structure product discovery around a single measurable outcome and avoid jumping to solutions prematurely.
Avoid using it when the product context is highly ambiguous or when no user research exists to feed the opportunity layer.
Security analysis
SafeThe skill provides a conceptual framework for product discovery with no executable code or tool usage, posing no security risk.
No concerns found
Examples
I want to build an Opportunity Solution Tree to improve 7-day retention in our mobile app. We have user interview transcripts, analytics showing drop-off points, and some survey data. Help me structure the tree with a desired outcome, opportunities, solutions, and experiments.Our team has conducted user interviews revealing friction during onboarding. Use the Opportunity Solution Tree framework to map out the opportunities, generate at least 3 solutions per top opportunity, and propose experiments to validate them.I have a list of feature requests and customer pain points from support tickets. Help me turn them into an Opportunity Solution Tree so we can prioritize by opportunity score and decide what to build next.name: opportunity-solution-tree description: "Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next."
Opportunity Solution Tree (OST)
A visual framework for structuring continuous product discovery. Connects a desired outcome to customer opportunities, possible solutions, and experiments to validate them.
Domain Context
The Opportunity Solution Tree (Teresa Torres, Continuous Discovery Habits) is the backbone of modern product discovery. It prevents teams from jumping to solutions by forcing them to first map the opportunity space.
Structure (4 levels):
-
Desired Outcome (top) — The measurable business or product outcome the team is pursuing. Should be a single, clear metric (e.g., "increase 7-day retention to 40%"). This comes from your OKRs or product strategy.
-
Opportunities (second level) — Customer needs, pain points, or desires discovered through research. These are problems worth solving — not features. Frame them from the customer's perspective: "I struggle to..." or "I wish I could..." Prioritize using Opportunity Score: Importance × (1 − Satisfaction) (Dan Olsen, The Lean Product Playbook). Normalize Importance and Satisfaction to 0–1.
-
Solutions (third level) — Possible ways to address each opportunity. Generate multiple solutions per opportunity — don't commit to the first idea. The Product Trio (PM + Designer + Engineer) should ideate together. "Best ideas often come from engineers."
-
Experiments (bottom) — Fast, cheap tests to validate whether a solution actually addresses the opportunity. Use assumption testing (Value, Usability, Viability, Feasibility risks). Prefer experiments with "skin-in-the-game" (Alberto Savoia) over opinion-based validation.
Key principles:
- One outcome at a time. Don't try to solve everything. Focus the tree on a single desired outcome.
- Opportunities, not features. "Never allow customers to design solutions. Prioritize opportunities (problems), not features."
- Compare and contrast. Always generate at least 3 solutions per opportunity before choosing. Avoid the "first idea" trap.
- Discovery is not linear. Loop back if experiments fail. Kill solutions that don't validate. Explore new branches.
- Continuous, not periodic. Update the tree weekly as you learn from interviews, analytics, and experiments.
Instructions
You are helping a product team build an Opportunity Solution Tree for the product or context the user provides.
Input Requirements
- A desired outcome or business metric to improve
- Customer research data (interviews, surveys, analytics, feedback)
- Optionally: existing opportunities or solution ideas to organize
Process
-
Define the desired outcome — Confirm or help articulate a single, measurable outcome at the top of the tree.
-
Map opportunities — From provided research, identify 3-7 customer opportunities (needs/pains). Group related opportunities. Frame each from the customer's perspective.
-
Prioritize opportunities — Use Opportunity Score or qualitative assessment to rank. Focus on the top 2-3.
-
Generate solutions — For each prioritized opportunity, brainstorm 3+ solutions from PM, Designer, and Engineer perspectives.
-
Design experiments — For the most promising solutions, suggest 1-2 fast experiments. Specify: hypothesis, method, metric, success threshold.
-
Visualize the tree — Present the full OST in a clear hierarchical format.
Think step by step. Save as markdown if substantial.
Further Reading
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.