Law VI: Decentralize Command
The hidden cost of centralized authority isn’t slow decisions — it’s the capability your team stops building while they wait for yours
You are good at your job. That is not a compliment. It is the setup.
Because somewhere along the way, being genuinely good — technically sharp, strategically sound, invested in outcomes — trained your organization to route every meaningful decision through you. Not because you designed it that way. Nor because your team lacks capability. But because the system learned, over time, that your involvement was the path of least resistance to a good outcome. So they brought you in. You weighed in. The decision got made.
And your team stopped developing the judgment to make it without you.
You didn’t see it forming. What you saw was a team that respected you, proposals that got better when you reviewed them, and outcomes that held when you were close to the work. What you were actually watching was your organization encoding a rational behavior: when your involvement reliably improves the outcome, the most rational move for everyone is to involve you. They are not failing to take initiative. They are responding accurately to the incentive structure you built around them.
This is the failure Decentralize Command addresses; not the leader who hoards authority out of ego or fear, but the leader who centralizes it through excellence, through care, through being the kind of person teams learn to depend on because depending on them works.
Think about the last proposal that landed on your desk. Not the big strategic one, rather the operational one. That scope adjustment, or the vendor call, the resource reallocation between two workstreams your team owns. The one that, two years ago, your team would have resolved without you. Yet now it has arrived because the system has learned that sending it to you is safer than deciding without you. Your team didn’t fail…they read the environment accurately and acted accordingly. And the environment is of your making.
Once that begins, other adaptations quickly emerge. Drive narrows to task completion. Creativity shrinks to compliance. Capability erodes, innately, because judgment is no longer exercised. Proposals arrive pre-narrowed: scoped to match what the system has historically approved, and stripped of the ambitious options — and thinking — your team decided wasn’t worth the revision cycle. Meetings that used to produce a recommendation now produce a briefing. Your team shows up with data, but you make the call. And everyone leaves having done exactly what the system trained them to do.
They down-regulate.
No leader, regardless of experience, has the same access to lived constraints, tradeoffs, and operational nuance as the people working inside the system every day. Even a leader who immerses deeply becomes, at best, a tourist. When every meaningful decision flows upward before action can occur, information compresses in transit. Context disappears. Tradeoffs flatten. By the time a decision returns downstream, it is reacting to a description of reality rather than reality itself, and the team that sent it up has been practicing waiting rather than deciding while it made the round trip.
Distance does not merely slow correction. It changes what the system learns.
The people with the lowest tolerance for this are the ones who came to do consequential work, the ones who had a view on the right call and came in expecting to be heard. They feel the friction first and most acutely. They stop bringing the ambitious option. Then they stop coming at all. What remains is a team shaped by what your system selected for: skilled at execution, practiced at escalation, genuinely uncertain what decisions are theirs to make.
When you look around and see a team that needs a lot of direction. What you don’t see is that you selected for it, one rewarded escalation at a time, until the people who wouldn’t escalate were gone.
Reversing this requires tolerating outcomes you could have improved by staying involved, watching your team make the call you would have made differently, and holding your position anyway. Most leaders won’t do that. The discomfort of watching a preventable mistake is more immediate than the cost of the capability your team never builds. The Doctrine’s foundational principle — that incentives govern behavior, always — is the Meta-Law, and it operates on you too. Your involvement is incentivized. It feels like leadership. It produces visible results. The people around you reward it. Staying close to the work is not a structural failure. It is a structurally rational choice that produces a structurally catastrophic outcome over time.
If authority is not distributed deliberately, it will centralize accidentally.
You cannot scale authority that lives in one person. It can only accumulate — more decisions queued, more context compressed, more capability atrophying in the people who should be building it — until the weight of what centralization concentrated becomes more than the system can carry.
And those systems eventually collapse under that centralized authority.
There is a specific point at which your team stops testing whether authority is real and accepts that it isn’t, where escalation stops being a habit and becomes an assumption so deep it no longer registers as a choice. Most leaders miss that point while it is happening. They identify it in retrospect, when the correction cost has already compounded into something structural. The Operator Insight paired with this Law is the cost curve: what intervention requires at the early window, what it requires after normalization has set in, and how to tell which side of it you are currently on.