Every operation I've ever walked into had procedures. Almost none had them written down where they mattered. The best server knew the wine service sequence; the opening cook knew the line check; the sales coordinator knew how contracts got filed. Then one of them gave notice, and the operation got measurably worse for six weeks.
That's not a staffing problem. That's a documentation problem wearing a staffing costume.
Why Manuals Fail
Most operations manuals die within 90 days of being written, for predictable reasons: they're binders instead of tools — 80 pages nobody opens mid-shift. They're written once and never touched as the operation changes. They're stored where nobody works — the office shelf instead of the station. And they're never tied to training, so using them was optional from day one.
An SOP that isn't referenced during onboarding and pre-shift isn't a standard — it's a suggestion with a staple in it.
The One-Page Rule
One task, one page. Every SOP I write has five parts:
- The standard — what "done right" looks like, in one sentence.
- The steps — in order, numbered, no step longer than a line.
- The clock — how long this should take.
- The owner — which role does it, and who checks it.
- The exception — what to do when it goes sideways.
If a task won't fit on a page, it's two tasks. The discipline of the single page is what keeps the document alive — a new hire can hold it, a manager can audit against it, and a shift lead can retrain from it in five minutes.
Rollout Is the Product
Writing the SOP is a third of the work. The rest is rollout: introduce each one in pre-shift, have the current best performer demonstrate it, and fold it into onboarding so every new hire learns the standard — not their trainer's personal version of it. Then review the library quarterly; ten minutes per document. The operations that do this stop re-teaching the same job every time someone leaves.
SOPs turn your best shift into every shift — and they make your business worth more, because a buyer or a bank can see an operation that runs on systems instead of memories.