The Postmortem Process and Timeline
What you'll learn: How a structured postmortem unfolds from initial writeup through closure, ensuring incidents lead to meaningful improvements.
The Four-Phase Journey
Once you've decided an incident warrants a postmortem (per the previous lesson), you need a repeatable process. Think of it like an investigation: gather evidence, discuss findings, assign homework, then verify completion.
Phase 1: Initial Writeup (24-48 hours)
The incident commander or a designated writer drafts the postmortem document while details are fresh. This includes the timeline, impact metrics, what went wrong, and what went right. It's a first draft—focus on capturing facts, not perfection.
Phase 2: Review Meeting (Within 1 week)
Gather the relevant team members for a 60-90 minute discussion. Walk through the timeline together, filling gaps and correcting misunderstandings. The goal is shared understanding, not blame. Everyone contributes their perspective. This meeting identifies root causes and generates potential action items.
Phase 3: Action Items and Ownership (Immediately after meeting)
Convert discussion insights into concrete, assigned tasks with deadlines. Each action item needs an owner and a due date. Examples: "Add timeout to API client" or "Update runbook with new diagnostic steps." These aren't vague wishes—they're trackable work.
Phase 4: Follow-Up to Closure (Ongoing)
Track action items like any other work. Review progress in team meetings. The postmortem isn't "done" until all critical items are completed or explicitly de-prioritized with documented reasoning. Some teams revisit the document 30-60 days later to verify changes were effective.
The Timeline Matters
Speed matters: memories fade, urgency wanes, and lessons get lost. The entire process should complete within 2-4 weeks maximum for most incidents. Critical outages might move faster.
Key Takeaway: A postmortem follows a structured timeline—writeup within 48 hours, meeting within a week, action items assigned immediately, and tracked through closure—turning incidents into concrete improvements rather than forgotten stories.