In many organisations, the CEO's effectiveness can mask the company's ineffectiveness. When a CEO travels or is unavailable, important decisions and trade-offs come to a standstill, revealing a deeper problem with execution speed. This issue is often misdiagnosed as a delegation problem, but it is, in fact, an execution problem. As companies grow, the volume and complexity of decisions increase, but the CEO's bandwidth does not expand at the same rate.
McKinsey's survey of over 1,200 managers found that fewer than half regarded decisions as timely, and 61 per cent said at least half the time spent making decisions was ineffective. In one example, a chemicals-company CEO was making hiring decisions four levels below the top. The problem was not that the CEO could not decide, but that the organisation still required the CEO to decide. This highlights the need for organisations to develop their decision-making capabilities.
The CEO Dependency Trap occurs when an organisation relies on the CEO's personal judgement to resolve decisions, trade-offs, and exceptions that should progressively become organisational capability. This trap is often created by success, as CEO intervention works in the short term, but the problem begins when a useful exception becomes the operating model. Over time, the organisation learns to take important issues upward, which can look like strong leadership but may actually be a weak execution capability.
Execution challenge is not simply to push decisions downward but to distribute judgement. Authority can be delegated through an organisation chart, but judgement cannot. Executives need to know not only that they can decide but also how the enterprise expects them to think, including which outcome has priority, what risks are acceptable, and when escalation is genuinely required. Clear priorities, explicit decision boundaries, and an understood risk appetite allow judgement to travel.
Amazon's approach to decision-making offers a useful illustration. In his 2016 shareholder letter, Jeff Bezos distinguished consequential decisions from reversible "two-way door" decisions that should use lighter processes, explicitly protecting decision speed as the organisation scaled. Strong organisations become precise about which decisions genuinely require the CEO and create enough context for the rest to move without waiting.
CEOs can unintentionally reinforce the dependency they complain about by asking executives to decide, then reopening decisions, or demanding ownership while rewarding people who seek approval before taking risks. The organisation learns from behaviour, not delegation speeches. For CEOs, recurring escalation should be treated as data, indicating potential issues with commercial principles or enterprise priorities.
The strongest CEO is not the one who personally keeps execution moving but the one who builds an organisation capable of keeping execution moving without them. For boards, CEO dependency can remain hidden while performance is strong, but succession risk is not merely the risk of losing a talented individual; it is the risk of discovering how much organisational capability was never built because the individual was always there.
Key points
- CEO dependency can become an execution constraint.
- Delegation moves authority, but scaling requires judgement to move with it.
- The execution question is: If your CEO were unavailable for the next 30 days, which important decisions would stop moving—and what does that reveal about the execution capability the organisation has actually built?
