Back to Details

prioritizing-roadmap

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Prioritizing Roadmap

路线图优先级排序

Scope

适用范围

Covers
  • Turning messy roadmap inputs into a ranked opportunity list + coherent roadmap
  • Defining a planning “season” (macro context) and success criteria
  • Using a common-currency scoring model (ICE + assumptions) to compare across teams
  • Producing an alignment-ready Roadmap Prioritization Pack
When to use
  • “What should we build next?”
  • “We need a Q2/Q3 roadmap.”
  • “We have too many requests and no way to compare them.”
  • “We need to prioritize across multiple teams/pods.”
When NOT to use
  • You don’t have any agreed goal / North Star / strategic intent (do product vision / goals first)
  • You need sprint planning or story-level estimation
  • You’re only choosing a single experiment within an already-fixed roadmap
  • You need a full customer discovery plan from scratch
涵盖内容
  • 将杂乱的路线图输入转化为排序后的机会列表及连贯的路线图
  • 定义规划“周期”（宏观背景）和成功标准
  • 使用通用货币评分模型（ICE+假设）进行跨团队对比
  • 生成用于对齐的路线图优先级包
适用场景
  • “我们接下来应该开发什么？”
  • “我们需要Q2/Q3的路线图。”
  • “我们收到太多需求，无法进行对比筛选。”
  • “我们需要在多个团队/小组间进行优先级排序。”
不适用场景
  • 尚未达成一致的目标/北极星指标/战略意图（需先制定产品愿景/目标）
  • 需要进行冲刺规划或用户故事级别的估算
  • 仅需在已确定的路线图中选择单个实验项目
  • 需要从零开始制定完整的客户探索计划

Inputs

输入项

Minimum required
  • Product + primary customer segment
  • Planning horizon + cadence (e.g., next 6 weeks, next quarter, rolling 12–24 months)
  • Success criteria (North Star / business goal) + 2–5 guardrails
  • Candidate opportunities (or current roadmap/backlog) with rough size/effort
  • Constraints: capacity, commitments, dependencies, deadlines, risk tolerance
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If still missing, proceed with clearly labeled assumptions and provide 2–3 roadmap options.
最低要求
  • 产品+核心客户群体
  • 规划周期+节奏（例如：未来6周、下一季度、滚动式12-24个月）
  • 成功标准（北极星指标/业务目标）+2-5个约束条件
  • 带有大致规模/工作量的候选机会（或当前路线图/待办事项）
  • 约束条件：产能、已承诺事项、依赖关系、截止日期、风险承受能力
信息缺失处理策略
  • 从references/INTAKE.md中选取最多5个问题进行询问。
  • 如果仍有信息缺失，基于明确标注的假设继续推进，并提供2-3个路线图选项。

Outputs (deliverables)

输出项（交付物）

Produce a Roadmap Prioritization Pack in Markdown (in-chat; or as files if requested):
  1. Context snapshot (goal, horizon, constraints, stakeholders)
  2. Season framing (what changed, key bets, explicit non-goals)
  3. Opportunity inventory with conviction level (known vs hypothesis) and evidence
  4. Prioritization model (common currency + ICE scoring + assumptions)
  5. Ranked opportunity list (top 10–20) + “parking lot”
  6. Roadmap draft (Now/Next/Later or quarterly themes) + update cadence (rolling plan)
  7. Decision narrative (why these, why now) + “Think Bigger” ideas
  8. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
生成Markdown格式的路线图优先级包（可在对话中展示；或按需生成文件）：
  1. 背景快照（目标、周期、约束条件、利益相关者）
  2. 周期框架（变化内容、核心投注、明确的非目标）
  3. 机会清单，包含确信度级别（已知/假设）及相关证据
  4. 优先级排序模型（通用货币+ICE评分+假设）
  5. 排序后的机会列表（前10-20项）+“搁置清单”
  6. 路线图草案（现在/下一步/后续或季度主题）+更新节奏（滚动计划）
  7. 决策说明（为何选这些、为何是现在）+“大胆构想”创意
  8. 风险/待解决问题/后续步骤（必须包含）
