Every company has one. That employee who “knows how things work”. The only one who understands the cost sheet, who knows the billing step by step, who knows exactly how to close the month. While he’s there, everything is going well. The problem appears the day he takes vacation, gets sick — or resigns.
At that moment, the company discovers an uncomfortable truth: part of its business process was not in the company. It was in someone’s head. And when that person leaves, the knowledge goes along with it. Being held hostage by an employee isn’t a sign of intentional mismanagement — it’s a trap that almost every company falls into without realizing it. This article shows how addiction forms, the real risk it creates, and how to reduce it without relying on luck.
How the company becomes a hostage without realizing it
No one consciously decides to concentrate a critical process on a single person. This happens gradually and silently, and almost always by the hand of a good employee. Someone competent takes responsibility, does well, and improves in their own way over the years. He creates shortcuts, memorizes exceptions, develops a method that only he knows – because he invented it.
Over time, that person becomes the only one who knows how to do that. And here’s the perverse detail: the better and more dedicated the employee, the greater the dependency tends to be, because he solves everything so well that no one else has to learn. The company gets used to the comfort of having someone who “knows”, without realizing that they have exchanged an operational problem for a much greater risk: the concentration of knowledge.
The risk that no one calculates
As long as the key employee is present and satisfied, the risk is invisible — and that’s precisely why it’s dangerous. The company operates every day on top of a dependency that does not appear in any report, until the day it materializes. And it materializes in very concrete ways.
A vacation saw a tense period, with the operation holding their breath until the person returned. An unexpected illness blocks an entire process. And the worst-case scenario – a dismissal, planned or not – can leave the company weeks trying to rebuild, in trial and error, a knowledge that went out the door. There is also the silent cost of everyday life: the company is vulnerable in internal negotiations, because everyone knows, even if no one says, that the process cannot stop. Dependence on a person is not only a risk of continuity; it is a structural weakness.
Knowledge in the head vs. knowledge in the company
The central difference is this: there is the knowledge that lives in people and the knowledge that lives in the company. The first is volatile — it hangs around with the person who carries it, goes in and out the door every day, and it can disappear without warning. The second is an asset – it stays, if transferred, it survives the exchange of any collaborator. Resilient companies are those that, over time, convert as much as possible from the first type to the second.
This conversion has three pillars. The first is documentation: recording how each process works, so that someone else can follow. The second is training: ensuring that more than one person knows how to perform critical tasks. And the third, the most powerful, is the system: embedding the process in the tool itself, so that the “right way to do it” is in the software, not in someone’s memory. It is about this third pillar that it is worth going deeper, because it solves what the other two alone do not support.
How does the system get the process out of people’s minds
Documentation ages and training is lost with turnover. The system, when well constructed, does something more lasting: it incorporates the process. Instead of relying on someone to remember the right order of the steps, the software guides you step by step. Instead of trusting that the person will apply the correct rule, the system enforces the rule. Knowledge ceases to be a memory and becomes part of the tool.
Think of the employee who “knows” that every order over a certain amount needs special approval, or that a certain customer has a different condition. If that’s just in his head, go away when he’s gone. If it’s in the system, the software itself requires approval, enforces the condition, prevents the error—regardless of who’s operating. This is how the process migrates from the person to the company. Not by chance, it’s the same movement as when the company decided to replace spreadsheets with a system: the logic that lived hidden in a formula that only one employee understood becomes a clear, recorded rule that is proof of team change.
The process automation takes this one step further. Tasks that relied on someone remembering to perform them—triggering a charge, sending an alert, updating a status—begin to happen on their own, guided by the rules of the business. The more of the process is built into the system, the less the company depends on a specific person remembering to do it, and in the right way.
Reducing dependency is not devaluing people
Practical care before following: reducing dependency is a process, not an event. The worst time to start documenting and distributing knowledge is just when the person who holds it is already leaving, with one foot out the door and unwilling to teach. The right time is now, with the employee present, valued, and collaborating — not under the strain of a dismissal. Companies that treat this as a routine, not as a response to a crisis, build resilience little by little, without friction and without depending on the last-minute goodwill of those who are leaving.
Here it is worth dispelling a common misunderstanding. Getting the process out of a person’s head is not a way to slow them down or to prepare to fire them. It’s the opposite: it frees the good employee from the role of being held hostage by their own knowledge. That employee who was unable to take a vacation in peace, who was interrupted with every doubt, who could not get sick without something getting stuck – this collaborator is now able to grow, delegate and use talent in more strategic things than being the “guardian” of a routine.
And from the point of view of those who lead, reducing dependency is what allows the company to grow. A business in which every critical process depends on an irreplaceable person has a low ceiling: it doesn’t scale, it doesn’t delegate, and it doesn’t easily survive team changes. Distributing knowledge — in documentation, in training, and especially in the system — is what transforms a fragile operation into a solid operation.
Does your company work for you or for an individual?
Where to start reducing dependency
If reading so far triggered an alert, the good news is that the first step is simple and doesn’t cost anything: mapping. List the company’s critical processes and, next to each one, how many people would know how to touch it if the incumbent were absent tomorrow. Where the answer is “one”, you’ve found a point of dependency — and prioritizing those points already shows where to attack first.
From there, the logic is to go from the riskiest to the least risky, one process at a time. Start with what would cause the most damage if it stopped, recording how it works and, when it makes sense, embedding that logic into the system so that it stops depending on memory. It’s not a one-weekend project, but each unlocked process is one less risk – and the company is becoming more solid with each one.
The question that remains is simple and revealing: if your key employee left tomorrow, how much of your operation would go along with it? If the answer scares, it’s not the employee’s problem — it’s the fact that the process never left their head. And this has a solution, without drama and without having to change anyone: it’s a matter of registering, distributing and, above all, embedding this knowledge in the tool that the company uses every day.
At Sulivam, we develop systems that place the business process within the software – the rules, the flows, the exceptions – so that the company stops depending on anyone’s memory. If you recognized your business in the first sentence of this text, it’s worth a conversation. A healthy company is one that continues to function even when someone, no matter how good, decides to follow another path.
