If One Person Goes on Holiday and the Business Slows Down, You Have Built a Dependency, Not a Team
Most growing businesses can name the people they cannot afford to lose. The operations manager who knows how every system really works. The general manager who can read a difficult service before it goes wrong. The commercial lead who remembers why a client was promised an exception three years ago. The founder who still seems to be required whenever a decision is expensive, unusual or politically awkward.
Those people are often described as indispensable, and usually with affection. Commercially, however, indispensability is a warning light. If performance drops when one person is absent, the organisation has concentrated too much knowledge, judgement or authority in one pair of hands. What looks like talent can also be key person dependency.
THE HERO PROBLEM IS AN OPERATING RISK
The easiest version to spot is knowledge dependency. One person knows the passwords, the supplier history, the workarounds, the real sequence of a process or the reason a particular customer needs handling differently. The harder version is judgement dependency. The procedure is written down, but everybody still waits for the experienced person to decide what the procedure means in this situation.
This is especially dangerous in experience-led businesses. Hotels, restaurants, spas, events and premium retail operate through thousands of small decisions made under pressure. A good manager adjusts staffing before the queue becomes visible, authorises a sensible recovery before a complaint escalates, recognises when a VIP request is genuinely important and knows which standard can flex without damaging the promise. Remove that judgement and the operation can become technically compliant while the customer experience deteriorates.
Key person dependency usually grows for sensible reasons. The business was smaller. The founder was close to everything. A strong employee stepped into gaps. Growth arrived faster than roles, systems and management capability matured. The hero became valuable precisely because the organisation had not yet encoded what the hero knew. Then the hero kept rescuing the business, which reduced the pressure to fix the dependency.
DOCUMENTATION IS NOT THE SAME AS TRANSFER
This is where many businesses make the wrong move and write more procedures. Documentation matters, but an SOP can only capture a repeatable task. It cannot fully capture pattern recognition, commercial trade-offs, confidence or context. If your strongest manager knows when to make an exception, the useful question is not simply, “What do you do?” It is, “What are you noticing, what are you weighing up, what would make you choose differently, and who else is being taught to make that call?”
The goal is not to make talented people less important. It is to make their capability more transferable. That means turning private knowledge into shared knowledge, private judgement into teachable principles and private authority into clear decision rights. A resilient team knows who can decide, what good looks like, where escalation is genuinely required and where people are expected to act without asking permission.
RUN THE ABSENCE TEST BEFORE THE ABSENCE HAPPENS
Start with an absence test. Pick the five people whose unexpected two-week absence would create the most disruption. For each one, ask what would actually slow down: information, decisions, customer relationships, quality control, technical capability, confidence or access. Then separate what can be documented from what must be coached and practised. That distinction is important. You solve missing information with systems. You solve missing judgement by developing people.
Next, watch where work queues behind a person. Approval piles, repeated “just checking with…” messages, customers asking for the same named individual and managers who cannot progress without the founder are all evidence of concentrated authority. Your weekly leadership meeting should help expose and reduce those queues, not merely report them. Used properly, it becomes a place to transfer context, clarify decision rights and make ownership visible.
There is also a cultural test. Some leaders say they want ownership while continuing to reward escalation. They correct every decision made differently from the way they would have made it, step back into problems the moment standards wobble and keep the most commercially useful context to themselves. The team learns the real rule quickly: do not decide, ask the expert. Dependency is then reinforced by leadership behaviour, not employee weakness.
BUILD JUDGEMENT, NOT JUST COVER
A stronger operating model makes capable people easier to multiply. Critical knowledge is visible. Decision principles are explicit. More than one person owns important relationships. Deputies are developed before they are urgently needed. Managers are coached through real decisions rather than only trained on policies. Leaders create room for people to exercise judgement, review the outcome and get better at it.
There is a simple commercial standard for this work: the business should be able to lose access to any one person for a sensible period without customers feeling a different company. Not without inconvenience, and not without redistribution of work, but without a collapse in quality, speed or confidence. If that is impossible today, growth is resting on a human single point of failure.
TEAM ALIGNMENT IS HOW DEPENDENCY BECOMES CAPABILITY
This is why team alignment is more than getting people to agree in a workshop. It is the practical work of making expectations, ownership, communication, decision-making and leadership behaviour strong enough for the organisation to perform without constant rescue. Q Branch People, Change & Performance works with leadership teams on precisely this part of the human system, connecting people development to the operational reality the customer eventually experiences.
If too much of your business still depends on the founder, one senior manager or a handful of go-to people, do not wait for a resignation, holiday or period of rapid growth to prove the risk. Map the dependency while the experts are still in the room, then use it as a development agenda for the wider team.
Comments