A capable operator gets promoted, works harder than ever — and the business stops moving. The most common structural cause of senior underperformance isn't a lack of effort or talent. It's a leader operating one level below their role, doing yesterday's job faster while the work their new role exists to do goes undone. From inside, it's almost invisible: everyone involved is busy.
Roles have levels, and the levels are different in kind
The underlying model comes from Elliott Jaques' work on levels of work: roles in an organisation differ not just in scope but in the time horizon and complexity of the work itself. A simplified ladder runs from leading yourself (a horizon of months), to leading a team (a year or two), to leading a business (two to five years), to leading multiple businesses (five to ten), and beyond. Each step up is not "the same work, bigger" — it's a different kind of work. The focus shifts from today's product or service, to improving the process that makes it, to designing the systems, to developing the business, to shaping the business model itself.
A well-structured organisation has each layer genuinely working at its level. The common failure is a leader who holds a role at one level while spending their days on the work of the level below — which crowds the person under them, and leaves a gap at the level the role was created to cover. Nobody is doing the two-to-five-year work, and nobody notices, because everybody is flat out.
The five reasons it happens
- They like the work of the old level. It's what they're good at, it's satisfying, and it gives quick wins. The new level's work is slower and more abstract.
- Nobody has clarified what the new level's work actually is. The promotion changed the title and the pay; no one ever described the different work.
- They don't trust their reports. So they check, redo and hover — which is the old level's work wearing a supervisory disguise.
- They think it will be quicker to do it themselves. In any single instance, it is. As an operating pattern, it guarantees the level below never develops.
- There is a genuine resource gap. Sometimes the layer below really can't carry the work yet — in which case the fix is to develop or restructure that layer, not to quietly absorb its work forever.
They try to do more of the same, faster — and leave a gap at the level the role is intended to deliver.
Why 'delegate better' isn't the fix
The standard prescription — time management and delegation training — treats the symptom. If the leader is holding lower-level work because the layer below can't carry it, no amount of calendar discipline changes anything: the work has nowhere to land. The durable fix is structural. Name the work of each level explicitly, then either develop the layer below until it can genuinely receive its work, or change the structure so it can.
Two tests you can run this week
First, the calendar test. Take your last month of meetings and blocks and sort each one honestly by the level of work it served. If well under half your time is genuinely at your role's level, you don't have a time-management problem — you have a structural one, and the calendar is just where it shows up.
Second, the horizon test. Look at the decisions you actually made this quarter and ask what time horizon each one truly operated on. A leader whose role is the three-year work but whose every decision resolves inside ninety days is anchored a level down — whatever the title says. The gap between the level you hold and the level you work at is the single most useful thing to measure, because unlike capability, it's fixable by design.