Every team has someone who “just knows how it works”: how payroll is run, where the supplier passwords live, why the monthly report needs a manual fix. It feels efficient until that person is ill, on holiday or hands in their notice. This Q&A explains how to find that exposure and shrink it without a big project.
What is the bus factor?
The bus factor is the smallest number of people who would have to disappear suddenly before a task, a system or the whole team stalls. If only one person can run invoicing, the bus factor for invoicing is 1. The name is morbid, but the idea is practical: it measures how much your operation depends on individuals.
What is key-person risk?
Key-person risk is the business damage that follows when a person with unique knowledge, access or relationships is unavailable. It is not only about resignations. Sick leave, parental leave, a long flight or a simple day off can expose the same gap.
How do you spot it?
Ask one question about every important task: who is the only one who knows how to do X? Then look for these warning signs:
- Colleagues say “ask Sam” and nobody else tries.
- Work waits whenever one person is away.
- Logins, licences or supplier accounts sit in one person’s name or inbox.
- The process exists only in someone’s head or in scattered chat messages.
- One person holds the relationship with a key customer or vendor.
How do you map critical tasks against people?
Build a simple grid. List your critical tasks in rows and your people in columns. For each cell, mark whether the person can do the task alone, can do it with help, or cannot. Count how many people can do each task alone. Any row with one name, or none, is a risk. Rank those rows by impact: what would stop within a day, within a week, or within a month?
What does cross-training involve?
Cross-training means a second person learns each critical task well enough to run it without help. Start with the highest-impact rows of your grid. Keep sessions short and practical: the expert does the task while the learner watches, then the learner does it while the expert watches. Real work beats slide decks.
Why write runbooks and SOPs?
A runbook is a step-by-step guide to a recurring task, written so a capable colleague can follow it cold. Good ones include:
- Purpose and trigger. What the task achieves and when it happens.
- Steps. Numbered, with screenshots or examples where it helps.
- Where things live. Folders, systems and contacts, though never the passwords themselves.
- Common problems. What usually goes wrong and how to fix it.
The best test is to ask someone else to follow the document. Wherever they get stuck, the document needs work.
How do shadowing and rotations help?
Shadowing lets a colleague sit in on a task, then take it over under supervision. Rotations go further: swap who owns a recurring duty every quarter or so. Rotation keeps skills fresh, reveals gaps in the documentation and means a backup has actually done the job rather than merely read about it.
What about access and credentials?
Knowledge is only half the problem. Check that critical accounts have at least two administrators, that shared tools use a team password manager, and that licences and domains are registered to the company rather than a personal email. Review who has access when people change roles, and remove it promptly when they leave. Never keep credentials in a notebook or a chat thread.
What is a simple step list?
- List the 15 to 20 tasks that would hurt most if they stopped.
- Build the task-by-person grid and highlight single-name rows.
- Pick the three riskiest tasks and name a backup for each.
- Write or update a runbook for each one.
- Run a shadowing session, then a supervised handover.
- Fix access: second admin, shared vault, company-owned accounts.
- Repeat quarterly with the next set of tasks.
How do you measure progress?
- Coverage. The share of critical tasks with at least two people able to do them alone. Aim to raise it each quarter.
- Documentation. The share of critical tasks with a tested runbook.
- Access resilience. The share of critical accounts with two or more admins.
- Absence test. Could the team handle a planned week without one key person? Try it for real.
Track these numbers on the same dashboard as your other operational KPIs. If you already use FulcrumGrid Command Center, you can keep the task grid, recurring review dates and these coverage metrics beside your normal work so they do not quietly lapse.
Frequently asked questions
What is a good bus factor?
At least two for every critical task. Three is better for work that stops revenue or breaks compliance. Perfection is not the goal; removing single names is.
Is the bus factor only a problem for small teams?
No. Small teams feel it most, but large companies often have isolated experts, legacy systems or niche roles that only one person understands.
How long does it take to reduce key-person risk?
Covering your three riskiest tasks typically takes a few weeks of short sessions. Making it a quarterly habit is what keeps the risk low.
What if the key person resists sharing knowledge?
Frame it as relief, not replacement: documenting and teaching lets them take leave without being called. Recognise the effort and include it in their goals.
Do runbooks go out of date?
Yes. Review each one after every use or at least twice a year, and name an owner so updates do not depend on goodwill.
FulcrumGrid Command Center
Make resilience part of your routine
FulcrumGrid Command Center lets you track KPIs, tasks and recurring reviews in one place, so cross-training and runbook updates actually get done.