Every workplace has at least one.
The person who knows how to fix the report when it breaks.
The person who remembers why the process has that weird extra step.
The person who knows which spreadsheet is actually current, who to call when something goes wrong, and what “we tried that once” really means.
Experienced, knowledgeable employees are obviously a good thing. The problem starts when important knowledge doesn’t exist anywhere else.
That’s tribal knowledge: information people need to do their jobs that lives primarily in someone’s head instead of somewhere the rest of the organization can reliably access it.
You can usually spot it with a simple question:
If that person unexpectedly took the next two weeks off, what would stop?
Maybe no one else knows how to prepare the monthly report. Maybe a project can’t move forward because one person knows the history behind all the decisions. Maybe the organization has documentation, process diagrams, and training materials, but when something unusual happens, everyone still says:
“Ask Sarah.”
That’s key-person dependency. And it often develops so gradually that nobody thinks of it as a problem.
Until Sarah isn’t available.
But before we start blaming Sarah for knowing too much, it’s worth looking at how she became the person everyone asks in the first place.
Being Sarah Can Feel Pretty Good
There’s an uncomfortable human side to this that is easy to skip when we talk about knowledge management.
Knowledge has value.
If Sarah is the only person who knows how an important process works, people need her. She’s included in conversations. Her opinion carries weight. She’s difficult to replace.
Most people aren’t sitting at their desks plotting how to withhold information from their coworkers. But it would also be naive to pretend people never recognize the security or influence that comes from being indispensable.
Sometimes knowledge gets protected. Someone trains a coworker on the steps but not the judgment behind them. They keep control of a responsibility long after they could have shared it. They answer questions as they arise but never create a resource that lets people stop asking.
Over time, expertise can turn into territory.
But that’s not necessarily what’s happening with Sarah.
She may be desperate for someone else to know what she knows.
Because there’s another way people become indispensable, and it’s probably even more common.
Sometimes the Expert Is Just Too Busy to Stop Being the Expert
Imagine you’ve done the same complicated task for eight years.
You can do it in 20 minutes.
Teaching someone else might take two hours. Writing instructions that account for all the exceptions might take half a day.
And you’re already busy.
So when someone asks how to do it, you say:
“I’ll just take care of it.”
That is completely rational today.
The problem is that you’ll probably make the same calculation next month.
Soon, you’ve become the only person who can do the task precisely because you’ve never had enough time to teach someone else how to do it.
Then the requests multiply.
Can you fix this?
Do you remember why we do it this way?
Can you handle this before you go on vacation?
Your expertise makes you valuable, but it also makes you a bottleneck.
And it creates a cycle:
The expert knows the most, so more work goes to the expert.
➡️Because more work goes to the expert, they have less time to teach others.
➡️Because others aren’t learning, the knowledge gap widens.
➡️Because the knowledge gap gets wider, even more work has to go to the expert.
Being indispensable can become a trap.
You can’t easily redistribute work when you’re overloaded.
Higher-value work gets squeezed between routine responsibilities you can’t delegate.
The organization depends on you so much that it’s hard for you to move on to anything else.
Everyone Else Pays for It Too
While Sarah fields questions all day, everyone else waits for answers.
Usually, the delay isn’t dramatic. Someone sends a message, Sarah is busy, work pauses, and eventually everyone moves on.
But multiply that across dozens of questions, processes, projects, and employees, and the cost starts to add up.
Work slows down. Managers have fewer options for distributing it. And if every difficult task goes to the person who already knows how to do it, other employees get fewer opportunities to develop that expertise themselves.
The organization hasn’t just concentrated knowledge.
It has concentrated capability.
And that’s a much bigger problem when Sarah leaves.
People retire. They accept new jobs. They take leave. Organizations restructure. Sometimes positions are eliminated before anyone realizes how much tribal knowledge is walking out the door with them.
The clients, systems, reports, processes, and deadlines are all still there.
Sarah isn’t.
A replacement may be perfectly capable and still spend months reconstructing information the organization once possessed.
Now they’re not just learning a new job.
They’re doing organizational archaeology.
The Answer Isn’t to Document Every Thought in Everyone’s Head
The obvious response to tribal knowledge is:
We need to document everything.
Suddenly everyone has another administrative task, a giant process-documentation project appears, and six months later a SharePoint library is full of documents nobody has opened since they were created.
More documentation doesn’t automatically mean more accessible knowledge.
Instead, start where the dependency causes problems, and match the solution to the problem.
A repeatable process might need clear documentation. A complicated responsibility may need cross-training and hands-on practice. A routine task might be better automated. Information people can’t reliably find may need a better shared home.
You don’t have to eliminate every knowledge gap. Start with the ones that create bottlenecks and find the simplest way to make that knowledge accessible to someone else.
Start With the Person You Can’t Afford to Lose
Here’s a simple exercise.
Ask your team:
Who in our organization could unexpectedly take the next two weeks off without work coming to a stop?
Then ask the harder version:
Who couldn’t?
If a name comes to mind immediately, you’ve found a place to start.
Don’t begin by asking that person to document everything they know. Sit down with them and figure out where the dependency actually lives.
- What do people ask them about over and over?
- What can nobody cover when they’re gone?
- What work have they wanted to hand off but haven’t been able to?
- What information would be difficult to reconstruct if they weren’t available tomorrow?
Those answers will tell you what actually needs to change.
Maybe that’s documentation. Maybe it’s cross-training, automation, better information management, or a process that needs to be redesigned so it doesn’t depend so heavily on one person.
And if you’re too close to the work to see those dependencies, we can help.
Advisicon can help you identify where critical knowledge, processes, and responsibilities have become concentrated in individual people and find practical ways to spread that capability across your team.
Because the goal isn’t to make your best people easier to replace.
It’s to make sure everyone can do their job better because of what those people know.
