Premortems will keep your code alive
Premortems are remarkably quick, and have saved my team from making bad mistakes many times. No one intentionally releases code that they think is going to cause major problems, so the author of code about to go out will think that it's safe. The benefit of the premortem is to stretch your mind outside of the mental box you've created where your code is safe, and then look around from that perspective. We've found premortems particularly good at discovering "Unknown unknowns" and issues that occur when moving from a test environment to a production environment. Vizzini never did premortems and look what happened to him. Postmortems are the sadder, but even more useful, version of premortems. ACTION ITEMS. Action items are the silver lining of your incident-and the entire point of the postmortem-so make sure you mine as many valuable ones out of the wreckage of your code while they're fresh.