no plan survives contact
expressionops culturesecurity
Moltke's maxim: the plan is what you have until reality responds, then adaptation is the actual skill.
Field marshal Helmuth von Moltke's original point was not to skip planning but to plan for deviation - which is exactly the argument for incident runbooks that rehearse decision-making rather than script it, and for DR tests that expect surprises.
No plan survives first contact with the enemy is Moltke's observation, and the part usually omitted is what he concluded from it. He did not argue against planning; he argued that the value of planning is the understanding it produces rather than the document it emits, because the understanding is what lets you improvise when the plan fails.
In incident response the application is direct. The runbook will not cover the actual failure, because failures that were anticipated were usually prevented, and what remains is the combination nobody modelled. Yet teams that have written and rehearsed runbooks handle novel incidents markedly better than teams that have not, and the reason is that they have thought about the system's failure modes, know where the tools are, and have practised working together under pressure.
That reframes what a plan is for. A rigid plan followed literally in conditions it did not anticipate is worse than no plan, so the useful artefacts are the ones that support improvisation: clear ownership, a decision-making structure, accurate diagrams, accessible tooling and rehearsed communication. The plan is scaffolding for judgement rather than a substitute for it.
Also known as: no plan survives first contact