Of everything I recommend to business owners, the least glamorous is the one I recommend most: write your processes down.
Not software. Not AI. A document that says how the work gets done here. It's called an SOP, a standard operating procedure, and I've watched the absence of one cost businesses more than any tool ever saved them.
Here's the plain version of what an SOP is: the steps to do a task, written so someone who isn't you could follow them. Who does it, when, in what order, and what "done" looks like. That's it. No binder full of corporate language required.
Sounds too simple to matter. Let me show you the three places it's the whole ballgame.
1. Business continuity: the vacation test
Ask yourself this about any task in your business: if the person who does it disappeared for a month, what happens?
Not fired, nothing dramatic. Vacation. Jury duty. A broken ankle. If the answer is "things wobble until they're back," that task lives in someone's head instead of in your business. And what lives in a head walks out the door every night.
I've seen it play out. The one person who knows how billing actually works leaves, and it turns out the "process" was forty little exceptions they'd memorized over six years. The business didn't lose an employee. It lost an organ.
An SOP is the difference between "we lost a person" and "we lost a person AND the ability to do the work." The first is sad. The second can be fatal. Somebody new picks up the document and the wheels stay on. Rough, maybe. But rolling.
And if you ever plan to sell your business, or hand it to family, this goes double. A buyer isn't paying for what's in your head. They can't buy that. They're paying for a business that runs without you, and the SOPs are the proof it can.
2. Hiring: training that doesn't take a month of shadowing
Without SOPs, training a new hire means they follow someone around for weeks, absorbing the job through osmosis. Three problems with that:
- It's slow. Weeks of two people producing one person's output.
- It's inconsistent. Each trainer teaches their own version, and after a few generations of that, everyone does the job differently and nobody's sure whose version is right.
- It's fragile. The quality of your training depends entirely on which employee happened to be available that week.
With SOPs, the new hire reads how it's done here, does it with the document open, and asks questions about the parts that need a human. They're useful in days, not weeks. The document does the remembering so people can do the judging.
It sharpens hiring before day one, too. When you've written down what the job actually involves, you know what you're hiring for. It's a lot easier to interview somebody when the job is a page of real steps instead of a vibe.
3. Policies: what protects you when something goes wrong
Here's the one owners don't see coming. An SOP isn't just instructions. Written down and followed consistently, it becomes your policy. And policy is what protects you when things get contentious.
A customer disputes a refund. An employee claims they were treated differently than a coworker. Somebody gets hurt and the question becomes "what's your procedure?" In every one of those moments, "our policy is whatever we did last time" is the worst possible answer. It converts every disagreement into your word against theirs.
A written procedure, applied the same way every time, ends most of those arguments before they start. This is how refunds work, for everyone. This is the safety check, done every time, initialed. Consistency isn't just fairness. It's protection.
The bonus reason: you can't automate a mystery
Regular readers know I spend my days on AI and automation. So here's something that might sound strange coming from me: the SOP comes before any of it.
Every automation I've ever built started from someone describing exact steps. Every AI tool that actually works got pointed at a well-understood process. You cannot automate what you cannot describe. When an owner hands me a written SOP, the diagnostic that usually takes days gets shorter and cheaper, because the discovery is already done. The businesses that win with AI are the ones that documented their processes back when it was unfashionable.
How to start without drowning
Don't try to document the whole business. That's how this project dies in week two. Instead:
- Pick ONE process. The one that would hurt most if its person vanished tomorrow.
- Have the person who does it write the steps WHILE doing it, not from memory. Memory skips the exceptions, and the exceptions are the whole point.
- Test it on someone who's never done the task. Where they get stuck, the document is wrong. Fix it.
- Date it, put it where people actually look, and touch it once a year.
One process a week and you're twelve deep in a quarter, which is more documentation than most businesses your size will ever have.
The takeaway
SOPs aren't paperwork. They're the difference in business continuity, in hiring, even in the policies that protect you when something goes sideways. They cost almost nothing to create, and they're the foundation everything else, including AI, gets built on.
Start with one. This week. The one that lives in exactly one head.