Decentralized command

Push decisions to the people closest to the problem, bounded by a clear commander's intent.

Why it works

A single leader cannot process every front-line decision fast enough; centralizing creates a bottleneck and slow, stale calls. Decentralizing — within explicit intent and boundaries — lets the people with the freshest information decide, which is faster and usually better. The clear intent is what keeps decentralized decisions coherent rather than chaotic.

How to do it

1. State the intent (the why and the end state) and the boundaries, then delegate the how.
2. Make sure each person knows what decisions are theirs to make without asking.
3. When someone escalates a decision they could own, hand it back with the context to make it.

Evidence

Decentralized command is the U.S. military "mission command" doctrine (rooted in Prussian Auftragstaktik). It parallels research on autonomy and on the speed/quality benefits of pushing decisions to where the information is. (mechanistic)

Decentralization fails without a genuinely clear intent and capable, trusted people; delegated authority into a vacuum produces inconsistency, not initiative.

Sources

• Mission command doctrine (U.S. Army ADP 6-0); roots in Auftragstaktik

Common mistake

Delegating tasks but not the authority to decide — so people still must ask permission for everything, recreating the bottleneck while calling it empowerment.