phuryn/pm-skills

opportunity-solution-tree

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/phuryn/pm-skills --skill opportunity-solution-tree

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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.
  1. 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.
  1. 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."
  1. Experiments (bottom) — Fast, cheap tests to validate whether a solution actually addresses the opportunity. Use assumption testing (Value, Usability, Viability, Feasibility risks). Prefer experiments with "skin-in-the-game" (Alberto Savoia) over opinion-based validation.

Key principles:

  • One outcome at a time. Don't try to solve everything. Focus the tree on a single desired outcome.
  • Opportunities, not features. "Never allow customers to design solutions. Prioritize opportunities (problems), not features."
  • Compare and contrast. Always generate at least 3 solutions per opportunity before choosing. Avoid the "first idea" trap.
  • Discovery is not linear. Loop back if experiments fail. Kill solutions that don't validate. Explore new branches.
  • Continuous, not periodic. Update the tree weekly as you learn from interviews, analytics, and experiments.

Instructions

You are helping a product team build an Opportunity Solution Tree for $ARGUMENTS.

Input Requirements

  • A desired outcome or business metric to improve
  • Customer research data (interviews, surveys, analytics, feedback)
  • Optionally: existing opportunities or solution ideas to organize

Process

  1. Define the desired outcome — Confirm or help articulate a single, measurable outcome at the top of the tree.
  1. Map opportunities — From provided research, identify 3-7 customer opportunities (needs/pains). Group related opportunities. Frame each from the customer's perspective.
  1. Prioritize opportunities — Use Opportunity Score or qualitative assessment to rank. Focus on the top 2-3.
  1. Generate solutions — For each prioritized opportunity, brainstorm 3+ solutions from PM, Designer, and Engineer perspectives.
  1. Design experiments — For the most promising solutions, suggest 1-2 fast experiments. Specify: hypothesis, method, metric, success threshold.
  1. Visualize the tree — Present the full OST in a clear hierarchical format.

Think step by step. Save as markdown if substantial.


Further Reading

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
phuryn
커뮤니티

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1시간 설치 수
4
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일