The CEO Who Cannot Stop Doing
The Comfort of Doing
Many CEOs — especially those who built their organisations from the ground up — carry a deep attachment to doing. They are good at it. They have a long track record of things getting better when they are personally involved. They trust their own judgment more than they trust the systems and people they have nominally put in place. And so they stay in the work: reviewing drafts, attending operational meetings, making decisions that should have been made two levels below them.
This feels productive. It generates visible output. It maintains the feeling of competence that comes from mastery of a domain. What it does not do is build the organisation that the CEO needs to be building — the one that can function, decide, and grow without the CEO's presence in every significant moment.
What Over-Involvement Costs the Organisation
When a CEO cannot stop doing, the organisation develops structural dependencies around that involvement. People stop making decisions autonomously because they have learned to wait for the CEO's input. They stop developing their own judgment because the CEO's judgment is always available. They stop taking ownership of outcomes because the CEO's presence creates a diffusion of accountability — when the CEO was involved in the decision, who is responsible if it goes wrong?
Over time, the organisation's decision-making capacity concentrates at the top in a way that becomes the primary constraint on its growth. Every decision that matters waits for the CEO. Every process that involves the CEO becomes a bottleneck. The CEO works harder than anyone in the organisation and produces the ceiling rather than the engine of its capability.
The Transition That Doesn't Happen
There is a transition that every founder-CEO needs to make: from being the best person in the room at the work to being the person who creates the conditions in which others can be better at it than they would be alone. This is a genuine loss — of identity, of the satisfaction of mastery, of the certainty that things are being done well because you are doing them yourself. And it is a transition that many CEOs never fully complete, because the pull of the familiar is powerful and the new role is harder to see and harder to feel competent in.
The CEOs who complete this transition successfully do so not by suppressing the desire to be involved but by redirecting it — toward the work of building leaders, designing systems, setting direction, and creating the culture in which good decisions are made consistently without requiring their direct involvement in each one. That is harder work than doing. It is also the only work that scales.
What Leadership Actually Requires at Scale
At scale, the CEO's primary product is not decisions or deliverables. It is context: the shared understanding of where the organisation is going, why it is going there, what is important, and what success looks like. Leaders who provide rich, honest, consistent context create organisations that can navigate complexity without requiring central direction at every point. Leaders who stay in the doing cannot provide this context, because they are too close to the operational to hold the strategic.
This is not abstract. It is the practical difference between an organisation that can absorb the CEO's absence without disruption and one that freezes when the CEO takes a week off. That resilience is the measure of whether leadership has happened — not whether the CEO is excellent at the work, but whether the organisation is excellent at the work without them.
The Question Worth Asking
The question worth asking, for any CEO who suspects they might be doing too much: if I stepped back from this decision, this meeting, this draft — what would happen? If the answer is "something I would not fully endorse," the real question is whether the gap is a capability gap in the team or a trust gap in the CEO. Those are different problems with different solutions. The capability gap requires development. The trust gap requires the harder work of understanding why the CEO has not been able to trust what has been built — and whether what has been built is actually trustworthy, or whether the doing has prevented it from becoming so.
Request Access at planets9.com