Every business has standard operating procedures. The question is where they live: in a documented system anyone can follow, or in the heads of whoever has been around longest. Most SOP projects fail not because documentation is hard, but because teams write the wrong kind — fifty-page manuals nobody opens. Here is the approach that survives contact with a real team.
Why most SOPs die in a folder
The classic failure: someone spends a month writing exhaustive documentation, it goes in a shared drive, the process changes three weeks later, and the documents are stale forever after. The root causes are always the same — too long, written far from the person doing the work, and owned by nobody.
The rules that make SOPs stick
- One page or less. If it takes longer to read than to do, it will not be read. Checklists beat narratives.
- Written by the doer, edited by the owner. The person who does the task drafts it; leadership only reviews for accuracy.
- Stored where work happens. Inside the project tool, linked from the task — not in a distant wiki.
- Screen recordings count. A five-minute Loom of the actual task is often better than a page of prose — and takes a tenth of the time.
- Every SOP has an owner and a review date. Unowned documentation is future misinformation.
Where to start: the bus-test list
Do not try to document everything. List the tasks that would stop the business if one specific person were unavailable for two weeks — that is your priority queue. In most service businesses it is ten to fifteen processes: invoicing, client onboarding, the delivery workflow, payroll, and the handful of things only the founder knows. Document those first; ignore the rest until they earn a spot.
Make it a habit, not a project
The sustainable version is a rhythm: every time someone asks “how do I…?” in chat, the answer becomes a one-page SOP. Within a quarter, your real operating manual exists — written by the team, in the team's language. This is one of the first systems we build in our monthly operations partnerships, and a workflow audit will tell you exactly which processes to start with. Get in touch.