opportunity-solution-tree

Build an Opportunity Solution Tree mapping outcomes to opportunities, solutions, and experiments.

5|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tarunccet/pm-skills --skill opportunity-solution-tree-tarunccet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunity-solution-tree
Source: https://github.com/tarunccet/pm-skills/tree/main/pm-product-discovery/skills/opportunity-solution-tree
Command: npx skills add https://github.com/tarunccet/pm-skills --skill opportunity-solution-tree-tarunccet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Opportunity Solution Tree helps teams avoid premature solutions by structuring product discovery around a single measurable outcome, surfacing customer opportunities, generating multiple solutions, and designing fast experiments to validate them.

Core Features & Use Cases

  • Outcome framing: Clarifies a single measurable objective (e.g., increase 7-day retention to 40%) that guides discovery work.
  • Opportunity mapping & prioritization: Extracts customer needs from research and ranks them using Opportunity Score or qualitative assessment.
  • Solution ideation & experiment design: Generates multiple solution approaches per opportunity and prescribes fast, cheap experiments (hypothesis, method, metric, threshold) to validate assumptions.
  • Use Case: Use when prioritizing roadmap choices, preparing discovery sprints, or converting interview transcripts into testable experiments.

Quick Start

Create an Opportunity Solution Tree for a single measurable outcome using the product description and any available customer research so I can prioritize opportunities, propose solutions, and design experiments.

Frequently Asked Questions about opportunity-solution-tree

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure product discovery around a measurable outcome?

Structure product discovery around a measurable outcome by mapping a desired objective to customer opportunities, multiple solution ideas, and validation experiments using an Opportunity Solution Tree. This prevents premature solutions by aligning discovery work directly with your target metric.

How do I convert customer research transcripts into testable experiments?

Convert customer research transcripts into testable experiments by extracting customer needs, prioritizing them as opportunities, generating solution options, and designing fast validation tests. The tree structure connects each interview insight directly to an experiment plan with hypotheses and metrics.

What is the best way to prioritize customer problems during continuous discovery?

The best way to prioritize customer problems during continuous discovery is to map them beneath a single desired outcome and rank them using an Opportunity Score or qualitative assessment. This ensures your team addresses the most impactful needs before brainstorming solutions.

Do I need a specific desired outcome to start opportunity mapping?

Yes, opportunity mapping requires a single measurable desired outcome, such as increasing 7-day retention to 40%, along with customer research inputs. Without a clear measurable objective and research data, the tree cannot effectively prioritize opportunities or propose validated solutions.

How does solution ideation work when building an Opportunity Solution Tree?

Solution ideation works by generating multiple distinct solution approaches for each prioritized customer opportunity. Each solution is then paired with a fast, cheap experiment that defines the hypothesis, testing method, target metric, and success threshold to validate assumptions before development.

When should I avoid using an Opportunity Solution Tree for product discovery?

You should avoid using an Opportunity Solution Tree when you lack a measurable desired outcome or sufficient customer research inputs, as the method depends on these to extract and prioritize opportunities. It is also less effective for teams seeking a single immediate fix rather than structured discovery.