模板：references/TEMPLATES.md

Workflow (8 steps)

工作流程（8个步骤）

1) Intake + decision framing

1) 信息收集+决策框架

  • Inputs: User context; references/INTAKE.md.
  • Actions: Confirm the decision (backlog vs quarterly roadmap vs annual planning), horizon, stakeholders, constraints, and “must-do” commitments.
  • Outputs: Context snapshot.
  • Checks: Everyone agrees what decision will be made and by when.
  • 输入项： 用户背景；references/INTAKE.md
  • 行动： 确认决策类型（待办事项/季度路线图/年度规划）、周期、利益相关者、约束条件及“必须完成”的承诺事项。
  • 输出项： 背景快照。
  • 检查点： 所有人就需做出的决策及完成时间达成一致。

2) Define the “season” + success criteria

2) 定义“周期”+成功标准

  • Inputs: Context snapshot.
  • Actions: Name the current season (macro context), define 3–5 season bets, and set success criteria (North Star + guardrails).
  • Outputs: Season framing section.
  • Checks: A stakeholder can restate “why now” and “what we’re optimizing for”.
  • 输入项： 背景快照。
  • 行动： 命名当前周期（宏观背景），定义3-5个周期核心投注，设定成功标准（北极星指标+约束条件）。
  • 输出项： 周期框架章节。
  • 检查点： 利益相关者能够复述“为何是现在”及“我们的优化方向”。

3) Build the opportunity inventory (separate truth vs hypotheses)

3) 构建机会清单（区分事实与假设）

  • Inputs: Candidate inputs (requests, ideas, problems).
  • Actions: Normalize each item into a problem/outcome statement; tag conviction level (Known / Belief / Hypothesis) and evidence; split discovery vs delivery.
  • Outputs: Opportunity inventory table.
  • Checks: Every item has an intended outcome metric and a confidence/evidence note.
  • 输入项： 候选输入（需求、创意、问题）。
  • 行动： 将每个条目标准化为问题/成果说明；标记确信度级别（已知/信念/假设）及相关证据；区分探索阶段与交付阶段。
  • 输出项： 机会清单表格。
  • 检查点： 每个条目都有预期成果指标及信心/证据说明。

4) Define the common-currency scoring model (ICE + assumptions)

4) 定义通用货币评分模型（ICE+假设）

  • Inputs: Inventory + success criteria.
  • Actions: Choose a primary “common currency” (e.g., North Star units, revenue, cost, risk reduction) and define ICE scales; estimate impact ranges and confidence based on evidence.
  • Outputs: Scoring model + filled scoring table.
  • Checks: Two people using the same scales would produce similar relative rankings.
  • 输入项： 机会清单+成功标准。
  • 行动： 选择核心“通用货币”（例如：北极星指标单位、收入、成本、风险降低）并定义ICE评分标准；基于证据估算影响范围及信心度。
  • 输出项： 评分模型+填写完成的评分表格。
  • 检查点： 不同人使用相同评分标准能得出相似的相对排序结果。

5) Stress-test the ranking (scenarios + constraints)

5) 对排序结果进行压力测试（场景+约束条件）

  • Inputs: Scored list + constraints.
  • Actions: Apply constraints (capacity, dependencies, deadlines); run 2–3 scenarios (base / aggressive / conservative); ensure a balanced portfolio (core, growth, quality, big bets).
  • Outputs: Shortlist (top set) + parking lot + key tradeoffs.
  • Checks: Tradeoffs and “no’s” are explicit; nothing critical is missing.
  • 输入项： 已评分的列表+约束条件。
  • 行动： 应用约束条件（产能、依赖关系、截止日期）；运行2-3种场景（基础/激进/保守）；确保组合平衡（核心业务、增长、质量、大额投注）。
  • 输出项： 候选短名单（前列项）+搁置清单+关键权衡点。
  • 检查点： 权衡点及“否决项”明确；无关键内容遗漏。

