A good post-mortem is a piece of technical writing. It should be readable by someone who wasn't...
A good post-mortem is a piece of technical writing. It should be readable by someone who wasn't there, convey the timeline clearly, and suggest concrete changes.
Most are none of these things. They're a wall of Slack screenshots.
Here's how to write one that people will read.
The structure
1. Summary (3 sentences). What happened. Impact. Duration. That's it.
I'll never forget my first post-mortem meeting. I was a junior engineer, and the server had crashed...
Writing a clear incident postmortem is one of those tasks that always lands at the worst time — right...
The Post-Mortem Nobody Learns From I've sat through hundreds of post-mortems. Most follow...
A look at why incident postmortems fail and how we can use MCP to enforce SRE-grade rigor.
A project dies. Not dramatically. No Viking funeral. No orchestral soundtrack. Just a slow quiet...
I read a post on Lobste.rs last week about dreading our LLM-written incident report future, and it...
