How long should an SOP be?

One page for most tasks in a small business. If a process genuinely needs more than two pages, it is usually two processes that should be separated. Length is the enemy of use.

Do I need software to manage processes?

No. Most small businesses do well with printed pages where the work happens plus a shared folder or pinned WhatsApp messages. Buy software when the number of documents makes finding them hard — not before, because software becomes another system nobody maintains.

What if my staff cannot read English well?

Write in the language the work is actually done in, use short numbered steps, and add photographs of the correct result where the task is physical. A procedure exists to be followed, not to be impressive.

How to Build Systems in a Small Business (Start With One SOP)

In most owner-led businesses, the operating manual is the founder’s memory. It is a remarkably efficient arrangement until the day it becomes the only copy — when a long-serving employee leaves, when you are unwell, when two customers get different answers to the same question.

"Building systems" sounds like a project requiring budget and software. In practice it is a series of one-page documents written by the person who already knows how the work is done. Here is how to produce the first one this week.

Step 1: choose the process that is already costing you

Do not start with the easiest process to describe. Start with the one whose failure you would find most embarrassing in front of a customer, or the one that most often pulls you back into the business.

Useful candidates in most small businesses: how an order moves from enquiry to delivery; how a new customer is set up; how stock is received and checked; how a complaint is handled; how the day is closed and cash reconciled; how a new employee spends their first week.

Step 2: describe it out loud before you write it

Writing a process from a blank page is slow and produces something formal and unusable. Instead, explain the process out loud as though teaching a capable new hire, and record yourself on your phone. Ten minutes of talking is roughly a page of procedure.

This also captures the things you would never have thought to write — the exceptions, the "unless it is a Friday", the supplier who needs to be called twice.

Step 3: write one page, in your team’s words

Structure that works, and fits on a page:

What this covers and who does it — one sentence each.
The steps — numbered, each starting with a verb. Aim for seven to twelve.
The three places it usually goes wrong — and what to do about each.
What "done properly" looks like — so the person can check their own work.
Who to ask if the situation is not covered — with a named role.

Write it in the language your team actually uses, including the local terms and the mix of languages people work in. A procedure written in careful formal English that nobody speaks on the floor will be politely ignored.

Step 4: test it on a real person and say nothing

Give the document to someone who does not normally do the task and ask them to follow it while you watch in silence. Resist every instinct to help.

Each point where they hesitate, guess or ask a question is a defect in your writing — not in them. Note it, fix it, and repeat once. Two rounds of this is usually the difference between a document that gets used and one that gets filed.

The two-week test

A useful standard for whether a process is genuinely documented: if you were unreachable for two weeks, could this task be performed correctly by someone using only the written procedure? If the honest answer is no, the process still lives in your head and the business still depends on you being available.

Step 5: put it where the work happens

A procedure in a folder on your laptop does not exist. Put it where the task is performed — printed and laminated by the machine, pinned in the store, saved as a pinned message in the team’s WhatsApp group, in a shared phone folder.

Accessibility beats elegance. A slightly scruffy printed page on the wall outperforms a beautifully formatted document three clicks deep in a drive nobody opens.

Step 6: build the habit, not the library

One process a fortnight is a realistic pace alongside running a business. In six months that is a dozen documented processes — which in most small businesses covers the great majority of daily work.

Add one rule to protect it: whenever something goes wrong twice, the correction goes into the relevant procedure the same week. That single habit is what stops your documentation from quietly becoming fiction.

Where AI genuinely helps here

Documentation is one of the clearest wins for AI in a small business, because the hard part is starting. Describe the process out loud, paste or dictate the transcript, and ask for it to be structured into numbered steps with the failure points marked. You then edit — which is much easier than drafting.

Keep the judgement with yourself: the tool does not know your suppliers, your exceptions or your team. More on this in how Ugandan entrepreneurs can use AI and on AI for entrepreneurs.

What changes when the systems exist

Quality stops depending on who is on shift. New hires reach competence in weeks rather than months. Staff turnover becomes an inconvenience instead of a crisis. You can delegate, because there is something to delegate to.

And the business becomes worth something to someone other than you — which matters if you ever intend to sell it, borrow against it, or hand it to your children. A business that runs on one person’s memory is a job. A business that runs on documented process is an asset.