Picture the one person who knows how your most important customer project really runs being out for two weeks starting tomorrow. Sick, no warning. How much would stall? How much would you have to guess?
If that question makes you uneasy, you probably have a bus factor of 1. This article is about what the metric means, why the risk is almost always underestimated, and how to reduce it without burying your team in documentation duties.
What the bus factor describes
The term sounds grim but it is an established concept from risk management. The question behind it: how many people would have to be unavailable, hit by a bus in the drastic version, before a project, a process or an entire area comes to a standstill?
If the answer is "one", you have a bus factor of 1. All the knowledge about something critical sits with a single person. As long as they are there, everything runs smoothly, and that is exactly the trap: the risk is invisible until it materialises.
Why the risk builds up quietly
No one consciously decides that everything should depend on one person. It happens on its own. Someone takes over an area, gets really good at it, becomes the fastest point of contact. So everyone asks that one person. Knowledge flows toward them, not away. With every problem solved, their lead grows, and so does the dependency.
Because everything works day to day, it goes unnoticed. The person is there, after all. They answer questions, solve problems, keep things running. That they have become the only source of critical knowledge only becomes clear when they are suddenly gone.
Latent risk becomes an acute problem
Three perfectly ordinary events turn the dormant concentration risk into an acute problem:
- Vacation. Two weeks away, and decisions pile up because no one knows the context.
- Illness. No warning. No handover, no preparation, just a gap.
- Resignation. The worst case. The knowledge leaves with the person and is often unrecoverable afterward.
In all three cases the effect is the same: the team is left with open questions and has to reconstruct what was actually known all along, just never captured anywhere.
Why "just write it down" does not work
The obvious answer is: document more. In practice this almost always fails for the same reasons.
Documentation that is meant to be created on top of the actual work has no priority in the daily grind. It gets postponed until there is time, which never comes. Even where something gets written, it goes stale quickly because no one maintains it. And the crucial part, why something runs one way and not another, rarely makes it in anyway. It lives in conversations, not in wikis.
That is precisely why the bus factor stays at 1 in many teams even though everyone knows it is risky. The problem is not lack of will, but that the usual fix creates work no one can do.
Secure knowledge straight from everyday work
The effective approach flips the logic: instead of forcing people to document on top of their work, collect the knowledge where it is created anyway, in the conversations themselves. That is exactly what a central knowledge base that fills itself does.
Sally joins meetings in Google Meet, Zoom, Microsoft Teams and Webex, documents phone calls and on-site appointments, and stores transcript, summary, decisions and tasks centrally. The key person's knowledge no longer sits only in their head, but in a searchable store the whole team can access.
When the person is out, you simply ask: "Where do we stand on project Y and what did we promise the customer?" The answer comes in seconds, with the source from the relevant conversation. The bus factor rises without anyone having to write a single extra line of documentation.
How to tackle it
- Identify critical areas. Where would a two-week absence hurt? Those are your weak spots.
- Ask honestly: bus factor 1? If only one person has the full context, the risk is real.
- Document conversations continuously. Once meetings, calls and appointments are captured automatically, knowledge spreads across the team on its own over time.
- Govern access. Simple roles let you decide who sees what, so sensitive topics stay protected.
For how Sally derives clear tasks from individual conversations, so that nothing slips even when a person is out, see the page on task recognition.
Conclusion
A bus factor of 1 is not a sign of negligence, but the natural result of people getting good at their jobs. It only becomes dangerous when the knowledge stays exclusively in one head. Documenting conversations continuously and automatically reduces key person risk in the background, with no extra effort.
You can try Sally as your central knowledge base for free and let it join your next meeting. That way you start spreading the knowledge that currently hangs on one person today.
