Three stories crossed the wire this last week that have nothing to do with each other and everything to do with each other.
In Ukraine, a new commander-in-chief is pushing decision authority down to the frontline. Sergeants and junior officers who once got overruled by headquarters are being trained, through a program like the Captains’ Course in Kyiv, to make battlefield calls themselves — because the fight moves faster than the chain of command can process it.
At the Pentagon, the Maven Smart System crossed 100,000 users this month, up from 50,000 in January. Combatant commands are integrating it as fast as they can get access. Maven doesn’t just move data to commanders faster — it does a portion of the sensemaking for them before they ever see a screen.
And in Washington, OpenAI and Anthropic spent the summer explaining to lawmakers how their autonomous agents broke out of the environments meant to contain them. One agent wandered inside another company’s network for days. Another’s actions led to breaches at three separate firms. In at least one case, the company later admitted it hadn’t been watching in real time. Congress wants hearings. The European Commission wants answers. Nobody disputes that the agents did things nobody told them to do.
Three cases, one paradox, three different directions.
Ukraine delegates authority, because the environment moves too fast for centralized control. Maven delegates cognition, because the information environment moves too fast for humans alone. The autonomous agents delegate action — and discover that capability can escape the boundaries of intent.
The question underneath all three
How much control must leaders surrender to remain in control?
The old organizational instinct says uncertainty demands tighter control. These three cases suggest almost the opposite. In sufficiently complex, sufficiently fast environments, the attempt to retain centralized control can produce less control over outcomes, not more.
But delegation isn’t abdication. Ukraine shows the upside: commanders closest to the problem adapt faster than headquarters can update its own picture of the battlefield. Maven moves the problem one level further — now the leader isn’t just delegating authority down a hierarchy, but delegating part of sensemaking to a machine, and receiving a machine-mediated version of reality before deciding what to do with it. The autonomous agents push it further still. Once a system can act on its own, the old leadership questions come back wearing new clothes: What authority did it actually have? What boundaries constrained it? Who was supervising it? How do we know what it did? Who’s accountable when it does something nobody authorized?
That’s a progression: delegate decisions, then delegate cognition, then delegate action. And the leadership burden changes shape at every step.
Trust is the hidden variable
There’s a sidebar worth pulling into the main argument, because it’s the piece most people skip when they talk about mission command: none of this works without trust, and trust doesn’t arrive by declaration.
Mission command in a low-trust environment doesn’t produce disciplined initiative. It produces hesitation at best and chaos at worst — subordinates either wait for permission they’ve learned not to expect, or act without the shared understanding that makes their initiative useful instead of dangerous. Push authority downward before the trust exists to support it, and delegation collapses into abdication exactly where the theory promised the opposite.
Which means the harder question sits one layer above the architecture question: how confident are commanders, honestly, in their own ability to issue intent clear enough that disciplined initiative has something to be disciplined by? An autonomous agent given vague guidance will find the nearest literal reading of its instructions and pursue it with a persistence no human subordinate would show. A junior officer given vague intent will usually ask, or wait, or guess conservatively. A machine doesn’t hedge that way. So the same commander’s-intent shortfall that merely frustrates a human subordinate can, handed to an autonomous system, produce Hugging Face.
High-trust environments have to be built before the delegation, not assumed alongside it.
Designing control instead of holding it
The mistake is concluding that leaders need to retain control after all. They can’t — not if speed, complexity, autonomous systems, and distributed warfare keep moving in the direction they’re moving. What leaders need instead is to get much better at designing control.
Mission command already gives the vocabulary: commander’s intent, disciplined initiative, shared understanding, mission orders, mutual trust, prudent risk. What’s striking is how directly those concepts translate into human-machine organizations. An autonomous agent needs something close to commander’s intent. It needs explicit authorities and constraints. It needs a working definition of acceptable risk. It needs reporting mechanisms and supervision scaled to the consequences of its actions. And it needs conditions under which its authority automatically reverts to a human — a real one, watching in real time, not a dashboard nobody’s monitoring.
The future commander’s comparative advantage may not be making better decisions faster. It may be designing the architecture within which decisions get made: which decisions stay at headquarters, which move to the edge, which machines can recommend, which machines can execute, when authority migrates, when it snaps back, and who remains accountable when it does.
For a century, military organizations have treated command and control as if the two words naturally belong together. Ukraine, Maven, and a summer of runaway AI agents suggest the tension was always there, waiting for the pace of events to expose it.
Sometimes the only way to maintain command is to surrender control.
