The Person Who Is Not Allowed to Get Sick

There is a person inside your company who is not allowed to have a bad week.

You have probably never said that out loud. It has never appeared in a job description or a review. But everyone knows who it is. When their name comes up on the vacation calendar, somebody makes a joke that is not entirely a joke. When they call out sick, a low hum of anxiety moves through the building. They are the one who knows why the process runs the way it runs, why that exception exists, why the numbers only reconcile if you do the thing in the specific order they always do it in.

They are not a bottleneck because they are difficult. They are a bottleneck because they are excellent, and because for years everyone has been quietly grateful that somebody had it handled.

That gratitude is the trap.

Here is what has actually happened. Over time, that person stopped being an employee and became infrastructure. Load bearing. And nobody ever made that decision. It accumulated, one favor and one workaround at a time, until a meaningful piece of your business existed only inside one human skull, with no backup, no documentation, and no plan.

The research on this is blunt. 47 percent of organizations now name key person dependency, meaning critical knowledge held by a single individual, as a significant operational risk, up sharply from 34 percent just a few years earlier (https://atlan.com/know/data-for-ai/tribal-knowledge/). And when that person walks, what leaves with them is not small. Roughly 42 percent of company knowledge is unique to the individual employee, which means when they go, their colleagues cannot effectively cover nearly half of what they were doing, and a new hire has to rebuild it from scratch (https://360learning.com/blog/institutional-knowledge/).

Sit with that for a moment. Not half their tasks. Half their understanding.

Now here is the part that stings, and I say it with real affection for the person in question, because they are usually the most loyal one you have.

The dependency is not their fault, and it is not their fault to fix either. They did not hoard the knowledge. They just showed up every day and did the job while the system quietly failed to keep up with them. The workaround they invented in year two became the process by year four. The spreadsheet they built to help became the source of truth. Nobody ever gave them the time or the tooling to make their knowledge visible to anyone else, so it stayed exactly where it started. In their head.

And it is costing them too. That person cannot really take a vacation. Cannot get promoted, because who would do their job. Cannot get sick without guilt. The reward for being indispensable is a cage, and the most valuable person in the building is often the most quietly exhausted.

When we start work with a company at Cause of a Kind, one of the first things we go looking for is not a technology gap. It is a person shaped one. Who is the single point of failure here. What lives only in their head. What happens on the day they finally take the job someone else is going to offer them. That conversation is usually uncomfortable, and it is always the most important one in the room.

Here is the wisdom, and it applies whether you have four employees or four hundred.

Dependence on a person is not loyalty. It is unbuilt system, and you are paying for it in a currency that never shows on a P&L. Good systems do not diminish your best people. They liberate them. When you finally get what is in their head into something durable, a real tool, a real process, a real piece of software, you are not replacing them. You are giving them permission to stop being a filing cabinet and go back to being the brilliant human you hired.

The strongest companies I know are not the ones with irreplaceable people. They are the ones where excellent people are free to grow, take a real vacation, get promoted, and leave the business stronger than they found it, because what they knew was captured while they were still here to explain it.

If a specific face appeared in your mind while you were reading this, and I would bet almost anything that one did, then you already know exactly where your risk lives.

Now ask yourself the harder question.

Do they know that you know, and have you ever done anything about it.