Skip to main content
Ionhour
Incidents

Post-incident reviews without the blame

A short template for writing up what happened, why it made sense at the time, and what you will change.

K

Kareem Arafa

July 28, 2026 · 1 min read

A review that hunts for someone to blame teaches the team to hide mistakes. A review that asks why each decision made sense at the time teaches the system to get better.

A template that fits on one page

  • What happened, as a timeline with timestamps.
  • What customers experienced, and for how long.
  • Why each decision looked reasonable with the information available.
  • What you will change, with an owner and a date for each item.

Write it while it is fresh

Hold the review within a few days, while people still remember what they saw. Your incident timeline already records when alerts fired and who acknowledged them, so start from that instead of from memory.

ShareXLinkedIn

Kareem Arafa

Founder, Ionhour

Kareem builds Ionhour and writes about the unglamorous work of keeping scheduled jobs, APIs and websites running.

Know the moment a job doesn’t run.

Cron jobs, websites, and APIs — watched 24/7, with alerts in Slack, SMS, or email.