Bus factor explained: how many departures break a team?
What the bus factor is, how to calculate it task by task, why a team-wide number can hide single points of failure, and how to raise it before someone leaves.
On a Tuesday morning, the production line stops. The one person who knew why the changeover runs in that exact order is on a plane. Nobody wrote the sequence down, because it never needed writing down. By noon the schedule is two days behind, and two people are quietly asking each other what else only he knew. That is a team with a bus factor of one.
The bus factor is the number of people who would have to leave a team before its work stalls because nobody left knows how it is done. A bus factor of one means a single departure stops something important. A bus factor of four means four people would have to go at once before anyone is truly stuck. The grim name comes from software teams asking "what if she gets hit by a bus?" You will also hear truck factor or lottery factor, which is the same idea with a happier ending.
Key takeaways
- The bus factor is how many people can leave before a piece of work stalls.
- Count it per task. A healthy team-wide number can hide tasks only one person can do.
- Any task with one name next to it is a single point of failure. Fix the costly ones first.
- Raise it by pairing a second person on the real work and capturing the reasoning in the owner's words.
It is a simple number, and most teams only count it after the loss.
What the bus factor measures
The bus factor is not about headcount, or how many people are copied on an email thread. It counts how many people can actually do a piece of work from memory and judgment, with no one to ask.
That knowledge lives in heads, not in files. The customer who only talks to one account manager. The machine setting one operator knows by feel. The reason the quarterly report is pulled a certain way, and why nobody has changed it in six years. When it sits with one person, the team is carrying a debt it has never written down.
Bus factor, single point of failure and key person risk
These terms overlap, and people use them loosely. A rough guide:
| Term | What it means | Example |
|---|---|---|
| Bus factor | How many people must leave before a piece of work stalls | Only Marta and Jonas can close the month, so the bus factor is two |
| Single point of failure | Any one thing whose loss stops the work: a person, a system, a supplier | The one server the scheduling tool runs on |
| Key person risk | The business risk of depending on one individual, often for clients or revenue | The founder who holds every major client relationship |
| Tribal knowledge | The undocumented know-how that creates a low bus factor | "Ask Priya, she knows how the discount approval works" |
A bus factor of one is a single point of failure that happens to be a person.
Why a bus factor above one is not automatically safe
This is where quick checks go wrong. A team of twelve might score a bus factor of five overall and feel fine. But that five is rarely spread evenly across the work.
You might have five people who can cover the front desk and one who can run payroll. A deep bench on the product side and a single person who understands the compliance calendar. The team number looks healthy while a few quiet single points sit underneath it, each with a bus factor of its own.
So the useful question is not "what is our bus factor?" It is "which pieces of our work have a bus factor of one, and what would losing each of them cost?" Some single points are cheap to rebuild. Others walk out the door with a client.
How to calculate your bus factor, task by task
You don't need a twenty-column spreadsheet. You need an hour and a willingness to hear an uncomfortable answer.
- List the critical tasks. Pick the ten or fifteen pieces of work that would actually hurt if they stopped for two weeks. Don't try to map everything.
- Write down who can do each one without help. Not who has seen it done. Who could pick it up on Monday if the owner left on Friday.
- Count the names. That count is the bus factor for that task. Any task with one name is a single point.
- Ask how long cover would take. If the honest answer is "weeks," treat a two-name task as a one-name task.
- Note what you would lose in the meantime. A client, a deadline, a regulatory filing, a relationship with a supplier.
A small example from a five-person finance team:
| Critical task | Who can do it alone | Bus factor |
|---|---|---|
| Month-end close | Marta, Jonas | 2 |
| Payroll | Marta | 1 |
| Supplier payments | Marta, Jonas, Eva | 3 |
| Bank reconciliation | Jonas, Eva | 2 |
| VAT return | Marta | 1 |
The team looks covered until you notice that two of the five tasks depend on Marta alone. Her two weeks of holiday in August is your early warning.
Signs your bus factor is low
You will often spot the risk before you finish counting. These signals tend to show up together:
- Questions route through one person. When someone is unsure, the answer is always "ask Priya." Priya is a bus factor of one with a name tag.
- Time off is a small crisis. When one person takes two weeks and the team rearranges itself around the gap, that gap told you what you needed to know.
- "It's easier if I just do it." Efficient for one person, fragile for everyone else.
- The documentation is missing or out of date. A document that no longer matches reality is not protection. It is false comfort.
None of this means the person is doing anything wrong. They are usually the most trusted people on the team, which is exactly why losing them hurts. For a longer list, see 7 signs tribal knowledge lives in one person's head.
How to raise a low bus factor
You don't need to fix every single point this quarter. Decide which ones you can live with and which ones you can't.
Start with the costly ones. Protect the tasks where a departure would cost you a client, a deadline or a season. The rest can wait for the next pass.
Pair people on the work, not just the meeting. A second person who has actually done payroll twice, with the owner beside them, is worth more than ten pages of notes.
Get the reasoning out, not just the steps. A checklist shows what to click. It rarely says why the order matters or what to do when something looks wrong. That judgment is what the next person is missing. These knowledge transfer interview questions are a good way to draw it out.
Put it where people already look. A handover nobody can find is the same as no handover. Here is how a knowledge base, a wiki and shadowing compare.
And if someone with a bus factor of one has already resigned, follow this 3-step plan for departing employees while they are still there. Every week of rebuilding from memory has a price, and you can put your own number on it.
Where OakHive fits
The hard part isn't deciding to capture what someone knows. It is that the people who hold the most are the busiest, so it gets postponed until it is too late to ask.
OakHive does the asking. Before someone leaves, an AI interviewer talks with them about their work, by voice and in their own language, and follows up when an answer is vague. What comes back is a handover guide for the successor, a summary for the manager that lists what wasn't covered, and a chat the team can ask later, in OakHive or in Microsoft Teams. The person leaving has nothing to prepare. See how it works.
The short version
The bus factor is how many people a team can lose before work stops. The team-wide number hides the tasks that depend on one person, so count it task by task. Then deal with the single points that would cost you most, starting with getting the reasoning out of people's heads while they are still around to explain it.
Frequently asked questions
What is the bus factor?
The bus factor is the number of people who would have to leave a team before a piece of work stalls, because nobody remaining knows how to do it. A bus factor of one means a single departure stops that work.
Why is it called the bus factor?
The name comes from software teams asking what would happen if a key developer were hit by a bus. It is also called the truck factor or lottery factor. The point is any sudden departure, including resignation, retirement or long leave.
How do you calculate the bus factor?
List your critical tasks, then write down who could do each one alone, without help. The number of names is the bus factor for that task. Any task with only one name is a single point of failure.
What is a good bus factor?
At least two for every critical task, and three for work that clients or regulators depend on. A high team-wide number means little if a few important tasks still rely on one person.
How do you increase the bus factor?
Pair a second person on the real work, capture the reasoning behind each task in the owner's own words, and keep it somewhere the team already looks. Start with the tasks where a departure would cost you most.
