Post-mortems & Retrospectives

Scope

Covers

• Running blameless incident post-mortems and project/OKR retrospectives
• Turning “what happened?” into system learnings + decisions (not blame)
• Creating follow-through: owners, due dates, success signals, and review cadence
• Adding kill criteria / triggers so future pre-mortems lead to real action
• Institutionalizing learning via a lightweight “Impact & Learnings” review

When to use

• “Run a postmortem / retrospective for <incident/project> and write the doc.”
• “We missed OKRs—lead a retro focused on learning and systemic blockers.”
• “Create an after-action review with action items and owners.”
• “Set up a weekly impact & learnings review so insights don’t die in docs.”
• “Do a pre-mortem and define kill criteria / pivot triggers.”