Why the things everyone "just knows" cause the most trouble

In most small businesses, the knowledge of how things actually get done lives in the heads of two or three people. The person who knows how to process a refund, order stock from the regular supplier, or close down the till properly is often the same person who is on holiday the week it all goes wrong.

The good news is that most of your daily operations are repeatable. They happen the same way, week in, week out. Writing those steps down is not paperwork for its own sake — it is a genuinely practical investment that pays you back three ways. Your customers get the same experience no matter who serves them. New starters become useful in days rather than months. And the small, avoidable mistakes that eat your time start to fade.

It also makes your business easier to step away from, whether that means a holiday, a period of illness, or eventually selling up. A business that runs on written procedures is worth more than one that runs on your memory.

Start with the tasks that cause the most friction

You do not need to document everything this month. Trying to do that is the fastest way to abandon the project entirely. Instead, pick the handful of tasks where things currently go wrong, slow down, or depend on one person. Good candidates tend to be:

• Anything that has gone wrong at least twice in the last few months
• Tasks only one person in the business knows how to do
• Anything with a deadline, a payment, or a legal requirement attached
• Questions customers ask again and again
• Processes that change depending on who is on shift

For a typical small firm, that might be opening and closing the premises, cashing up the till, ordering stock, taking a booking, onboarding a new client, or handling a complaint or refund. Choose five. Get those right, embed them, and then add more. Five solid procedures beat thirty half-finished ones.

Write procedures people will actually read

The biggest reason procedure documents fail is that they are written like manuals rather than instructions. Keep each one to a single page and write it for someone doing the task for the very first time, in plain English. A few principles that make a real difference:

• Start with the outcome — describe what "done" looks like before listing steps
• Number every step, with one clear action per step
• Say who does it, and roughly when
• Note the common mistakes, the awkward edge cases, and what to do about them
• Write "check the invoice against the delivery note", not "undertake a reconciliation"
• Add a photo, screenshot, or short screen recording for anything involving software or equipment

Test each one by asking someone who has never done the task to follow it word for word. Wherever they hesitate or ask a question, that is a gap in your writing, not in them. Fix the document, not the person, and you will end up with something genuinely robust.

Store them where people already look

A procedure nobody can find is worse than no procedure at all, because it creates the illusion that the information exists. Choose one obvious home and stick to it — a shared folder in whatever cloud storage you already use is usually the simplest. Give files searchable, practical names such as "Opening Checklist – Weekdays" or "Handling a Refund – Retail".

For anything performed at a specific spot, print it. A laminated card by the till, the coffee machine, or the van dashboard gets used far more often than a document buried three folders deep. To keep things tidy:

• Keep a single index page listing every procedure and who owns it
• Put a "last reviewed" date at the top of each document
• Name one person responsible for keeping each procedure current

Bring the team with you

Procedures imposed from above get ignored. Procedures that staff helped write get followed, because they reflect how the work is really done. Ask the person who performs a task daily to draft the first version — they will know the shortcuts, the workarounds, and the bits that always go wrong. Your job is then to tidy it up, fill in the reason behind each step, and make sure it meets your standards.

Review them on a sensible cycle: quarterly for most, and immediately whenever something changes. A new supplier, a new till system, a change in the rules — update the document that same week while everyone still remembers what changed. If a procedure causes more friction than it removes, change it. The document serves the work, never the other way around.

Common traps to avoid

The usual reasons this kind of project stalls are predictable, and easy to sidestep once you know them.

• Writing too much. A forty-page manual will not be read. One page per task will be.
• Documenting everything at once. Start with five tasks, prove the value, then expand.
• Ignoring the review date. Out-of-date procedures teach people that procedures can't be trusted.
• Keeping old steps "just in case". If a step no longer applies, delete it. Clutter hides the important bits.
• Assuming the team will find it. Point people to it, mention it in inductions, and refer to it in your own day-to-day work.

Written procedures are not about tying anyone down. They are about freeing up the people who currently spend their time answering the same questions, fixing the same errors, and covering for absence. Start small, keep it plain, and let the consistency do the rest.