FM-10: Leadership Saturation
Hands-on leadership praised. Strategic work postponed. The pattern has a name.
Justin R. Greenbaum · The Lexicon · April 2026
A CEO sits in the daily engineering standup because architecture decisions keep getting reversed two levels down. A COO clears the small-vendor purchase order list each morning because procurement will not sign anything off without her review. A general counsel reviews routine vendor NDAs that her three direct reports are afraid to commit to without her name on them. A division president takes the call from a frustrated customer because the regional GM does not have the authority to offer the resolution the customer is asking for.
None of these leaders are mismanaging their time. Each one is absorbing a structural load the system has routed upward, faster than it has equipped lower layers to absorb it.
This has a name. It is Leadership Saturation.
The pattern is this. Volume, ambiguity, and risk travel upward faster than authority travels downward. Senior leaders become the default resolution mechanism for problems whose ownership was never installed elsewhere. Decision quality degrades as the queue grows past what any one person can think clearly about. Availability becomes sporadic. Strategic work gets displaced by operational triage. The leader’s calendar fills with arbitration.
Saturation masquerades as accessibility. The executive who responds at midnight is praised for hands-on leadership. The leader who attends every operational meeting is described as engaged. The CEO who personally clears the small-vendor list is celebrated for not losing touch with the work. The signal the system reads is gratitude. The condition underneath is structural overload.
What Leadership Saturation gets mistaken for is the thing that makes it durable.
The misdiagnoses all rhyme. Strong leadership. High engagement. Flat hierarchy. Hands-on management. Each is a hero narrative. Each is how the system rewards the behavior that is killing it. Leaders who refuse the next escalation get scored as disengaged. The org is praised for being unbureaucratic while every nontrivial decision routes through the same six people. Retention conversations focus on coaching the executive instead of redesigning the queue.
None of these are substitutes for distributed authority. A leader cannot decide faster than the work is generated. A leader cannot strategize while arbitrating. A leader cannot delegate what the organization has not equipped lower layers to receive.
The misdiagnoses are not incidental. They are the mechanism. Hero narratives are how Leadership Saturation survives contact with the board.
The pattern recurs and changes costumes. In one organization it shows up as an executive team running on adrenaline because the layer below has no real decision rights. In another, as a chief of staff function that quietly expanded because routine work needs an arbitrator and there is no one else equipped to be one. In a third, as an open-door culture that has calcified into the only door.
The conditions that produce saturation are structural, not individual. This is why coaching the executive does not interrupt it. Better calendars raise the throughput on the existing queue. Stronger assistants compress more decisions into the same available hours. A new chief of staff is a new amplifier on the same input.
What interrupts it is structural. Hard limits on what the executive layer is allowed to decide. Decision rights pushed down with the authority to actually use them. Error tolerance baked into lower layers, so leaders are not the only safe place for ambiguity to land. Explicit redistribution, repeatedly enforced. If leaders are always available, the system will never mature.
When Leadership Saturation has a name, the options change.
The leader inside it stops mistaking responsiveness for effectiveness. The team below stops reading every escalation as a personal failure. The board stops treating burnout at the top as a personnel issue. The organization stops applauding the behavior that is collapsing it.
Naming does not fix. Naming changes what can be seen. What can be seen is what can be acted on.
If any of this feels familiar, it has a name and a taxonomy.
The canonical definition of FM-10, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-10.
A role-specific view of how the same pattern looks from the operator’s seat is at dripractice.com/lens/01.
A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.
Next in The Lexicon: FM-03, Responsibility Without Authority. It is the upstream condition that produces saturation in the first place. Accountability assigned where decision rights are not.
Subscribe to The Lexicon.
So true and painful, Justin. What you’re naming here is the gap between ‘strong leadership’ as a story and leadership as a system design problem. We’ve all seen the overloaded exec calendar and called it commitment. What this gives us is language to say: this isn’t about effort, it’s about unfinished delegation, undefined decision rights, and zero error budget below the top layer. That’s a structural diagnosis, not a pep talk about prioritization.