Your Business Should Run Without You for a Week

At my old NGO job, I was the person who knew where things were. Not officially — nobody put that in my job description — but if you needed last year’s grant report, or wanted to know which version of the budget spreadsheet was the real one, or needed the code for the store cupboard, you asked me.

It worked fine, until it didn’t. I took two weeks of annual leave — properly off, phone away, out of the country — and by day four my manager had called twice. Nothing had gone wrong exactly. It’s more that nothing could move forward without me confirming where a particular file was, or who’d said what in a meeting three months earlier. The organisation hadn’t broken. It had just quietly stalled, waiting for me to come back and unstick it.

I think about that a lot now, because it’s the exact pattern I see in almost every small business I work with. Things aren’t chaotic, not really. There’s a filing system. There are processes, more or less. Everyone can tell you roughly how things work. And then volume goes up, or the one person who holds it all in their head is unavailable, and the whole thing wobbles.

Amazon, whatever else you think of it, does not have this problem. I spent nine years there, and one thing that never stopped surprising me was how little anything depended on any one person remembering anything. Processes were documented down to a level that felt almost excessive when I first arrived — until I watched someone go out on leave for three months and come back to find their work had simply continued without them, exactly as designed. That’s not luck. That’s the difference between something being organised and something being systemised. Organised means people know how it works. Systemised means anyone could find out how it works, without you.

I don’t think most small business owners need Amazon-level documentation — that would be its own kind of madness for a business with one or two people. But the diagnostic underneath it is worth stealing: if you disappeared for a week, genuinely unreachable, what would actually stall? Not in a vague “oh it’d be fine” way — specifically. Which client would have no idea what happens next. Which invoice wouldn’t get sent. Which process only exists because you remember the steps in order.

Whatever comes to mind when you ask yourself that isn’t a character flaw. It’s not proof you’re disorganised or a bad manager. It’s just information. It’s the exact map of where your business currently depends on you being present, rather than on something being designed. And once you can see the gap clearly, it’s usually much smaller and much more fixable than it feels when it’s just a background hum of anxiety.

That’s really the whole shift — from hoping things hold together to designing them so they do. Not perfection, not a system for everything. Just enough intentional structure that your absence is an inconvenience rather than a crisis.

Your turn: if you vanished for a week starting tomorrow, what’s the first thing that would actually break?