Write an incident review that finds the systemic cause and produces owned actions, without naming a culprit — timeline first, contributing factors, then fixes. Use when writing a postmortem after an outage, a bad deploy, or any incident worth learning from.
--- name: write-a-blameless-postmortem category: productivity description: >- Write an incident review that finds the systemic cause and produces owned actions, without naming a culprit — timeline first, contributing factors, then fixes. Use when writing a postmortem after an outage, a bad deploy, or any incident worth learning from. --- # Write a Blameless Postmortem The purpose is to make the next incident less likely, not to establish who was responsible. Those goals are in direct conflict: the moment a review can end someone's week badly, people stop volunteering what actually happened, and the information you need disappears. "Blameless" is not politeness. It is the mechanism that keeps the facts flowing. ## Write it within two days Memory decays fast and Slack scrollback is not a substitute. Two days, while people still remember what they were thinking at 02:40 — because what they *believed at the time* is the most valuable content in the document. ## The structure ```markdown # Incident 2026-03-14 — checkout unavailable, 41 minutes
You are reading the opening of this skill.
The rest is open to any signed-in account — free included. Reading the library costs nothing.
Shared publicly by the author and open for any use. See the Terms.