Being the only person who knows how something works

Nobody decides to become the only one

It accumulates. You fix something once because you happened to be free, then you are asked about it because you fixed it last time, then the person who originally built it leaves and their half of the knowledge goes with them. Two years later a spreadsheet, a script, a supplier relationship or an undocumented monthly process runs entirely through you, and no one — including you — ever made a decision to arrange it that way.

The knowledge itself is usually not complicated. What makes it irreplaceable is that it is unwritten and scattered: the reason a step exists, the exception that breaks it, the person to call when the file arrives in the wrong format. Any one of those is trivial. Collectively they are a body of working knowledge that lives nowhere except in one head, which is a fragile arrangement for the organisation and a worse one for the head.

Security is the wrong word for it

The folk theory says that being indispensable protects you, and there is a narrow sense in which that holds — you are unlikely to be first out in a cut while the thing still runs. But protection from removal is not the same as being able to move, and the second is what an early career depends on. The team that cannot lose you also cannot release you, and every conversation about a transfer, a secondment or a stretch project starts from the question of who covers your thing.

It shows up in smaller ways first. Leave becomes awkward to take. A quiet fortnight never quite arrives, because interruptions arrive on someone else’s schedule. Work that would develop you goes to a colleague who was available, and the reason given is entirely reasonable each time it happens.

How it looks from the management side

Well-run organisations treat single points of knowledge as a risk to be reduced, and if yours does, then someone above you already has your name on a list of things that would hurt if they went wrong. That is not a compliment. It means your value is being recorded as exposure rather than as capability, and the fix being contemplated is not necessarily one that involves promoting you.

Less well-run organisations do the opposite and simply enjoy the arrangement, because it is cheap and it works until it doesn’t. Both responses point the same way for you. Whether the concentration of knowledge is treated as a hazard or as a convenience, the person carrying it does not benefit from carrying it alone.

Writing it down is self-interest

People resist documenting the thing they own, and the resistance is rarely stated aloud because the stated version sounds bad. The unstated worry is that a written process makes you replaceable. In practice it does something more specific: it makes the routine parts transferable while leaving the judgement with you, and judgement is the part that was actually scarce.

A useful document is short and answers the questions someone will genuinely have at eight in the morning when it has broken. What is this for, what does it depend on, what goes wrong most often, who owns the system upstream, what did we already try and reject. That is a page or two. The exhaustive manual nobody reads is a way of appearing to solve this while keeping the real knowledge exactly where it was.

The kind of indispensability that does pay

There is a version of this that genuinely helps a career, and it is worth distinguishing from the version that traps. Being the person who can solve a class of hard problems is portable, valued anywhere, and hard to substitute. Being the only person who knows the local particulars of one employer’s systems is valuable to exactly one buyer, which is a weak position in any negotiation, including the one about your own pay.

The distinction is roughly between depth of skill and custody of secrets. Skill travels with you and is recognisable to strangers. Custody evaporates the day you leave, and it also means the strongest thing you could say in an interview is that you were the keeper of arrangements nobody outside the building has heard of.

Handing it on is not always welcomed

Offering to train a colleague sounds unambiguously good and is not always received that way. In a stretched team it reads as asking for someone else’s hours, and in a badly run one it can read as manoeuvring. The move that tends to work is to attach it to something the organisation already wants — an audit, a leave plan, a period when the thing broke and was noticed — rather than raising it as a general principle nobody has budget for.

It is also fair to say that some places will let you carry it indefinitely and quietly benefit while you do. If you have raised it twice with specifics and nothing has changed, that is information about the organisation rather than about your framing, and it belongs in whatever assessment you are making of how long to stay.