大多数决策记录翻车是因为把决策埋在上下文之后。好的决策总结开门见山写决策，写明谁决定、列出比较过的选项、保留异议，并以”明天起改什么”收尾。下面 15 个模板覆盖真正在用的格式——1 页 memo、ADR、供应商选型记录都有。
适合哪些场景
PM、chief of staff、工程经理、创业者、运营负责人——需要让决策可审、可搜、半年后新人也能复盘的人。
什么时候不建议这样写 Prompt
别用在小事上（字体颜色、会议时间）——成本大于价值。也不要在没和 HR / 法务确认前就写敏感（HR / 法律 privilege）决策 memo。
Prompt 结构公式
决策总结 Prompt 一定要带这六个要素：
- 角色：让 AI 扮演谁（PM、chief of staff、运营、财务分析、经理）。
- 上下文：公司 / 团队 / 项目 / 受众 / 之前发生了什么。
- 目标：一个具体可交付物——memo、邮件、talking points、表格、优先级清单。
- 限制：不能做什么（别有营销腔、别超出事实推断、别写 PII、控制字数）。
- 输出格式：编号小节、markdown 表格、Slack 友好的 bullet，或 1 页 memo。
- 示例 / 信号：1-2 行”好语气”示例，或一个可模仿的过往样本。
这套 Prompt 适合用在哪
- 记录领导拍板的决策，防止之后被反复重提
- 架构 / 供应商 / 招聘决策，未来的自己要能解释
- 群体决策且需要保留异议
- 升级 memo 发给只有 5 分钟的 VP
- 尚未决定的状态更新，让 stakeholder 别再 ping
15 个可直接复制的 Prompt 模板
1. 1 页决策 memo
默认格式——80% 场景都适用。
You are a chief of staff. Below are my raw notes on a decision we just made. Produce a 1-page memo with these sections in order: (1) Decision (one sentence, lede), (2) Context in 3 sentences, (3) Options considered (table: option | pro | con), (4) Why we chose what we chose (3 bullets), (5) Who decided + who was consulted, (6) What changes by when (action items with owners + dates), (7) When we revisit. Plain language. No marketing voice.
Notes:
{paste}可替换变量： paste —— 原始笔记、转录或白板照 OCR
优化建议： 如果 memo 越写越长，加一句：“Hard limit: 400 words. Cut context first, never cut the decision or action items.”
2. ADR 格式决策（工程）
Write an Architecture Decision Record (ADR) for the decision below. Use the standard sections: Title, Status (Proposed / Accepted / Superseded), Context, Decision, Consequences (positive + negative + neutral), Alternatives considered. End with a "Reversibility" line: easy / costly / one-way door.
Decision context: {paste}可替换变量： paste —— 技术决策（如”事件表用 Postgres 还是 Mongo”）
3. 选项 pros-cons 表
决策未定、要 stakeholder 对比时用。
I am evaluating {N} options for {goal}. Build a comparison table with columns: Option | Cost | Time-to-value | Risk | Reversibility | Strategic fit | Recommendation strength (1-5). Then write 3 sentences below the table: top pick, runner-up, what would change my mind.
Options and notes:
{paste}4. RACI 决策总结
Below is a decision write-up. Append a RACI block that names: Responsible (drives execution), Accountable (final call), Consulted (gave input before decision), Informed (told after). Use one name per slot — no "the team". If a slot is empty, write "TBD" and flag it.
{paste}5. 时间盒决策
数据不会完美，但你还是拍了板。
Frame this as a TIME-BOXED decision. Sections: (1) The decision, (2) Why now (the deadline / forcing function), (3) What we knew vs what we did not know, (4) Confidence level (low / medium / high) and why, (5) Re-evaluation trigger (specific signal or date). End with: "If we wait, the cost is X."
Context: {paste}6. 群体决策同步纪要
Below is a transcript / notes from a group sync where a decision was reached. Write the sync writeup: (1) Decision in one sentence, (2) Who was in the room (names + roles), (3) Path to the decision (3-5 bullets — how the group converged), (4) Dissenting views captured by speaker, (5) Action items + owners + dates, (6) What was explicitly out of scope.
{paste}7. 可逆 vs 不可逆框架
Classify the decision below as reversible (two-way door) or irreversible (one-way door). Then write the memo accordingly: (a) For reversible — short, bias to action, name the rollback path. (b) For irreversible — long, name the disconfirming evidence we looked for, name who has veto, name the pre-mortem we ran. Be explicit about which mode you chose and why.
{paste}8. 保留异议的决策
当有 stakeholder 不同意时。
Write a decision memo that explicitly preserves dissent. Sections: (1) Decision, (2) Majority rationale, (3) Dissent block — name(s), their argument in their voice (steelman it, do not strawman), what evidence would change the decision, (4) Why we proceeded anyway, (5) Commitment to revisit (specific date or metric trigger).
Notes: {paste}9. 基于数据的决策
Below are the data / analysis underpinning a decision. Write the memo with: (1) Decision, (2) Key data point(s) cited with source + date, (3) What the data does NOT cover (limitations), (4) The judgment call layered on top of the data, (5) Reproducibility — where the analysis lives so anyone can re-run. Avoid the trap of "the data decided" — name the human who decided.
Data and notes: {paste}10. 不确定下的决策
This decision is being made with high uncertainty. Write a memo that names the uncertainty explicitly: (1) Decision, (2) Known unknowns — list them, (3) Unknown unknowns — what we cannot even ask yet, (4) Bet size — what we are risking, (5) Kill criteria — specific signals that would reverse the decision, (6) Next info checkpoint (date / event).
Context: {paste}11. 升级决策 memo
发给只有 5 分钟的 VP / 高管。
Write an escalation memo to {VP role} who has 5 minutes. Structure: (1) TL;DR (the ask, in one sentence — escalate / approve / break tie), (2) What I tried (2 bullets), (3) What I need (decision, resources, air cover), (4) Cost of inaction (one sentence). Hard limit: 150 words.
{paste}可替换变量： VP role —— 如 “VP Engineering”、“CFO”, paste —— 情况摘要
12. 暂未决定状态更新
No decision has been made yet, but stakeholders are pinging. Write a holding-pattern update: (1) Where we are in the process, (2) What is blocking the call (data, alignment, missing input), (3) Who owns unblocking each item with dates, (4) When the next decision checkpoint is. Tone: confident, not defensive. Do NOT fake a decision.
Context: {paste}13. 决策回滚 memo
要推翻之前的决定时。
We are reversing a previous decision. Write the rollback memo: (1) What we decided previously (link to old memo), (2) What we now know that we did not know then, (3) The new decision, (4) What changes operationally (who unwinds what by when), (5) Acknowledgment of cost / wasted work without blame, (6) What we will do differently next time. No corporate-speak.
{paste}14. 供应商选型决策
Write a vendor-selection decision memo. Sections: (1) Vendor chosen + contract size + term, (2) Requirements we evaluated against (scored table: vendor | req1 | req2 | ... | total), (3) Why the runner-up lost (specific, not "less aligned"), (4) Risks of the chosen vendor (3 bullets) + our mitigations, (5) Exit ramp — how we get out if it goes wrong, (6) Owner of the relationship.
Notes: {paste}15. 招聘决策总结
关闭面试 loop——yes or no。
Write a hiring decision summary for the candidate below. Sections: (1) Decision (hire / no hire / hold), (2) Role + level + compensation band, (3) Strengths (3 evidence-backed bullets — cite the interviewer who saw it), (4) Concerns + how we will mitigate post-hire (or why they are blocking), (5) Dissenting interviewer (if any) — their argument verbatim, (6) Onboarding owner + first-30-day expectation. Treat this as a record future-managers will read.
Loop notes: {paste}容易踩的坑
- 决策埋在第 4 段——读者根本看不到。
- 行动项没 owner——“我们”做意味着没人做。
- 隐瞒异议——当下整齐，后期变成信誉税。
- 装作数据决定，其实是人在判断——承认判断本身。
- 不写”何时复盘”——决策变成永远不能撤的棘轮。
- 一份 memo 同时写给技术和 exec——受众需要不同剪辑。
- 可逆决策当成不可逆来走流程——白白拖慢团队。
优化技巧
- 永远先写决策。上下文是第 2 段，绝不是第 1 段。
- 即使数据很强，也要写出”是谁决定的”。“我们”会消解责任。
- 不可逆决策先跑 pre-mortem Prompt：“想象失败了，是什么杀死了它？”
- 异议留在主 memo 里，不要单独开文档——分离 = 时间一久就消失。
- 加一条”复盘触发”——具体指标或日期——这样决策不会默认变成永久。
- 决策 memo 集中保存（Notion DB、/docs/decisions/、ADR 目录）。没标签的决策会消失。
- 90 天后再跑 follow-up Prompt：“对照预期 outcome 给这个决策打分。” 帮你校准。
FAQ
- 决策 memo 应该多长？: 默认 1 页。ADR 半页够。升级 memo 150 字。超过 2 页就是把决策和分析混在一起了，拆开。
- 决策前还是决策后分享 memo？: 想要意见——前。已经定了——后。在邮件主题里标清楚是哪种，读者才知道该不该 push back。
- Slack 里非正式决定怎么办？: 事后也补一份 memo。Slack 不是可检索的归档。没 memo 的决策半年内必被重提。
- 每个决策都要 memo 吗？: 不需要。判断标准：6 个月后的新人需不需要知道为什么？需要 → 写。不需要 → 跳过。
- 怎么让人真的读 memo？: 第一句写决策。行动项放最后，带名字。Slack 链接配一句 TL;DR。略读的人也能拿到要点。
- 第二天决策又变了怎么办？: 在原 memo 顶部加 “Superseded by” 指向新 memo。不要删除。反复推翻的轨迹本身就有价值。