Most leadership roles come with a job description. It sets out responsibilities, reporting lines, accountabilities and expectations. It describes the team you will lead, the decisions you will make and the outcomes you will be responsible for delivering.
Then you start doing the job, and over time another role begins to form around the one you were actually hired to do. You become the person people call when something is unclear, the person who remembers why a decision was made three years ago, or the person who knows which stakeholder needs a phone call before an announcement goes out. You might be the one who can calm a difficult customer, interpret an ambiguous policy, get two teams talking again or navigate the process that everyone knows does not quite work.
None of this necessarily appears in your position description. Yet, gradually, the organisation can become dependent on you doing it.
The role you hold and the load you carry are not always the same
We tend to think about leadership load in terms of the formal responsibilities attached to a position: team size, budget, operational complexity, strategic accountability and regulatory exposure. Those things certainly create load, but some of the most consequential leadership load is informal. It accumulates through relationships, history, judgement, trust and repeated problem-solving.
Perhaps you are the person who can get Finance to move quickly because you know who to speak to. A senior executive might regularly ask you to sense-check difficult decisions because they trust your judgement. Your team may have learned that bringing an issue to you is faster than navigating the formal process, while clients might insist on dealing with you because you have carried the relationship for years. There may even be important organisational history that nobody properly documented but you still remember.
Individually, these things can look like evidence that you are good at your job. Often they are. The issue is not that capable people become trusted or that experienced leaders develop valuable relationships. The issue begins when personal capability quietly becomes organisational dependency.
Useful people attract more usefulness
Organisations rarely set out to create this kind of dependency. It usually develops for perfectly rational reasons. Someone proves reliable, so they are given more responsibility. They solve a difficult problem, so people bring them the next one. They build trust with an important stakeholder, so they become the natural point of contact. They understand a complicated process, so colleagues ask them rather than spending hours trying to interpret it themselves.
Each decision makes sense in isolation. Repeated over months or years, however, something structural can happen. Work begins to route through the person rather than through the organisation. Their judgement becomes a control mechanism, their relationships become infrastructure, their memory becomes organisational knowledge and their availability becomes part of the operating model.
The difficult part is that none of this necessarily looks like failure. Quite the opposite. The person continues solving problems, decisions continue being made and important relationships remain intact. From the organisation's perspective, the arrangement can appear to be working extremely well.
That apparent success is precisely what can conceal the weakness underneath it.
When high performance conceals structural weakness
Consider a leader who seems indispensable. They know the major customers, can answer almost any operational question, are routinely approached by their team for advice and have the confidence of senior executives. When a complicated problem emerges, things seem to move once they become involved.
It is easy to look at that situation and see exceptional leadership. It may well be exceptional leadership. But there is another question worth asking: what has the organisation become dependent on that person carrying?
That question shifts the focus from the individual's performance to the structure supporting it. Could someone else make the same decisions with reasonable confidence? Does the team understand the principles behind the leader's judgement, or have they simply learned to ask them? Are important stakeholder relationships held by the organisation or primarily by one individual? Is critical knowledge captured and accessible? If that leader disappeared for six weeks, would responsibility transfer cleanly, or would decisions, relationships and unresolved problems begin accumulating around the empty chair?
These are not questions about whether the leader is capable. They are questions about whether the organisation has successfully converted individual capability into organisational capability.
The invisible second job
This is why some leaders eventually find themselves carrying what amounts to two roles. There is the visible role they were employed to perform: leading the team, delivering strategy, managing performance, meeting targets, attending meetings and making the decisions formally assigned to them.
Alongside it, an invisible role can develop. It consists of remembering context, interpreting ambiguity, connecting people, rescuing difficult situations, translating between functions, escalating issues, reassuring others, troubleshooting exceptions and holding together the spaces between formal responsibilities.
That second role rarely arrives as a deliberate assignment. It accumulates one exception, one relationship, one workaround and one “Can you just take a look at this?” at a time. Eventually, a leader can spend a significant proportion of their capacity maintaining organisational continuity without either the leader or the organisation fully recognising that this is what they are doing.
From the outside, the person simply looks busy. From the inside, they may experience something different: despite building a capable team and trying to distribute work, everything important still seems to find its way back to them.
Why this is not simply a delegation problem
The conventional response to an overloaded leader is often that they need to delegate more. Sometimes that is entirely appropriate, but delegation is an incomplete answer when the underlying problem is structural.
A leader cannot simply delegate a relationship that exists primarily because of years of personal trust. They cannot transfer judgement if nobody else has been given the context or authority required to exercise it. Institutional memory cannot be delegated if it has never been captured, and responsibility cannot be distributed effectively when decision rights remain ambiguous. Telling somebody to let go achieves very little if the organisation continues routing uncertainty back to them whenever circumstances become difficult.
This helps explain why capable leaders can remain overloaded even after making genuine efforts to delegate. They may have successfully transferred tasks while continuing to carry the judgement, risk, relationships and exceptions behind those tasks. The visible work has moved, but much of the underlying load has not.
That distinction matters because otherwise we risk diagnosing an organisational design problem as a personal productivity problem.
Looking beyond formal responsibility
A more useful conversation therefore starts with something broader than What are you responsible for? It also asks: What are you carrying that the organisation has never formally recognised?
The answer might include decisions that other people technically have authority to make but continue bringing back to you. It might include relationships that cannot yet function effectively without your involvement, knowledge that exists primarily in your head, conflicts you repeatedly mediate because the operating structure does not resolve them, or exceptions that require your judgement because the formal process works only when circumstances are normal.
It can also include less visible forms of load. A team may have come to rely on one leader to provide reassurance whenever uncertainty rises. Senior colleagues may depend on that person to translate between competing priorities. Customers may expect access to them because that is how trust has historically been maintained.
None of these things automatically indicates dysfunction. Leadership inevitably involves judgement, relationships, ambiguity and trust. The structural concern is concentration. When too much organisational continuity depends on one person's presence, responsiveness, memory or judgement, leadership load is no longer only a question of how much that individual can handle. It has become a question about how the organisation itself operates.
The job description is only the beginning
A position description tells us what an organisation intended a leader to carry. It does not necessarily tell us what the organisation has gradually learned to depend on them carrying.
That difference matters for succession because a replacement can inherit the formal role without inheriting the informal infrastructure surrounding it. It matters for resilience because a team can appear well staffed while still being highly dependent on one person's judgement. It matters for decision speed because authority can be distributed on paper while decisions continue travelling back to the same individual. And it matters for leadership wellbeing because someone can become overloaded by responsibilities that are largely invisible when their workload is assessed.
This is why asking a heavily relied-upon leader to become more efficient, manage their time better or delegate more can sometimes miss the problem entirely. Before trying to change the person, it is worth examining the system that has formed around them.
The more revealing question may be:
What wasn't in the job description — but now depends on them anyway?