Your Business Runs on One Person's Memory

It's the Monday after someone's annual leave starts. A client rings asking where their order is up to. Nobody's quite sure. The quote template lives on one laptop. The supplier login is in someone's head. And the person who "just knows how it works" is on a beach in Queensland with their phone buzzing anyway.

If that sounds familiar, you're not disorganised. You're running on memory. Most growing businesses are.

Memory is not a system

If a process requires one person's presence to function, it's a dependency, not a process.

Here's what it usually looks like:

• The same person answers the same question three times a week
• Leave gets planned around "who can cover", and the honest answer is nobody
• New starters learn by shadowing, and every trainer teaches it a little differently
• Licence renewals and insurance dates sit in a spreadsheet only one person ever opens
• The founder is still approving decisions they made years ago

None of these feel like a crisis on a normal day. They become one the day that person is sick, resigns or simply burns out.

Why it happens

It isn't laziness. It's how businesses grow.

At three people, memory is the fastest system you've got. Everyone sits in the same room and a quick question gets a quick answer. Each workaround made sense at the time. The problem is that the business keeps growing and the workarounds never get replaced.

The part most people miss is this: knowledge doesn't get written down because the person who holds it is the person with the least spare time. They're busy being the go-to. The business quietly rewards them for it, so nothing changes until they leave.

The second thing people miss: documenting it isn't the whole fix. A Word document nobody can find is still memory, it's just stored on a hard drive. The fix is putting the knowledge where the work actually happens.

How to get it out of their head

This is the same sequence we use in the Discovery & Clarity and Systems Architecture phases of our Operational Excellence Framework, cut down to something you can start on your own.

1. 1

   Find the dependencies. List your recurring tasks and mark every one that only a single person can do. You'll usually find the list is longer than you expected.

2. 2

   Rank by risk, not by annoyance. For each one, ask: what breaks if this person is gone for two weeks? Payroll, invoicing, compliance dates and client onboarding normally go to the top.

3. 3

   Capture it while they do it. Don't ask your busiest person to write an SOP from scratch. Record them doing the task next time (a screen recording with them talking it through is perfect), then turn it into steps. Twenty minutes instead of a lost afternoon.

4. 4

   Put it where the work happens. Attach the steps to the recurring task in your project system, so the instructions show up when the job is due. If someone has to go hunting for the procedure, they won't.

5. 5

   Hand it over and watch. Next time the task comes around, someone else does it with the original owner on standby. Gaps show up fast, and you fix them on the spot.

6. 6

   Give it an owner and a review date. Processes drift. Someone needs to be responsible for keeping the steps current, and a review date makes sure it actually happens.

What this looks like in practice

A logistics and warehousing business we work with was managing stock levels, delivery requests and collection requests through spreadsheets and emails. The real system was a handful of people who knew what was where. When clients wanted to know what stock they had, they rang and asked, and someone had to go and check.

We moved the whole thing into ClickUp. Warehouse staff now log incoming stock through a form that updates client inventory automatically. Clients have their own portal showing live stock, and they request deliveries and collections through structured forms that drop straight into the team's workflow. Drivers complete delivery records digitally.

The knowledge that used to live in a few people's heads now lives in the system. Clients can see it for themselves, and the phone rings a lot less.

The 5-question dependency test

Pick one person in your business. Start with yourself, it's usually the most revealing.

If you answer "no" to more than one question, you've pinpointed a potential operational risk.

Your task for this week

Pick one recurring task that only one person can do. Next time they do it, record it. That recording is your first SOP, and the first piece of your business that no longer depends on someone remembering.