Every service-based business has at least one person who is, quietly, the keeper of the keys. They know how the booking system works, why the third Tuesday of the month is always busier, which client prefers a phone call over email, and where the spreadsheet with the actual numbers lives.
When that person is in, things run. When they take a day off, something always slips. And when they leave the business entirely, the gap takes months to close, sometimes longer.
This is one of the most consistent patterns I see in small businesses, and it is almost always invisible until something happens that brings these problems to light.
The Risk That Hides in Plain Sight
Most founders see the person who "just knows how everything works" as a strength of the business. In some ways they are.
They make the day-to-day move faster.
They prevent small problems from becoming big ones.
They are, often, the reason things have not broken yet.
But the same person is also a single point of failure. And the longer the business runs on their knowledge, the higher the cost when that knowledge becomes unavailable, whether through holiday, illness, or a resignation letter you did not see coming.
Concentrated knowledge is one of those risks that compounds quietly. It works perfectly for years, and then one day it stops, and the recovery is expensive.
How Knowledge Gets Concentrated in the First Place
Nobody designs a business this way on purpose. It happens through three very normal patterns.
The first is that early on, every founder does everything. They are the person with all the answers because they made all the decisions. That is fine when the team is small.
The second is that as the team grows, certain people become the natural go-to for particular things.
The bookkeeper learns the quirks.
The practice manager learns the relationships.
The senior staff member learns the patterns.
They become indispensable, and the business benefits from that.
The third is that nobody writes any of it down, because it would feel like overkill at the time. Every time someone asks a question, the answer is given verbally, and the asker moves on. The knowledge stays in the same place it has always been.
By the time you notice, you have a business where 2-3 people are carrying 80% of the operational knowledge between them. And if any one of them is unavailable, the business pays a tax, as if tax wasn't annoying enough already.
What "Paying a Tax" Actually Looks Like
When key people are unavailable, the cost shows up in a few predictable ways.
Clients wait longer for things.
Decisions queue up.
Other staff spend hours trying to reconstruct information that one phone call would have answered.
Mistakes get made because the person doing the work was missing the context the absent person would have provided.
For a one-day absence, this is usually absorbed. For a two-week holiday, it starts to be felt. For a resignation, it can shape the entire next quarter.
A study by Panopto found that knowledge workers spend an average of 5.3 hours per week waiting for information from colleagues or trying to find it themselves. That cost exists even when everyone is at their desk. When someone is away, the cost multiplies.
Why Hiring or Cross-Training Alone Does Not Fix This
The instinct, once a business notices this pattern, is to hire support for the key person, or to cross-train another staff member into the same role.
Both can be the right move. Neither, on its own, fixes the underlying problem.
If the knowledge still lives in someone's head, you have just moved the bottleneck to two people instead of one. The risk is reduced but not removed.
And the cross-trained person is now also building knowledge that lives in their head, ready to leave with them.
The actual fix is documentation. Boring, plain, accessible documentation that anyone in the business could read and act on. That is what turns concentrated knowledge into a business asset, rather than a personal one.
What Documentation Actually Needs to Look Like
It does not need to be a 200-page operations manual. In fact, the businesses that try that approach usually fail, because the document becomes too big to maintain and too unwieldy to use.
What works is shorter, focused, and accessible like these:
A one-page workflow for each core process.
A checklist for anything that happens repeatedly.
A simple "if this, then that" document for decisions the team makes regularly.
A list of clients with their preferences.
A glossary of internal terms.
The test is simple: if a competent person joined the team tomorrow, could they get themselves up to speed on this part of the business by reading the document? If yes, the document is doing its job. If no, the knowledge is still living in someone's head, and the document is just useless decoration, really.
Eg.
A 6-person professional services firm had a senior practitioner who was, by every measure, fantastic. She had built half the client relationships, knew every quirk of the delivery process, and was the person everyone went to with questions.
When she took 4 weeks of long-service leave, the team found themselves rebuilding context from scratch on 3 separate matters, missed a key client review, and spent the equivalent of a full extra week of effort trying to operate without her.
The fix was not to demand that she write a manual. What was actually done was spending 2hrs with her, in the first week back, building a one-page reference document for the 3 workflows that had caused the most trouble in her absence. That single document, written once, became the foundation for how the team handled those workflows going forward.
3 months later, the same staff member took 2 weeks of annual leave, and the team barely noticed.
Where to Start This Week
If reading any of this has surfaced one person in your business whose absence would cause real problems, start there.
Pick the one thing they do that would be hardest to cover if they were unavailable. Sit with them for an hour. Map it out. Write it down. Make sure someone else can read it and act on it.
That single hour of work will pay for itself the first time that person is on leave.
Next Steps
If you want a structured way to find every place your business has knowledge concentrated in one person, an Operations Review is designed to surface exactly that. It maps where the risk is and where the quickest fixes will give you the most resilience.
Book a chat with us to hear more about it.