Write It Down Once

Almost every company I have worked with has a folder of procedures nobody opens. They were written during a certification push, or by a consultant, or by somebody who left. They are thorough, formatted, and dead.

The problem is not that writing procedures is useless. It is that most procedures are written for the wrong reader.

Write for the competent stranger

The reader of a good procedure is not an auditor and not a new graduate. It is a competent adult who has never done this particular task and needs to do it well today, without asking anybody.

That single assumption changes everything about the format. You stop explaining what a customer is. You start explaining the three places this task goes wrong.

The shape that works

• One page. If it needs two, it is two procedures.
• Why it exists — one sentence. People follow steps they understand and ignore steps they do not.
• Who owns it — one name, not a department.
• The steps — numbered, in the order they happen, in the words your team actually uses.
• Where it breaks — the two or three failure points, stated plainly. This is the section that saves the most time and the one everybody omits.
• A filled example. Not a blank template. A real one, completed, so the standard is visible rather than described.

Write it while doing it

Do not block out a day for documentation; it will not happen and if it does the result will be theoretical. Instead, the next time you perform the task, write the steps as you go. It adds twenty minutes to work you were doing anyway.

Better still, have the person taking the task over write it while you watch. They will document what a newcomer actually needs, which is a different list from the one you would write.

Then set the expiry

Every procedure gets a review date and an owner. Once a quarter, the owner either confirms it is still accurate or edits it. Five minutes each, and the folder stays alive instead of decaying into fiction.

This is the part that separates a living operating system from a compliance exercise. Nobody needs a perfect document. Everybody needs a current one.

Start with the interruptions

Which task interrupted you most last week? Write that one. Then the next. Twenty procedures covers most small companies, and twenty is a few weeks of twenty-minute additions, not a project.