The SOP people actually follow

Somewhere on your shared drive there is a folder of procedures. Someone wrote them during a quiet month, filed them neatly, and told the team where to find them. Open that folder now and look at the last edited dates. If most of them stopped changing a year ago, they are not procedures. They are archaeology.

Ask why nobody uses them and the answers are consistent. They are too long to read while working. They were written for an inspection, not for the person doing the job. They describe a version of the work that no longer exists. So people ask the colleague who knows instead, and the document loses without a contest.

A procedure people follow is short. One page, sometimes less. Steps in the order they actually happen, in the words the team already uses. It says what a finished job looks like and where the result goes. Anything that is background, history or justification belongs in a different document.

It has an owner, and the owner is a name, not a department. That person answers questions about it and has the authority to change it. A document that belongs to everyone belongs to no one. It goes out of date quietly, with nobody responsible for noticing.

It lives at the point of work. Linked from the tool where the job is done, or pinned in the folder the team opens every day. If following the procedure means hunting through three folders first, people will stop hunting. Distance from the desk is the quiet reason most procedures die.

And it changes when reality changes. A rule shifts, a step disappears, and the document is updated that same week rather than at the next review cycle. AI helps here: it can draft the first version from how the work is really done, spot where practice and the written steps have separated, and prepare the correction. A person decides what the new truth is. The test is simple. Hand your procedure to someone who has never done the job. If they cannot get through it without asking a colleague, the document is not finished.