Change management
Most self-inflicted outages arrive through change, and so do a large share of security problems.
Nothing was wrong until somebody altered something. That is an argument for knowing what changed and being able to put it back, not for making change slow. Heavy processes produce a different failure: people route around them, so the risky changes happen without any record at all. The aim is reversibility and visibility rather than ceremony.
Checked against the primary source.
