The person everyone routes around to
Every growing business has one. The person who “just knows how it works.” When a weird order comes in, when the system does something strange, when a customer has an unusual request — everyone knows who to ask. It feels efficient. It feels like a strength.
It’s a single point of failure, and it usually stays invisible until the day that person is on vacation, out sick, or gone.
Why it feels fine until it doesn’t
Relying on one person works, right up until it spectacularly doesn’t. The work flows, the answers come fast, nothing’s written down because nothing needs to be — the knowledge is right there in someone’s head.
Then they take a two-week trip, and three things stall because nobody else knows the steps. Or they leave for another job, and you find out how much of the business was actually running on memory. The cost was always there. It was just deferred.
Key-person risk, in plain terms. It’s the exposure you carry when the loss of one person would seriously disrupt the business. Software people call it the “bus factor” — how many people would have to get hit by a bus before the work stops. If the answer is one, that’s worth fixing before circumstances fix it for you.
How to spot it
You don’t need an audit to see it. The signs are everywhere once you look:
- The same name comes up every time there’s a question — “ask Maria, she’ll know.”
- Work visibly slows or stops when one specific person is out.
- Nobody else has done a given task start-to-finish in the last year.
- The “how” exists only as something people learned by watching, never written down.
- You, the owner, can’t take a real week off without your phone going off.
That last one is the tell most owners feel before they can name it.
What it’s quietly costing you
Key-person dependency doesn’t just create risk. It caps the business.
You can’t grow past the bottleneck — every new hire, new location, or new line of work still has to route through the one person who knows. You can’t take time off without staying on call. And if you ever want to sell the business, a buyer will discount it hard the moment they realize it runs on someone who might not stay.
The dependency feels like leverage. It’s actually a ceiling.
It’s not about the person
Worth saying plainly: this isn’t a knock on the person who holds the knowledge. They’re usually your best employee, and they didn’t create the gap on purpose. The problem is structural — the business never built a way to hold the knowledge anywhere but in one head.
So the fix isn’t “replace them” or “make them write a manual this weekend.” It’s to deliberately move critical knowledge out of memory and into something the business owns.
How to start de-risking it
- Find the dependencies. List the tasks that would stall tomorrow if a specific person were unreachable. That short list is your real risk map.
- Capture the judgment, not just the steps. The valuable part isn’t “click here, then here.” It’s when do you deviate, and why — the calls the expert makes without thinking. (Documenting that is its own skill.)
- Cross-train for real. Have a second person actually do the task, start to finish, while the expert is still around to correct them.
- Make ownership explicit. Decide who owns each critical process on paper, so it’s not just whoever happened to learn it first.
A warning: writing a document is not the finish line. A binder nobody opens fails the same way memory does — documentation alone doesn’t equal stability. The goal is knowledge the business can actually use without the original person in the room.
Where this usually goes
The hardest part is seeing your own dependencies clearly — the person who holds the knowledge can’t always see what they know, and you’re too close to it to map it cold. That’s a big part of what an operations diagnostic does: find the points where your business depends on one person, and lay out what to fix first.
If your business has a name everyone routes around to, a short strategy session is a low-risk way to figure out how exposed you actually are.
