Nobody told the person who needed to know

A delivery moves from Tuesday to Thursday. The person who moved it knows. The customer who planned their week around Tuesday does not. Neither does the colleague who promised to be there to receive it.

Nothing went wrong in the work itself. The failure was a message that did not get sent.

Small changes cause big annoyance

Most of the complaints a business gets are not about the change. A delay is usually forgivable. What people remember is finding out late, or finding out from someone else.

Inside the team it works the same way. A price changes, a person goes on leave, a supplier switches. Each of those means someone else has to adjust, and each depends on someone remembering who that someone is.

The rule lives in one head

Ask who needs to hear when a booking moves, and you will usually get an answer like "well, the customer, and Sam, and probably whoever is on the desk." That answer is correct and it is also fragile. It works while the person answering is in the building and not rushed.

Make a change map

You can fix most of this with one page. Do it like this:

1. List the five changes that happen most often: date moved, price changed, item out of stock, person unavailable, job finished.
2. Next to each one, write who must be told. Name roles, not only people, so it still works when someone is away.
3. Add how and how fast. A text within the hour is a different promise from an email by the end of the week.

Keep it to one page. If it runs longer, nobody will use it.

Put the trigger where the change happens

The page only helps if it is in front of the person making the change. Put it next to the calendar, the order screen or the job board, not in a folder. The best version is a short checklist that appears at the moment the date is edited or the status is switched.

Say what changed and what happens next

A good change message has three parts: what is different, what it means for the reader, and what you are doing about it. "Your delivery is now Thursday. Someone will be there between 9 and 12. Reply if that does not work and we will find another slot." That is shorter than an apology and it does more.

Where a tool can help

Once the map exists, a tool can follow it. It can watch for the change, draft the message to each person on the list, and put it in front of a human to approve. Without the map, a tool has to guess who matters. With it, the tool is only doing what the page already says.

Try it this week

Pick the change that happens most often in your business. Write down who needs to hear about it, and how fast. Then check the last three times it happened and see whether they did.

If you have a change that always surprises someone, tell us what it is in the comments. We read every one. For examples of how we build this kind of work, see octyn.co/casestudies.