Bus Factor: Meaning, How to Calculate It and How to Raise It
Author: Kevin Baur BSc
Published on
Contents
Imagine one person on your team is gone from tomorrow. Not for two days, but for months or for good. Which work stops? Who still knows how month end close works, where the logins for the online shop are or what was agreed with your biggest client? That is exactly the question the bus factor answers. This guide explains what the term means, how to calculate it for your team in a few minutes, what a bus factor of 1 tells you and how to raise it in six steps.
What is the bus factor?
Wikipedia defines the bus factor as the minimum number of team members that have to suddenly disappear from a project before the project stalls due to lack of knowledgeable or competent personnel. It measures the risk that comes from information and capabilities not being shared. A low number means knowledge sits with a few people. A high number means many people know enough to carry on.
The name is deliberately grim: what happens if someone gets hit by a bus? But it covers any sudden absence. Wikipedia lists a new job, parental leave or a change in life status, and illness, accidents and retirement belong on the list too. Because the bus image is a bit dark for many teams, the same measure goes by friendlier names:
- Truck factor or truck number: the older term from software development.
- Lottery factor: someone wins the lottery and quits the next day.
Wikipedia also notes that a bus factor of one is a single point of failure: a whole process depends on one person.
Where the term comes from
The idea comes from software development. Wikipedia cites an early example from 1994, when Michael McLay publicly asked what would happen to the Python language if its creator Guido van Rossum were hit by a bus. The term truck number appears in Jim Coplien's pattern work on software organizations from 1994 onward and in the book Organizational Patterns of Agile Software Development, published in 2004.
The problem itself exists in every company, with or without code: the payroll run only one person can do, or the key account only the sales director knows.
How to calculate the bus factor: a simple example
For a team you do not need special software. Three steps are enough:
- List the tasks your team cannot work without.
- For each task, count how many people can do it without help.
- The lowest number is your team's bus factor.
Why the lowest number? Because losing exactly those people stops everything, however well other tasks are covered. Wikipedia illustrates it with a bakery: 30 people make bread in three steps. Ten know how to mix the ingredients, all 30 can knead the dough, but only five know how to bake. If those five disappear, there is no bread, so the team's bus factor is 5.
A made up example from a small office shows how quickly the number drops to 1:
| Critical task | Who can do it without help? | Bus factor |
|---|---|---|
| Sending invoices | Anna, Ben, Carla, Dev | 4 |
| Chasing overdue payments | Anna, Carla | 2 |
| Running payroll | Anna | 1 |
| Online shop and payment provider | Ben | 1 |
| Contract with the biggest client | Emma | 1 |
| Whole team | lowest value | 1 |
The team has five people but a bus factor of 1, three times over. For each of those rows, one absence is enough to stop the task. Write down names, not just counts, to see whether one person carries several ones. A skills matrix is the right tool for this: the count under each column is the bus factor of that task.
What is a good bus factor?
There is no official standard. A value of 1 is always a warning sign, because that part of the work has no redundancy. From 2, someone can step in, but one holiday plus one sick day can still stop the task. For work that happens daily or in several places at once, 3 is more comfortable. The goal is not for everyone to be able to do everything. That would be expensive and impossible for most teams.
How common low values are shows up in a 2016 study by Guilherme Avelino and colleagues. They estimated the truck factor of 133 popular projects on GitHub and found that 65 percent had a truck factor of 2 or less. The study is about software, but small teams outside IT know the pattern just as well.
What the bus factor does not tell you
The measure is simple, and that is also its limit:
- Large projects hit 1 quickly: the more different skills a project needs, the more likely there is a gap somewhere, even with thousands of people on board.
- It says nothing about recovery: a task a new person can learn in two days is less critical than one that takes years of experience.
- It says nothing about probability: whether an absence is likely, for example because someone retires next year, needs a separate look.
Researchers do not agree on one way to calculate it either. Avelino and colleagues note that there is no consensus about how to calculate the truck factor. A 2026 paper shows that computing it exactly for large projects is a very hard mathematical problem. For a team of ten or twenty people, the simple count above is still all you need.
Bus factor vs key person risk
The risk of a business depending on individual people is much older than the bus factor. It is usually called key person risk or key man risk. Wikipedia draws the line like this: the bus factor looks at technical experts with knowledge only they have, while key person risk traditionally covers executives. Some companies insure against losing them with key person insurance, which pays a fixed sum to cover costs such as temporary help or recruiting a successor.
Money does not replace knowledge, though. According to Wikipedia, a person only lowers the bus factor if they are both key and irreplaceable. They become replaceable once others share what they know. For leadership roles, the guide to succession planning shows how.
How to increase your bus factor in 6 steps
Wikipedia names three levers: reduce complexity, document all processes and keep that documentation up to date, and encourage cross training. In practice that becomes this sequence:
1. Find the ones
Do the count from the example for your team. Add the vacation test: what would stop if this person were away for four weeks without a phone? Every task with a one goes on the list, the one that would hurt most first.
2. Reduce complexity
Some tasks only one person can do because they grew that way over years: special cases, workarounds, a spreadsheet full of macros nobody else understands. Before you train anyone, check what can be simplified or dropped.
3. Write the process down
Anything recurring belongs in a short instruction. The SOP examples show how. Keep it current, because an outdated instruction gives false confidence.
4. Train a second person
Writing things down is rarely enough, because much of the knowledge is tribal knowledge that only passes on by doing the work together. Job shadowing, a second pair of eyes on important tasks and rotating who does the task all help. In software teams, pair programming and shared code ownership serve the same purpose.
5. Share access and contacts
In an emergency, what is often missing is not the skill but a password, a phone number or a signing authority. Decide for each critical task who gets access in an emergency, and keep contacts in a shared place instead of in someone's head or private phone.
6. Name a backup and test it
Give every one a named backup and let that person do the task alone once while the experienced colleague is still around. Only then do you know whether your bus factor really went up. If someone leaves anyway, an employee handover document helps, and the free knowledge loss calculator gives a rough idea of what an unplanned departure can cost.
Conclusion
The bus factor is the number of people who would have to drop out before your team can no longer move forward. You can calculate it in a few minutes: list the critical tasks, count who can do each without help and take the lowest number. Every one is a to do: simplify, write it down, train a second person, share access and test the backup. Start with the task that would hurt most, and capture the knowledge while the person who has it is still there.
Frequently asked questions
- What does bus factor mean?
- The bus factor is the number of team members who would have to suddenly disappear before a project stalls because nobody else knows how the work is done. A low bus factor means important knowledge sits with very few people.
- How do you calculate the bus factor?
- List the tasks your team cannot work without and count, for each task, how many people can do it without help. The lowest number is the team's bus factor. For large software projects, researchers have built methods that estimate it from the code history.
- What is a good bus factor?
- There is no official standard. A bus factor of 1 is always a warning sign. Important tasks should have at least two people who can do them alone, and work that happens daily or in several places at once is safer with three.
- What is the difference between the bus factor and key person risk?
- Both describe dependence on individuals. Key person risk is the older business term and traditionally covers executives, often insured with key person insurance. The bus factor focuses on experts whose knowledge nobody else has, which money cannot replace.
- What should you do about a bus factor of 1?
- In the short term, write down the person's access, contacts and most important steps and name a backup. Then simplify the task, train a second person and let them do it alone once while the experienced colleague can still answer questions.