Incident Postmortems

A postmortem policy, a blameless template, honest timelines, contributing factor analysis and action items that really close, plus the review rhythms that turn every outage into a lesson for engineers, teams and managers.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Incident Postmortems, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Incident Postmortems

Writing blameless reviews after production incidents that explain what happened, why, and which concrete actions will prevent it happening again.

  1. Postmortem policy with clear severity triggers
  2. Blameless postmortem template for the team
  3. One searchable home for every postmortem
  4. Evidence capture checklist for live incidents
  5. Postmortem roles for owner, facilitator and approver
  6. Backfilled postmortem for a recent outage
  7. Blameless language guide for write-ups
  8. Postmortem turnaround targets and reminders
  9. Postmortem action items in the issue tracker
  10. Weekly postmortem review meeting
  11. Unreviewed incident backlog check
  12. Monthly sweep of open action items
  13. Overdue action item escalation path
  14. Monthly incident trend digest
  15. Quarterly postmortem quality audit
  16. Near-miss and good-catch reporting
  17. Monthly postmortem reading circulation
  18. Annual incident year in review
  19. Building an accurate incident timeline
  20. Contributing factors instead of a single root cause
  21. Five whys practice and its limits
  22. Facilitating a blameless review meeting
  23. Interviewing responders without leading questions
  24. Writing action items that prevent recurrence
  25. Executive summary for non-engineering readers
  26. Quantifying incident impact honestly
  27. Studying public postmortems from other companies
  28. Choosing postmortem tooling, documents or incident platform
  29. Severity scale recalibration from past incidents
  30. Incident tagging scheme for trend analysis
  31. Accepting risk on actions you will not do
  32. Cutting time from incident to published postmortem
  33. Linking postmortems to the changes that triggered them
  34. Postmortem visibility and redaction rules
  35. Public incident report after a major outage
  36. Multi-team postmortem for a major incident
  37. Incident story at an engineering all-hands
  38. Replaying a past incident as a team exercise
  39. Incident evidence pack for auditors or regulators
  40. Your first postmortem when your change caused it
  41. Manager's role in postmortems and follow-through
  42. Lightweight postmortems for a small startup team
  43. Postmortem for a third-party vendor outage
  44. Postmortem after data loss or corruption
  45. Security incident postmortem with restricted details
  46. Supporting responders after a stressful incident
  47. Postmortem programme metrics and reporting
  48. Resilience engineering and learning from incidents study
  49. Postmortem facilitator guild across teams
  50. Structured postmortem data for automated reporting

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Postmortem policy with clear severity triggers

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Without a written rule, postmortems happen for the incidents that embarrassed someone senior and get skipped for the quiet ones that will recur.

First tasks

  • List the last ten incidents and mark which ones got a written review
  • Draft review triggers by severity, customer impact and data exposure
  • Set the draft and review meeting deadlines in business days
  • Publish the policy and link it from the incident response guide

Blameless postmortem template for the team

A blank page produces wildly different write-ups: one engineer writes three lines, another writes a novel with no actions. A shared template with fixed sections for summary, impact, timeline, contributing factors, what went well, where we got lucky and action items makes every postmortem comparable and much faster to start. Write prompts into each section so a tired author knows what good looks like.

First tasks

  • Collect three past postmortems and note which sections were useful
  • Ask the agent to draft a template with prompts from those examples
  • Fill the draft template for one past incident and cut empty sections
  • Save the template where authors start every new postmortem

One searchable home for every postmortem

Postmortems scattered across chat threads, personal documents and old wiki spaces cannot be searched when the same failure returns two years later. One folder or space with a fixed naming convention, a short index and consistent tags means anyone can find every past review of the payment service in under a minute. Move the existing ones now, while people still remember where they are.

First tasks

  • Search chat, wiki and shared drives for existing postmortems
  • Agree a file naming convention with date, service and summary
  • Move or link each existing postmortem into the new location
  • Build an index page with date, severity and services for each review

Make it yours.

Install Incident Postmortems, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.