Commander's Intent

011 min

Commander's Intent at a glance

• What it is: A short statement of purpose and desired end state, written for people who must improvise.
• Origin: Prussian mission-type command under Moltke; defined today in US Army doctrine ADP 5-0 (2019).
• Use it when: Other people will carry out work, and conditions may change before you can reply.
• Watch for: A statement that repeats the mission, or lists tasks, is not an intent.

022 min

The problem Commander's Intent solves

A plan is a list of steps written at one moment, for the conditions known at that moment. Conditions then change. ADP 5-0, the US Army's doctrine on how operations are run, says that no plan can account for every possibility and that most plans must change rapidly during execution if they are to succeed.

The person who wrote the plan is often not present when it stops fitting. The person carrying it out has three options. They can follow the steps even though the steps no longer make sense. They can stop and wait for new orders. Or they can improvise without knowing what the leader needs. The first two waste time or cause harm. The third is a guess.

The receiver pays the cost first. They face the changed situation alone, and they are blamed afterwards for whichever option they chose. The sender usually finds out later.

The sender also makes the problem worse without noticing. The sender knows the reason behind every step, so the reason feels too obvious to write down. This is the curse of knowledge: once you know something, it is hard to imagine what the other person does not know. Commander's intent is a fixed place in the message where the reason is written down on purpose.

Chip and Dan Heath describe the same pattern outside the army: in business, no sales plan survives contact with the customer, and in a classroom, no lesson plan survives contact with teenagers. Their answer is the same in every case. Say the most important goal in a form that still works after the plan breaks.

032 min

How Commander's Intent works

ADP 5-0 defines the statement by what it does for subordinate commanders: it helps them act to achieve the commander's desired results without further orders, even when the operation does not unfold as planned. A subordinate is a person at a lower level of command who carries out part of the work.

The doctrine gives the statement three parts.

Two rules from the same text shape how the statement is written. First, commanders write the intent themselves. Second, it must be easy to remember and clearly understood by commanders and staffs two echelons lower, meaning two levels of command below the author. The shorter the statement, the easier it is to understand and recall.

The mechanism is a change in what the subordinate checks. A plan says what to do. An intent says what must still be true after the work is done. When a plan step stops fitting, the subordinate asks two questions about each option. Does it serve the purpose? Does it move the situation toward the end state? Any option that passes both is allowed, even if no one planned it.

Key tasks add something the end state alone does not give. When the plan no longer fits, subordinates use key tasks to keep their efforts focused on the end state. A subordinate may change their own steps, but the key tasks name what the whole group still has to do.

This only works if the subordinate is allowed to decide. ADP 5-0 says mission command requires an environment of trust and shared understanding among commanders, staffs and subordinates. Shared understanding is the same idea as common ground: both sides know what the other side knows. The doctrine pairs intent with mission orders. Through mission orders, commanders focus leaders on the purpose of the operation rather than on the details of how to perform assigned tasks.

041 min

A Commander's Intent template

A statement with the three doctrine parts can be written for any team. Fill in each line with one sentence. If a line needs more than one sentence, the line is probably carrying a plan step.

Read the statement aloud to someone two levels below you. Ask them what they would do if their first step failed. If the answer surprises you, the statement is not clear yet.

051 min

Where Commander's Intent comes from

The idea is older than the phrase. Field Marshal Helmuth von Moltke of Prussia wrote that officers face many situations in which they must act on their own view. In his words, it would be wrong if an officer had to wait for orders at times when no orders can be given. But most productive are his actions when he acts within the framework of his senior commander's intent. ADP 5-0 prints this passage at the start of its section on mission command.

The Prussian style of command is called Auftragstaktik, which means mission-type tactics. A commander gives subordinates a clear objective, a timeframe and the forces they need. The subordinates choose the methods. Wikipedia's summary of the history says the Prussian army rethought its methods after its defeat by Napoleon at Jena-Auerstedt in 1806.

The current US Army definition is in ADP 5-0, dated 31 July 2019. This article did not confirm in which year the exact phrase "commander's intent" first entered US doctrine, so it gives no date. It is a doctrinal concept from military practice. It is not a research finding, and the evidence for it is doctrine and experience.

061 min

Two real uses of Commander's Intent

The two cases differ in one variable: how much the statement contains. The army statement has a purpose, key tasks and an end state. Southwest's line is a purpose only. It is enough for daily choices such as whether to add a free service, because every employee can test the idea against it. It does not say what the company should look like at the end of a project, so it cannot guide a project the way an army intent can.

072 min

A worked example for a software team

This example is illustrative. A staff engineer leads a team of four that must move seven years of customer order history from an old database to a new one over a weekend. The plan lists the order of tables and the time for each.

