Back to Details

discover-outcomes

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Discover Outcomes

探索成果

Overview

概述

Define outcomes that describe measurable behavior change or business impact, not features. Build a clear outcome ladder so opportunity discovery and solution ideas have a shared target.
定义可衡量的行为变化或业务影响类成果，而非功能特性。构建清晰的成果层级，让机会探索和解决方案构思拥有共同的目标。

Position in Workflow

在工作流中的位置

Step 1 of product strategy workflow:
  1. /discover-outcomes
    - Define outcomes (THIS)
  2. /discover-opportunities
    - Identify opportunities
  3. /ideate-solutions
    - Explore solution concepts
  4. /discover-assumptions
    - Validate with experiments
产品战略工作流的第1步：
  1. /discover-outcomes
    - 定义成果（本环节）
  2. /discover-opportunities
    - 识别机会
  3. /ideate-solutions
    - 探索解决方案概念
  4. /discover-assumptions
    - 通过实验验证

Inputs (ask if missing, max 5)

输入项（若缺失需询问，最多5项）

  • Business or product goal (north star)
  • Target segment or market
  • Baseline metrics or current state
  • Time horizon for change
  • Constraints (budget, compliance, strategy)
  • 业务或产品目标（北极星指标）
  • 目标细分群体或市场
  • 基准指标或当前状态
  • 变化的时间范围
  • 约束条件（预算、合规性、战略方向）

Workflow

工作流程

  1. Separate outcomes from outputs
    • Outcomes are measurable changes; outputs are features or deliverables.
  2. Outcome laddering (OST-style)
    • Start with the top-level outcome.
    • Ask: "What must be true for this to happen?" to create 2-3 supporting levels.
  3. Write precise outcome statements
    • Use actor + behavior change + context + metric.
  4. Attach metrics and baselines
    • Include leading and lagging indicators.
    • Specify baseline, target, and time window.
  5. Prioritize outcomes
    • Score impact, controllability, time-to-learn, and strategic fit.
  6. Handoff
    • If outcomes are set, move to 
      /discover-opportunities
      or 
      /discover-assumptions
      .
  1. 区分成果与产出
    • 成果是可衡量的变化；产出是功能特性或交付物。
  2. 成果层级构建（OST风格）
    • 从顶层成果开始。
    • 通过提问：“要实现这一点，必须满足哪些条件？”来创建2-3个支撑层级。
  3. 撰写精准的成果陈述
    • 采用“参与者 + 行为变化 + 场景 + 指标”的结构。
  4. 关联指标与基准
    • 包含先行指标和滞后指标。
    • 明确基准值、目标值和时间窗口。
  5. 对成果进行优先级排序
    • 从影响力、可控性、学习周期和战略契合度四个维度打分。
  6. 交接推进
    • 若成果已确定，进入
      /discover-opportunities
      或
      /discover-assumptions
      环节。

Outcome Statement Templates

成果陈述模板

Increase [actor behavior] in [context] from [baseline] to [target] within [time].
Reduce [friction/cost/risk] for [actor] during [context] by [amount] within [time].
Increase [actor behavior] in [context] from [baseline] to [target] within [time].
Reduce [friction/cost/risk] for [actor] during [context] by [amount] within [time].

Output Format

输出格式

undefined
undefined

Outcome Discovery

Outcome Discovery

Context Summary

Context Summary

[1-3 sentences]
[1-3 sentences]

Outcome Ladder

Outcome Ladder

  • Level 1 (Top outcome): ...
    • Level 2: ...
      • Level 3: ...
  • Level 1 (Top outcome): ...
    • Level 2: ...
      • Level 3: ...

Metrics

Metrics

  • Outcome: ...
    • Leading indicators: ...
    • Lagging indicators: ...
    • Baseline: ...
    • Target: ...
    • Time window: ...
  • Outcome: ...
    • Leading indicators: ...
    • Lagging indicators: ...
    • Baseline: ...
    • Target: ...
    • Time window: ...

Prioritized Outcomes

Prioritized Outcomes

  1. ... (impact X, controllability X, time-to-learn X, strategic fit X)
  2. ...
  1. ... (impact X, controllability X, time-to-learn X, strategic fit X)
  2. ...

Open Questions

Open Questions

  • ...
  • ...

Next Step

Next Step

Proceed to opportunity discovery. Run 
/discover-opportunities
.
undefined
Proceed to opportunity discovery. Run 
/discover-opportunities
.
undefined

Quick Reference

快速参考

  • Outcomes = behavior or business change; outputs = features.
  • Always include baseline + target + time window.
  • Keep ladder depth to 2-3 levels unless complexity demands more.
  • 成果 = 行为或业务变化；产出 = 功能特性。
  • 务必包含基准值 + 目标值 + 时间窗口。
  • 除非复杂度要求，否则层级深度保持在2-3级。

Common Mistakes

常见误区

  • Writing features as outcomes
  • No baseline or time window
  • Skipping leading indicators
  • Ladders that are too deep or too vague
  • 将功能特性写成成果
  • 未设置基准值或时间窗口
  • 遗漏先行指标
  • 层级过深或过于模糊