opportunity-solution-tree
# ClaudeWave Editor Description The Opportunity Solution Tree skill helps product teams structure discovery work by mapping a single desired outcome through customer opportunities, proposed solutions, and validation experiments. Use this when starting discovery cycles, prioritizing what to build, or connecting business metrics to customer problems without jumping prematurely to solution design.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/opportunity-solution-tree && cp -r /tmp/opportunity-solution-tree/pm-product-discovery/skills/opportunity-solution-tree ~/.claude/skills/opportunity-solution-treeSKILL.md
## 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):** 1. **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. 2. **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. 3. **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." 4. **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 **$ARGUMENTS**. ### 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 1. **Define the desired outcome** — Confirm or help articulate a single, measurable outcome at the top of the tree. 2. **Map opportunities** — From provided research, identify 3-7 customer opportunities (needs/pains). Group related opportunities. Frame each from the customer's perspective. 3. **Prioritize opportunities** — Use Opportunity Score or qualitative assessment to rank. Focus on the top 2-3. 4. **Generate solutions** — For each prioritized opportunity, brainstorm 3+ solutions from PM, Designer, and Engineer perspectives. 5. **Design experiments** — For the most promising solutions, suggest 1-2 fast experiments. Specify: hypothesis, method, metric, success threshold. 6. **Visualize the tree** — Present the full OST in a clear hierarchical format. Think step by step. Save as markdown if substantial. --- ### Further Reading - [The Extended Opportunity Solution Tree](https://www.productcompass.pm/p/the-extended-opportunity-solution-tree) - [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery) - [Product Trio: Beyond the Obvious](https://www.productcompass.pm/p/product-trio) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.