The procedure comes before the automation

Why robots and AI agents fail where nobody has written down how the work is really done

By The Human Union team · 25 Oct 2026 · 5 min read

Walk round any factory that has been going for thirty years and you will find a machine in the corner under a dust sheet. It cost a lot. It worked at the demonstration. It never worked on the floor, and nobody can quite say why.

The reason is almost always the same. The machine was bought to do a job as management understood it. The job as it was actually done had six extra steps, two of which were the whole reason it worked, and nobody had asked the operator.

Automation runs on procedure

A robot does what it is told. An agent does what its instructions say. Both are only as good as the description of the job they were given, and on most physical sites that description does not exist. There is a procedure in a binder from 2014, and there is what people do, and they drifted apart years ago.

So the robot is programmed from the binder, or from a consultant's week of watching, and it meets reality on the first shift. The operator used to tap the part before loading it to knock off the burr. The robot does not. The line jams. The robot goes under the dust sheet and the operator goes back to doing it by hand, with the added job of explaining to visitors what the machine was for.

The same thing is about to happen with agents

Firms are being sold AI agents to handle scheduling, parts, notes and customer messages. The pitch is sound. The failure will be identical: the agent will be built from the official process, and the official process is not what happens. The booking agent will give every job an hour, because the system says an hour, and the engineers know repeats need ninety minutes and have been quietly working round it for a decade.

Get the real procedure first

The fix is not clever. Before anything is automated, get the actual procedure from the people who do it: step by step, from a recent real job, with the why at each step and the exceptions they handle without thinking. Not the binder version. The Friday afternoon version.

Then mark each step. This one needs hands and judgement: person. This one is repeatable physical work: robot, one day. This one is reading, checking and passing on: agent, now. The marked-up procedure is the specification for everything that follows, and it was written by the only people who could have written it.

Firms that do this find the robot they were about to buy is the wrong one, the agent needs three rules nobody had mentioned, and two of the problems they wanted to automate away disappear once the procedure is simply written down and shared. That is a cheap discovery to make before the purchase order rather than after.


If this is on your mind, we would like to hear how your team learns. Thirty minutes with our team, no slides.

See it with your own example

Thirty minutes with our team, using a question from your own work.

Book a demo