How to Write an SOP in 20 Minutes (Even If You Hate Documentation)
Let's be honest about why you don't have SOPs.
It's not because you don't know your processes. You know them better than anyone. It's because the idea of sitting down to write them out feels like homework assigned by a version of yourself you'll never be. Somewhere along the way, "standard operating procedure" started to mean a formal document with numbered sections and a table of contents, and no owner running six jobs at once has an afternoon for that.
Here's the reframe that changes everything: an SOP is not a document. It's a recording of you doing something you were going to do anyway.
Once you see it that way, the 20 minutes stop sounding like a gimmick and start sounding like math. You were already going to send those invoices this week. The only difference is that this time, you'll press record first.
Why This Matters More Than It Seems
When a process lives only in your head, you are the process. Every question comes to you, every task waits for you, and training anyone means hours of your time repeated for every new person. That's the quiet reason so many owners stay stuck doing everything: handing something off feels like it costs more than keeping it.
An SOP flips that cost. Record a task once, and you've created something that trains every future person who ever touches that task, answers questions before they're asked, and keeps things running the same way whether you're in the office or actually taking a day off. It's the difference between being the business and owning one.
The 20-Minute Method
Here's the whole thing, start to finish.
Minutes 1 through 10: Do the task on camera. Pick one task you do regularly. Sending an invoice, scheduling a social post, onboarding a new client, processing a refund. Open a free screen recorder (Loom is the easiest, but Zoom recording a screen share to an empty meeting works too, and so does your phone camera pointed at a physical task) and simply do the task while talking out loud. Narrate like you're showing a new hire sitting next to you: "I open this, I click here, I always double-check this part because it goes wrong if you don't."
Don't perform. Don't redo takes. The stumbles and side comments are where the real knowledge lives, because the things you say offhand ("oh, and ignore that field, we never use it") are exactly the things a written manual would forget.
Minutes 10 through 15: Turn the recording into steps. Most recording tools transcribe automatically now, and if yours doesn't, an AI tool can turn your transcript into a clean numbered list in seconds. You're not writing anything from scratch. You're editing words you already said. Tighten the rambles, number the steps, bold anything that's a warning or a rule.
Minutes 15 through 20: Add the three lines that make it an SOP. At the top of the document, answer three questions in one line each. When does this task happen (every Friday, when a new client signs, when an invoice hits 30 days)? What does done look like (the client received the welcome email and the folder exists)? Who do you ask when something unexpected happens?
That's it. Save the video and the steps together in a folder anyone on your team can reach, name it something a human would search for ("How we send invoices," not "SOP-004-AR-Process"), and you're done. One task, documented forever, in the time it takes to drink a coffee.
The Part Nobody Tells You
You don't need fifty SOPs. You need about five to start, and they should be the tasks you'd hand off first: the inbox routine, invoicing, scheduling, posting content, and whatever your version of client onboarding is. Document one per week and you'll have a real operations manual in about a month, without ever sitting down to "write documentation."
And if a task changes later? Record it again. Twenty minutes. The recording is always cheaper than the version of you personally re-explaining it for the tenth time.
Where This Goes Next
Here's what happens after the first few SOPs exist, and we've watched this with our own clients: handing things off stops feeling risky. The fear was never really about other people's competence. It was about everything living in your head, where nobody else could check it. Once the process exists outside of you, delegation goes from a leap of faith to a handoff with instructions.
That's when a business starts running on systems instead of memory. And that's the moment owners finally get to step into the CEO role their business has been waiting for.
If you'd rather skip straight to that part, building the systems is literally what we do. We record, document, and organize the backend of your business so it runs whether you're in the room or not. But even if you never call us, press record on one task this week. Twenty minutes. You'll wonder why anyone ever made documentation sound hard.
