“咱们 sync 一下”就是失调的代价——一段话能写清、一个 thumbs-up 能定的事,被拖成 30 分钟会。好的对齐 memo 在第 3 行就给出明确决策、把 trade-off 老实摆出来、点清谁要批 / 谁要被咨询 / 谁要被告知,并给异步回应方式,让本来在会上沉默的人也能真正表态。要开的会用 会议议程 Prompt 把流程压紧。
适合哪些场景
跨团队 lead、协调 eng + design + GTM 的 PM、在职能间穿梭的创业者、一个话题开过 5 次对齐会的人。
什么时候不建议这样写 Prompt
纯社交 / kickoff 别用。真要现场辩论的决策也别用。
Prompt 结构公式
每个 Prompt 都要带这六个要素:
- 角色:AI 扮演谁——Chief of Staff / 经理 / 分析师。
- 上下文:团队 / 组织 / 范围 / 数据。
- 目标:一个交付物——计划、memo、谈点、文档。
- 限制:字数、必含字段、受众级别。
- 语气:自信、中性、事实。
- 示例:1-2 份过往作品锚定格式。
这套 Prompt 适合用在哪
- 会前对齐 memo
- 决策 memo
- trade-off 框架
- 异步升级
- 决策后 memo
12 个可直接复制的 Prompt 模板
1. 会前对齐 memo
Decision: `{decision}`. Stakeholders: `{stakeholders}`. Write a 1-page memo: (1) Context, (2) Decision needed, (3) 2-3 options with trade-offs, (4) Recommendation + why, (5) What changes if we decide, (6) Async response form (approve / pushback / questions).
可替换变量: decision, stakeholders
2. trade-off 表
For decision `{decision}`, build a trade-off table: rows = options, columns = key dimensions (cost, time, quality, risk, learning). Be honest — every option should have downsides.
可替换变量: decision
3. 异步回应设计
Design async response: (1) Approval signal (👍 / specific text), (2) Pushback format (one line + reason), (3) Question format, (4) Deadline. Reduce ambiguity for stakeholders responding in batches.
4. 干系人映射
For this decision, who needs: (a) Approval (decider), (b) Consult (input before), (c) Inform (notified after), (d) Involve (does the work). RACI without the acronym. Skip anyone who doesn't fit.
5. memo 内预复盘
Include a "what could go wrong" section: 2-3 failure modes, what we'd see, how we'd course-correct. Be specific.
6. 建议强度刻度
Mark my recommendation: STRONG (I will quit if this isn't the call), CONFIDENT (I think this is right), LEAN (I prefer this but reasonable people could disagree), NEUTRAL (genuinely unsure). Be honest.
7. 一页约束
Compress this draft memo to 1 page. Cut: history, restatements, unnecessary background. Keep: decision, options, recommendation, ask. Test by reading aloud — > 5 min = too long.
8. 升级 memo
Two teams disagree. Write an escalation memo: (1) The shared goal, (2) Each side's position + rationale (steel-man), (3) Trade-off the decider must weigh, (4) What I recommend + why. Don't take cheap shots at the opposing side.
9. 决策后发布
Decision is made. Write the rollout memo: (1) Decision + 1-sentence rationale, (2) What changes, (3) When, (4) Who to talk to about it, (5) What we won't entertain re-litigating. Polite but firm.
10. 决策后记录
Decision: `{decision}`. Record: (1) What was decided, (2) Who decided, (3) Date, (4) Options not chosen + why, (5) What would cause us to revisit. Don't skip "why not" — future decisions need it.
可替换变量: decision
11. 跨职能对齐文档
For an initiative across eng / product / design / GTM, write the alignment doc: (1) Goal, (2) Per-team scope, (3) Per-team success metric, (4) Dependencies between teams, (5) Cadence. ≤ 500 words.
12. memo 卫生
Audit my memo: (1) Is the decision clear by line 3? (2) Are trade-offs honest? (3) Recommendation explicit? (4) Async response possible? (5) Length ≤ 1 page? Output fix list.
容易踩的坑
- 没具体上下文——输出泛泛。
- 不核对——AI 会编。
- 受众模糊——深浅不当。
- 没字数限制——读者不读完。
- 所有场景一个模板——读者麻木。
- 没”需要什么决定”。
- 不附原数据。
优化技巧
- 指明受众级别。
- 限长:战术 1 页,执行 3 条。
- 开头先放”要什么决定”。
- 附原数据链接。
- 发前念出来。
- AI 出稿,人审核。
- 存样本,重用格式、刷新内容。
FAQ
- 文档多长?: 战术 1 页,执行 3 条 + 链接。
- AI 能取代分析师 / 经理吗?: 初稿模板可以;判断不行。
- 多久刷一次?: 按节奏;受众疲劳就调。
- 要写风险吗?: 要。装没风险下次失去信任。
- 怎么核对?: 附数据源;peer 看数字。
- AI 能自己出数据吗?: 不能。要连真实数据源。