opportunity-solution-tree

Guide product managers through Opportunity Solution Tree discovery to create testable problem statements.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill opportunity-solution-tree-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunity-solution-tree
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/opportunity-solution-tree
Command: npx skills add https://github.com/ch-m-n/dotfile --skill opportunity-solution-tree-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague stakeholder asks into outcome-led discovery plans that prevent teams from jumping straight to feature ideas without understanding the problems worth solving.

Core Features & Use Cases

  • Structured OST facilitation: Extract desired outcomes, generate three opportunities with evidence, and map solutions with experiments to keep teams divergent before converging.
  • POC evaluation framework: Score feasibility, impact, and market fit to recommend a proof-of-concept that balances effort and learning.
  • Real-world use case: When a stakeholder requests a new feature, capture the context, opportunities, and experiments before drafting requirements.

Quick Start

Start by summarizing the stakeholder request and asking for an Opportunity Solution Tree mapping to define outcomes before exploring solutions.

Frequently Asked Questions about opportunity-solution-tree

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

FAQPage Schema
How do I turn vague stakeholder requests into testable product hypotheses?

Opportunity solution tree discovery transforms vague stakeholder requests into testable hypotheses by clarifying desired outcomes, exploring customer opportunities, and mapping parallel solutions before committing to build work.

What is an opportunity solution tree in product discovery?

An opportunity solution tree is a structured product discovery framework that maps desired outcomes to evidence-backed customer opportunities and parallel solutions, preventing teams from jumping straight to feature ideas without understanding the problem.

How do I evaluate proof-of-concept experiments for product features?

You evaluate proof-of-concept experiments by scoring feasibility, impact, and market fit for each mapped solution, which recommends a POC that balances development effort with learning value.

When should I use outcome-driven product discovery instead of building requested features?

Use outcome-driven product discovery during early phases when desired outcomes must be clarified and customer opportunities explored, ensuring teams evaluate parallel solutions before committing to build work.

How do I structure product strategy around outcome-driven development?

You structure outcome-driven product strategy by collecting stakeholder context, generating three evidence-backed opportunities, mapping three solutions per opportunity, and scoring each to select a proof-of-concept experiment.