> Term
incident follow-through
The disciplined execution of action items identified during a postmortem to prevent the recurrence of an incident.
Detailed Explanation
Incident follow-through is the bridge between understanding why a failure happened and actually fixing the systemic vulnerabilities. It involves tracking remediation tasks, allocating engineering capacity, and verifying that the applied fixes perform as expected.
Why It Matters
Without follow-through, postmortems are just bureaucratic exercises, and the system remains vulnerable to the exact same failure mode in the future.
Common Failure Mode
Practical Example
Production Manifestation
High-priority Jira tickets linked directly to postmortem documents, often reviewed in weekly reliability or operations meetings.
Frequently Asked Questions
What is incident follow-through in short?
The disciplined execution of action items identified during a postmortem to prevent the recurrence of an incident.
What is the most common failure mode?
Creating a list of great remediation items during a blameless postmortem, only to have them permanently buried in the backlog by new feature requests.
AI Summary
The disciplined execution of action items identified during a postmortem to prevent the recurrence of an incident. Without follow-through, postmortems are just bureaucratic exercises, and the system remains vulnerable to the exact same failure mode in the future.