首頁
opportunity-solution-tree
phuryn/pm-skills
建立「機會解決方案樹」（OST）以系統化地進行產品探索——將預期成果與機會、解決方案及實驗相互對應。
...展開全部機會解決方案樹（OST）
一個用於架構持續產品探索的視覺化框架。將預期成果與客戶機會、可能的解決方案，以及用於驗證這些方案的實驗相互連結。
領域背景
「機會解決方案樹」（Teresa Torres，《持續探索習慣》）是現代產品探索的支柱。它透過強制團隊先繪製機會空間地圖，避免團隊倉促跳到解決方案。
結構（4 個層級）：
預期成果（頂層）— 團隊所追求的可量化商業或產品成果。應為單一且明確的指標（例如：「將 7 天留存率提升至 40%」）。此指標源自您的 OKR 或產品策略。
機會（第二層）—— 透過研究發現的客戶需求、痛點或渴望。這些是值得解決的問題——而非功能。 請從客戶角度來表述：「我難以……」或「我希望能夠……」使用「機會分數」進行優先級排序：重要性 × (1 − 滿意度)（Dan Olsen，《精實產品手冊》）。將重要性和滿意度標準化為 0–1 範圍。
解決方案（第三層）—— 針對每個機會的可能處理方式。每個機會應產生多種解決方案——不要只鎖定第一個想法。產品三人組（產品經理 + 設計師 + 工程師）應共同發想。「最好的點子往往來自工程師。」
實驗（最底層）—— 透過快速、低成本的測試，驗證解決方案是否真正解決了該機會。採用假設驗證（價值、可用性、可行性、可實施性風險）。相較於基於主觀意見的驗證，應優先選擇具有「利益相關」（Alberto Savoia）的實驗。
關鍵原則：
- 一次只專注於一個成果。不要試圖解決所有問題。讓決策樹聚焦於單一期望成果。
- 機會，而非功能。「絕不讓客戶來設計解決方案。應優先處理機會（問題），而非功能。」
- 比較與對照。在做出選擇前，務必針對每個機會至少提出 3 種解決方案。避免陷入「第一個想法」的陷阱。
- 探索過程並非線性。若實驗失敗，請回溯檢討。淘汰未經驗證的解決方案，並探索新的分支。
- 持續進行，而非定期更新。根據訪談、分析與實驗的成果，每週更新決策樹。
操作指引
您正在協助一個產品團隊為$ARGUMENTS 建立「機會解決方案樹」。
輸入要求
- 期望達成的成果或需改善的商業指標
- 客戶研究資料（訪談、問卷調查、分析數據、回饋意見）
- （可選）：需整理的現有機遇或解決方案構想
流程
定義期望成果— 確認或協助闡明樹狀圖頂端單一且可量化的成果。
梳理機會— 根據提供的研究資料，識別 3 至 7 項客戶機會（需求／痛點）。將相關機會進行分組。並從客戶視角闡述每項機會。
機會優先級排序— 運用「機會評分」或定性評估進行排序。重點聚焦於前 2 至 3 項。
構思解決方案— 針對每個優先級最高的機會，分別從產品經理、設計師和工程師的角度腦力激盪出 3 種以上的解決方案。
設計實驗— 針對最具潛力的解決方案，提出 1 至 2 項快速實驗。需明確指定：假設、方法、指標及成功門檻。
視覺化呈現樹狀圖— 以清晰的分層格式呈現完整的 OST。
循序漸進地思考。若內容充實，請儲存為 Markdown 格式。
延伸閱讀
- 擴展版機會解決方案樹
- 什麼是產品探索？終極分步指南
- 產品三要素：超越顯而易見之處
- 持續產品探索大師班 (CPDM)（影片課程）
---
name: opportunity-solution-tree
description: Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.
---
## 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.
2. **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.
3. **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."
4. **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.
2. **Map opportunities** — From provided research, identify 3-7 customer opportunities (needs/pains). Group related opportunities. Frame each from the customer's perspective.
3. **Prioritize opportunities** — Use Opportunity Score or qualitative assessment to rank. Focus on the top 2-3.
4. **Generate solutions** — For each prioritized opportunity, brainstorm 3+ solutions from PM, Designer, and Engineer perspectives.
5. **Design experiments** — For the most promising solutions, suggest 1-2 fast experiments. Specify: hypothesis, method, metric, success threshold.
6. **Visualize the tree** — Present the full OST in a clear hierarchical format.
Think step by step. Save as markdown if substantial.
---
### Further Reading
- [The Extended Opportunity Solution Tree](https://www.productcompass.pm/p/the-extended-opportunity-solution-tree)
- [What Is Product Discovery? The Ultimate Guide Step-by-Step](https://www.productcompass.pm/p/what-exactly-is-product-discovery)
- [Product Trio: Beyond the Obvious](https://www.productcompass.pm/p/product-trio)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
所有檔案
1 個檔案安裝 opportunity-solution-tree
請下載並將技能檔案解壓縮至您的 .claude/skills/ 目錄中。
下載 ZIP複製儲存庫並將技能檔案複製到您的專案中。
git clone https://github.com/phuryn/pm-skills/tree/main/pm-product-discovery/skills/opportunity-solution-tree # Copy SKILL.md to your .claude/skills/ directory
複製
