How to write SOPs for a small business without drowning in process

Most founders know they should write things down. The intent is right; the usual result is a folder of documents nobody opens. SOPs fail not because the idea is wrong but because they are built like manuals — too long to write, too detailed to maintain, too dull to read. The version that works is much smaller.

A standard operating procedure has one job: to make a result happen the same way without you in the room. Everything that does not serve that job is overhead.

The minimum viable SOP

Think of one page, not a binder. A useful SOP captures only four things:

• Inputs. What has to be true or in hand before the work starts.
• The steps that change the outcome. Not every keystroke — the few decisions and actions where doing it wrong produces a worse result.
• The output standard.What “done well” looks like, concretely enough that two people would agree on it.
• The checkpoints. The one or two moments where a second look is worth it, and who looks.

That is enough for someone capable to own the result. Detail beyond it tends to make the document harder to keep current than the work is to do.

Write the ones that buy back attention first

The instinct is to document what is easy to document. Resist it. Start with the work that comes back to you most often — the recurring decisions and handoffs that interrupt your week. Onboarding a client, closing the month, handling an escalation, quoting a job. Each of these, written once and owned by someone else, removes a standing claim on your attention.

A practical rule: if a question lands on your desk more than a few times a month and the answer is roughly the same each time, that answer belongs in an SOP, not in your head.

An SOP is a living thing, not a monument

The reason short SOPs survive and long ones rot is maintenance. A one-page procedure can be corrected in two minutes when reality changes; a forty-step document quietly drifts out of date until people stop trusting it. Keep them short enough that the owner — not you — can keep them true.

The test

You do not need a perfect library. You need the result to happen without you. A good SOP passes a simple check: hand the page to a capable person who has not done the task, and the output meets the standard without a stream of questions coming back to you. When that is true, the knowledge has left your head and joined the business — which is the entire point.