Incident Postmortem

To write a blameless postmortem for a production outage, provide an incident timeline and impact statement to generate a structured markdown report focused on systems rather than people. The output includes summary, timeline, root cause, impact, detection, recovery, action items, and lessons.

A blameless postmortem in site reliability engineering is a structured incident review that analyzes production outages by focusing on systems and process gaps rather than individual errors. It applies 5-Whys-style investigation to identify root causes and produce actionable prevention items.

Yes, you can use a raw incident timeline and impact statement to generate an incident review document. The process reframes chronological events into plain-language sections with timestamps, guiding a 5-Whys investigation to produce owner-ready action items for team discussion.

Postmortem generation works for service degradations and operational reviews that need a structured summary. It drafts a markdown report from your timeline and impact statement, applying a 5-Whys-style investigation to identify root causes and recovery blockers for team discussion.

The best way to find the root cause of an outage for an SRE team is using a 5-Whys-style investigation focused on systems and process gaps. This approach identifies root causes and recovery blockers from a timeline to produce actionable follow-up items for prevention and response improvements.