Maneuver Warfare¶
Win by targeting the enemy's cohesion and decision-making rather than their mass — out-cycling and dislocating their command-and-control through five coupled commitments (schwerpunkt, OODA dominance, gaps-and-surfaces, mission command, maneuver) so their force cannot be brought to bear.
Core Idea¶
Maneuver warfare — articulated by Boyd, Lind, and the US Marine Corps, with roots in Blitzkrieg and Liddell Hart's indirect approach — holds enemy cohesion and decision-making, not enemy mass, as the primary operational object. Wins come from out-cycling and dislocating the opponent's command-and-control so their force cannot be brought to bear at the decisive point. It binds five coupled commitments: schwerpunkt, OODA-loop dominance, gaps-and-surfaces, mission command, and maneuver itself, defining itself against attrition warfare.
Scope of Application¶
The doctrine lives across the operational-doctrine subfields of military strategic studies; its reach is within that domain.
- US Marine Corps capstone doctrine — MCDP 1 Warfighting, the fullest codification.
- Land maneuver and joint campaign design — the 1940 Wehrmacht campaign, 1967 Israel, 2003 Iraq.
- Air and naval operations — the schwerpunkt/OODA logic wherever decision-cycle advantage rules.
- Counterinsurgency (inverted) — insurgents out-cycling a slower state's command cohesion.
- The attrition-warfare contrast — the rival mass-on-mass doctrine planners classify against.
Clarity¶
Naming maneuver warfare separates three things operational argument collapses: the doctrine (a bundled prescription), the primitive of maneuver (repositioning for advantage), and the rival doctrine of attrition. Its central wager becomes arguable — the object is the adversary's cohesion, not their mass — and a planner can ask whether an operation truly attacks the enemy's ability to decide or is an attrition contest in maneuver vocabulary. It also makes the doctrine's preconditions checkable rather than assumed.
Manages Complexity¶
Open-ended operational planning collapses to a small closed set of standing questions: where is the schwerpunkt, where are the gaps and surfaces, how does one's OODA cycle compare, does commander's intent license the tempo, what maneuver captures advantage. Because the five commitments are coupled — each worthless without the others — the planner tracks a handful of parameters and reads the outcome off their joint state, plus one load-bearing branch: maneuver campaign or attrition grind mislabelled.
Abstract Reasoning¶
The doctrine licenses a diagnostic classifying the operation, locating the seam, and auditing the coupled package against its preconditions, an interventionist stance attacking the decision system and refusing the attrition contest (with paired non-predictions from the coupling), boundary-drawing between doctrine and primitive and against attrition, and an order-of-events sequence that exploits decision-cycle disruption to deepen penetration self-reinforcingly.
Knowledge Transfer¶
Within military strategic studies the five-commitment package transfers as mechanism — vocabulary, diagnostics, precondition audit, and interventions carry across land, air, naval, and joint operations and the whole lineage from Blitzkrieg. Beyond the home domain the case is unusual: appearances in red-team operations, startup disruption, and organisational politics are deliberate analogical borrowings of the doctrine, vocabulary and all, not independent rediscoveries. What genuinely travels across substrates is carried by the component parents — OODA/feedback-tempo, subsidiarity, binding_constraint, maneuver — not by the named package.
Relationships to Other Abstractions¶
Current abstraction Maneuver Warfare Domain-specific
Parents (3) — more general patterns this builds on
-
Maneuver Warfare is part of Feedback Prime
The OODA competition is a feedback constituent in which observed effects update orientation and subsequent action.
-
Maneuver Warfare is part of Maneuver Prime
Positional maneuver is one of the doctrine's named coupled commitments and supplies advantage without direct resource contest.
-
Maneuver Warfare is part of Mission Command Prime
Mission command is the decentralized control architecture that lets maneuver warfare sustain tempo under changing local conditions.
Hierarchy paths (13) — routes to 7 parentless roots
- Maneuver Warfare → Feedback
- Maneuver Warfare → Maneuver → Positional Advantage → Asymmetry
- Maneuver Warfare → Mission Command → Coordination → Concurrency
- Maneuver Warfare → Mission Command → Coordination → Dependency
- Maneuver Warfare → Mission Command → Authority Delegation Under Uncertainty → Delegation of Authority → Authority
- Maneuver Warfare → Mission Command → Goal Congruence (Alignment) → Coordination → Concurrency
- Maneuver Warfare → Mission Command → Coordination → Task Interdependence → Dependency
- Maneuver Warfare → Mission Command → Goal Congruence (Alignment) → Coordination → Dependency
- Maneuver Warfare → Mission Command → Coordination → Mobilization → Latent Realizable Capacity
- Maneuver Warfare → Mission Command → Goal Congruence (Alignment) → Coordination → Task Interdependence → Dependency
- Maneuver Warfare → Mission Command → Goal Congruence (Alignment) → Coordination → Mobilization → Latent Realizable Capacity
- Maneuver Warfare → Mission Command → Coordination → Task Interdependence → Network → Reservoir-Flux Network → Conservation Laws → Invariance
- Maneuver Warfare → Mission Command → Goal Congruence (Alignment) → Coordination → Task Interdependence → Network → Reservoir-Flux Network → Conservation Laws → Invariance
Neighborhood in Abstraction Space¶
Maneuver Warfare sits in a crowded region of the domain-specific corpus (31st percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Unclustered & Miscellaneous (309 abstractions)
Nearest neighbors
- Commander's-Intent Ambiguity — 0.87
- Target Fixation — 0.87
- Operational Pause — 0.85
- Attrition Trap — 0.85
- Centipede Game — 0.84
Computed from structural-signature embeddings · 2026-07-12