Before: The staff engineer sends the plan only. "Migrate the tables in this order. Table A first, then B, C and D. Start Saturday at 22:00."

On Saturday night, an engineer finds that table C has rows with missing dates. The plan says to migrate C next. The engineer can run the migration and lose the rows, or stop and wait. The staff engineer is asleep. The engineer waits for three hours.

After: The staff engineer sends the same plan with an intent.

The same engineer finds the same missing dates. They check the options against the intent. Dropping the rows breaks the end state, because an order would be lost. Waiting for a reply delays the purpose. The engineer migrates the rows with valid dates, copies the rows with missing dates to a holding table so that no order is lost, and continues with table D. They leave a note saying which orders are not yet searchable.

The structural change is that the "After" message names what must stay true. It does not name more steps. The engineer chose a step no one had written, and it was still the one the staff engineer would have wanted.

The same pattern fits other roles.

081 min

A script to use tomorrow

Add the intent to the message you already send. These lines can be pasted into a chat or said in a meeting.

• "Here is the plan. The reason for it is [purpose]. When it is done, [end state] should be true."
• "If a step stops working, use your judgment. Choose the option that still gets us to [end state]. You do not need to ask me first."
• "Tell me what you would do if [the step most likely to fail] fails. I want to check that you and I would choose the same thing."

The last line is a check. Doctrine asks that the intent be understood two levels down. This question tests it before the work starts.

091 min

The overuse trap

The adjacent trap is micromanagement with an intent attached. The author writes the statement, then still expects to approve each decision. The tell is that people keep asking permission for choices that sit inside the intent. They stop trusting that the statement is real.

There are other ways it fails.

• The statement repeats the mission. ADP 5-0 says the purpose in the intent does not restate the why of the mission statement. If the intent and the task say the same thing, the subordinate learns nothing new.
• It is a list of tasks. A subordinate cannot choose a new step from a list of old ones. The tell is that every line starts with a verb and none says why.
• It is too long or too full of jargon. A British Army officer, Captain Andy Wiltshire, wrote in 2021 that intent statements can be hard to understand, especially for junior commanders and staff. A statement that nobody can remember is not available when the plan breaks.
• The situation changed but the intent did not. If the purpose itself is no longer true, subordinates will follow words that no longer describe the goal. The fix is a new statement, not a longer one.
• The subordinate has no authority to act. Doctrine treats trust as a requirement. Without it, the intent is read and then ignored.

101 min

Commander's Intent vs. nearby concepts

Three neighbours are often mixed up with it. The deciding axis in each case is what the statement is for.

A business goal such as "reach 10,000 users" is also not an intent. It states a result but not the purpose behind it. A subordinate who sees only the number may reach it in a way that defeats the reason it was set.

The cooperative principle in conversation is a looser relative. It describes how speakers try to give a listener the amount of information the listener needs. Commander's intent applies the same attention to one job: it chooses the information the listener will need when the plan fails.

112 min

Where the evidence for Commander's Intent is contested

Three points are open to challenge.

The Prussian history is overstated. Auftragstaktik is often said to have given the Prussians their victory at Königgrätz in 1866. The Wikipedia article on Auftragstaktik says that claim is difficult to accept, since no appreciation of Auftragstaktik had been officially accepted at that time. It adds that some Prussian commanders acted against orders, which is not the same as acting within a clear intent. The fair reading is that the practice has Prussian roots, but the doctrine was written later and its early results are disputed. The article is a general reference, not a peer-reviewed history, so this claim needs checking in military histories before it is repeated.

Written statements often fail in practice. Wiltshire argues that British Army intents are full of effects verbs, objective names and acronyms, which makes them hard for junior readers. He says the doctrine's structure is sound but rarely followed. This is one practitioner's experience, not a measured study. It shows a practical risk: the idea is easy to state and hard to write well.

There is little controlled evidence that it improves results. The sources used here are doctrine, a practitioner's opinion and the Heaths' examples. The Heaths use a company slogan as an example, but ADP 5-0's definition asks for more than a slogan: it asks for purpose and an end state. None of the sources tested teams with and without an intent statement.

For a practitioner, the useful response is to test it locally. Write one statement. Ask two people at a lower level to say it back and say what they would do if the plan failed. If they differ from you, the statement needs another draft.

?8 questions

Questions people ask

▶3 videos

Watch

• 

  Understanding Commander's Intent

• 

  Decision Making: Commanders Intent

  Cascade Rifles

• 

  K6 Sends - Commander's Intent - Podcast 1

  16th Sustainment Brigade

§4 sources

Sources