opportunity-solution-tree

Guide users through creating an Opportunity Solution Tree connecting outcomes, problems, and solutions.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Johnnnmai/100x-product-manager --skill opportunity-solution-tree-johnnnmai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunity-solution-tree
Source: https://github.com/Johnnnmai/100x-product-manager/tree/main/skills/opportunity-solution-tree
Command: npx skills add https://github.com/Johnnnmai/100x-product-manager --skill opportunity-solution-tree-johnnnmai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill guides product managers through the process of identifying and validating product opportunities by systematically mapping customer problems to potential solutions and defining experiments to test them, preventing the "feature factory" anti-pattern.

Core Features & Use Cases

  • Outcome Definition: Helps clarify and define measurable business outcomes.
  • Opportunity Generation: Facilitates brainstorming and selection of customer problems to solve.
  • Solution Mapping: Generates potential solutions for identified opportunities.
  • POC Selection: Evaluates solutions based on feasibility, impact, and market fit to recommend a Proof-of-Concept.
  • Experiment Design: Assists in defining clear hypotheses and experiment plans for validation.
  • Use Case: A product manager receives a vague feature request. They use this Skill to define the underlying desired outcome, explore multiple customer problems that could drive that outcome, brainstorm solutions for the most critical problem, and then select the best solution to test with a small experiment.

Quick Start

Use the opportunity-solution-tree skill to start building an Opportunity Solution Tree for a new product initiative.

Frequently Asked Questions about opportunity-solution-tree

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

FAQPage Schema
What is an opportunity solution tree and when should I use it for product discovery?

An opportunity solution tree maps desired business outcomes to customer problems, potential solutions, and experiments. Use it during product discovery to prevent the feature factory anti-pattern by systematically validating opportunities before committing to development.

How do I map customer problems to potential solutions for a vague feature request?

Start by defining the underlying desired outcome, then generate multiple opportunity options representing customer problems. Brainstorm solutions for the most critical problem, and evaluate them based on feasibility, impact, and market fit to select a proof-of-concept.

How do I design experiments to validate product strategy and test potential solutions?

Design experiments by defining clear hypotheses and creating experiment plans that test your selected proof-of-concept. This iterative learning approach validates whether your mapped solutions effectively address customer problems and drive your target outcomes.

What's the best way to select a proof-of-concept from multiple generated product solutions?

Select a proof-of-concept by evaluating each potential solution against three criteria: feasibility, impact, and market fit. This structured evaluation ensures you test the solution most likely to validate your product strategy and solve the identified customer problem.

Can I use this opportunity solution tree approach for iterative product discovery and validation?

Yes, the opportunity solution tree supports iterative learning through defined experiments. You can continuously refine your product discovery by testing hypotheses, validating solutions, and adjusting your approach based on experimental outcomes and customer feedback.

Why does my product team fall into the feature factory anti-pattern and how can structured discovery prevent it?

The feature factory anti-pattern occurs when teams build features without validating underlying problems. Structured product discovery prevents this by mapping outcomes to opportunities, forcing teams to identify customer problems and test solutions before development.