If you got hit by a bus tomorrow, how long until your company stalled?

Not "would it survive." Survival is the floor. The real question is how many days, weeks, or months pass before decisions stop getting made, deals stop closing, and the team starts looking sideways at each other waiting for someone to tell them what to do.

That answer is your bus factor. And if it's smaller than you think, you don't have a leadership team. You have a single point of failure with a payroll attached.

A bus factor audit is the most uncomfortable hour you can spend as a founder. It also might be the single highest-leverage exercise on your calendar this quarter. This is how to run one.

‍

What a Bus Factor Audit Actually Measures

The phrase started in software engineering. The bus factor of a project is the minimum number of team members who'd need to get hit by a bus before the project grinds to a halt. Low bus factor means too much knowledge lives in too few heads.

For a startup, the bus factor isn't about code. It's about decisions, relationships, and judgment. Four things, specifically.

When you map all four, you usually find the same thing. The bus factor of your company is one. It's you.

And that's not a flex. It's a liability hiding behind a hustle.

If you want the broader diagnostic, how to score bus factor across every function rather than just the founder's desk, that's covered in The Bus Factor Test. This piece is the founder-facing version: a structured audit you run on yourself.

‍

Why Founders Build Their Own Bus Factor Problem

Founders don't centralize decisions because they want control. Most of them centralize because nobody set up the alternative.

You started as the doer. Then you became the doer who also coordinates other doers. Then somewhere around 25 employees, the model breaks. The reason it breaks isn't capacity. It's that the company outgrew its operating infrastructure before the founder outgrew the habit of being the operating infrastructure.

Bain's research on scaling companies lands on what they call the growth paradox: growth creates complexity, and complexity is the silent killer of growth. Only one in nine companies sustains profitable growth over a decade. When Bain asked the ones who stalled what stopped them, 85% pointed at internal factors, not market forces. The barriers executives named most often included complexity of decision making slowing the company down.

That's the bus factor, described from 30,000 feet. The constraint isn't the market. It's the operating system.

John Maxwell calls it the Law of the Lid. A leader's capacity caps the team's potential. If every meaningful decision routes through you, your team's ceiling is whatever you can personally absorb in a week. Most weeks, that's not much. You're tired.

The Bamboo Tree story is the right reframe here. For five years, a planted bamboo seed shows nothing above ground. Then in year six, it grows 90 feet in six weeks. The growth was always happening, just underground, in the root system. Distributed leadership works the same way. The visible scaling comes after the invisible system gets built.

The bus factor audit is the first crack at that system.

‍

The Bus Factor Audit: 60 Minutes, One Whiteboard

Block 60 minutes on your calendar this week. Put a whiteboard or shared doc in front of you. Walk through these five steps in order.

Step 1: List the Last 20 Decisions You Made

Open your calendar and inbox. Look at the last two weeks. Write down 20 decisions you personally signed off on. Not feedback you gave. Decisions you owned.

Include the small ones. "Approved a contractor invoice." "Said yes to a vendor switch." "Decided to delay the launch by a week." "Picked the agency for the rebrand." "Greenlit the new hire."

Twenty is a magic number. It surfaces the pattern. Five doesn't tell you anything. Fifty makes you stop reading this article.

Step 2: Code Each Decision With a Letter

For each of the 20 decisions, write one letter beside it:

• A. Only you could have made it. The decision genuinely required founder-level context, authority, or relationships that don't exist anywhere else in the company yet. Board matters. Co-founder conflict. Betting the company on a pivot.
• B. Someone else could have, with better context. They had the authority to decide. They just didn't have the information you had. The customer history, the strategic rationale, the thing you know because you were in the room.
• C. Someone else could have, with clearer criteria. They had the information. They didn't know what "good" looked like. They couldn't tell whether a $30K spend was reasonable or reckless because nobody ever told them where the line was.
• D. Someone else could have, and should have. They had the context. They had the criteria. They had the authority on paper. It came to you anyway, because that's how it's always been done.

Most founders run the audit and find that 12 to 15 out of 20 decisions are B, C, or D. Only 5 to 8 are real A's. That's the gap. Those B/C/D decisions are the founder bottleneck made visible.

If that pattern sounds familiar, we've written about the underlying dynamic in The Founder Bottleneck.

Step 3: For Each B/C/D, Name the Missing System

This is where the audit stops being a diagnosis and starts being a roadmap. For every B, C, or D decision, write what would have made it delegatable. The letter tells you the answer:

• Every B needs written context. A one-page customer brief. A recorded walkthrough of the strategic logic. The thing in your head, moved somewhere someone else can read it.
• Every C needs written criteria. A spend threshold. A decision framework. A definition of what "good" looks like in that category, specific enough that someone could apply it without calling you.
• Every D needs explicit decision rights. Not "run it by me." Not "keep me posted." A named owner who decides, and a company that knows they decide.

You'll start to see clusters. Maybe five of your B/C/D decisions are all about hiring. Maybe seven are about vendor or budget calls under $25K. Maybe four are about customer escalations.

Those clusters tell you what to systematize first.

Step 4: Run the Disappearance Drill

