Ask yourself an uncomfortable question: how many of your employees would have to be hit by a bus tomorrow for a critical process in your company to grind to a halt?
If the answer is "one," you have a bus factor of 1. And with it a problem you probably already know - just under different names: "Ms. Berger handles that." "You'll have to wait until Mr. Kaminski is back from vacation." "Only the colleague who left last year knew that."
This article explains where the term comes from, how to spot knowledge monopolies in your company, what knowledge loss really costs - and how to tackle the problem systematically without locking your people into documentation workshops for weeks.
What Is the Bus Factor?
The term comes from software development. As early as the nineties, developers were asking: how many people can a project afford to lose at most (the "bus" being the drastic metaphor for it) before nobody understands the code anymore? A project with a bus factor of 1 hangs on a single person. If that person is gone, everything stops.
Software teams responded with code reviews, pair programming, and mandatory documentation. Not out of kindness, but because they had seen the damage too many times.
Small and midsize businesses have a bus factor too - people just rarely talk about it. Instead of code, it's about processes: Who knows how to fill out the customs paperwork for the Switzerland shipment? Who knows the password for the main supplier's portal? Who knows why the invoice for the Müller account always has to be adjusted manually before it goes out?
The insidious part: in a software team, at least the code lives in a repository. In an SMB, process knowledge often lives nowhere. It sits in people's heads, in email inboxes doubling as filing systems, and in workflows that run on a shout across the hallway - as long as the right person is sitting at the right desk.
How to Spot Knowledge Monopolies
Knowledge monopolies don't hide. They're actually quite visible in everyday work - you just have to listen. Here are the typical warning signs:
"Only Ms. X knows that"
The classic. If this sentence comes up regularly in your company, you have a map of your knowledge monopolies - you just have to take it seriously. For one week, write down every topic where people point to a single person. The list will get longer than you'd like.
Vacation coverage fails
Ms. Berger is away for two weeks. Officially, Mr. Schulz is covering for her. In practice, the work piles up on her desk, because Mr. Schulz carries the title of "backup" but has neither the access rights nor the detailed knowledge. After her vacation, Ms. Berger spends three weeks working through the backlog. If vacation in your company means work sits still instead of moving forward, that's not a staffing problem. It's a knowledge problem.
The resignation shock
An employee resigns, and panic spreads in the leadership team - not because of the open position, but because of what he's taking with him. The remaining weeks of the notice period turn into a frantic "handover": the departing colleague is supposed to document in four weeks what he built up over fourteen years. The result is usually a Word document that forgets half of it and that nobody can find six months later.
More signals you should take seriously
- New hires take forever to get up to speed, because onboarding means: "Sit next to your colleague and watch."
- The process manual exists - as a PDF from 2021, created for a certification, untouched ever since. What it says has little to do with how things actually run.
- Certain people are unfireable - not because of their performance, but because nobody knows what comes after them. And by the way, they know it too.
- Questions always route through the same people. Anyone who gets interrupted constantly because "only he knows that" is a walking knowledge monopoly - and a bottleneck for everyone else on top of it.
What Knowledge Loss Really Costs
There are no credible blanket figures here - treat any study promising "knowledge loss costs X euros per employee" with caution. But you can honestly run the numbers for your own company. The costs come from four line items:
1. Rebuilding the knowledge. When knowledge leaves with a person, it has to be rebuilt from scratch. The successor experiments, makes mistakes, asks suppliers and customers things that were settled internally long ago. Do the sober math: how many months does a successor need to reach the predecessor's level? For specialized knowledge, it's rarely under six months - the salary runs the whole time, full output doesn't.
2. The mistakes in the meantime. The incorrectly filled-out customs declaration, the missed deadline on the framework agreement, the customer whose special terms nobody remembered. A single one of these mistakes can cost more than a year's salary - and they happen precisely when the knowledge that would have prevented them is gone.
3. The everyday bottleneck. Knowledge monopolies cost money even without a resignation, every single day. Decisions wait until the one person has time. Projects slip because one calendar is the bottleneck. And the knowledge holders themselves never get to their actual work because they're busy answering questions.
4. The leverage problem - honesty demands we name this one too. Someone who is irreplaceable negotiates differently. That's human, and the people involved often aren't even aware of it. But a company that depends on individual heads holds structurally weak cards in salary negotiations, during change, and in conflicts.
The exact amount differs from company to company. The direction doesn't: knowledge lost to a resignation is almost always more expensive than anything prevention would have cost.
How to Dismantle Knowledge Monopolies Systematically
The bad news first: the reflex of "we need to document everything!" fails reliably. A documentation workshop gets scheduled, everyone groans, twenty pages get written that nobody maintains - and a year later the next outdated Word template sits untouched in the team folder. Documentation as a one-off project doesn't work, because processes change and paper doesn't notice.
What works instead, in four steps:
Step 1: Make the monopolies visible
You can't dismantle what you don't know about. Create an unvarnished overview: which processes exist, who has mastered them - and which ones have exactly one name next to them? Don't ask only the managers. They often know surprisingly little about how the work actually gets done. The boss says "that runs through SAP"; the team knows it actually runs through three Excel spreadsheets and one colleague's experience. Knowing both is the real insight.
This is exactly where tools like wissa.ai come in: an AI conducts short interviews with your employees - 15 to 20 minutes per person, via chat, no workshop required. If someone says "Max and Hanne handle the complaints," both are automatically invited next. The system works its way from one knowledge holder to the next and, at the end, shows you in black and white who knows what alone - a bus factor analysis backed by evidence from the interviews, instead of gut feeling from the management meeting.
Step 2: Prioritize by risk, not alphabetically
Not every monopoly is equally dangerous. Rate two dimensions: how critical is the process for the business, and how likely is it that the person drops out (retiring in two years? Known to be unhappy? The only person with access to the banking portal?). Start in the top right corner - critical process, shaky knowledge holder.
Step 3: Spread the knowledge across more heads
Documentation alone isn't enough - knowledge also has to actually land with a second person. Proven methods: real backup arrangements in which the backup regularly performs the process themselves (not just watches). Rotation for recurring tasks. And the simple rule: every critical process needs at least two people who have mastered it, plus a description that would get a third person through it in an emergency.
Step 4: Keep the documentation alive
This is where most companies fail. Process documentation is only worth as much as its last update. Build updating into everyday work: when a process changes, the documentation gets adjusted in the same breath - not "at some point." Short, regular conversations beat the big annual workshop. And if the documentation updates itself after every conversation and shows you what changed since the previous version, all the better - then it's a living working tool instead of a PDF graveyard.
The most important advice at the end of this section: start small. One department, the five most critical processes, the two biggest knowledge monopolies. One dismantled monopoly is worth more than a concept covering everything.
Conclusion: The Bus Rarely Comes - the Resignation Always Does
Thankfully, the bus from the metaphor almost never actually hits anyone. But employees resign, retire, fall ill, or move into different roles. The question isn't whether your company will lose knowledge holders, but when - and whether the knowledge leaves with them or stays.
If you want to know where your knowledge monopolies sit without scheduling workshops: wissa.ai finds them through AI interviews - 15 to 20 minutes per person, GDPR-compliant with EU hosting, voluntary participation, no performance evaluation. The beta waitlist is open: €149 per month with 12 interview credits, free for the people being interviewed.
FAQ
What does a bus factor of 1 mean?
A bus factor of 1 means the loss of a single person paralyzes a process or an entire project, because only that person has the necessary knowledge. The higher the bus factor, the more people would have to drop out at the same time before things get critical. The target for every business-critical process: a bus factor of at least 2.
How do I find out where knowledge monopolies exist in my company?
Listen for sentences like "only Ms. X knows that," check which topics sit still while individual people are on vacation, and ask the employees themselves - not just the management level. The systematic way is structured interviews with everyone involved, from which you can read off which processes hang on exactly one name.
Isn't a handover from departing employees enough?
No. A handover in the final weeks of a notice period can't capture knowledge that grew over many years - the departing colleague himself no longer knows everything that has become second nature to him. Securing knowledge only works while the person is still relaxed and on board, not after they've resigned.
What does knowledge loss cost when someone resigns?
There is no credible blanket figure. Run the numbers for your own case: months until the successor reaches full productivity, mistakes and missed deadlines during the transition, projects left sitting. With specialized knowledge, the total quickly exceeds a year's salary - prevention is almost always cheaper.
Don't knowledge holders resist sharing their knowledge?
Less often than feared. Most knowledge monopolies arise not from intent but from lack of time - nobody ever asked. Many knowledge holders are relieved when they're no longer the bottleneck for every question and can finally take a vacation without worrying. What matters is the framing: voluntary, respectful, and without performance evaluation.