Almost every SME we visit has a folder of standard operating procedures. Very few have SOPs that anyone uses. The documents were written once, usually under pressure from a customer audit, and have since drifted out of step with how the work is actually done. Staff learn the real process from whoever trained them, and the folder becomes a record of intentions rather than practice.

Write from Observation, Not from Memory

The first mistake is writing the procedure at a desk. What ends up on paper is the process as management believes it happens, which is rarely the process that produces the output. Stand at the workstation. Watch a full cycle. Note the order of steps, the tools picked up, the judgement calls made and the moments where the operator hesitates. Those hesitations are where errors live, and they are exactly what the SOP has to resolve.

One Page, One Process, One Owner

A procedure that runs to twelve pages will not be read on a busy floor. Break the work into discrete processes and give each one a single page: purpose, scope, the numbered steps, the checks, and what to do when the check fails. Name an owner and a review date on the document itself. Anonymous procedures decay because nobody is accountable for keeping them true.

Write for the Newest Person on the Team

The test of an SOP is whether a competent new hire can follow it without asking a colleague. That means no unexplained abbreviations, no assumed sequence, and specifics wherever a range exists — not "tighten securely" but the torque value, not "check the temperature" but the acceptable band and the action outside it.

Control the Version, or Lose the System

Every controlled document needs an identifier, a revision number, an approval and a location. If two versions can circulate at once, the system has failed regardless of how well the procedure was written. A simple register listing every SOP, its revision, owner and next review date is enough for most SMEs, and it is the first record an ISO auditor will ask to see.

Train, Then Verify

Issuing a procedure is not implementing it. Brief the team, run the process under observation, and then check compliance a week later without warning. Where practice has already diverged, the question is not who disobeyed but whether the procedure is workable. If the written method is slower or clumsier than the workaround, staff are right and the document needs revision.

Done properly, an SOP is not bureaucracy. It is the mechanism by which a business stops depending on the memory of a few people — and it is the foundation on which quality control, training and certification all rest.