Mission Command,
from doctrine to code.
Field notes on how decentralised command actually works, why it fails, and how we encode it in software built for the tactical edge — where the network is contested and the decision can't wait.
What is Mission Command? From Prussian Tactics to Modern Operations
How a 19th-century Prussian insight — that orders go stale the moment they leave headquarters — became the doctrine (CAF, US Army ADP 6-0, NATO AJP-01) for winning in chaos.
Read →Commander's Intent: The Missing Link in Tactical Decision-Making
Operations fail not because plans are bad, but because intent is misunderstood. What makes commander's intent work — and why most organizations get it wrong.
Read →Why Mission Command Fails (and How to Fix It)
Mission Command demands more from everyone, but most organizations are built to punish the very behaviours it requires. Why it fails in practice — and how to fix it.
Read →From Doctrine to Software: Encoding Mission Command in Opspex
Doctrine sits on shelves. How Opspex encodes commander's intent in software so it travels across echelons — and holds up when communications are jammed.
Read →Base Defense: The Perfect Mission Command Training Scenario
Every training establishment runs Base Defense. Most do it wrong. Why it's the anchor scenario for learning Mission Command at the tactical edge.
Read →Offline-First Design: Mission Command in Denied Environments
When comms die, doctrine keeps you alive. Why Opspex is built to run in denied, jammed, and disconnected environments from the ground up.
Read →The Future of Tactical Edge Computing: LVC, Digital Twins, and Intent-Driven Warfare
The next generation of warfighting isn't about better guns — it's about faster OODA loops. LVC, digital twins, and intent-driven decision support at the tactical edge.
Read →Want the platform behind the theory?
These ideas are built into the Opspex platform. If they map to a problem you own, let's talk.
Get in touch