Solving the Postmortem Completion Crisis in Engineering Teams

Why Nobody Completes Postmortem Action Items (and How to Fix It)

Engineering teams frequently experience the same incident multiple times despite having documented the fix in a postmortem. Data shows that the majority of teams complete less than 40% of their postmortem action items.

Why This Matters

The technical reality is that postmortem action items often live in static documents that are never reopened or Jira tickets that are immediately deprioritized. This failure in accountability creates a cycle where known fixes are never implemented, leading to systemic instability and repeated outages that could have been prevented.

Key Insights

• Most engineering teams complete less than 40% of their postmortem action items, leading to recurring incidents.
• Static documents like Google Docs contribute to ‘write once, forget forever’ behavior where information is never revisited.
• Standard issue trackers like Jira fail because they do not maintain the connection to the original ‘postmortem commitment.’
• High-end incident management tools like Rootly and incident.io cost $20-45 per user, which is often prohibitive for teams with fewer than 50 engineers.
• Structured forms and weekly Slack digests create social pressure and visibility that significantly improve completion rates.

Practical Applications

• Use case: Small engineering teams can implement AutoBrief to enforce action item owners and due dates via a structured form rather than a blank document.
• Pitfall: Relying on the phrase ‘We’ll create a Jira ticket’ without persistent tracking usually results in the fix being forgotten until the next outage.
• Use case: Reducing the postmortem process from 90 minutes to 10 minutes using low-friction tools increases the likelihood of completion.
• Pitfall: Storing action items in documentation that lacks a reminder system leads to zero accountability and repeated technical debt.

References:

• https://dev.to/solobuilder/why-nobody-completes-postmortem-action-items-and-how-to-fix-it-37ee
• https://autobrief.dev