Back to Details

define-opportunity-tree

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Opportunity Solution Tree

Opportunity Solution Tree

An Opportunity Solution Tree (OST) is a visual framework for product discovery that connects business outcomes to customer opportunities and potential solutions. Developed by Teresa Torres, it prevents the common trap of jumping straight to solutions by ensuring every feature idea traces back to a customer need and measurable outcome.
Opportunity Solution Tree（OST）是一种用于产品探索的可视化框架，它将业务成果与客户机会及潜在解决方案关联起来。由Teresa Torres开发，它避免了直接跳到解决方案的常见误区，确保每个功能想法都能追溯到客户需求和可衡量的成果。

When to Use

使用场景

  • During continuous product discovery to organize learning
  • When prioritizing what opportunities to pursue
  • To communicate product strategy to stakeholders
  • When you have too many feature ideas and need structure
  • After user research to connect insights to action
  • When aligning team on what outcomes matter most
  • 在持续产品探索过程中整理学习成果
  • 确定要优先推进的机会时
  • 向利益相关者传达产品战略时
  • 功能想法过多需要结构化梳理时
  • 用户研究后将洞察转化为行动时
  • 团队对齐核心成果优先级时

Instructions

操作步骤

When asked to create an opportunity solution tree, follow these steps:
  1. Define the Desired Outcome Start at the top with a clear, measurable business or product outcome. This should be something you can influence through product changes. Express it quantitatively when possible (e.g., "Increase 30-day retention from 40% to 55%").
  2. Identify Opportunity Areas Branch out to 3-5 opportunity areas.places where customer needs or pain points could be addressed. Opportunities are not solutions; they're customer problems, needs, or desires. Phrase them from the customer's perspective.
  3. Add Supporting Evidence For each opportunity, note the evidence that supports it: user research quotes, behavioral data, support tickets, or market trends. Strong opportunities have multiple evidence sources.
  4. Brainstorm Solutions For each opportunity, generate 2-4 potential solutions. Don't self-censor at this stage. Solutions can range from quick experiments to major features. Keep them specific enough to evaluate.
  5. Define Assumption Tests For each promising solution, identify the riskiest assumption and design a lightweight experiment to test it. Good tests validate whether the solution will actually address the opportunity.
  6. Prioritize the Tree Not all branches are equal. Mark which opportunity and solution you'll pursue first based on potential impact, confidence, and effort. The tree is a living document.you'll iterate as you learn.
  7. Visualize the Structure Create a tree diagram showing the hierarchy: outcome at top, opportunities below, solutions beneath each opportunity, and experiments at the leaves.
当需要创建机会解决方案树时，请遵循以下步骤：
  1. 定义期望成果 从顶部开始，明确一个可衡量的业务或产品成果。该成果应是可通过产品变更影响的内容。尽可能用定量方式表达（例如："将30天留存率从40%提升至55%"）。
  2. 识别机会领域 延伸出3-5个机会领域，即可以解决客户需求或痛点的方向。机会不是解决方案，而是客户的问题、需求或诉求。要从客户视角进行表述。
  3. 添加支撑证据 为每个机会标注支撑它的证据：用户研究语录、行为数据、支持工单或市场趋势。有说服力的机会需具备多种证据来源。
  4. 头脑风暴解决方案 为每个机会生成2-4个潜在解决方案。此阶段不要自我设限。解决方案可以从快速实验到重大功能不等，要具体到可评估的程度。
  5. 定义假设测试 针对每个有前景的解决方案，识别最具风险的假设，并设计一个轻量化实验来验证它。好的测试能够确认解决方案是否真的能解决对应的机会问题。
  6. 为树进行优先级排序 并非所有分支都同等重要。根据潜在影响、可信度和实施成本，标记出首先要推进的机会和解决方案。这棵树是一份动态文档，会随着学习迭代更新。
  7. 可视化结构 创建树状图展示层级结构：顶部是成果，下方是机会，每个机会下是解决方案，叶子节点是实验。

Output Format

输出格式

Use the template in 
references/TEMPLATE.md
to structure the output.
使用
references/TEMPLATE.md
中的模板来构建输出内容。

Quality Checklist

质量检查清单

Before finalizing, verify:
  • Outcome is measurable and within product team's influence
  • Opportunities are customer-centric (needs/problems, not features)
  • Each opportunity has supporting evidence documented
  • Multiple solutions exist per opportunity (not jumping to one)
  • Assumptions are explicit and experiments designed
  • Prioritization is clear (which branch to explore first)
最终确定前，请验证：
  • 成果可衡量且在产品团队的影响范围内
  • 机会以客户为中心（需求/问题，而非功能）
  • 每个机会都记录了支撑证据
  • 每个机会对应多个解决方案（未直接跳到单一方案）
  • 假设明确且已设计实验
  • 优先级清晰（明确首先探索哪个分支）

Examples

示例

See 
references/EXAMPLE.md
for a completed example.
请查看
references/EXAMPLE.md
获取完整示例。