Core Definition (BLUF)
Mission command is the Army’s approach to command and control that empowers subordinate decision making and decentralized execution. Commanders issue a clear purpose and end state, allocate resources, and require competent subordinates to adapt when the plan meets reality. It is not unrestricted freelancing. It is freedom inside intent.
Doctrinal Framework
- Pub: ADP 6-0 Mission Command: Command and Control of Army Forces (31 July 2019)
- Echelon: all; this garden applies it at detachment and small-team scale
- Coverage: full on principles; partial on C2 systems (philosophy over staff warfighting-function wiring)
- Lineage: Prussian Auftragstaktik after Jena; long US practice (illustrated in the pub across historical cases)
ADP 6-0 separates mission command (the approach / philosophy) from command and control (the function of directing forces). Earlier doctrine blurred the labels; use the 2019 framing.
Mechanics
Seven principles (ADP 6-0):
- Competence - leaders and teams can actually do the tasks; without this, decentralization is chaos.
- Mutual trust - flows both ways; built by shared experience, not slogans.
- Shared understanding - common picture of the problem, the enemy, and the purpose.
- Commander’s intent - clear purpose, key tasks, end state; understood two echelons up when possible.
- Mission orders - tell what and why, not every how.
- Disciplined initiative - subordinates act when the plan breaks, still inside intent and ethics.
- Risk acceptance - commanders underwrite smart risk; zero-risk cultures kill initiative.
Operating logic:
- Plans die at first contact; tempo favors the side that decides faster under uncertainty.
- Decentralize decision authority to the level that can see the fight.
- Push information down so initiative is informed, not blind.
- Build the culture in training and garrison, or it will not appear under pressure.
Application
At detachment / small-element scale:
- The commander (or team lead) writes intent as purpose + end state + constraints (legal, ROE, risk), not a script.
- Tasks are issued as mission orders: task, purpose, resources, deadline, backbrief required.
- Subordinates adapt when the site, adversary, or environment changes, then report.
- After-action reviews judge decisions against intent, not against verbatim plan compliance.
Example: advance element finds the primary facility compromised. Intent was a vetted, low-signature property inside a defined box. They execute the alternate that still meets intent and report the change - without waiting for permission to breathe.
Mission command pairs with Troop Leading Procedures (personal leader sequence) and Detachment Mission Planning (full team planning cycle). It fails if competence and shared understanding are assumed rather than trained.
Related Concepts
Enables: decentralized execution, tempo, disciplined initiative under friction.
Requires: competence, mutual trust, shared understanding, honest risk acceptance.
Pairs with: METT-TC (problem frame), Detachment Mission Planning, Troop Leading Procedures.
Contrasts with: detailed command (scripted control), pure freelancing without intent.
Failure Modes
- Intent as vibes - “make it secure” is not intent. No end state, no legitimate initiative.
- Mission orders that are still scripts - thirty mandatory steps signals no trust in competence.
- Trust without competence - decentralization without training produces preventable disaster.
- Punishment for honest initiative - one public hanging of a good-faith call and the culture dies.
- No shared understanding - two people, two missions, same label.