When I ran everything in my head, the business could not run without me. A day off meant a backlog. A new hire meant a week of me narrating tasks out loud. The fix was boring and it worked: write the standard operating procedures down, one repeatable task at a time.
This is the exact format I settled on after a lot of bad attempts.
One task, one page
A good SOP covers a single repeatable task end to end. Not "marketing." Not "onboarding." Something like "send the welcome email to a new customer" or "reconcile the weekly card statement." If you can't do the task in one sitting, it is two SOPs.
The five sections that actually get used
- Trigger — what starts this task. A new signup, a Monday morning, an invoice landing in the inbox.
- Owner — the role responsible, not a person's name. Roles outlive employees.
- Steps — numbered, in order, each starting with a verb. "Open the billing dashboard." "Filter by last 7 days." No paragraphs.
- Done looks like — the observable end state. "The customer shows as Active and got the receipt." This is what lets someone check their own work.
- If it breaks — the two or three things that go wrong most often and what to do.
That last section is the one people skip and the one that saves the most time. Half of every "quick question" interruption is a known edge case nobody wrote down.
Write it while you do it, not after
The cheapest time to write an SOP is the next time you do the task anyway. Open a doc, narrate each click as you make it, paste in the screenshot if the UI is fiddly. Fifteen minutes of friction now versus explaining it out loud five more times later.
Store them where the work happens
An SOP nobody can find is the same as no SOP. Keep them next to the tool they describe: a pinned doc in the billing folder, a linked page in the project tool, a short link in the team chat topic. If finding the SOP takes longer than guessing, people guess.
Review on a real cadence
Tasks drift. The dashboard moves a button, the vendor changes a form. Put a quarterly reminder to re-run each SOP exactly as written and fix whatever no longer matches. If it still works as written, you spent two minutes confirming it. If it doesn't, you just caught a silent failure before it cost you.
Start with the three that hurt most
Don't try to document everything. List the tasks where an interruption costs you the most focus, pick the top three, and write those this week. Momentum from three working SOPs beats a perfect template you never fill in.
If you'd rather start from filled-in examples than a blank page, I packaged a set of ready-to-edit small business SOPs (onboarding, billing, support, hiring, weekly ops) you can adapt in an afternoon: https://orgdoc.gumroad.com/l/ofzwla
Top comments (0)