6) Draft the roadmap (sequencing + cadence)

6) 起草路线图（排序+节奏）

  • Inputs: Shortlist + scenario choice.
  • Actions: Convert priorities into a roadmap (Now/Next/Later or quarterly themes), sequencing by dependencies and learning; define a rolling plan cadence (e.g., rolling 12–24 months, refreshed every 6 months).
  • Outputs: Roadmap draft + update cadence.
  • Checks: The roadmap is coherent, feasible, and resilient to new inputs.
  • 输入项： 候选短名单+场景选择。
  • 行动： 将优先级转化为路线图（现在/下一步/后续或季度主题），按依赖关系及学习成果排序；定义滚动计划节奏（例如：滚动式12-24个月，每6个月更新一次）。
  • 输出项： 路线图草案+更新节奏。
  • 检查点： 路线图连贯、可行，且能适应新的输入内容。

7) Write the decision narrative + alignment plan

7) 撰写决策说明+对齐计划

  • Inputs: Roadmap draft + rationale.
  • Actions: Write “why these, why now”; include a “Think Bigger” section; define how the roadmap will be communicated and updated.
  • Outputs: Decision narrative + comms/rollout plan.
  • Checks: A cross-functional partner can explain the roadmap without you in the room.
  • 输入项： 路线图草案+理由。
  • 行动： 撰写“为何选这些、为何是现在”；加入“大胆构想”章节；定义路线图的沟通及更新方式。
  • 输出项： 决策说明+沟通/推广计划。
  • 检查点： 跨职能伙伴可在你不在场的情况下解释该路线图。

8) Quality gate + finalize the pack

8) 质量校验+最终确定包内容

  • Inputs: Full draft pack.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Add Risks/Open questions/Next steps.
  • Outputs: Final Roadmap Prioritization Pack.
  • Checks: Pack is shareable as-is; assumptions, owners, and cadence are explicit.
  • 输入项： 完整的草案包。
  • 行动： 参照references/CHECKLISTS.md进行检查，并使用references/RUBRIC.md进行评分。添加风险/待解决问题/后续步骤。
  • 输出项： 最终的路线图优先级包。
  • 检查点： 包可直接共享；假设、负责人及节奏均明确。

Quality gate (required)

质量校验（必填）

  • Use references/CHECKLISTS.md and references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 使用references/CHECKLISTS.md和references/RUBRIC.md。
  • 必须包含：风险、待解决问题、后续步骤。

Examples

示例

Example 1 (B2B SaaS): “Prioritize our next-quarter roadmap for a collaboration product across Growth + Core.”
Expected: season framing, scored opportunity inventory, a Now/Next/Later roadmap, and a clear decision narrative with explicit non-goals.
Example 2 (Marketplace): “Prioritize 6 months of roadmap across supply, demand, and trust & safety.”
Expected: a common-currency model that makes cross-team tradeoffs comparable and a rolling plan refreshed on a fixed cadence.
Boundary example: “Give me a 2-year roadmap, we don’t have goals or constraints.”
Response: ask for goals/constraints; if unavailable, produce options + assumptions and recommend doing product vision + North Star first.
示例1（B2B SaaS）： “为协作产品的增长团队+核心团队确定下一季度路线图的优先级。”
预期输出：周期框架、已评分的机会清单、Now/Next/Later路线图，以及包含明确非目标的清晰决策说明。
示例2（平台型产品）： “为供应、需求及信任与安全团队确定6个月路线图的优先级。”
预期输出：可实现跨团队权衡对比的通用货币模型，以及按固定节奏更新的滚动计划。
边界示例： “给我一份2年路线图，我们没有目标或约束条件。”
回应：询问目标/约束条件；若无法获取，则提供带假设的选项，并建议先制定产品愿景+北极星指标。