opportunity-solution-trees
Opportunity Solution Trees
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 you're 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. Frame them from the customer's perspective: "I struggle to..." or "I wish I could..." Prioritize using Opportunity Score: Importance × (1 − Satisfaction) (Dan Olsen).
-
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.
-
Experiments (bottom) — Fast, cheap tests to validate whether a solution addresses the opportunity. Use assumption testing (Value, Usability, Viability, Feasibility).
More from pmprompt/claude-plugin-product-management
prd-writer
Generate comprehensive product requirements documents. Use when starting a new feature or product initiative and need structured documentation.
530feature-prioritization-assistant
Calculate RICE scores and prioritize features systematically. Use when building your product roadmap and need to make data-driven prioritization decisions.
272thinking-in-bets
Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions.
237product-led-growth
Use when asked about "product-led growth", "PLG strategy", "self-serve growth", "freemium model", "free trial design", "product-led sales", "PQL", or "bottoms-up growth". Helps design and optimize product-led growth motions where the product drives acquisition, activation, and monetization. Based on frameworks from Elena Verna and Hila Qu.
216user-feedback-synthesizer
Analyze collections of user feedback to identify patterns and themes. Use when you have user feedback from multiple sources that needs synthesis.
209shape-up
Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable scope, and collaborative shaping to ship meaningful work predictably.
198