This is the part most founders skip. It's also where the audit gets honest.

Picture this. You're unreachable for 30 days starting Monday morning. Not "checking email occasionally on vacation." Truly gone. Phone off. No Slack. No Signal. No proxy.

Write down what happens in week one. Then week two. Then weeks three and four. Be specific. Which customer escalates and to whom? Which deal stalls because the close requires your signature? Which hire doesn't happen? Which payment doesn't get approved? Which engineering decision gets deferred indefinitely because nobody has clarity on the trade-off?

For most pre-Series-B founders, the answer at week two is "the company starts breaking in obvious ways." That's the bus factor. And it's a number you can shrink.

Step 5: Pick One Fix and Ship It This Week

The audit's value is in step five. Otherwise, it's just a journaling exercise that makes you anxious.

Pick the single highest-frequency B, C, or D from your list. That's your starting point. Build the smallest possible system that would let one other person make that decision next time:

• Write the context down. Twenty minutes. One page. Not a polished document. The three things someone would need to know to make this call the way you'd make it.
• Name the criteria. What's the threshold? What's the trade-off you're actually weighing? What would make this a yes, and what would make it a no?
• Name the owner. Out loud, in writing, to the person and to the team. "Priya owns vendor decisions under $25K. She doesn't need my sign-off."
• Let the first one go badly. They will make a call you wouldn't have made. Unless it's catastrophic, let it stand. Debrief after. The lesson costs less than the bottleneck.

That's a complete delegation handoff. It took you twenty minutes. Do that twice a week for a quarter and your bus factor doubles.

For the deeper version of this move, how to delegate without losing your standards is worth an hour of your time.

‍

What a Good Bus Factor Looks Like

Most early-stage companies will never get a bus factor of 5 or 10, and they don't need to. The realistic targets scale with the company.

The shift happens by intentional design. You build it through three things:

A real operating cadence. Weekly, monthly, quarterly meetings where decisions get made on the calendar, not in your inbox. The cadence becomes the coordination mechanism that you used to be.

Documented decision rights. Every role has a list of decisions they own outright. Not "consults the founder." Owns. Founders push back here because it feels risky. The risk is much higher in the other direction. Keeping decisions clustered creates a brittle company.

Written context. The reason most B and C decisions land on the founder is that the context to make them is locked in the founder's head. A two-paragraph customer summary, a one-page strategy doc, a recorded loom on "how we think about pricing." These are the asset class founders consistently under-invest in.

Patrick Lencioni's core argument about organizational health applies directly here. Healthy organizations, in his framing, have high clarity and fast information flow. Unhealthy ones have neither, which means every decision has to route through whoever holds the context. The bus factor is a measurement of how widely that clarity is actually distributed.

‍

The Hidden Cost of a Low Bus Factor

Most founders rationalize a low bus factor by telling themselves it's temporary. We'll fix it after the next round. After the next hire. After the launch.

But low bus factor compounds in three directions you don't see at first.

It compounds against retention. The best operators in your company want to make calls. When every meaningful decision requires the founder's blessing, your strongest hires interpret it as a ceiling on their growth. They leave. Often quietly. Often before you noticed they were even unhappy.

It compounds against speed. Every decision routed through one person becomes a queueing problem. Three decisions waiting on you isn't bad. Thirty is. The team learns to slow down because they know the bottleneck. Slowness becomes culture.

It compounds against executive coaching ROI. Coaching works when there's space to apply new behaviour. If your week is 100% reactive, answering questions, approving things, putting out fires, there's no surface area for new habits. The founder who needs coaching the most is the one whose calendar can't accommodate it.

The bus factor audit doesn't solve any of these. But it's the first time you can see them all on one page. That visibility is the unlock.

‍

When the Audit Reveals Something Painful

Sometimes the audit reveals the obvious. You need to delegate more, write more down, hire a senior operator. Sometimes it reveals something harder.

It might reveal that the COO you hired six months ago isn't actually operating at the level the role requires. It might reveal that your VP of Sales has all the customer relationships and would take 60% of them out the door if she left. It might reveal that the entire company runs on tribal knowledge that you've spent three years assuming everyone knew.

It might also reveal that the fix is a hire. If the audit points at organizational memory rather than any single process, the question becomes structural: Chief of Staff or COO?

Don't bury those findings. The whole point of the audit is to surface what's unsaid. Sit with the discomfort. Then act.

The transition from founder mode to CEO mode is essentially a series of bus factor improvements. Every time you turn a B or C decision into a documented, delegated process, you're building the company that exists without you in the room. That's not abandonment. That's leadership. The full version of that transition is mapped in our guide to scaling yourself out of every decision.

A useful mental model: every founder who builds a great company eventually has to fire themselves from their own first job. The audit shows you which version of yourself you're still doing.

‍

Conclusion

The bus factor is the single most honest measurement of how much of your company is actually a company versus how much is just an extension of you. The number isn't moral. A bus factor of one isn't a character flaw. It's an operating state. And operating states change when you change the operating system.

Run the audit. Pick one fix. Ship it this week. Then again next week. The compounding starts there.

Choose hard.

‍

‍

Frequently Asked Questions