In most small businesses, the process lives in one person's head. It works, right up until that person is away.
You can spot it easily. Ask two people to describe the same job. If you get two different answers, there is no process. There is a habit, and habits do not survive a new hire, a busy week or a holiday.
Eight steps to get it out of someone's head and into something the business owns.
01
Watch the job being done before you write anything
Sit with the person doing it. Do not ask them to describe it, because nobody describes their own work accurately. They will skip the three things they do without thinking, and those three things are usually the process.
02
Map what happens, not what is supposed to happen
There is the official version and the real version. Write the real one. If people work around a step, that workaround is now part of the process, and it is telling you the official step does not work.
03
Mark every place the work changes hands
Handovers are where things get lost. Person to person, team to team, system to system. Each one needs a clear trigger and a clear owner. Most delays are not slow work; they are work sitting still between two people.
04
Write the document for the person who has never done it
Not a summary for someone who already knows. Exact clicks, exact names, exact wording. If a new person cannot follow it alone on their first day, it is a reminder, not an SOP.
05
Design the exceptions on purpose
Every process has awkward cases: the refund, the rush job, the customer who will not fit the form. Decide in advance who handles them and how. Undocumented exceptions become one person's private knowledge, and that person eventually takes a holiday.
06
Put the document where the work happens
Not in a folder nobody opens. Link it from the tool people are using when they need it. Documentation stored away from the work is documentation nobody reads, no matter how good it is.
07
Delete the dead steps ruthlessly
Old code and old instructions are what break things. One file we opened had the same job written out eighteen times over, plus about 1,060 lines that did nothing but looked like they did. Nobody could tell which version was actually running. Documentation rots the same way.
08
Give each document an owner and a review date
An SOP nobody owns is wrong within a quarter, and being wrong is worse than not existing. People follow it, get a bad result, and stop trusting every other document you have written.
Write it down before you automate it
Automating a process you have not mapped just makes the mess run faster and with fewer people watching.
Map first. Then remove the steps that exist only because of an old tool. Then automate what is left. Skipping the middle step is how businesses end up with an automated version of a workaround somebody invented in 2019.
The test that tells you it worked
Hand the document to someone who has never done the job. Ask them to do it, alone, without asking questions.
Every question they have to ask is a gap. Write the answer into the document and hand it to the next person. Two or three rounds and you have something real.
It is not a glamorous exercise. It is the difference between a business that can hire and one where every new person costs a senior person a fortnight.