There is a role that accumulates quietly in founder-led companies. It has no job description. Nobody applies for it. The founder does not choose it deliberately. It forms in the gap between a growing organisation and the infrastructure that organisation needs to function — and by the time it is visible, it has been the operating reality for months or years.
The role is Chief Escalation Officer.
The job title says CEO. The job description, if you wrote it honestly from the calendar and the inbox and the pattern of decisions that arrive each day, says something different. It says: the person through whom every significant decision must pass before the organisation can move.
How the role forms
In the early life of a founder-led company, centralised decision-making is not a problem. It is a feature. The founder is the fastest, most informed, most reliable decision-maker in the organisation. They have the market knowledge, the context, the judgment. Routing decisions through them produces better outcomes than the alternative. The organisation rewards it. The founder stays central. The pattern deepens.
The problem arrives later, when the company has grown past the point where one person’s presence can carry it.
At that point the pattern does not change — it compounds. The founder is still the routing point for decisions. But there are more decisions than before, more people waiting, more things stalled when the founder is unavailable. The organisation has grown around the bottleneck rather than past it. The founder works harder to keep up. The team waits longer. The company moves at the speed of one person’s available attention.
Nobody made a decision to build this. The organisation drifted into it, one escalated decision at a time, because nobody built the alternative.
What the pattern costs
The direct cost is visible in the founder’s calendar. Decisions that belong two levels below arriving at the top. Operational questions consuming hours that should go to strategic work. The inability to take a holiday without the organisation quietly degrading. The meeting that cannot start until the founder arrives to resolve the ambiguity the team could not resolve alone.
The indirect cost is less visible but larger.
The team learns from the pattern. They learn that making independent decisions leads to correction — the founder will step in and change things, which means their judgment was wrong, which means the cost of being wrong falls on them personally. The rational response is to escalate rather than decide. To ask rather than act. To wait rather than risk.
This is not a failure of the team. It is a rational adaptation to the structural conditions they are operating in. The escalation pattern is not caused by a team that cannot make decisions. It is caused by a team that has learned, correctly, that the cost of making decisions independently is higher than the cost of waiting.
The founder who interprets this as a capability problem hires differently, trains more, expresses frustration, sets expectations. The escalation continues. The problem was never capability.
The trap inside the pattern
What makes the Chief Escalation Officer pattern persistent is not that it is invisible. Most founders can see it clearly enough. It is that the two obvious responses to it both make it worse.
The founder who works harder — who becomes more available, answers faster, resolves escalations more efficiently — becomes more load-bearing. The organisation’s dependence deepens. The ceiling lowers.
The founder who steps back — who stops answering, pushes decisions back to the team, insists on independence — creates a different problem. The team does not have what they need to decide well without the founder. The strategy is not documented. The decision rights are not defined. The context that would allow them to know what the founder would do is locked in one person’s head. Without it, the decisions that get made independently are the wrong ones, and the founder steps back in to correct them, and the team learns once again that independence leads to problems.
Work harder or step back. Both reinforce the pattern. This is the structural trap at the centre of the role — and the reason that identifying it as a management behaviour problem produces so little change. It is not a management behaviour problem. It is a Double Bind.
What the exit requires
The way out of the Chief Escalation Officer role is not a change in the founder’s behaviour, though behaviour will have to change eventually. It is the construction of what is missing: the structural alternative that allows the organisation to make good decisions without the founder present.
That means documenting the strategy so that the priorities, the direction, and the decision-making logic are accessible to everyone who needs them — not locked in the founder’s head where only the founder can retrieve them. It means defining decision rights so that ownership is clear and the team knows which decisions they are expected to make alone, which to consult on, and which to escalate. It means building the shared context that allows people two levels below the founder to reason from the same starting point.
None of this is fast. It requires the founder to do structural work while still managing the operational load that the structural work is designed to reduce. The pattern does not improve before it is replaced.
But the role has a cost that compounds. Every year the Chief Escalation Officer remains the operating system of the company, the organisation pays the Stagnation Tax on a structural dependency that was never designed in and can be designed out — but only by building what was never built.
The second essay in this series addresses what that building specifically requires — and why role clarity is the first, most load-bearing piece of it.