One of the most misleading signs of organisational success is the indispensable person. 

Every growing organisation has them. They are the people everyone trusts. The people clients ask for by name. The people who know the history, understand the nuance, spot the risks, rescue difficult projects and solve problems before others have fully understood them. They are often deeply committed, highly capable and central to the organisation’s progress. 

At first, this looks like a strength. And in many ways, it is. Organisations need talented people. They need individuals with judgement, expertise, credibility and commitment. The problem begins when the organisation becomes dependent on these people in ways that cannot be sustained. 

The very people who helped the organisation grow can unintentionally become the points at which growth begins to constrain itself. 

This is rarely their fault. In fact, it often happens because they are good. Because they are trusted, more decisions come to them. Because they are responsive, more problems are escalated to them. Because they are knowledgeable, others defer to them. Because they care about quality, they intervene repeatedly. Because clients value them, relationships become concentrated around them. 

Over time, excellence breeds dependency. 

The organisation may continue to celebrate these individuals, but beneath the surface a different pattern may be forming. Work slows down because everyone is waiting for the same person. Decisions are deferred because authority is unclear. Junior colleagues do not develop because the expert keeps stepping in. Other leaders hesitate because they are unsure whether they are truly empowered. Clients become attached to one person rather than confident in the organisation as a whole. 

The individual remains impressive. The system remains fragile. 

This is one of the most important distinctions leaders must learn to see. A bottleneck is not always a poor performer. A bottleneck is often a high performer around whom the organisation has failed to build sufficient capability, clarity and trust. 

In founder-led and entrepreneurial organisations, this pattern is especially common. Early growth depends on people who can stretch across boundaries. Roles are fluid. Problems are solved through relationships. Knowledge circulates informally. People do what needs to be done. The organisation moves quickly because capable individuals carry complexity personally. 

This is effective for a time. But it does not scale indefinitely. 

As the organisation grows, the volume of decisions increases. The number of relationships expands. The range of work broadens. Quality standards need to be maintained across more people and more projects. The organisation can no longer rely on a small number of exceptional individuals to hold everything together. 

If it tries to do so, those individuals become overloaded. Their calendars fill with approvals, reviews, escalations and informal consultations. They become the default route through which uncertainty is resolved. They may feel valued, but they also become exhausted. The organisation may describe them as essential, but it has actually placed them in an unsustainable position. 

The danger is that leaders misdiagnose the problem. 

When work slows down, they may assume people need to be more efficient. When decisions are delayed, they may ask senior colleagues to respond faster. When quality is inconsistent, they may involve the expert even more. When clients complain, they may route more conversations back to the most trusted person. 

These responses often make the problem worse. 

The issue is not simply that one person is too busy. The issue is that too much organisational capability is concentrated in too few places. The solution is not to ask the bottleneck to work harder. The solution is to redesign the system so that capability is more widely distributed. 

This begins by recognising the different forms bottlenecks can take. 

Some are decision bottlenecks. These occur when one person is required to approve too many things. The organisation may believe this protects quality or consistency, but in practice it slows momentum and discourages ownership. If every meaningful decision requires escalation, people learn to wait rather than think. 

Some are knowledge bottlenecks. These occur when critical information is held by individuals rather than captured in accessible methods, tools, records or routines. New colleagues struggle to learn because the organisation has not codified how things work. The expert becomes not only a contributor but the living archive of the organisation. 

Some are relationship bottlenecks. These occur when key clients, partners or stakeholders trust an individual more than the institution. This may be commercially useful in the short term, but it creates risk. If the relationship cannot be transferred, scaled or supported by others, the organisation’s external confidence is tied too closely to one person. 

Some are quality bottlenecks. These occur when standards depend on personal review rather than shared understanding. The expert becomes the final safeguard because the organisation has not yet built common criteria for what good work looks like. 

Some are cultural bottlenecks. These occur when one person carries the tone, values or identity of the organisation. People look to them to interpret what matters. Without them, culture becomes less clear. 

