A blameless postmortem, in ten parts.

Ten parts that help a team learn from a bad day without looking for someone to blame. Fits a 45-minute review.

Running the 45 minutes

  1. The day before: the author fills parts 01–04 and shares them.
  2. First 30 minutes: walk the timeline together and fill parts 05–07.
  3. Last 15 minutes: agree on the action items, one owner each.

The example is Acme Shop, a made-up online store. Every section uses the same story.

  1. Header

    The facts a reader needs before anything else.

    Fields

    • Title
    • Date
    • Severity
    • Status
    • Authors
    • Tickets

    Example

    Title
    Checkout down for 47 minutes
    Date
    4 Mar 2026, 14:02 to 14:49 UTC
    Severity
    SEV1 (all customers could not pay)
    Status
    Final, reviewed 7 Mar
    Authors
    Priya (incident lead), Sam
    Tickets
    OPS-412 to OPS-416, SHOP-88
  2. 01 Summary

    Three sentences: what broke, who felt it, how it ended.

    Hints

    • Write it last, read it first.
    • No jargon a new hire would need to look up.

    Example

    For 47 minutes nobody could pay at Acme Shop. The certificate on our payments API had expired, so checkout could not reach it. We renewed it by hand and checkout came back at 14:49 UTC.

  3. 02 Impact

    Who was affected, how badly, and for how long. Use numbers.

    Hints

    • Count people or orders, not just minutes.
    • Say what customers saw, in their words.

    Example

    • All checkouts failed for 47 min: about 1,900 orders not placed.
    • Customers saw "Payment declined", so many thought their card was the problem.
    • No data lost. No one was charged twice.
  4. 03 Detection

    How we found out, and how long that took.

    Hints

    • Write the time from "it broke" to "a person knew".
    • Did an alert fire? If a customer told you first, say so.

    Example

    No alert fired. Support saw angry posts on social media at 14:21, 19 minutes after checkout broke. Our health checks called the API from inside our network, behind the load balancer where TLS had already ended, so they never saw the expired certificate.

    An outside check would have caught this in 1 minute, not 19. That's the kind of check we build at StatusTick.

    See how
  5. 04 Timeline

    Times in UTC. What we saw, what we thought, what we did.

    Hints

    • Include the wrong guesses. They show where the tools misled you.
    • Copy times from chat and alerts, not from memory.

    Example

    1. 14:02Certificate expires. Checkout starts failing.
    2. 14:21Support sees posts about failed payments and pages on-call.
    3. 14:28On-call checks the card provider first, because the error said "declined".
    4. 14:31Status page updated: "Payments are failing. We're working on it."
    5. 14:39Expired certificate found. The runbook still points to the old DNS provider.
    6. 14:49Certificate renewed by hand. Checkout works again.
  6. 05 Contributing factors

    The conditions that made this possible, and the ones that made it last longer.

    Hints

    • Ask "why did the system allow this?", never "who did this?".
    • Keep two chains apart: why it broke, and why it took so long.

    Example

    Why did it break?

    1. A1The payments API certificate expired.
    2. A2Auto-renewal had been failing since we moved DNS providers in January.
    3. A3The renewal job still used the old provider's API key.

    Why did it take 47 minutes?

    1. B1No alert on renewal errors or on soon-to-expire certificates.
    2. B2Our checks called the API behind the load balancer, where TLS had already ended, so they never saw the expired certificate.
    3. B3The error message said "declined" and sent us to the card provider first.
    4. B4The runbook described the old DNS setup.
  7. 06 What went well

    The things that helped. There are always some.

    Hints

    • Write this part while the good is fresh, it fades first.
    • Name tools and habits worth keeping.
    • Also write down where you got lucky. Luck is not a plan.

    Example

    • Support paged on-call within minutes of the first posts.
    • No double charges: the payment retries were safe to repeat.
    • The status page was updated within 10 minutes of the page.
  8. 07 What was hard

    Where people struggled: tools, information, timing.

    Hints

    • Describe the situation, not anyone's skill.
    • "We didn't know X" is more useful than "X was missed".

    Example

    • The error message pointed at the wrong system.
    • The renewal steps in the runbook were 8 months old.
    • It happened during the busiest hour of the week.
  9. 08 Action items

    Each one fixes a factor from part 05. Owner, date and ticket for every row.

    Hints

    • One owner per row, not a team.
    • Mark each as prevent, detect or recover, and check you have some of each.

    Example

    ActionTypeFixesOwnerDueTicket
    Fix auto-renewal for the new DNS provider and test a renewal in stagingPreventA2, A3Priya14 MarOPS-412
    Add a "What depends on this provider?" step to the migration checklistPreventA2Priya28 MarOPS-416
    Alert on renewal errors and on certificates expiring within 14 daysDetectA1, B1Sam10 MarOPS-413
    Check checkout from outside our network every minuteDetectB2Sam14 MarOPS-415
    Show "Temporary problem, you were not charged" instead of "Payment declined" when the payments API is downRecoverB3Lee21 MarSHOP-88
    Update the certificate runbook for the new DNS setup, with a 5-minute manual renewalRecoverB4Jo17 MarOPS-414
  10. 09 Thanks

    Who helped, and how.

    Hints

    • Thank the people who noticed and spoke up, not only the fixers.

    Example

    Thanks to Lee in support for paging fast, to Priya for staying calm on the call, and to Jo for writing the renewal steps down while fixing them.

  11. 10 Links

    Dashboards, chat logs, graphs and tickets.

    Hints

    • Link the incident chat so readers can see the real order of events.

    Example

    • Incident chat: #inc-2026-03-04-checkout
    • Certificate dashboard, payments API error graph

That's all ten parts.

Take it to your next review.

Download Markdown