The Kill Chain Has a Thinking Problem - by Won YI

Fox and Lion

SubscribeSign in

The Kill Chain Has a Thinking Problem<br>Speed is not the bottleneck in modern command. Judgement is.

Won YI<br>Jun 08, 2026

Share

Moltke is often reduced to a single line: “No plan survives contact with the enemy.” The tacit admission behind it: the battlefield cannot be predicted or controlled, only navigated.<br>The central vulnerability in the modern kill chain is not sensor range or data throughput. It is the moment when information becomes a valid basis for action. A system can be fast, and apparently confident, while the ground on which that confidence rests is still degraded, incomplete, or contested.<br>This gap matters.

Subscribe to Fox and Lion for the latest defence analyses, jobs, news, and more.

Subscribe

The Clock Has Changed

The logic Moltke pointed toward later crystallised as Auftragstaktik: commanders express intent, subordinates decide method. The space between is filled with judgement. That logic has not disappeared, but the clock it runs on has changed in ways not fully reflected in modern-day doctrines.<br>Across multinational exercises, the same pattern appears. Systems are connected. Data is transmitted. Decisions - still arrive late. The cause is usually not a failure of interface, it is a mismatch of tempo. Command structures operate on one tempo, the operational environment moves on another.<br>The window between sensing, interpreting, deciding, and acting has compressed to seconds. NATO interoperability has improved how systems talk to each other, but it has not changed how people think. Data flows across coalition networks - while humans interpret the same picture through different mental models, different national constraints, and different institutional habits.

Soldiers with the Kansas Army National Guard prepare a rock drill prior to a combined-arms rehearsal at the National Training Center.<br>This is not a new problem. Before digital solutions arrived, armies used something much simpler: a rock drill. Commanders moved stones in the dirt to build a shared picture before the fighting started. This was not just primitive visualisation, it was a tool for aligning decision-making under pressure. Stones and dirt were just the medium. The problem it addressed persists.

Autonomy Improves Execution. It Does Not Replace Command.

When human cognition lags behind the battlefield tempo, the instinctive answer is to add sensors, accelerate processing, and push autonomy further to the edge. Cut the human out where latency appears to be the bottleneck.<br>That can indeed improve execution speed, but command quality is a different problem.<br>A more fundamental issue arises when several valid things are true at once. Sensor data, prediction models, command intent, coalition rules of engagement (ROE), and national caveats can all be valid, without pointing in the same direction. Under normal tempo, those differences can be resolved through coordination or escalation. Under compressed tempo, that window closes before a resolution is possible. Acting before loss of track may mean moving before identity is confirmed; clearing coalition authority may take longer than the tactical window allows.<br>Consider what this looks like in practice. A UAS feed drops, but the telemetry remains active. An EW system reports effect achieved, but no command node has confirmed authority over the next action. A model predicts target movement, but ROE still requires positive identification before action. Each input is valid, yet cannot be the sole basis for a decision. The decision problem is no longer speed, it is whether there is a sound enough basis to act at all, while the clock is counting down. Validity under compression .<br>Most current command architectures have no good way to make that kind of tension visible. Their instinct is to fuse: take multiple inputs and resolve them into a single, cleaner picture. That is genuinely useful, most of the time. The problem arises when the conflict is not between competing data points but between competing valid obligations.<br>A system built around fusion will still produce an output, but to do that, it must resolve those tensions somewhere. It usually does so silently, without flagging which obligation was deprioritised or giving the commander the chance to make that call deliberately.<br>The conflict does not disappear. It just gets buried.

The Missing Layer

There is a layer missing between machine action and command intent. It is not hard to describe, though it is difficult to build. It needs to keep conflict visible before the system turns it into a single, clean, and possibly false answer. It needs to show which truths are in play, where they conflict, what each course of action costs, and who has authority to move next, given current conditions. This is what a sound decision basis looks like.<br>That shift must be dynamic. In a five-second decision cycle, rigid hierarchical authority models produce the...