All Episodes
Fixing Your Bus Factor: How to Eliminate Single Points of Failure

Fixing Your Bus Factor: How to Eliminate Single Points of Failure

0:00|0:00

Discover how undocumented tribal knowledge and a low "bus factor" create invisible bottlenecks that threaten your company's daily operations and valuation. Learn a practical 20-minute exercise to spot your single points of failure, plus a screen-recording strategy to successfully transfer critical processes to a backup.

Show Notes

This show was created with Jellypod, the AI Podcast Studio. Create your own podcast with Jellypod today.


Chapter 1

The Number Hiding in Your Business

Ryan Haylett

Your office manager calls out sick on a Monday. By ten o'clock, nobody can say how the invoices go out, which jobs get dispatched first, or why one customer always gets a special rate. And the business isn't even failing. It's just stuck, because one person's brain is the system.

Dave Rowley

I like that you said brain, because that's exactly where it lives. There's a name for it, the bus factor. It's the minimum number of people who'd have to suddenly disappear before a process, a department, or the whole company stops working. Some folks call it the truck factor.

Ryan Haylett

And the knowledge that causes it has a name too. Tribal knowledge. Undocumented habits, homemade spreadsheet workarounds, unwritten exception rules, that mental list of how things actually get done. It's held by individual people instead of living in the business.

Dave Rowley

Here's what makes it sneaky. It feels efficient. One source describes it as completely free right up until the moment it's catastrophic. There's no line item on any report that says we depend on one person to reconcile these accounts. So it just grows quietly for years.

Ryan Haylett

And then the bill shows up. SHRM puts the cost of replacing an employee at 50 to 200 percent of their annual salary. Two hundred percent. And a lot of that isn't the recruiting fee. It's the months where work gets done slower or worse because the knowledge walked out the door.

Dave Rowley

There's a daily cost too, even if nobody ever quits. McKinsey Global Institute has an estimate, widely cited, that knowledge workers spend about 1.8 hours a day searching for information. That's roughly 9.3 hours a week. Basically a full workday, every week, spent hunting for answers that live in a coworker's head.

Ryan Haylett

Which is a fun tax to pay. And if you ever want to sell, it gets worse. One exit planning advisor said two thirds of American businesses are owned by boomers, and only one in five that list for sale ever sells. The first blocker is that everything lives in the owner's head.

Dave Rowley

Buyers want to know if they're buying a system or a person. If it's a person, that shows up as a lower offer or a longer transition. So even if you never plan to sell, it's still a measure of how fragile your day to day is.

Ryan Haylett

Okay, so how do you actually measure it? It takes one sheet of paper and about twenty minutes. List the eight to twelve processes that would cost you money, customers, or compliance if they stopped this week. Commission runs, vendor reconciliations, dispatch, regulatory filings.

Dave Rowley

Then beside each one, write every person who could run it Monday without asking a question. And the phrase could figure it out doesn't count. Your bus factor is the lowest number on the sheet. Not the average.

Ryan Haylett

Because averaging is how a company with one irreplaceable bookkeeper convinces itself it's a two and a half. And watch for the repeated name. If one person shows up on seven of twelve rows, your real number is worse than any single row shows.

Dave Rowley

And these hide in odd places. One example from the research was a weekly commission run that took a bookkeeper three full days, merging two reports by hand because an export stripped the job IDs. It had never been late, which is exactly why nobody looked at it.

Chapter 2

Raising the Number Without Writing a Binder

Ryan Haylett

Now the instinct is to say, fine, everybody write an SOP. Ten pages, whole binder. And that usually fails. Documentation written as a separate task rots, because the process changes and nobody's job is updating the document.

Dave Rowley

There's a human reason too. If you ask an expert to write down everything they know, it can sound like you're asking them to make themselves replaceable. Being the only one who knows something feels like job security, so that mandate fights a real incentive.

Ryan Haylett

So don't ask them to write. Record them doing it. Next time they run the process, they share their screen or record audio and talk through it. And you give them real prompts. What decisions did you make, and why? What exceptions do you handle? What breaks if this step is skipped?

Dave Rowley

Walk me through the last time you did this. That works better than document your work, because it captures real scenarios instead of theory. And if you can, keep the steps inside the tools you already use, like a checklist in your CRM or a form in your field software, so doing the work and recording the work are the same thing.

Ryan Haylett

Then comes the test most people skip. A process isn't covered because a binder exists. It's covered when a backup runs it start to finish, alone, while the expert sits on their hands and says nothing.

Dave Rowley

Sitting on your hands is brutal for experts. But every spot where the backup stalls is a gap in the recording, and you fix it right there. One source says a process counts as covered when a second person has run it end to end within the last ninety days. Anything older is a claim, not a number.

Ryan Haylett

Okay, quick wins for this week. One. Pick your five highest damage weekly processes and find the one with only a single name beside it.

Dave Rowley

Two. The next time that person runs it, have them record their screen and talk through the edge cases. Twenty minutes, no polishing.

Ryan Haylett

Three. Hand that recording to a second person and let them run the whole thing while the expert watches silently. Write down every place they get stuck.

Dave Rowley

And that's the takeaway. Experience is an asset. Depending on one person's memory is a liability. Build it so the expertise outlives the absence.

Ryan Haylett

If you want help improving the systems that power your business, you can learn more at modularity.us.