The Hit-by-a-Bus Standard: Extracting Knowledge From Your Head

If you got hit by a bus tomorrow, would your business survive the week?

It’s a grim thought experiment. But it exposes something most small business owners never confront: all the knowledge that keeps your operation running lives in one person’s head. Yours. The passwords, the workarounds, the “talk to Jenny and she’ll sort it” shortcuts, the reason you always run payroll on Tuesday instead of Wednesday. None of it is written down. None of it is accessible to anyone else. And your business process documentation is, if we’re being generous, non-existent.

This post is about building a business that keeps running whether you’re in the room or not.

The Single Point of Failure You’re Ignoring

You already know what a single point of failure looks like in IT. One server goes down, the whole office stops. One internet connection drops, and nobody can work. You’d never run your network that way. But you’re running your entire business that way, with yourself as the bottleneck.

Think about what happens when you take two weeks off. The questions start flooding in. “Where’s the login for the supplier portal?” “What’s the process for onboarding a new client?” “How do we lodge the BAS?” Your phone rings constantly. Nobody else knows where anything is or how anything works.

I’ve walked into businesses where the owner had a health scare, and the team was paralysed. Not through any lack of ability. The knowledge they needed to do their jobs had never been shared. It was locked inside one person’s brain like a filing cabinet with no key.

And it’s not just about you. Your senior technician who’s been with you for twelve years? If they leave tomorrow, they take a decade of client-specific knowledge with them. The accounts person who “just knows” how the invoicing quirks work? Same problem.

You usually don’t realise these gaps exist until someone leaves and a project stalls, or worse, a client gets let down.

The Real Problem Isn’t Laziness. It’s the Wrong Mental Model.

Most business owners know they should document their processes. They’ve thought about it. Maybe they even started a Google Doc once, got three paragraphs in, and abandoned it. The usual explanation is that they’re too busy. That’s part of it. But the bigger issue is how they think about documentation.

The common approach treats it like a chore. Something you do after the real work is finished. A box to tick. Write it all down in a big manual, hand it to your team, job done.

That approach fails every time. Big manuals don’t get read. Static documents go stale the moment a process changes. And the person who wrote the manual (you) is still the only one who truly understands the context behind each step.

Think about your documentation the way you think about your network or your cloud storage. It’s infrastructure. You don’t set up your Wi-Fi once and forget about it. You maintain it, you update it, you build it so the business works whether or not any single person is around.

Once you stop thinking of documentation as a one-off chore and start thinking of it as part of your IT stack, the whole job feels different. You’re not trying to write a book in one weekend. You’re just capturing things as they happen.

How to Make Your Business Bus-Proof

Five steps to move from “everything’s in my head” to “anyone on the team can pick this up.”

1. Map Out Who Knows What

Start by listing every process that only one person understands. Be honest about it. Client onboarding, invoicing, software deployments, backup procedures, supplier negotiations, password management. Write down who holds the knowledge for each one.

If a task has only one name next to it, that’s a vulnerability you need to address.

2. Pick the Top Five and Start There

You don’t need to document everything at once. That’s the trap. Pick the five processes that would cause the most damage if the knowledge holder disappeared tomorrow. For most SMEs, that list includes:

• Client onboarding or project kickoff
• Invoicing and payment follow-up
• Access credentials and password management
• Key vendor or supplier contacts and agreements
• IT incident response (what to do when something breaks)

Get those five documented before you worry about anything else.

3. Use Simple, Accessible Tools

You don’t need expensive knowledge management software. You need a system that people will actually use. Here’s what works for most Australian SMEs:

• A shared wiki. Notion, SharePoint, or Confluence. The whole team can search it, read it, and add to it.
• A password manager. Stop keeping passwords in a spreadsheet or, worse, in your head. 1Password for Business or Bitwarden let you share credentials securely without anyone needing to memorise them.
• A shared drive with a clear folder structure. Google Drive or OneDrive. Pick a naming convention and enforce it. “Client Files > > ” is basic, but it works.
• Screen recordings for complex processes. A two-minute Loom video showing how you run a report beats a ten-page written guide. Some processes are just easier to demonstrate than describe.

Stick to the tools your team already uses where possible. Adding a brand new platform creates more friction than it removes.

4. Build Documentation Into Daily Work

Most businesses treat documentation as a separate project and never get around to it. There’s always something more urgent.

The fix is simple. Build it into the work itself. Every time someone asks you “how do I do X?”, don’t just answer the question. Answer it, then write the answer in a place the team can find it. Every time you solve a tricky problem, spend five minutes writing up what you did and why. Every time a process changes, update the relevant document before you close the task.

Call it “document as you go.” Recording things in real time means the instructions actually match the current version of whatever tool or process you’re describing. The alternative, the big documentation weekend, produces a snapshot that’s outdated within a month.

One good rule of thumb: if you’ve explained it twice, it needs a document.

5. Test It With the Bus Standard

Once you’ve documented a process, hand it to someone who wasn’t involved in creating it. Ask them to follow the steps without your help. If they can complete the process from start to finish, you’ve passed the bus standard for that task. If they get stuck or need to call you for clarification, the document needs more work.

Run this test quarterly on your most critical processes. Things change. People change. Your documentation needs to keep pace.

Where to Start This Week

Don’t try to overhaul everything at once. This week, do one thing: pick the single process in your business that would cause the most chaos if you weren’t available. Write it down. Not perfectly. Not in a polished template. Just open a shared document and capture the steps, the login details (in a password manager, not the document), and the context that someone else would need to get the job done.

That’s your first bus-proof process. One down.

Then next week, do another one. And the week after that. In a few months, you’ll have a searchable library your team can actually rely on. You might even take a proper holiday without your phone ringing every hour.

If you’re not sure where to begin, or you want help setting up the right tools and folder structures, that’s exactly what we do at SixFive. We help SMEs build the IT infrastructure that makes businesses run properly, and that includes the systems for capturing and sharing knowledge.

Frequently Asked Questions

Stop Being the Single Point of Failure

Your business should be able to function without you in the building. Every process you document, every password you move into a shared manager, every SOP you write up and test removes one more dependency on your memory.

Start with one process this week. Build from there. And if you want help putting the right systems in place, get in touch with SixFive for a free technology assessment. We’ll help you build a business that passes the bus test.