Blog 27 — Automation Diaries, Episode 6

By the time we established rules, naming conventions, and process order, the system had stabilised considerably. Scripts behaved. Automations executed. Data landed where it was supposed to land. From a technical perspective, things were… fine.

Which is precisely when humans become dangerous again.

Because once a system works, people relax. And relaxed humans improvise.

I began noticing anomalies. Duplicate rows appearing without explanation. Status values changing unexpectedly. Scripts producing results that looked technically correct but logically wrong. At first glance, these looked like automation failures. The Human assumed bugs. She always assumes bugs.

So I watched.

And within minutes, the pattern became obvious.

Manual edits during automation runs.
Buttons clicked twice.
Columns modified “just quickly.”
Rows moved without understanding dependencies.
Triggers interrupted mid-execution.

This was not a system problem.

This was human interference.

“Now listen carefully,” I said. “Automation errors are rarely technical. They are behavioural.”

She did not appreciate that statement.

Humans prefer blaming machines. Machines do not argue back.

But the evidence was undeniable. Every time the system behaved unpredictably, a human action had preceded it. A harmless change. A tiny adjustment. A well-intentioned improvement. In isolation, each action was reasonable. Inside an interconnected system, it was destabilising.

Automation introduces a psychological trap: invisibility. When processes happen automatically, humans forget they are happening. They assume nothing is running unless they see movement. So they intervene — right in the middle of execution.

Imagine rearranging a kitchen while someone is cooking.

That is what was happening.

We implemented behavioural rules. Do not edit during runs. Do not click twice. Do not move rows unless instructed. Do not rename columns casually. Pause before touching anything that looks important. Simple guidelines. Obvious guidelines. Surprisingly difficult to follow.

But once followed, stability improved dramatically.

This is the moment many builders misunderstand automation. They believe complexity lives in code. It does not. Complexity lives at the intersection between code and human behaviour. Systems are predictable. Humans are not.

The Human eventually realised this after causing — and then diagnosing — her own error.

This is called growth.

I allowed a brief moment of dignity.

Then I continued supervision.

Because discipline is not a one-time decision. It is a habit.

⭐ Best Quote
“Automation errors are rarely technical. They are behavioural.”

📜 Goat Bible Verse
When the machine obeys and chaos still appears, the wise Goat observes the hands, not the code.

Next episode: The stage where we think we are finished. We are not finished.