Why SOPs fail, and the one-page version that works
Nobody reads a 20-page SOP. How to write a one-page standard operating procedure your team will actually use, with a simple structure you can copy.
Most SOPs are written once, saved in a folder and never opened again. The problem isn’t that teams hate process. It’s that the documents are too long to use while working.
Why long SOPs fail
- They’re written for an audit, not for the person doing the job.
- Nobody owns them, so they go out of date.
- The important steps are buried in paragraphs.
- They try to cover every exception, so they cover nothing clearly.
The one-page structure
Every SOP gets one page and five parts:
- Goal: one sentence on why this process exists.
- Owner: one name, responsible for keeping it current.
- When it happens: the trigger, such as “a new order is confirmed”.
- Steps as a checklist: numbered, short, one action each.
- What “done” looks like: how anyone can check the work is complete.
If it doesn’t fit on one page, it’s probably two processes.
How to write your first one in 30 minutes
- Ask the person who does the job to talk you through it while you write.
- Turn every sentence into a checklist step.
- Remove any step that only exists because “we’ve always done it”.
- Ask someone new to follow it. Wherever they get stuck, fix the wording.
Keep it alive
Review each SOP for 15 minutes once a month. When something goes wrong, update the SOP the same day. A living one-pager beats a perfect manual nobody reads.
Why this matters for AI
AI and automation work best on clear, repeatable processes. A one-page SOP is often the step that makes a process ready to automate.
Map the process first with the free 10-minute process map. The One-Page SOP Kit gives you an editable template and five filled examples.
So, how might we turn our longest SOP into one page this week?