opportunity-solution-tree
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.
Security Assessment
About opportunity-solution-tree
opportunity-solution-tree helps a product team build an Opportunity Solution Tree (OST), a visual framework from Teresa Torres' Continuous Discovery Habits for structuring product discovery. It solves a common failure mode — teams jumping straight to solutions — by forcing them to first map the opportunity space, connecting a single desired outcome to customer opportunities, candidate solutions, and experiments that validate them.
The skill structures the tree across four levels: a measurable desired outcome at the top (a single metric drawn from OKRs or strategy), customer opportunities framed as needs and pains rather than features, multiple solutions per opportunity generated by the Product Trio of PM, Designer, and Engineer, and fast, cheap experiments at the bottom to test assumptions across value, usability, viability, and feasibility risks. It prioritizes opportunities using the Opportunity Score, Importance × (1 − Satisfaction), and enforces key principles: focus on one outcome at a time, prioritize problems over features, generate at least three solutions before choosing to avoid the first-idea trap, loop back when experiments fail, and update the tree continuously as new learning arrives. Its process walks from defining and confirming the outcome, through mapping and prioritizing 3–7 opportunities, generating solutions, and designing 1–2 experiments per promising solution (each with a hypothesis, method, metric, and success threshold), to visualizing the full tree in a hierarchical format and optionally saving it as markdown.
The skill targets product managers, designers, and engineers doing continuous discovery who need to organize research into a coherent, prioritized map of what to build next. It works best when a desired outcome and customer research (interviews, surveys, analytics, feedback) are available, and it can also organize existing opportunities or solution ideas.
FAQ
What framework is this skill based on?
It is based on the Opportunity Solution Tree from Teresa Torres' Continuous Discovery Habits, structuring discovery as outcome → opportunities → solutions → experiments.
What inputs does it need?
A desired outcome or business metric to improve, and customer research data such as interviews, surveys, analytics, or feedback. Optionally, existing opportunities or solution ideas to organize.
How are opportunities prioritized?
Using the Opportunity Score, calculated as Importance × (1 − Satisfaction) with both normalized to 0–1, or a qualitative assessment, focusing the tree on the top 2–3 opportunities.
Why does it insist on multiple solutions per opportunity?
To avoid the 'first idea' trap. The skill has the Product Trio generate at least three solutions per opportunity before choosing, comparing and contrasting them rather than committing to the first idea.
What does an experiment specification include?
Each experiment specifies a hypothesis, method, metric, and success threshold, favoring fast, cheap, skin-in-the-game tests over opinion-based validation.
Install opportunity-solution-tree
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
phuryn/pm-skills