In many companies, efficiency looks good on paper until one key person is away for a week.
Then a proposal does not go out, a customer issue does not move forward, a decision waits, or the information exists only in one person's head. The problem is not that the organization has good people. The problem is that good work has not been turned into a shared operating model.
To me, key person dependency is not primarily a people risk. It is a leadership and business risk.
Sometimes key person dependency is admired for the wrong reason. Every organization has people who get things done. That is valuable, of course. The problem begins when the business relies too heavily on specific people constantly compensating for gaps in structures, responsibilities, processes or systems.
At that point the organization is not truly efficient. It is vulnerable.
Key person dependency looks like efficiency until daily work breaks
Key person dependency usually develops gradually.
Growth brings more customers, more work and more exceptions. At the same time, some people learn to carry a wider part of the whole than others. They know how things really move forward, who needs to be called, what has been promised to the customer, what delivery can actually do, and how the system needs to be interpreted so the picture is true rather than just a neat-looking report.
From the outside, this can look like high performance. From the inside, it is often a system that works only because certain people keep patching it.
Typical signs include:
- sales or delivery slows down as soon as one experienced person is away
- important information is spread across the CRM, email, Slack and people's heads, but not in one place that can be managed
- proposals, project kickoffs or customer handovers are consistently good only when handled by certain people
- leadership gets the reports, but practical bottlenecks depend on informal knowledge
- there are people in the organization who receive every difficult situation because the wider model does not hold
A structure like this can last for a while. It often lasts surprisingly long when the organization has conscientious people.
But it does not scale in a healthy way.
Key person dependency is a commercial risk, not just a people risk
I think this matters especially for commercial leadership.
Key person dependency is not only an HR topic or a line management topic. It shows up directly in sales, customer experience, predictability and profitability.
If sales depends too much on individual people, the pipeline is not truly manageable. Proposal quality varies, progression criteria drift and onboarding new people becomes slower. If delivery depends too much on tacit knowledge, quality varies, workload increases and the customer experience starts to depend on whose desk the issue happens to land on. If decision-making depends on too few people, the organization reacts slowly exactly when it should be learning fast.
I have seen this very concretely in difficult change situations.
When I moved to lead Fonecta's ecommerce unit after a merger, the starting point was difficult. The team was overloaded, the quality of work had declined and customers were visibly dissatisfied. Situations like that quickly reveal how much the operation has depended on informal practices, individual people stretching themselves and unclear responsibilities.
In practice, we had to make visible where work was really getting stuck. Where were projects waiting for decisions? Where did customer promises not match delivery capacity? Where did responsibility shift unclearly? Where were the same people solving the same problems week after week?
The situation was not fixed by simply adding pressure or hoping for a better attitude. Goals had to be clarified, project practices renewed, weekly leadership strengthened and day-to-day bottlenecks made visible and removed. When the operating model became clearer, the unit's efficiency improved by more than 30 percent.
The essential lesson was this: performance does not recover sustainably if the organization remains dependent on certain people rescuing daily work.
Repeatability does not mean building a robotic organization
Trying to reduce key person dependency sometimes creates resistance. People worry that everything will become bureaucratic, mechanical and over-standardized.
I think that is the wrong trade-off.
The goal is not to remove strong people, judgement or flexibility. The goal is to remove the kind of ambiguity that forces strong people to spend their time on the same rescue work again and again.
A good operating model does not turn people into robots. It makes a few critical things visible:
- what stages the work actually has
- what criteria move the work forward
- what information is needed for the next decision
- who owns the next move
- where information should live so it does not disappear with people
When these things are in place, good people can spend their time where they are at their best: understanding customers, making decisions, solving problems, using commercial judgement and supporting teams.
Without that clarity, the best people in the organization easily become internal repair crews.
At Eeco, sales scaled when good work was made visible
At Eeco, this showed up especially in sales.
When I led sales and marketing, the goal was to grow B2B sales without every additional step depending on more manual work or individual memory. We sold ecommerce platforms, integrations, ongoing development and marketing automation to SMEs. Deal sizes varied, sales cycles were long and quality had to stay consistent.
When this kind of sales depends only on a few people's personal ways of working, it is difficult to lead and even harder to replicate.
That is why we built the sales stages, progression criteria, use of materials, CRM practices and automations in a way that made good work more visible and more repeatable. With the model we built, we were able to generate roughly one million euros in annual ecommerce platform sales with two salespeople.
Looking back, the important thing was not that everyone did everything in exactly the same way. The important thing was that the best work became visible enough to be led, improved and taught to others.
The same idea applies far beyond sales.
If an organization wants to use CRM, automation or AI properly, reducing key person dependency is often one of the most important starting points. Technology does not remove key person dependency if the operating model is still unclear. At most, it can accelerate the ambiguity.
Five questions that reveal key person dependency
If I were assessing whether an organization is too dependent on individuals, I would ask at least these five questions.
1. Where does work stop if one person is away?
This is a simple but revealing test. If critical customer situations, proposals, decisions or handovers always wait for the same person, the problem is not just resourcing. The problem is the model.
2. Where does the information really live?
If important customer information, pricing logic, decision history or project progress mainly lives in people's memory, the organization is vulnerable. Information does not need to be everywhere, but it does need to be findable and manageable.
3. Which handovers require informal adjustment?
Many organizations look functional until you inspect the interfaces. The handovers between sales and delivery, marketing and sales, account management and projects, or leadership and daily work quickly reveal whether a real model exists.
4. What are the best people doing that they should not have to do?
If the best salespeople, experts or project leads spend their time searching for information, fixing materials, sorting things out internally or coordinating manually again and again, the organization is wasting capacity in the wrong place.
5. What does leadership review every week?
Key person dependency does not disappear by itself. It requires a leadership rhythm where problems are not discovered only in a monthly report. Leadership needs to see where work stops, where workload grows, where quality varies and where too much of the work rests on individual people.
Where should the work begin?
Reducing key person dependency usually does not begin with a large change programme. Often it starts in a much more ordinary place.
First, I would identify the critical points where work stops because of individual people. Where does a customer's issue fail to move forward without a specific person? Where does a decision always wait for the same person? Where is the customer promise, pricing, delivery detail or next step only in someone's memory?
Second, I would define what is actually missing at those points. Is it information, ownership, decision criteria, process, system use or leadership rhythm?
Third, I would bring these topics into weekly leadership. Key person dependency does not disappear because it was identified once in a workshop. It starts to decrease only when leadership systematically reviews where work stops, why it stops and what needs to change so the same problem does not repeat week after week.
The goal is not to make the organization perfectly process-driven. A better goal is to make critical work visible enough that it can be led even when daily work does not go according to plan.
Closing
I do not believe in organizations where everything is scripted into something impersonal.
I believe in organizations where strong people do not have to keep rescuing the system.
That is one of the most important tests of leadership. Are we building a business that works only when certain people stretch themselves? Or are we building an operating model where success does not depend on individual people's memory, calendar and energy?
Growth, scaling sales, leading change and using technology often sound like separate conversations. In practice, they share the same foundation: good work needs to be made visible, shareable and manageable.
Otherwise the heroes can keep the wheels moving for a while.
But the business is not yet running on its own strength.