Charmain Bogue
Every organization has one. The person who knows where everything is, who has the relationships no one else has, who gets called when something goes sideways. They're described as invaluable. They're also a liability that most leaders don't recognize until the person gives notice or goes on leave.
Charmain Bogue of Washington, D.C. describes this as one of the most predictable and avoidable organizational problems she sees. The indispensable employee didn't become indispensable by accident. They became that way because knowledge got concentrated rather than distributed, because documentation didn't happen, because a single person's relationships substituted for institutional ones.
How It Happens
Indispensability builds slowly. Someone is good at their job and takes ownership because they care. Nobody is told to document anything, so they don't. Processes develop informally around one person's preferences and availability. Years pass, and the organization has a functioning system that only one person fully understands.
The person often doesn't realize how much they're carrying until someone tries to back them up and can't. By that point, the knowledge concentration is so deep that the only fix is to make the person available for a long handoff period, which they may or may not be willing or able to provide.
What This Costs the Organization
The most obvious cost is what happens when the indispensable person leaves. The organization loses the knowledge, the relationships, and often the clients or stakeholders who were loyal to that individual specifically. Recovery takes months and sometimes years.
The less obvious cost shows up before that. When one person is indispensable, everyone else is underutilized in some way. The skills and judgment that could be distributed across the team stay with one person. That limits growth at the team level and makes the organization dependent on a single point of failure in a way that smart operations design specifically tries to avoid.
What Good Leaders Do About It
Bogue has seen organizations try to solve this problem too late, after the indispensable person is already heading out the door. The better approach is continuous: knowledge sharing is treated as a normal professional obligation, not an emergency measure. People are expected to document what they know and to bring others into their relationships as a matter of practice.
The conversation Bogue has with leaders is often about how to structure that expectation without making the indispensable person feel threatened. People who have built their identity around being needed can resist knowledge transfer even unconsciously. The framing matters: this isn't about replacing anyone; it's about building an organization that can function and grow rather than one that requires any single person to be available at all times.
The measure of a well-run organization isn't whether it has people who are extremely good at their jobs. It's whether the organization can function without them for a week, a month, a year. If the answer to that question is unclear, the indispensability problem has already taken root. The time to address it is now, not when someone hands in their resignation.