pm-roadmap

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Product Roadmap Planning

产品路线图规划

Framework for building outcome-focused, theme-based roadmaps.

用于构建以成果为导向、基于主题的路线图的框架。

Roadmap Structure

路线图结构

Strategic Goal
├── Theme 1: [Outcome-focused name]
│   ├── Now: [Initiative with success metric]
│   ├── Next: [Initiative with success metric]
│   └── Later: [Initiative with success metric]
├── Theme 2: [Outcome-focused name]
│   ├── Now: ...
│   └── Next: ...
└── Theme 3: [Outcome-focused name]
    └── ...

Strategic Goal
├── Theme 1: [Outcome-focused name]
│   ├── Now: [Initiative with success metric]
│   ├── Next: [Initiative with success metric]
│   └── Later: [Initiative with success metric]
├── Theme 2: [Outcome-focused name]
│   ├── Now: ...
│   └── Next: ...
└── Theme 3: [Outcome-focused name]
    └── ...

Roadmap Template

路线图模板

markdown

undefined

markdown

undefined

Product Roadmap: [Product/Team]

Last Updated: YYYY-MM-DD | Owner: [PM Name] Strategic Goal: [One sentence]

Theme 1: [Outcome, not feature name]

Why: [Business/user outcome this theme drives] Success Metric: [How we know this theme is working]

Now (Current Quarter)

Initiative	Outcome	Status	Owner
[Initiative]	[Measurable result]	[🟢/🟡/🔴]	[Team]

Initiative	Outcome	Status	Owner
[Initiative]	[Measurable result]	[🟢/🟡/🔴]	[Team]

Next (Next Quarter)

Initiative	Outcome	Confidence	Dependencies
[Initiative]	[Expected result]	[High/Med/Low]	[Blockers]

Initiative	Outcome	Confidence	Dependencies
[Initiative]	[Expected result]	[High/Med/Low]	[Blockers]

Later (Future)

Initiative	Outcome	Open Questions
[Initiative]	[Hypothesis]	[What we need to learn]

Initiative	Outcome	Open Questions
[Initiative]	[Hypothesis]	[What we need to learn]

Decisions & Trade-offs

Decision	Options Considered	Chosen	Rationale
[What]	[A, B, C]	[B]	[Why]

Decision	Options Considered	Chosen	Rationale
[What]	[A, B, C]	[B]	[Why]

What We're NOT Doing (and Why)

[Feature/initiative]: [Reason for exclusion]

undefined

[Feature/initiative]: [Reason for exclusion]

undefined

Time Horizons

时间范围

Horizon	Commitment Level	Detail Level	Changes
Now	Committed	High (initiatives, owners, metrics)	Rare
Next	Planned	Medium (initiatives, outcomes)	Monthly
Later	Exploratory	Low (themes, hypotheses)	Frequently

时间范围	承诺等级	详细程度	变动频率
当前	已承诺	高（举措、负责人、衡量指标）	极少
下一步	已规划	中（举措、成果）	每月调整
未来	探索性	低（主题、假设）	频繁调整

Audience-Specific Views

分受众视图

Audience	Show	Hide
Executive	Themes, outcomes, strategic alignment	Implementation details
Engineering	Initiatives, dependencies, sizing	Business rationale
Sales/CS	Timeline, customer impact, messaging	Technical details
Full team	Everything	Nothing

受众	展示内容	隐藏内容
高管	主题、成果、战略对齐情况	实现细节
研发团队	举措、依赖关系、工作量评估	商业逻辑说明
销售/客户成功	时间线、客户影响、对外话术	技术细节
全体团队	全部内容	无

Building Process

构建流程

Gather inputs — strategic goals, OKRs, discovery findings, tech debt
Group into themes — cluster related work by outcome, not feature type
Prioritize themes — use
```
pm-prioritization
```
(RICE/ICE/OST)
Place in horizons — Now=committed, Next=planned, Later=exploratory
Define success — each theme needs a measurable outcome
Identify dependencies — cross-team blockers, technical prerequisites
Create audience views — tailor detail level per stakeholder group
Review cadence — monthly for Now/Next, quarterly for Later

收集输入 — 战略目标、OKRs、调研发现、技术债
按主题分组 — 按产出成果而非功能类型聚类相关工作
主题优先级排序 — 使用
```
pm-prioritization
```
（RICE/ICE/OST框架）
归入对应时间范围 — 当前=已承诺，下一步=已规划，未来=探索性
定义成功标准 — 每个主题都需要有可衡量的成果
识别依赖关系 — 跨团队阻塞项、技术前置条件
创建分受众视图 — 根据不同利益相关方调整内容详细程度
设置评审节奏 — 当前/下一步内容每月评审，未来内容每季度评审

Anti-Patterns

反模式

Anti-Pattern	Problem	Instead
Feature list roadmap	No strategic context	Theme by outcome
Date-driven promises	Creates false precision	Use horizons
No "not doing" section	Scope creep	Explicitly exclude
Static document	Stale in weeks	Set review cadence
One view for all	Wrong detail level	Audience-specific views

反模式	问题	替代方案
仅罗列功能的路线图	缺乏战略上下文	按成果划分主题
绑定固定日期的承诺	造成虚假精确性	使用时间范围划分
无「不做事项」板块	容易出现范围蔓延	明确排除不做的内容
静态文档	数周内就会过时	设置固定评审节奏
所有受众共用同一视图	内容详细程度不匹配	提供分受众专属视图