The whole point of a postmortem is to change behavior. The pack is built around that — not around filling in boxes.
Eight sections; opinions baked in for each.
A 6-page guide for running the meeting without blame.
Track quality of postmortems over time, not just count.
A real outage, lightly redacted, fully completed.
Notion for the meeting, Markdown for the repo, PDF for the leadership digest.
Pre-built database + page template. Drop into your workspace and run your next postmortem from it.
For repo-resident postmortems. Pairs well with our ADR templates for cross-linking.
Print-ready leadership digest format. The audience reads outcomes, not timestamps.
6-page PDF you hand to whoever is running the meeting. Reduces blame, increases learning.
If something isn’t answered here, ask in your intro email — we keep this list short on purpose.
Yes — that’s where it shines. The pack is designed for teams of 5–50 engineers where every incident matters and the postmortem ritual is still being established.
The action-item tracker is Notion by default, but the template lists the field shape so you can mirror it into Jira or Linear. We include the schema in the pack.
Live meeting: 60–90 min. Pre-work by the IC: 1–2 hr. Follow-up tracking: 10 min/week. Our rubric helps you see if you’re investing the right amount.
Yes — the format collects the fields auditors look for. We include guidance on what to redact for external sharing and what to retain internally.
We do bespoke kits, too. Send a paragraph about the problem and we’ll come back inside 48 hours.