The person is not a database

Organizations often discover key-person dependency at the moment someone leaves. The response is usually documentation: write down the process, record the walkthrough, move files into the shared drive.

Documentation matters. It also captures only part of what the person was holding.

Knowledge includes judgment

Experienced people know which rule matters in which circumstance. They know when a dashboard is wrong, which customer exception is genuinely risky, who needs to be consulted before a change, and what happened the last time the organization tried something similar.

Much of that knowledge is relational and contextual. It cannot be transferred by listing steps alone.

Dependency is architecture information

A person becoming indispensable can be flattering to the person and dangerous to the system. Often it means several interfaces have collapsed into one human being.

They are not only doing their job. They are translating, remembering, routing, reconciling, and absorbing ambiguity for everyone around them.

The answer is not to make every person interchangeable. Expertise is valuable precisely because it is not generic.

The design goal is to make expertise legible enough that the system can learn around it: shared context, overlapping knowledge, explicit decision principles, relationships that extend beyond one person, and time for others to practice before the expert disappears.

If the organization stops working when one person leaves, the question is not only what that person knew. It is what the system had quietly asked them to become.

I once wrote a blunt version of this problem: no single point of failure. If you have two jobs, you need two people who know enough about each other's work to cover it. Instead, organizations often have one person doing two jobs, which works beautifully if everyone is fully staffed and nothing ever breaks.

Shared capacity does not mean making people interchangeable. It means allowing knowledge to cross-pollinate before a crisis forces the transfer. Rotations, paired work, shared relationships, and overlapping context can make an organization less dependent on heroic memory without erasing expertise.