blameless-postmortem-process
Use after a significant incident (user-visible downtime, data loss, rollback, slow resolution, missed alert) to run a postmortem that is blameless, written, and widely shared, turning the incident into organizational learning that prevents recurrence.
Pinned to revision e4081cbb4d29, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.