Standard Operating Procedure (SOP)

Without a written procedure, each person invents their own version of the task. Quality drifts, errors repeat and nobody is sure who owns the fix. A team cannot grow from five people to fifty on memory alone. A new hire needs a document to follow, not a colleague to shadow for weeks.

Writing the steps down also improves the work. Spelling out each step exposes needless complexity and decisions nobody had made explicit. An SOP is also what makes delegation possible, and what lets an AI agent take over a task later, because an agent can only follow steps that exist in writing.

• Pick a task done often enough to matter, such as a weekly report or a client hand-off.
• Record yourself doing it once and explain the reason for each step, not only the click.
• Turn the recording into a numbered checklist with a title, an owner, the steps, a quality check and the place the output goes.
• Follow your own checklist the next time and fix any line that left you guessing.
• Store all SOPs in one place, named in a consistent way, and review them every quarter. Delete steps nobody follows.

An SOP is a short document that says how a task is done in your business: what triggers it, who does it, the steps in order, what a good result looks like and where the finished work is stored. Typical examples are onboarding a new client, sending an invoice, publishing a blog post or handling a refund.

It is not a policy or a long manual. It is a checklist that someone new could follow on their first day.

• Writing a manual instead of a checklist. If it takes more than a few pages, nobody will open it during the task. Keep each SOP to one task.
• Writing it from memory. Steps recalled at a desk differ from steps actually taken. Document the task while someone is doing it.
• No owner. An SOP nobody is responsible for goes out of date. Name one person per document.
• Leaving out the why. A step with no reason gets skipped when it feels inconvenient. One line of purpose helps people follow it.
• Never reviewing. Tools and clients change. Review each SOP on a fixed rhythm and delete steps nobody follows.
• Storing them in many places. If people cannot find the SOP in under a minute, they will do it from memory.