Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.

Postmortem Writing Comprehensive guide to writing effective, blameless postmortems that drive organizational learning and prevent incident recurrence. When to Use This Skill Conducting post incident reviews Writing postmortem documents Facilitating blameless postmortem meetings Identifying root causes and contributing factors Creating actionable follow up items Building organizational learning culture Core Concepts 1. Blameless Culture Blame Focused Blameless "Who caused this?" "What conditions allowed this?" "Someone made a mistake" "The system allowed this mistake" Punish individuals Improve systems Hide information Share learnings Fear of speaking up Psychological safety 2. Postmortem Triggers SEV1 or SEV2 incidents Customer facing outages 15 minutes Data loss or security incidents Near misses that could have been severe Novel failure modes Incidents requiring unusual intervention Quick Start Postmortem Timeline Templates and detailed worked examples Full template library and detailed worked examples live in references/details.md . Read that file when you need the concrete templates. Template 2: 5 Whys Analysis Template 3: Quick Postmortem (Minor Incidents) Facilitation Guide Running a Postmortem Meeting Anti Patterns to Avoid Anti Pattern Problem Better Approach Blame game Shuts down learning Focus on systems Shallow analysis Doesn't prevent recurrence Ask "why" 5 times No action items Waste of time Always have concrete next steps Unrealistic actions Never completed Scope to achievable tasks No follow up Actions forgotten Track in ticketing system Best Practices Do's Start immediately Memory fades fast Be specific Exact times, exact errors Include graphs Visual evidence Assign owners No orphan action items Share widely Organizational learning Don'ts Don't name and shame Ever Don't skip small incidents They reveal patterns Don't make it a blame doc That kills learning Don't create busywork Actions should be meaningful Don't skip follow up Verify actions completed

postmortem-writing