Incident Postmortem

After an incident, the last thing your team wants to do is write a report. But skipping the postmortem means you learn nothing, fix nothing, and repeat the incident. The report itself isn't the problem — the effort to produce it is.

Incident Postmortem takes your raw incident data — logs, alert history, timestamps, Slack threads, monitoring screenshots, or just a bullet-point brain dump — and produces a complete postmortem document in Google SRE format. Timeline reconstruction, contributing factors, root cause analysis, impact assessment, and a prioritized action item list.

The format is blameless by design. The goal is to identify systemic failures, not finger-point. The output reflects that: it focuses on what failed and how to prevent recurrence, not on who was on call.

This is useful even for small teams who don't have a formal SRE practice. A clean postmortem after a bad deploy builds trust with customers, focuses remediation work, and creates institutional memory. This skill makes it fast enough to actually happen.