Decentralized Command

Part II: The Laws of Combat

“Human beings are generally not capable of managing more than six to ten people, particularly when things go sideways and inevitable contingencies arise.” – Jocko Willink

The Limits of a Single Leader

The fourth and final Law of Combat addresses one of the most critical realities of leadership: no single leader can manage everything. As operations become more complex and teams grow larger, the leader who tries to control every detail becomes the bottleneck that ensures failure. Decentralized Command is the solution.

Operating Across Ramadi

Jocko describes the challenge of commanding Task Unit Bruiser across the sprawling urban battlespace of Ramadi. Multiple SEAL platoons were operating simultaneously in different sectors of the city, each conducting independent missions in coordination with different U.S. Army and Marine units, as well as Iraqi forces. The distances involved, combined with the unreliability of communications in urban terrain, meant that Jocko simply could not be everywhere at once.

If Jocko had tried to make every decision for every element, operations would have ground to a halt. Junior leaders would have been waiting for permission while enemy fighters maneuvered against them. The pace of combat far outstrips the ability of a single leader to process information and issue orders for multiple teams.

Instead, Jocko implemented Decentralized Command. He ensured that every junior leader – every platoon commander, every squad leader – understood the overall mission, the boundaries within which they could operate, and the commander’s intent. Then he empowered them to make tactical decisions on the ground without waiting for his approval.

The Platoon Commander’s Decision

During one operation, a SEAL platoon commander encountered an unexpected situation: enemy fighters had repositioned to a location that was outside the planned area of operations. The platoon commander had to make a rapid decision. He could pursue the enemy and exploit the tactical advantage, or he could hold position and wait for guidance from Jocko.

Because the platoon commander understood the commander’s intent (to clear the area of enemy fighters and secure the neighborhood for Iraqi security forces), he made the call to pursue. He maneuvered his platoon to engage the enemy, coordinated with adjacent units, and successfully neutralized the threat. He reported the situation to Jocko after the fact.

This is Decentralized Command in action. The junior leader had the authority, the understanding, and the confidence to make a decision that advanced the mission without waiting for orders from above.

The Principle: Empower Junior Leaders

Decentralized Command does not mean leaderless chaos. It means a carefully structured system where junior leaders are empowered to make decisions within a clearly defined framework. The senior leader sets the strategic direction, defines the boundaries, and ensures that everyone understands the “why.” Within those boundaries, junior leaders have the freedom and the responsibility to act.

The Elements of Decentralized Command

The Decentralized Command Spectrum

Decentralized Command exists on a spectrum between two extremes:

When Decentralized Command Fails

Business Application: The Micromanaging Executive

The CEO Who Couldn’t Let Go

Leif describes a rapidly growing company where the CEO had been intimately involved in every decision during the startup phase. As the company grew to several hundred employees, the CEO continued to insist on approving every significant decision across all departments. The result was predictable: decisions were delayed for days or weeks while they waited in the CEO’s queue. Talented managers felt disempowered and frustrated. Some of the best people left because they wanted to lead, not just execute orders.

When Leif introduced the concept of Decentralized Command, the CEO initially resisted. “I can’t trust my people to make the right decisions,” he said. Leif’s response was direct: “Then you haven’t trained them properly, and that’s your failure, not theirs.”

The CEO began by clearly defining his strategic intent for each department. He then set explicit decision-making boundaries: decisions under a certain financial threshold or within certain operational parameters could be made by department heads without his approval. He invested in training and mentoring his leaders, gradually expanding their authority as they demonstrated competence.

Within six months, the pace of decision-making increased dramatically. The CEO was freed from the daily decision bottleneck to focus on strategy and vision. And the managers, now empowered to lead, were more engaged, more effective, and more likely to stay.

Building Decentralized Command in Your Organization

The Leader’s Dilemma

Decentralized Command requires leaders to navigate a fundamental tension: they are responsible for everything (Extreme Ownership), but they cannot control everything (Decentralized Command). The resolution is that the leader creates the conditions for success – training, boundaries, communication, trust – and then allows junior leaders to operate within those conditions.

Trust Through Training

The foundation of Decentralized Command is trust, and trust is built through training. In SEAL Team, operators train together for months before deploying. They rehearse scenarios, conduct live-fire exercises, and debrief extensively after every training event. By the time they reach the battlefield, the senior leader trusts the junior leaders because he has seen them perform under pressure hundreds of times. In business, the equivalent is investing time in developing your people before you need them to perform independently. The leader who skips training and then complains about having to micromanage has only themselves to blame.

Key Takeaways

← Previous: Chapter 7 Next: Chapter 9 →