What It Actually Means
Most businesses of any age have some. They are typically in a shared drive, written during a push to document things, and materially out of date. That comes less from carelessness than from keeping documentation somewhere separate from the work.
What They Are Actually Worth
The value lies in three specific things the document enables.
Consistency. The task is done the same way, so the output is predictable and problems are traceable to a step rather than to a person.
Handover. Somebody new can perform the task without shadowing someone for a fortnight. This is where SOPs pay for themselves most obviously, and it is felt sharply when a long-serving person leaves without one.
A basis for improvement or automation. You cannot automate a process nobody has described. Written down, the redundant steps become visible, and roughly half the value of writing an SOP is discovering how much of the process exists for reasons that expired.
Why Most Fail
They live away from the work. A document in a folder is consulted by new starters for a week and then never again, because doing the task does not involve opening it.
Nobody owns them. Written by whoever was asked, owned by nobody, so when the process changes the document does not.
They are written for the wrong reader. Either so detailed nobody reads them, or so vague they describe the intention rather than the steps. The useful test is whether a competent person unfamiliar with the task could follow it and get the right result.
They document the ideal rather than the actual. Written by a manager describing how it should be done, while the people doing it use a different route with three workarounds. The document is then wrong from the day it is finished, and the real process remains undocumented.
What Actually Works
Attach the procedure to the point of use rather than storing it separately.
That means the steps appear inside the system where the work happens, as a checklist that is part of doing the task rather than a document about doing the task. Completion is recorded because completing the task records it. The procedure updates when the process does, because they are the same thing.
At that point the documentation has become a workflow, which is why process documentation frequently ends up as a software question rather than a writing exercise. Where this matters enough to build around, SOP software is the deliberate version.
What To Ask
Of your own business, more than of a supplier.
- Which tasks would stall if one specific person were away for a month? Those are the ones to document first, in that order.
- When was each SOP last used by somebody doing the work? The date it was last used tells you more than the date it was last updated.
- Does the written process match what people do? Ask the people, not the manager.
- What would break if we followed it exactly? The answer reveals the undocumented workarounds the process depends on.
Start with the handful that carry real risk. A business with five accurate, used procedures is in a considerably better position than one with sixty in a folder nobody opens.
More terms are in the glossary.