Mistakes Used to Get Caught by Accident

An invoice goes out at the wrong rate. Three months ago that would not have happened, because Sarah typed the invoices by hand and she knew that client was still on the old pricing. She would have paused, frowned, and gone to ask someone. Nobody ever asked Sarah to check pricing. It was not in the process, it was not in her job description, and it did not appear in the handover notes. It happened because she was looking at the thing.

That gap is easy to miss, because it is hard to miss something nobody ever named. When a process gets written down, the sequence of steps is often easier to capture than what the person noticed while doing them. Re-keying a figure gives someone a reason to read it. Formatting a document gives someone a reason to see the client name at the top. Some of those checks were never formal decisions anyone documented, so they tend to sit in the same place as everything else nobody can find because it was never written down. They came with the work, and they can leave with it.

A common answer is to put a human in the loop, or to add a review step at the end. That assumes the check is a known thing you forgot to include. Often nobody can name it, so the review gets written as look it over before it goes out. Reading something to confirm it looks right is different work from producing it. The second can be a weaker form of attention, and adding it does not necessarily put back what you removed. Clean-looking output can invite a quicker glance, especially on a busy Thursday.

So the more useful question before you automate anything is not what are the steps. It is what does the slow version give a person a reason to look at. Ask the people doing it now what they have caught in the last six months, and what made them stop. The answers may be surprisingly specific: a client whose PO numbers often come through wrong, a supplier whose dates need a second read, a job type where the hours rarely add up the first time.

Those answers become part of the brief for the new process. Some of what comes back will turn out to be a rule rather than a judgment, and a rule can be written into the system as a flag that fires every time without anyone remembering. Some of it is real judgment, and that is where you decide deliberately what technology carries and what stays with a person, with a reason to look rather than an instruction to review. Either way, the check becomes something you chose. What is worth asking this week is simple enough. On the process you are about to speed up, who is currently looking at it closely, and what will give them, or anyone, that same reason afterward?