---
title: Postmortem Writing
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/postmortem-writing/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/postmortem-writing/
last_updated: 2026-06-20
---

# Postmortem Writing

> Write effective blameless postmortems with root cause analysis, timelines, and action items.

A complete method for writing blameless postmortems that turn incidents into organizational learning instead of finger-pointing. It supplies the structure: timeline, root cause analysis, detection and response review, impact, lessons, and tracked action items, plus facilitation guidance for the postmortem meeting itself. The outcome is incidents that don't recur, because every contributing factor gets a concrete, owned fix.

## Use cases
- Conducting a post-incident review after a SEV1 or SEV2
- Writing a standard postmortem document with timeline and impact
- Running a Five Whys root-cause analysis
- Facilitating a blameless postmortem meeting
- Producing a quick postmortem for a minor incident
- Reviewing patterns across incidents quarterly

## Benefits
- Fewer repeat incidents because action items are concrete, owned, and tracked to closure
- Faster, calmer incident reviews with a ready structure and facilitation script
- Psychological safety that surfaces real causes instead of hidden ones
- Sharper detection and response over time by analyzing the gaps each incident exposes

## What’s included
- Standard postmortem template with executive summary, timeline, RCA, detection, and impact
- Dedicated Five Whys analysis template mapping root causes to improvement types
- Quick postmortem template for minor incidents
- Prioritized action-item table with owners, due dates, and ticket links
- 60-minute postmortem meeting facilitation guide with timing and tips
- Anti-pattern and do's-and-don'ts reference to keep reviews blameless and useful

## Who it’s for
Engineering, SRE, and on-call teams who want incident reviews that prevent recurrence rather than assign blame.

## How it runs
An incident you do not learn from is an incident you have scheduled to repeat. Outages become blameless, evidence-backed documents with owned action items, all on a seven-day clock.
1. Checks the trigger first: severe incidents, customer-facing outages over 15 minutes, data loss, near-misses and novel failure modes all qualify, then locks the cadence of draft within 2 days, meeting by day 5, finalized document and tickets by day 7.
2. Builds the minute-by-minute timeline and an executive summary with quantified impact: affected customers, duration, revenue and support load, because vague impact produces vague fixes.
3. Digs to root cause with a structured 5 Whys where every why carries an evidence line, and pairs it with the Swiss Cheese model: listing every defense layer whose hole lined up (review gap, missing test, unrepresentative staging, slow alert) instead of hunting one villain.
4. Applies the blameless filter to every sentence: names become roles, 'engineer X broke it' becomes 'the pipeline had no canary stage so the bad release ran for 8 minutes', because blame kills the information flow the document exists to capture.
5. Maps detection and response gaps explicitly: what fired and when, how long orientation took, where the rollback decision stalled, and where the team simply got lucky.
6. Converts findings into Pareto-prioritized action items where the top one or two P0 fixes should prevent 80 percent of recurrence, every item gets a ticket, an owner and a due date (orphan action items are banned), and a quarterly review checks whether closed actions actually stopped repeats.

## FAQ
### We're a small team without formal SEV levels, is this overkill?
No, it scales down: a dedicated quick postmortem template exists for minor incidents, while the full structure (timeline, RCA, detection review, impact) is reserved for the ones that hurt. You can adopt the blameless framing and Five Whys without ever defining severity tiers.

### How does writing a document actually prevent incidents from recurring?
The document is the enforcement mechanism: every contributing factor must end in a concrete action item with an owner, a due date, and a ticket link, tracked to closure. The Five Whys template maps each root cause to an improvement type, so fixes target causes rather than symptoms.

### Will it dig through my logs and find the root cause for me?
No. It structures the analysis: the timeline, the Five Whys, the meeting facilitation, but the investigation itself runs on your telemetry and your engineers' knowledge. It makes the thinking rigorous; it doesn't do the debugging.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [Building a multilingual AI content pipeline](https://forgehouse.ai/guides/ai-content-pipeline/)