An SOP written from memory, after the fact, by the person who's done the task a hundred times tends to skip exactly the steps that person no longer thinks about consciously. Those are usually the steps a new hire actually needs.
An SOP that gets used isn't the one with the most detail. It's the one written the way someone who's never done the task actually needs to read it.
Most SOPs get written once and quietly ignored after that
An SOP that reads correctly to the person who wrote it can still fail the person trying to follow it for the first time, because the writer's assumed context isn't on the page. A document is only genuinely useful once it's tested against someone without that context.
Write it while doing the task, not from memory afterward
Writing an SOP by recalling how a task generally goes skips small steps that feel too obvious to mention but aren't obvious to someone new. Write it while actually performing the task, capturing every click and decision as it happens, not from a general memory of the process.
In Stelaah, a workflow's actual steps live next to the work itself, so an SOP can link directly to the real screen instead of describing it from memory. See how automations works.
Show the actual screen or interface, not just a list of steps
A purely text list of steps forces a new hire to translate instructions into an interface they've never seen. A screenshot or a short recording of the actual screen removes that translation step and prevents most of the "wait, where do I click" confusion.
Name the common exceptions, not just the happy path
Most SOPs describe only the smooth version of the task, which leaves a new hire stuck the moment something doesn't go as documented. Name the two or three most common exceptions explicitly, and what to do when they come up, rather than leaving them undocumented.
Test it on someone who genuinely didn't write it
The only real test of an SOP is whether someone unfamiliar with the task can complete it using nothing but the document. Have an actual new hire, or someone unfamiliar with the process, follow it literally and flag every place they got stuck.
A simple checklist
If you do nothing else, do these five things:
- Write the SOP while doing the task, not from memory afterward.
- Include screenshots or a short recording of the actual screen.
- Name the common exceptions, not just the smooth path.
- Test it on someone who genuinely didn't write it.
- Fix the exact places a real reader got stuck, not what looks incomplete.
Do that, and an SOP becomes a document a new hire can actually follow alone, not one that only makes sense to the person who wrote it.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
