Commander's Intent: The Missing Link in Tactical Decision-Making

A 2008 Canadian Defence Academy study found a disturbing pattern: operations fail not because plans are bad, but because intent is misunderstood.

LCol Jeff Stouffer and Dr. Kelly Farley’s research, Command Intent: International Perspectives and Challenges, consolidates decades of military literature on one simple truth: if your team doesn’t understand why they’re doing something, they can’t adapt when things go wrong.

This post explores what makes commander’s intent work — and why most organizations get it wrong.

What Commander’s Intent Actually Is

Commander’s Intent is not a mission statement. It’s not a vision. It’s not a list of objectives.

Commander’s Intent: A concise statement of the purpose of the operation, the desired end-state, and key tasks. It provides the unifying focus that guides decision-making at all echelons, even when communications fail or the situation changes rapidly.

The Three Components

Purpose: Why are we doing this? What problem are we solving?
Desired end-state: What does success look like when we’re done?
Key tasks: What critical actions must happen to achieve the end-state?

What It’s Not

Commander’s Intent is not:

A detailed plan (that’s the operations order)
A list of constraints (those are limitations)
A suggestion (it’s the commander’s authoritative direction)
Static (it can be refined, but the core purpose remains)

The “What/Why” vs. “How” Distinction

This is the critical boundary that separates Mission Command from micromanagement.

What the Intent Provides

Element	Responsibility
What we’re achieving	Commander defines
Why it matters	Commander defines
When it’s needed	Commander defines (timing constraints)
How to do it	Subordinate decides

Why This Matters

When subordinates understand the what and why, they can:

Adapt methods when conditions change
Seize unexpected opportunities that advance the purpose
Make trade-offs that preserve the end-state
Act decisively when communications are degraded

When they only receive the how, they:

Wait for new orders when the plan breaks
Miss opportunities outside the prescribed method
Lack authority to make necessary trade-offs
Become paralyzed without explicit direction

Why Most Intent Statements Fail

Research from the Canadian Defence Academy identifies common failure modes:

1. Vagueness

Bad intent: “Secure the area and prepare for follow-on operations.”

Problem: What does “secure” mean? What area? What does “prepare” look like?

Better: “Establish control of Hill 234 and the valley corridor to prevent enemy reinforcement of Sector 7, enabling 2nd Battalion’s assault on D+2.”

2. Too Much Detail

Bad intent: “Move to Grid 4521, establish perimeter with sentries at 50m intervals, call for artillery on any movement beyond 200m, then report.”

Problem: This is a task list, not intent. It tells the subordinate how to do the job, not why.

Better: “Isolate the enemy battalion in Grid 4500 to prevent their withdrawal to the river crossing, enabling our main force to conduct a decisive engagement.”

3. Multiple Conflicting Purposes

Bad intent: “Minimize casualties while achieving maximum destruction of enemy forces and maintaining political neutrality.”

Problem: These objectives conflict. When forced to choose, the subordinate has no guidance on priority.

Better: “Destroy the enemy command node at Grid 3321. Risk to friendly forces is acceptable within the constraints of Rules of Engagement Section 4.”

4. No End-State Definition

Bad intent: “Conduct reconnaissance of the northern sector.”

Problem: When is this done? What constitutes successful reconnaissance?

Better: “Determine enemy disposition, strength, and movement patterns in Grid 4400-5500 by 1800 hours, enabling the commander to decide on assault or bypass by 2000 hours.”

The Cognitive Science of Shared Understanding

Dr. Oshin Vartanian’s research on intention integration reveals a critical insight: understanding intent isn’t passive reception — it’s active construction.

When a subordinate receives an intent statement, their brain:

Encodes the explicit information (the words)
Infers implicit context (the situation, constraints, priorities)
Integrates with existing mental models (training, experience, doctrine)
Validates through feedback (questions, confirmation, rehearsal)

The “Brief Synopsis” Test

