slow is smooth, smooth is fast
expressionops culture
The special-operations cadence rule: hurrying breeds errors, and errors cost more time than care ever did.
During incidents it is the antidote to panic typing: the deliberate command executed once beats the fast one executed three times with a rollback in between. Change windows run on the same physics.
Slow is smooth, smooth is fast comes from military and emergency-services training and transfers cleanly to incident response. Moving deliberately produces fewer errors, fewer errors mean less rework, and less rework arrives at the resolution sooner than hurrying does.
The failure it addresses is specific to pressure. Under stress people skip verification, act on the first hypothesis, run commands without reading them, and make changes in parallel so that nothing can be attributed. Each of those feels faster and each extends the incident, most expensively when a hurried change causes a second fault on top of the first.
The practices that operationalize it are unremarkable and hard to sustain: state the hypothesis before acting, make one change at a time, read the command before pressing return, and keep a running log so the sequence is reconstructible afterwards. The phrase earns its place because it gives a name to the instinct being resisted. Telling someone to calm down does not work; telling them that deliberate is the fast route is an argument they can act on while the pressure is still there.