Here’s an uncomfortable question for any small-business owner or team lead: if one specific person on your team didn’t show up tomorrow — not forever, just for two weeks — what would quietly stop working? For a lot of small teams, the honest answer is “a frightening amount.” The invoices only that one person knows how to run. The client who will only talk to that one account manager. The server password that lives in exactly one head.
Software teams have a slightly morbid name for this: the bus factor. It’s the number of people who would have to get hit by a bus (or, more cheerfully, win the lottery and quit) before a critical part of your operation grinds to a halt. The lower the number, the more fragile you are. In most small businesses the bus factor is one — and nobody notices until that one person is on holiday, out sick, or gone for good.

Why a low bus factor is a risk you can’t see
The reason this danger stays invisible is that, most of the time, everything works fine. The person who knows how to do the thing is there, doing the thing, and the business hums along. The risk only shows up on the one day you can least afford it: a family emergency, a sudden resignation, a two-week flu. Suddenly the “we’ll just ask Sarah” plan collapses because Sarah is the problem.
And it’s rarely dramatic. It’s not usually one heroic genius holding the company together. It’s a dozen small, mundane things — how the deposit reconciliation works, which supplier to call when the usual one is out, where the logo files live, the exact order you have to click through to close the month. None of it is hard. It’s just that only one person knows, and it’s never been written down.
Finding where your knowledge is trapped
You can’t fix what you can’t see, so start by finding your single points of failure. You don’t need a fancy audit — a board and ten minutes of honesty will do. Look at your recurring work and ask one blunt question of each task: if this person were out for two weeks, could someone else do this from what’s written down?
On a kanban board, this is easy to make visible. If you tag cards by owner, scan for any column — or any cluster of recurring cards — that’s tied to a single name. A whole lane that only ever moves when one person touches it is a flashing warning light. These are your bus-factor-one tasks, and they’re the ones to tackle first.

Rank them by damage, not by volume. A task someone does fifty times a day but which is dead simple to learn is low risk. A task someone does once a month that would take a newcomer a week to reverse-engineer is high risk. Go after the second kind first.
Write the “how,” not just the “what”
Most boards capture what needs doing — “Run payroll,” “Send the monthly client report.” The bus factor lives in the gap between the what and the how. The fix is to move the how out of someone’s head and onto something durable.
The lightest version of this is wonderful: write the steps directly onto the card. A short checklist on the “Run payroll” card — where to log in, which report to pull, who to email, what to double-check — turns a task only one person understands into one anyone careful can follow. For anything longer, link the card to a simple written procedure. It doesn’t have to be polished; a plain, ugly, accurate checklist beats a beautiful document that doesn’t exist.

The trick is to write it while the work is being done, not in some imagined future “documentation week” that never arrives. Next time the expert runs the task, have them jot the steps as they go. Twenty minutes, once, and a bus-factor-one task becomes a bus-factor-two.
Cross-train with small, real handoffs
Written steps are the foundation, but people learn by doing. The most reliable way to raise your bus factor is to let a second person actually run the task — with the expert watching, not doing. One real run-through where someone follows the checklist and hits the confusing parts will teach you more about the gaps than any amount of re-reading.
You don’t need a formal program for this. Rotate ownership of a recurring card every few months. Before someone takes a planned vacation, have them hand off their live cards to a colleague a week early — while they’re still around to answer questions — rather than dumping everything in a frantic briefing the afternoon before they leave. A board makes this clean: reassign the cards, and the new owner can see exactly what’s in flight and where it stands. This is really just delegation done deliberately — handing off the work before you’re forced to, instead of after.

Build the habit into your routine
The bus factor isn’t a project you finish; it’s a condition you maintain. New processes appear constantly, and every one of them starts life stuck in a single person’s head. The goal is to catch them before they calcify into another hidden risk.
A recurring review is the natural home for this. If you already do a weekly board review, add one question to it: did anything become a one-person job this week? When the answer is yes, make a card to write the steps down or schedule a handoff. It takes seconds and quietly keeps your fragility from creeping back up. And when you finally sit down to document a messy area, you may discover a pile of stale, half-understood work that nobody actually owns — which is a fine moment to clear out the cards you’re never going to finish while you’re in there.
Start with your scariest single point of failure
You don’t need to document your entire business this week — that’s the kind of overwhelming goal that guarantees nothing happens. Instead, pick the one task that scares you most. The thing where, if you’re being honest, you’d be genuinely stuck if the person who handles it vanished for a fortnight.
Put a card on the board for it. Next time it runs, have the steps written down. Then have one other person do it once, start to finish. That’s it — you’ve just taken your most dangerous bus-factor-one task and made it a two. Do that a handful of times across the year and you’ve turned a fragile operation into a resilient one, without ever setting aside a single dedicated “process” day. The best time to raise your bus factor is on an ordinary Tuesday when everyone’s present — not the morning you find out someone isn’t.