Kearney’s research on corporate application of Mission Command recommends a simple validation technique:

Ask team members to give a brief synopsis of the instructions they’re given. This deliberate approach creates confidence and builds trust.

This isn’t about testing memory. It’s about revealing misalignment in understanding before it matters.

Building the Common Operating Picture

Shared understanding requires more than clear communication. It requires:

Calibration: Ensuring everyone interprets terms the same way
Context: Providing the situational background that makes intent meaningful
Rehearsal: Practicing decision-making within the intent framework
Feedback: Creating channels for questions and clarification

Intent Across Echelons: The Nesting Problem

Mission Command requires intent to flow downward while maintaining coherence. This creates the nesting challenge:

The Hierarchy of Intent

Strategic Level (National Command)
  ↓
Operational Level (Theatre Commander)
  ↓
Tactical Level (Battalion/Company)
  ↓
Execution Level (Platoon/Squad)

Each level’s intent must:

Align with the level above (support the higher purpose)
Enable the level below (provide meaningful guidance)
Remain distinct (not simply repeat the higher intent)

Where It Breaks Down

Common failure modes:

Translation loss: Each echelon rephrases intent, losing precision
Over-specification: Higher echelons dictate methods, removing subordinate discretion
Misalignment: Tactical actions don’t actually support operational objectives
Cognitive overload: Too many competing intents from different sources

The Opspex Solution: Encoding Intent for Machines and Humans

Opspex was built to solve the intent alignment problem at scale.

How Opspex Encodes Intent

Structured Intent Representation: Opspex captures commander’s intent in a formal, machine-readable format that preserves the purpose-end-state-key tasks structure across echelons.
Doctrinal Validation: Using ATP-112 (tactical formations) and ACP-125 (SALUTE reporting), Opspex ensures that tactical observations and actions align with doctrinal standards recognized across NATO forces.
Multi-Objective Scoring: The platform evaluates courses of action against weighted measures of effectiveness (MOEs) and measures of performance (MOPs) that reflect operational and strategic priorities — not just tactical success.
Intent Rehearsal: Teams can war-game deviations and see how their decisions cascade up or align with nested intents, building the shared understanding that makes Mission Command possible.

Practical Application

In Opspex’s Base Defense scenario (our first use case), the platform enables:

Company commanders to input higher-echelon intent (e.g., “maintain base integrity while shaping the information environment”)
Platoon leaders to test tactical variants (raid responses, defensive positions, reconnaissance pushes)
Real-time scoring of how each action contributes to or conflicts with broader objectives
After-action reviews that reveal misalignment before it becomes a problem

The Bottom Line

Commander’s Intent is the linchpin of Mission Command. Without it, decentralized execution becomes chaos. With it, empowered subordinates become force multipliers.

But intent isn’t just about writing a good statement. It’s about:

Precision: Clear purpose, defined end-state, prioritized tasks
Understanding: Validating that the team actually gets it
Alignment: Ensuring tactical actions support operational objectives
Rehearsal: Practicing decision-making within the intent framework

In our next post, we’ll explore why Mission Command fails — the trust gaps, competence issues, and communication breakdowns that turn theory into tragedy. And we’ll show how Opspex builds the “safe-to-fail” environment where teams learn to operate within intent.

References

Stouffer, J. & Farley, K. (eds.). Command Intent: International Perspectives and Challenges. Canadian Defence Academy Press, 2008.
Vartanian, O. “Judging Intention: Integrating Insights from Cognitive Science and Neuroscience.” In Command Intent, 2008.
Canadian Armed Forces. B-GJ-005-300/FP-001: Operational Art and Command.
U.S. Army. ADP 6-0: Mission Command.
Kearney. “Mission Command: Applying a Military Leadership Philosophy to High-Performance Teams.” February 2025.

← Previous: What is Mission Command?
Next: Why Mission Command Fails (and How to Fix It) →