Each of these bottlenecks requires a different response, but the underlying principle is the same: organisational maturity depends on converting individual strength into shared capability. 

This should not be confused with reducing the importance of talented people. The aim is not to make exceptional colleagues less valuable. It is to multiply their value. A truly mature organisation does not trap its best people in endless rescue work. It uses their insight to build methods, develop others, improve systems and raise the capability of the whole organisation. 

The first step is to make bottlenecks visible without blame. 

Leaders should ask where work regularly slows down, which decisions repeatedly escalate, which colleagues are consulted before anything important can move, which relationships are overly concentrated, and which areas would suffer most if a key person were absent for several weeks. These questions should be framed as system questions, not personal criticisms. 

The second step is to distinguish between value-adding involvement and dependency. 

There are decisions where senior expertise genuinely matters. There are relationships where experienced judgement is essential. There are moments when a founder or senior leader should intervene. But not every issue requires the most senior or most capable person. If expert involvement is routine rather than selective, the organisation is probably under-designed. 

The third step is to codify what good looks like. 

Many bottlenecks persist because people cannot act confidently without an expert’s implicit judgement. The expert knows what quality looks like, but others do not. The expert understands the client’s preferences, but others have not been equipped to interpret them. The expert can spot risk, but the organisation has not created common risk indicators. 

Codification does not mean turning professional judgement into a mechanical checklist. It means making the foundations of judgement more visible. Principles, standards, templates, decision criteria, playbooks, case examples and review routines can help others learn how to think, not merely what to do. 

The fourth step is to clarify decision rights. 

People often escalate because they are uncertain whether they are allowed to decide. Ambiguity creates caution. Caution creates delay. Delay reinforces centralisation because eventually the issue reaches the person everyone trusts. 

Clear decision rights do not eliminate escalation. They make escalation purposeful. People should know which decisions they own, which decisions require consultation, which decisions require approval and which decisions should be escalated because the risk, cost or strategic significance is genuinely high. 

The fifth step is to develop leaders around the bottleneck. 

Capability does not spread by instruction alone. It spreads through deliberate development. High-performing individuals should be supported to coach others, delegate judgement progressively, expose colleagues to complex work and create opportunities for others to lead. This requires time and discipline. It may feel slower at first, but it is the only way to build depth. 

The sixth step is to change what the organisation rewards. 

Many bottlenecks are sustained by recognition systems that celebrate heroic effort. The person who saves the project is praised. The person who works late to fix a recurring issue is admired. The leader who personally intervenes in every problem is seen as committed. 

But if organisations only reward rescue, they will get more rescue. Mature organisations also reward prevention, capability-building, delegation, knowledge-sharing and system improvement. They recognise leaders not only for what they personally deliver but for the strength they build around them. 

This is especially important for founders and senior executives. If they continue to derive status from being indispensable, others will adapt accordingly. They will wait, escalate and defer. If, however, senior leaders visibly value distributed capability, the organisation begins to change. 

The question is not, “Who is the most capable person here?” The better question is, “How do we ensure that this capability becomes part of the organisation rather than remaining dependent on one individual?” 

That shift is central to scaling. Organisations do not become stronger merely by hiring more good people. They become stronger when good people are connected through clear systems, shared standards, effective routines and deliberate development. 

A talented individual can carry a project. A capable organisation can carry a portfolio. A trusted expert can protect quality in one area. A well-designed system can protect quality across many areas. A founder can model culture for an early team. An institution can embed culture across generations of leaders. 

The temptation is to treat bottlenecks as evidence of importance. In reality, they are often signals of incomplete institutionalisation. 

The best people should not become organisational choke points. They should become sources of leverage. Their knowledge should teach the system. Their judgement should shape standards. Their relationships should strengthen institutional trust. Their experience should develop others. Their excellence should become contagious. 

When good people become bottlenecks, the answer is not to remove them from the centre overnight. Nor is it to diminish their role. The answer is to help the organisation grow around them. 

That is how individual brilliance becomes institutional capability. 

And that is how growing organisations move from dependence to scale.