Commander's Intent

TL;DR

Commander's Intent: Communicate what success looks like and why — not just what to do. When your team knows the end-state you're trying to achieve, they can adapt their actions intelligently when plans break down, rather than waiting for orders that may not arrive.

What Is Commander's Intent?

The problem Commander's Intent solves is ancient: no battle plan survives contact with the enemy. By the time an order works its way down a military chain of command, conditions have changed. A unit that executes orders literally — regardless of whether those orders still make sense given current reality — is dangerous. But a unit that improvises without guidance is equally dangerous.

Commander's Intent is the bridge. It is a brief, clear statement that appears at the top of every US Army operations order, specifying: (1) what the commander wants to achieve, (2) why it matters (the higher-level goal it serves), and (3) what the end-state looks like. It is not a list of tasks. It is a statement of purpose — specific enough to guide decisions, brief enough to be memorized.

The formal doctrine was developed in the US Army in the late 1970s and 1980s as a response to studies of failed military operations. The research found that execution failures were often not due to poor orders but to junior officers who, when orders became inappropriate due to changed conditions, didn't know what decision to make in their commander's absence. They defaulted to literal compliance or froze.

The fix was counterintuitive: give less guidance about tactics, and more guidance about purpose. A soldier who knows the commander wants to "secure the bridge so that the division can cross at dawn" can make reasonable tactical decisions if their squad's original approach is blocked. A soldier who only knows "take the northwest corner of the bridge" cannot.

The principle has since been adopted well beyond military contexts — in product development (Amazon's Working Backwards defines the end-state before any tasks), in organizational design (OKRs attempt to do something similar), and in any leadership context where teams need to make decisions autonomously.

How It Works

Commander's Intent Format (US Army Standard)

1. Purpose (the "why")
   "We are securing this position in order to enable..."
   One level up from the current mission — why does this matter?

2. Key Tasks
   The 2-4 things that absolutely must happen for the mission to succeed.
   Not an exhaustive task list — the load-bearing requirements.

3. End-State
   What does success look like when the mission is complete?
   Described specifically enough to be recognizable.
   "The bridge is secured, all enemy forces have withdrawn from
   the north bank, and our forces control the crossing point."

The test:
  A subordinate who has read only the Commander's Intent
  and received no further orders should be able to:
  (a) recognize success when they see it
  (b) make reasonable tactical decisions when original plans fail
  (c) explain their decisions in terms of the stated purpose

Three Real-World Examples

The Battle of Gettysburg (1863)

Confederate General Robert E. Lee's famous order on the second day of Gettysburg was to attack "if practicable" — a formulation that left significant discretion to General Longstreet, who interpreted it as permission not to attack when he judged conditions unfavorable. The resulting delay is widely analyzed as a missed opportunity.

The historical lesson: Commander's Intent requires specificity about what "success" looks like, not just permission to act. Lee communicated a task ("attack") but not a clear end-state or purpose clear enough to guide Longstreet's decision about timing and commitment. Compare to the Union Army's situation: General Meade communicated a clear intent to hold the high ground — enabling corps commanders to make mutually reinforcing decisions without real-time coordination.

Amazon's PR/FAQ

Jeff Bezos's Working Backwards process requires teams to write the press release and FAQ before designing a product. The press release is, functionally, Commander's Intent: it specifies what success looks like (a product customers love, described in their language) without prescribing how to achieve it. Engineering, design, and product teams can then make independent decisions aligned toward that end-state.

This solved a problem Amazon had at scale: teams were receiving feature requirements and executing them literally without understanding why — leading to products that met specs but missed the point. Working Backwards forced the purpose to be specified first.

SpaceX Mission Definition

SpaceX's mission — "making humanity multiplanetary" — functions as Commander's Intent at the company level. It is specific enough to guide decisions: reusability is required (single-use rockets are incompatible with the economics of multiplanetary transport). But it doesn't prescribe how reusability is achieved, what the timeline is, or which planet comes first.

When engineers face a design decision, they can evaluate options against the mission intent without requiring Musk to adjudicate every choice. The intent filters the decision space without specifying every decision.

When to Use It

✅ Use Commander's Intent when:

Leading teams in high-uncertainty environments where conditions change faster than orders can be issued
Communicating a project goal to a team that will work semi-autonomously
Delegating significant decisions to people with less context than you have
Designing organizational structures where teams need to make decisions at the edges without constant escalation
Setting quarterly or annual organizational goals (OKRs are an attempt at this)

❌ Use cautiously or differently when:

Highly procedural tasks where literal compliance is exactly right (manufacturing, surgical procedures)
Situations where the team lacks the skill or judgment to translate intent into appropriate action
When the intent is genuinely ambiguous even to the leader — communicate what you know, clarify what you're uncertain about

Pairs well with	Why
Precommitment	Intent is the precommitment of purpose; individual teams execute
OODA Loop	Intent enables fast OODA cycling without re-escalation at each step
Two-Way Door	Commander's Intent is most valuable for Two-Way Door tactical decisions
Scenario Planning	Scenarios define which intents apply under which conditions

Common Misuses and Limitations

Confusing Commander's Intent with vague goals. "Grow the business" is not Commander's Intent — it lacks specificity about what success looks like and why this mission matters to the higher-level goal. Commander's Intent is precise about the end-state even when it's not precise about tactics.

Using it as a substitute for adequate context. Commander's Intent assumes the team has sufficient skill and contextual knowledge to translate purpose into appropriate action. If they don't — if they're new to the domain or operating in an unfamiliar environment — they also need training, context, and more explicit guidance.

Failing to cascade it. In a hierarchy, every level needs its own Commander's Intent, consistent with the level above. The company's intent → the division's intent → the team's intent. If the company communicates intent but divisions then issue only task lists, the benefit doesn't reach the front line.

Not updating the intent when strategy changes. If the situation changes materially and the stated intent is no longer correct, teams operating under the old intent will make rational but wrong decisions. Keeping intent current is the leader's ongoing responsibility.

OODA Loop — Commander's Intent enables fast OODA cycling at the team level without escalation
Precommitment — both models involve binding future decisions to an existing framework
Scenario Planning — scenarios are the context within which different intents apply

FAQ

How is Commander's Intent different from just setting goals?

Goals specify what to achieve. Commander's Intent specifies what success looks like, why it matters (the next level up), and which 2–4 things must happen for the mission to succeed. It is richer and more directional than a goal, specifically designed to enable correct autonomous decision-making when plans break down. A goal says "increase retention by 10%." Commander's Intent says "by end of Q3, customers in the enterprise segment have successfully onboarded and are using at least 3 core features, enabling us to unlock the upsell motion in Q4."

How long should a Commander's Intent be?

Brief enough to be memorized — 1–3 paragraphs in military doctrine. The test is whether a team member who has read it once can act consistently with it under pressure without referring back. If it requires constant re-reading, it's too complex. Jeff Bezos's PR/FAQ runs longer, but the "press release" section — the true intent statement — is usually one page.

What's the "one level up" principle?

Commander's Intent should always reference the purpose one level above the current mission. The platoon commander's intent references the company commander's goal. The product team's intent references the business objective it serves. This enables teams to make intelligent trade-offs: if achieving the stated task would actually undermine the higher-level purpose, they should escalate or adapt — not comply blindly.

Apply with AI

🚀 Write your Commander's Intent in MindMax →

What Is Commander's Intent?​

How It Works​

Three Real-World Examples​

The Battle of Gettysburg (1863)​

Amazon's PR/FAQ​

SpaceX Mission Definition​

When to Use It​

Common Misuses and Limitations​

Related Models​

FAQ​

Apply with AI​

Further Reading​