What Makes a Good SOP?

Most organizations have SOPs that no one actually uses. They exist, technically, in a shared drive somewhere — but the people doing the work follow their own version, learned from a coworker, because the written one doesn't match reality or is too painful to use in the moment.

Why most SOPs fail

They're often written once, by someone documenting from memory, and never updated as the process changes. They're written to look thorough rather than to be usable — dense paragraphs instead of scannable steps. And they're written for an audience of auditors or new hires in the abstract, not for someone mid-task trying to remember the next step.

What a good SOP actually looks like

It's scannable, not a wall of text. Numbered steps, short sentences, and visual breaks let someone find their place quickly while actually doing the task.

It covers the exceptions, not just the happy path. The moments people most need an SOP are the unusual cases — what to do when a customer wants an exception, what to do when a system is down. An SOP that only covers the standard flow doesn't help there.

It says who to ask, not just what to do. When a step is ambiguous or something goes wrong, the SOP should say who to escalate to, not leave the person guessing.

It's owned by someone, with a review date. SOPs that don't have an owner rot the moment the process changes. A named owner and a periodic review keeps it trustworthy.

It was written by, or validated with, the person doing the work. SOPs written entirely from a manager's mental model often miss the real friction points a frontline employee runs into daily.

How to tell if yours are working

Ask a few frontline employees whether they actually use the written SOP or their own version. If it's the latter, the SOP isn't documentation — it's a compliance artifact nobody relies on, which means the real process still lives entirely in people's heads.

Where this connects

SOP development is one output of good process mapping — the map shows you what the process actually is; the SOP is how you make that repeatable for everyone else.