Incident postmortem template

A blameless postmortem: summary, timeline, five whys to the root cause, what went well or wrong, and owned actions.

Use this templateFree, opens in your browser. No sign-up.

Incident postmortem template
Root cause: five whys
What went well
What went wrong
Where we got lucky
Summary
INC-2291 · SEV-1 · EU checkout failing
When
2026-10-14, 09:12–10:03 UTC (51 min)
Impact
18% of EU checkouts failed; ~2,300 orders, ~$96k delayed
Detection
Error-rate alert on checkout-api, 4 min after deploy
Root cause
DB connection pool cut from 50 to 5 by a config change
Status
Resolved · reviewed 2026-10-16
Time (UTC)
Event
09:08
Deploy v4.18 (config: db.pool.max = 5)
09:12
Error-rate alert fires, on-call paged
09:16
SEV-1 declared, #inc-2291 opened, lead named
09:31
Payment provider suspected, ruled out
09:44
Pool exhaustion spotted in DB metrics
09:52
Rollback to v4.17 started
10:03
Error rate back to normal, monitoring
Blameless: we look for gaps in systems and process, not people to blame.
Why 1? Checkout returned HTTP 500s
Why 2? checkout-api ran out of DB connections
Why 3? Pool max dropped from 50 to 5
Why 4? Typo in a shared config file, approved without a diff
Why 5? Config changes skip CI and canary
Alert fired within 4 minutes
Rollback took 11 minutes
Clear status updates every 15 min
40 min chasing the payment provider
No dashboard for pool usage
Config diff not shown in the PR
Happened in EU morning, not peak US
A DBA was online by chance
Action items
Action
Owner
Priority
Due
Ticket
Run config changes through CI + canary
Priya (platform)
P0
Oct 28
PLAT-812
Alert on DB pool usage > 80%
Marco (SRE)
P1
Oct 24
SRE-430
Show rendered config diff in PRs
Lena (dev tools)
P1
Nov 4
DX-219
Add pool exhaustion to the runbook
On-call rotation
P2
Nov 11
SRE-431
Postmortem: INC-2291 checkout outage
The incident postmortem template as it opens in Kelvo: 5 boxes, 9 sticky notes, 3 tables and 4 links, in 4 sections.

What's on the board

Root cause: five whys
Why 2? checkout-api ran out of DB connections · Why 4? Typo in a shared config file, approved without a diff · Why 1? Checkout returned HTTP 500s · Why 3? Pool max dropped from 50 to 5 · Why 5? Config changes skip CI and canary
What went well
Alert fired within 4 minutes · Rollback took 11 minutes · Clear status updates every 15 min
What went wrong
40 min chasing the payment provider · No dashboard for pool usage · Config diff not shown in the PR
Where we got lucky
Happened in EU morning, not peak US · A DBA was online by chance

Table 1 columns: Summary, INC-2291 · SEV-1 · EU checkout failing.

Table 2 columns: Time (UTC), Event.

Table 3 columns: Action, Owner, Priority, Due, Ticket.

Also on the board

  • Blameless: we look for gaps in systems and process, not people to blame.
  • Action items

How to use this template

  1. Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
  2. Double-click any box to change its text. Replace the examples with your own content.
  3. Paste a table. Paste comma- or tab-separated text and it becomes a table. Tab moves to the next cell and adds rows as you go.
  4. Paste code as code. Paste a snippet and it becomes a code block with syntax colouring; Tab indents inside it.
  5. Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.

Good for

  • postmortem
  • incident
  • sre
  • root cause
  • engineer
  • Designing a schema or an API before writing it
  • Explaining a tricky flow in a code review or design doc
  • Agreeing on team conventions such as branching and reviews

Related templates

  • ER diagram (database schema) template previewER diagram (database schema)

    Entities as tables with columns, types and keys, joined by one-to-many relationships — sketch a schema before the migration.

  • UML class diagram template previewUML class diagram

    Classes with fields and methods, associations with multiplicity, and an interface with two implementations.

  • State machine template previewState machine

    Every state an order can be in and the events that move it — the source of truth for status logic and tests.

  • Sequence diagram (request flow) template previewSequence diagram (request flow)

    Numbered steps across Client, API gateway, service, database and a third party — how one checkout request really travels.

  • Incident response template previewIncident response

    Detect, triage, mitigate, communicate, resolve and learn — an on-call runbook in one view.

  • Observability stack template previewObservability stack

    Metrics, logs and traces through OpenTelemetry into Prometheus, Loki and Tempo, with Grafana, alerting and SLO notes.

All software engineering diagram templates · All templates

Use the incident postmortem template