Help us improve
Share bugs, ideas, or general feedback.
From pm-product-discovery
Builds Opportunity Solution Trees (OST) mapping outcomes to customer opportunities, solutions, and experiments. Guides continuous product discovery and prioritization.
npx claudepluginhub phuryn/pm-skills --plugin pm-product-discoveryHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-product-discovery:opportunity-solution-treeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A visual framework for structuring continuous product discovery. Connects a desired **outcome** to customer **opportunities**, possible **solutions**, and **experiments** to validate them.
Builds Opportunity Solution Trees (OST) for product discovery, mapping desired outcomes to customer opportunities, solutions, and experiments. Use to structure discovery work and prioritize builds.
Creates an opportunity solution tree mapping desired outcomes to opportunities and potential solutions. Use for outcome-driven product discovery, prioritization, or communicating product strategy.
Use this skill when the user asks about "opportunity solution tree", "OST", "Teresa Torres framework", "build my OST", "map opportunities to solutions", "how should we structure our discovery", "connect outcomes to opportunities", "continuous discovery framework", or wants to visually structure the relationship between outcomes, opportunities, and solutions. Also use this skill when a user has a list of ideas and wants to organize them against user outcomes.
Share bugs, ideas, or general feedback.
A visual framework for structuring continuous product discovery. Connects a desired outcome to customer opportunities, possible solutions, and experiments to validate them.
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:
You are helping a product team build an Opportunity Solution Tree for $ARGUMENTS.
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.