opportunity-solution-tree

Solid

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.

Web & Frontend 11,809 stars 1394 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

## 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....

Details

Author
phuryn
Repository
phuryn/pm-skills
Created
3 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

opportunity-solution-tree

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

4,665 Updated 1 weeks ago
deanpeters
AI & Automation Listed

opportunity-solution-tree

Builds an Opportunity Solution Tree (OST) - desired outcome at the top, prioritized opportunities, candidate solutions, and assumption tests that connect discovery work to a measurable business outcome. Use when planning continuous product discovery, deciding what to research next, structuring quarterly discovery work, or aligning a product trio (product manager / designer / engineer) on what to test.

1 Updated today
varunk130
AI & Automation Listed

opportunity-mapping

Map opportunities using Teresa Torres' Opportunity Solution Trees. Use when asked to identify opportunities, find product gaps, explore new areas, map the solution space, or connect business outcomes to customer needs and testable solutions.

2 Updated today
AashutoshR2062
Testing & QA Listed

continuous-discovery-habits

Product discovery framework based on Teresa Torres' "Continuous Discovery Habits". Use this skill whenever the user is doing product discovery work — even if they do not explicitly say "OST," "Teresa Torres," or "discovery." Triggers include: (1) building, critiquing, or restructuring an opportunity solution tree, (2) identifying, organizing, or prioritizing customer opportunities, (3) designing assumption tests before committing to a feature, (4) writing or critiquing interview snapshots from customer conversations, (5) generating multiple solution candidates for an opportunity (especially with How Might We), (6) mapping a current-state customer experience or journey to surface unmet needs, (7) diagnosing why a product team is shipping without moving outcomes, (8) running a discovery pre-mortem before committing to a solution branch, (9) building or strengthening a weekly customer-interview habit, (10) connecting business outcomes to product outcomes to opportunities to solutions in a single coherent tree.

0 Updated 3 days ago
tomaszstaniak
Testing & QA Solid

continuous-discovery

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

1,169 Updated 2 weeks ago
wondelai