Writing SOPs People Actually Follow
Every company has SOPs. Most of them live in a shared drive nobody opens, written by someone who doesn’t do the work, formatted like a legal document, and updated last year — if ever. When a new person joins, they learn by watching a colleague, not by reading the manual. The SOP exists; the knowledge lives in people’s heads.
That’s the problem an SOP should solve, and most don’t. Here’s how to write procedures that people actually use.
Short beats comprehensive
The instinct is to document everything. Resist it. An SOP that tries to cover every scenario becomes a document nobody reads. A good SOP answers one question: “How do I do this task correctly?”
Keep it to one page if possible, two at most:
- Title — what this procedure is, in plain language.
- Purpose — one sentence on why it matters.
- Steps — numbered, in order, each starting with a verb.
- What can go wrong — the two or three most common errors and how to avoid them.
If a task needs more than two pages, it’s probably two tasks. Split it.
Write with the people who do the work
The worst SOPs are written by consultants or managers who describe how the work should happen in theory. The best ones are written with the people who do it every day, because they know the steps that aren’t in any manual — the workaround for the system’s quirk, the check that catches the error before it becomes a problem.
Sit with the person, watch them work, and document what they actually do — then clean it up. The result is an SOP grounded in reality, not aspiration. And because they helped write it, they’ll follow it.
Visual beats text
People don’t read paragraphs on a warehouse floor or in a busy kitchen. They glance at pictures and checklists. Use:
- Photos of the actual workspace, screens, or equipment — not generic clip art.
- Simple diagrams where a picture explains a sequence better than words.
- Checklists for verification steps — checkboxes work because they demand an action, not just comprehension.
A laminated one-page card at the workstation beats a fifty-page binder in the office every time.
Assign one owner per SOP
Every SOP needs a named owner — not a department, a person. That person is responsible for:
- Keeping the document current when the process changes.
- Answering questions and resolving ambiguities.
- Reviewing it on a schedule, even if nothing seems to have changed.
Without an owner, the SOP drifts from reality within months. With one, it stays a living tool.
Control versions so everyone uses the same one
Nothing undermines an SOP faster than three versions floating around — one in an email, one printed and taped to a wall, one in a folder that was never updated. Use version numbers, dates, and a single storage location that everyone knows.
When the process changes, update the SOP, increment the version, and tell the affected people. Remove the old copies. This takes discipline but prevents the confusion that makes people stop trusting the documents.
Train and spot-check, don’t just distribute
Sending an SOP by email and expecting compliance is like handing someone a recipe book and expecting dinner. Training on a new or updated SOP should take fifteen minutes — walk through it, demonstrate the steps, let people ask questions.
Then spot-check. Not to catch people doing things wrong — to verify that the SOP matches reality and that people can follow it. If they can’t, the problem is the document or the training, not the people.
Review regularly — even when nothing seems wrong
Schedule a review for every SOP — quarterly for critical processes, annually for stable ones. The question isn’t “does this still apply?” It’s “does this still match how we actually work?”
Processes drift. Tools get updated. Workarounds become habits. Regular review keeps the SOP connected to the real work — and keeps it worth following.
Where to start
- Pick the three tasks where errors are most costly or most frequent.
- Write a one-page SOP for each, with the person who does the work.
- Add photos or a checklist — whatever makes it scannable.
- Assign an owner and set a review date.
- Train the relevant people in fifteen minutes, then spot-check after a week.
Good SOPs aren’t documentation. They’re the difference between a business that depends on specific people and a business that runs on reliable processes — and that difference shows up in quality, consistency, and the freedom to grow.