Postmortem Follow-Up Tracking
Action item delivery.
Overview
Action items in the postmortem are useless without follow-up tracking. Most teams write the items; few teams complete them. The discipline below is what converts written intent into shipped reliability improvements.
- Action-item delivery. Each item carries a completion target. Without tracking, items live in a Google Doc and die there.
- Named owner per item. Real human, not a team alias. Accountability requires a name.
- Tracking system. Items live in Jira or Linear, not in the postmortem doc. The ticketing system is the source of truth.
- Monthly review plus stale escalation. Outstanding items reviewed each month; aging items escalate to leadership.
The approach
Three habits convert action items into shipped work: a named owner per item, ticket-system tracking, and a monthly review that surfaces stale items before they age out.
- Per-action owner. Real human named, not a team alias. The owner’s name appears on the ticket and in the postmortem.
- Ticket-system tracked. Jira, Linear, or equivalent. Action items become real work that competes with feature work, not separate paperwork.
- Monthly review. Outstanding items reviewed monthly. The review forces attention; stale items get re-prioritised or escalated.
- Stale escalation plus per-severity SLO. Aging items escalate to leadership; per-severity completion SLO documented (Sev-1 within 30 days, Sev-2 within 60).
Why this compounds
Each completed action item produces a real reliability improvement that compounds. The team learns that postmortems drive change; the next postmortem gets better action items because they matter.
- Better reliability. Completed action items shrink the recurring incident classes. Last year’s outages stop being this year’s outages.
- Cultural signal. Completed actions show that postmortems matter. Engineers invest more in writing good ones.
- Faster incident response. Past lessons applied to future incidents. The team’s catalog of fixed-issue patterns grows.
- Year-one investment, year-two habit. The first quarter of tracking takes effort. By year two the cadence runs itself and the backlog stays current.