把指示寫清楚一次：比任何工具都更省時間

It is a Tuesday morning and the owner has stepped out for an hour. The phone rings. A regular customer wants the usual order, with one change. The person who answers has heard the owner explain the change once, weeks ago, while they were both busy with something else. She writes the new detail on a scrap of paper, puts the paper down to answer another call, and forgets where she put it. By the afternoon the order goes out the old way. The customer is polite about it. The owner spends the evening apologising and remaking the order, and wondering why a job she explained so often still goes wrong when she is not in the room.

This article was drafted with AI assistance. It is written in plain English for people who run businesses, not for people who build software, and it makes no claim about any particular product. It is about one habit that saves more evenings than any new tool: writing the instruction down once, clearly, where the work happens.

The instruction lives in one head

Most small businesses run on instructions that were never written down. The owner knows how an order is taken, how a complaint is handled, and how a delivery is booked. She explained it all at some point, out loud, to someone who was also doing three other things. That is how most knowledge moves in a small business. It works until the owner is away, or the person who was told leaves, or the day is busy enough that memory slips.

Memory is a poor place to keep a working instruction. It changes a little each time it is remembered. One person remembers the step about checking the date and forgets the step about writing it in the book. Another remembers both steps and adds a step of their own that nobody asked for. After a few months, three people are doing the same job three different ways, and each of them is sure theirs is the way it has always been done.

Writing it down fixes the drift. It does not need to be long. It needs to say what happens, in what order, and what counts as done. When the instruction is written, a new person can follow it without guessing, and the owner can check the work against the same words the worker read. The argument about how it has always been done ends, because the words are there to look at.

That is the relief worth picturing. The owner steps out, the phone rings, and the person who answers opens the same short note the owner wrote. The order is taken the same way it was taken last week. The change is written in the same place it is always written. Nothing depends on remembering a conversation from weeks ago. The owner comes back to work that looks the way she expected it to look.

What a clear instruction looks like

A clear instruction names the job in plain words. "Take the order" is not clear enough, because it leaves the hard parts out. A clearer version says what to ask, what to write down, and where to write it. Ask for the name, the number, and the date the customer wants it. Write all three in the order book, on the line for that day, before hanging up. Read the date back to the customer before ending the call. Each sentence can be checked. A person reading it knows when she has finished, and the owner checking later knows what to look for.

A clear instruction also says what to do when the usual case does not happen. Most mistakes happen at the edge, not in the middle. The customer changes an order. The supplier is late. The payment does not go through. If the note only covers the easy day, the worker has to guess on the hard day, and guessing is where the scrap of paper comes from. One extra line for each common exception is enough. If the customer changes an order, cross out the old line, write the new line underneath, and tell the owner when she returns. If the supplier is late, ring this number and write down what was said. The worker still uses judgement. She just does not have to invent the procedure while the customer waits.

And a clear instruction is short enough to be used. A page that nobody reads is no better than a conversation nobody remembers. If the job takes ten steps, write ten short steps. If it takes three, write three. Leave out the reasons and the background unless the reason changes what the worker should do. The note is a tool for doing the job, not a history of the job. When the job changes, change the note the same day, and throw the old copy away. Two versions of the same instruction, kept in different drawers, will cause the very mistake the note was meant to prevent.

Keep it where the work happens

Where the note lives matters as much as what it says. A note in the owner's notebook helps nobody but the owner. A note pinned above the phone helps the person answering the phone. A note kept in the same book as the orders helps the person writing the orders. Put the instruction where the hands are, not where it is tidy to file.

The same applies to anything that follows instructions, whether it is a person or a system. A system will follow the words exactly as written, including the gaps. If the instruction says to write the date down but never says where, the system will put it somewhere, and that somewhere may not be where anyone looks. If the instruction says to check the order but never says what checking means, the check will be whatever the reader imagines. Vague words produce vague work. Precise words make the checking easy, because the owner can see in a minute whether the date is in the book, on the right line, read back to the customer.

That is why writing instructions down is worth doing before buying anything new. A new tool will follow a vague instruction just as faithfully as a person will, and it will do it faster, which only spreads the mistake further. A clear note, used every day, shows what the job actually is. It shows which steps take the longest, which steps go wrong most often, and which steps nobody needs to do by hand at all. Only then is it worth asking whether part of the job could be handed over, and to what.

The short version

Write the job down once, in short sentences, in the order it happens. Say what to ask, what to write, and where to write it. Add one line for each common exception. Keep the note where the work happens, change it the day the job changes, and throw the old copy away. The gain is ordinary and it is large: the same job done the same way, whether the owner is in the room or not, and an evening that belongs to the owner instead of to an apology.

Ready-made AI agents for small businesses, built in public.