Skip to content

Write it down without blame.

What happened, minute by minute. Who it hurt and for how long. Why it happened, in systems, not names. Then follow-ups with owners, tracked in a table until the last one is done.

SEdited by SamEngineering8.7k uses40 min to fill

All templates

Preview of the Incident postmortem template

Postmortem: Slow exports, Nov 12

Postmortem: Slow exports, Nov 12

Severity
SEV-2
Lead
SSam
Status
Done
Duration
47 minutes

Exports took up to nine minutes for 47 minutes. No data was lost. 212 workspaces were affected.

Timeline

Timeline

TimeWhat happened
14:02Export queue passes 2,000 jobs
14:09Sam is paged, starts this page
14:31Second worker pool added
14:49Queue back under 50 jobs

Why it happened

  • One large workspace exported 31,000 pages at once
  • Exports and imports share a single queue

Follow-ups

More like this

Teams who use this template usually keep these three next to it in the sidebar.

Browse all 24 in the gallery
  • Product spec

    Problem, proposal, open questions and a decision log reviewers can sign.

    Engineering · 22.1k uses

  • Quarterly roadmap

    Bets for the quarter in one table, as a timeline for the all-hands.

    Product · 11.9k uses

  • Weekly team meeting

    A standing agenda that carries open items over from last week.

    People · 18.4k uses

Your copy of incident postmortem, ready in a click.

Free for personal use. Your team can start on Plus with a 14-day trial, no card needed.