Back to Details

post-mortems-retrospectives

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Post-mortems & Retrospectives

事后复盘与回顾会议

Help the user run effective post-mortems and retrospectives that drive genuine learning using frameworks from 11 product leaders.
帮助用户借助11位产品领导者的框架，开展能带来真正学习成果的有效事后复盘和回顾会议。

How to Help

如何提供帮助

When the user asks for help with post-mortems or retrospectives:
  1. Understand the context - Ask whether this is after a failure, a success, or a routine checkpoint
  2. Set the right tone - Help them frame the exercise as learning-focused rather than blame-focused
  3. Structure for insights - Guide them toward formats that surface actionable learnings
  4. Ensure follow-through - Help them create mechanisms to act on what they learn
当用户请求事后复盘或回顾会议相关帮助时：
  1. 了解背景 - 询问这是在失败后、成功后，还是常规检查点的复盘
  2. 设定正确基调 - 帮助他们将这项活动定位为以学习为重点，而非追责
  3. 构建洞察结构 - 引导他们采用能挖掘可落地经验的形式
  4. 确保跟进执行 - 帮助他们建立机制，将所学内容转化为行动

Core Principles

核心原则

Pre-mortems need kill criteria

事前复盘需要终止标准

Annie Duke: "A pre-mortem is only effective if it results in 'kill criteria' - pre-determined signals that will trigger a pivot or shutdown." Identify early signals that a project is failing during the pre-mortem and pre-commit to specific actions if those signals are met.
Annie Duke："事前复盘只有在制定了‘终止标准’时才有效——即预先确定的、会触发转向或项目终止的信号。" 在事前复盘期间识别项目失败的早期信号，并承诺如果出现这些信号就采取具体行动。

Reframe failure as growth

将失败重新定义为成长

Carole Robin: "The acronym is A-F-O-G, another F-ing... Another Fucking Opportunity for Growth. My question, when something has gone wrong or a person has experienced a failure, my first question is always, so what did you learn?" When a failure occurs, immediately ask "What is the lesson here?" to maintain perspective during painful setbacks.
Carole Robin："这个缩写是A-F-O-G，Another F-ing... 又一个他妈的成长机会。当出现问题或有人经历失败时，我的第一个问题总是，你学到了什么？" 当失败发生时，立即问"这里的教训是什么？"，以便在挫折中保持正确视角。

Call them retrospectives, not post-mortems

称之为回顾会议，而非事后复盘

Eeke de Milliano: "Instead of calling something a postmortem, call it a retrospective, so that it's a positive thing. Like, 'Hey, we're learning from this thing.'" Reframing helps normalize failure and focuses the team on learning rather than blame.
Eeke de Milliano："与其叫事后复盘，不如叫回顾会议，这样它就成了一件积极的事。比如，‘嘿，我们正从这件事中学到东西。’" 重新命名有助于将失败正常化，让团队专注于学习而非追责。

Institutionalize learning reviews

制度化学习复盘

Ben Williams: "We have these team level impact and learnings reviews... The teams continuously document any learnings from data exploration, from experimentation, from user research." Hold weekly "Impact and Learnings" reviews focused on insights rather than status updates, and socialize learnings across the entire company.
Ben Williams："我们开展团队层面的影响与学习复盘……团队持续记录从数据探索、实验和用户研究中获得的任何经验。" 每周召开"影响与学习"复盘会，重点关注洞察而非状态更新，并在全公司范围内分享所学内容。

Grade OKRs for learning, not performance

为学习而非绩效给OKRs评分

Christina Wodtke: "What matters is, why 80%? Really focus on the learning... Make sure your grading is secondary to retrospective." The value of grading OKRs lies in the retrospective analysis of why a goal was or wasn't hit, not the number itself. Use end-of-quarter retrospectives to identify systemic blockers.
Christina Wodtke："重要的是，为什么是80%？真正专注于学习……确保评分是回顾会议的次要部分。" OKR评分的价值在于回顾分析目标达成或未达成的原因，而非分数本身。利用季度末的回顾会议识别系统性障碍。

Make it blameless

保持无追责氛围

The goal is to understand what happened and why, not to assign blame. Create psychological safety so people can share honestly without fear of punishment.
目标是了解发生了什么及原因，而非追责。营造心理安全感，让人们可以坦诚分享而不必担心惩罚。

Questions to Help Users

可用于帮助用户的问题

  • "What did we learn that we didn't know before starting this project?"
  • "If we had to do this again with the same information we had at the start, what would we do differently?"
  • "What signals did we see early that we ignored or missed?"
  • "What systemic issues contributed to this outcome that we should address?"
  • "What kill criteria should we set for similar projects in the future?"
  • "How will we ensure these learnings actually influence future decisions?"
  • "我们学到了哪些项目开始前不知道的东西？"
  • "如果我们要在项目启动时的信息基础上重新做一次，会有什么不同的做法？"
  • "我们早期看到了哪些被忽略或错过的信号？"
  • "哪些系统性问题导致了这个结果，我们需要解决？"
  • "我们应为未来类似项目设定哪些终止标准？"
  • "我们将如何确保这些经验真正影响未来的决策？"

Common Mistakes to Flag

需要指出的常见错误

  • Blame-focused framing - Turning the exercise into finding fault rather than understanding systems
  • No follow-through - Running retrospectives but never acting on the learnings
  • Only reviewing failures - Missing the opportunity to learn from successes and understand what drove them
  • Optimizing the score, not the learning - Focusing on what percentage of OKRs were achieved rather than why
  • One-time events - Running retrospectives only for big failures instead of making them a regular practice
  • 追责导向的定位 - 将活动变成寻找责任人而非理解系统问题
  • 无跟进执行 - 召开了回顾会议但从未将所学付诸行动
  • 仅复盘失败 - 错失了从成功中学习、了解成功驱动因素的机会
  • 优化分数而非学习 - 关注OKRs的完成百分比而非背后原因
  • 一次性活动 - 仅在重大失败时才开展回顾会议，而非将其作为常规实践

Deep Dive

深入了解

For all 13 insights from 11 guests, see 
references/guest-insights.md
如需获取11位嘉宾的全部13条洞察，请查看
references/guest-insights.md

Related Skills

相关技能

  • running-effective-meetings
  • running-decision-processes
  • planning-under-uncertainty
  • running-effective-meetings
  • running-decision-processes
  • planning-under-uncertainty