/

/opportunity-solution-tree

by Dean Petersdeanpeters/product-manager-skills7.1k stars

851

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.

3 files
22.5 KB
Updated 2 months ago
GitHub
2 warnings

Ask your Agent

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/opportunity-solution-tree

This session only. Nothing lands on disk.

template.md

671 B raw

≈168 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Opportunity Solution Tree Template

Use this template to map outcomes, opportunities, solutions, and experiments.

Template

## Desired Outcome
- [Business or product metric to move]

## Opportunities (Problems to Solve)
1. [Opportunity 1]
2. [Opportunity 2]
3. [Opportunity 3]

## Solutions per Opportunity
**Opportunity 1 Solutions:**
- [Solution 1]
- [Solution 2]
- [Solution 3]

**Opportunity 2 Solutions:**
- [Solution 1]
- [Solution 2]
- [Solution 3]

## Experiments (per solution)
- [Experiment for Solution 1]
- [Experiment for Solution 2]

## POC Selection
- **Chosen solution:** [Solution]
- **Rationale:** [Feasibility, Impact, Market Fit]

Source: SKILL.md on GitHub

Third-party checks

2 warnings17d5 checks · Risk SAFE

Gen Agent Trust Hub17d
The skill is a framework for product discovery and Opportunity Solution Tree construction. It contains no executable code, network calls, or sensitive data access, and functions solely as an interactive text-based guide.
Socket17d
No alerts
Snyk17d
Risk: MEDIUM · 1 issue
Runlayer7mo
3/3 files flagged
ZeroLeaks5mo
Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at b68bf96. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 2 months ago

Capability

argument-hint: [stakeholder request or outcome]
type: interactive
theme: discovery-research

Other metadata

intent: Guide product managers through creating an Opportunity Solution Tree (OST) by extracting target outcomes from stakeholder requests, generating opportunity options (problems to solve), mapping potential solutions, and selecting the best proof-of-concept (POC) based on feasibility, impact, and market fit. Use this to move from vague product requests to structured discovery, ensuring teams solve the right problems before jumping to solutions—avoiding "feature factory" syndrome and premature convergence on ideas.
best_for: [ "Turning a stakeholder feature request back into a problem worth solving", "Connecting a desired outcome to opportunities, solutions, and tests", "Showing why one solution was chosen over the alternatives" ]
scenarios: [ "A stakeholder asked for a specific feature and I want to reframe it as a problem first", "I need to show leadership why we picked this solution over the three alternatives" ]
estimated_time: 30-45 min