John Allspaw says any ‘after-action’ or ‘postmortem’ document (in my domain of web operations and engineering) has two main goals: To provide an explanation of how an event happened, as the organization (including those closest to the work) best understands it. To produce artifacts (recommendations, remediations, etc.) aimed at both prevention and the improvement of detection and response approaches to aid… Read more »
Posts Tagged: Procedures
The real problem with just making shit up
If you have experience and can reapply knowledge, you’re going to devise and follow a process/procedure based on your experience. OR you’re going to find someone with more relevant experience and get their help crafting the process/procedure. If you’re not following a procedure you’re making shit up. Making shit up is what you do when… Read more »
Following procedures” is not the same as “doing the right thing
Following procedures” is not the same as “doing the right thing. This seems to be the main thesis of John Allspaw’s 9,300 article. It’s a great point, but he (possibly intentionally) overlooks the fact that good procedures save time and reduce risk EVERY TIME. But in his article John goes so far out of his way to demonize… Read more »