Commander’s intent

What it is

Commander’s intent is a short statement fixing three things before people disperse: why the action is being taken, what must remain true whatever else changes, and what the finished state looks like. It is written for the person who cannot reach you when conditions turn. The detail of the plan stays negotiable. The purpose does not.

Where it comes from

The practice is Prussian. Helmuth von Moltke the Elder, chief of the Prussian General Staff from 1857, set it out in his Instructions for Large Unit Commanders of 1869. Detailed orders reaching beyond the immediate situation are usually worthless, he argued, because every movement changes the conditions they assume. A directive should state the aim at the top and let subordinate commanders add the detail they can see, acting on their own judgement rather than waiting for orders, so long as the action serves the superior’s aim. German doctrine later called the method Auftragstaktik, a label coined by the officers who opposed it.

The English phrase belongs to the United States Army. The 1982 edition of Field Manual 100-5, Operations, first carried doctrine resembling Auftragstaktik, the 1986 edition adopted mission orders outright, and the 1993 edition asked commanders for the “willingness and ability to act independently within the framework of the commander’s intent” (Gunther, 2012). ADP 6-0 of 31 July 2019 now defines it as a clear and concise expression of the purpose of the operation and the desired end state, one that helps subordinate commanders act “without further orders, even when the operation does not unfold as planned”. Chip and Dan Heath took the term into business writing in Made to Stick (2007).

What it corrects

The situation is distributed execution: people acting at once, conditions changing faster than anyone can be consulted. A competent person answers with a thorough plan, and thoroughness is the trap. The more specific the plan, the more assumptions it embeds about facts that will have moved by Tuesday. When they move, the work splits two ways. Some keep executing instructions that no longer serve any purpose, because the instruction is what they were given. Others improvise, sensibly, toward goals that turn out to differ from each other. Ordinary care does not help, because care is spent on detail, and detail is the perishable part. Nothing in a long plan tells the reader which lines were load-bearing and which were one way of many.

How it works

1. State the purpose in one sentence: why this is being done at all.
2. Describe the end state in observable terms, so someone else can tell when it has arrived.
3. Name the two or three conditions that must hold whatever else changes.
4. Say what is delegated and to whom, by name, including the freedom to leave the plan.
5. Give a default for lost contact: what to do when the plan no longer fits.
6. Delete every instruction that need not be decided centrally.

Worked example

Nelson’s memorandum, marked secret, was written aboard Victory off Cadiz on 9 October 1805. Its arithmetic assumed forty sail: two lines of sixteen ships and an advanced squadron of eight. Its purpose was an end state rather than a manoeuvre, the enemy fleet “captured or destroyed” rather than driven off. Its delegation was explicit: “The second in command will, after my intentions are made known to him, have the entire direction of his line.” Something must be left to chance, he wrote, and he covered that gap with a default: “in case signals can neither be seen nor perfectly understood, no captain can do very wrong if he places his ship alongside that of an enemy.”

Twelve days later almost none of that arithmetic held. At Trafalgar on 21 October the British had 27 ships of the line against 33, no advanced squadron was formed, and the fleet went in as two columns. Nelson was shot early and died three hours later, at half past four. Collingwood took over. Eighteen of the 33 Franco-Spanish ships were captured or destroyed and no British ship of the line was lost. The plan’s numbers did not survive the first hour. The purpose, the delegation and the fallback did, which is why no captain waited for an order that could no longer come.

In a Business Case Weekly case

In the McDonald’s case, the value war of 2024 reaches a company roughly 95 percent franchised, so headquarters cannot simply order the discount: it is funded from other people’s margins, and each owner reads their own unit economics. That is the fork where commander’s intent does work. It asks what must remain true for the system whichever promotion runs, what end state would count as proof that value has been re-earned, and on what condition an operator may leave the corporate plan without breaking the promise. The case still asks you to cast the vote and name your number; intent settles only what it is about.

In your answer

• “The purpose of this decision is …, and it holds even if the mechanism changes.”
• “Whatever else moves, these two things must remain true: …”
• “We will know the end state has arrived when …”
• “Where the plan cannot be followed, the default is …, and … decides locally.”

Common misuse

The common counterfeit is a slogan. “Win on value” names an ambition and settles nothing, because it gives no basis for the trade-off it will be used to justify. The test: hand the statement to two capable people separately, give each the hardest local choice, and see whether they reach the same answer without calling you. If they do, it is intent. If they call, you wrote a mood. A subtler failure: an intent carrying ten non-negotiables is a plan in a purpose’s clothes, and it removes the judgement it claims to license.

References

• Julian S. Corbett, ed., Fighting Instructions 1530–1816 (Navy Records Society, 1905). Prints Nelson’s memorandum of 9 October 1805 in full: two pages, the shortest way to see the method on paper. gutenberg.org/ebooks/16695
• ADP 6-0, Mission Command: Command and Control of Army Forces (Headquarters, Department of the Army, 31 July 2019). Paragraph 1-45 carries the definition. The official link has moved; a mirrored copy sits at irp.fas.org/doddir/army/adp6_0.pdf
• Michael J. Gunther, Auftragstaktik: The Basis for Modern Military Command? (School of Advanced Military Studies, US Army Command and General Staff College, 2012). Moltke’s 1869 instructions through to FM 100-5, in an evening: the DTIC record
• Wikipedia, Battle of Trafalgar, for fleet strengths, losses and the hour of Nelson’s death.