4 min read

The most useful automation often looks ordinary

Automation is often discussed through impressive demonstrations. In production systems, the most consequential changes are frequently small, repetitive, and difficult to notice from the outside.

  • AI system design
  • Workflow automation
  • Human oversight

Look at frequency before spectacle

The useful automation involved copying reference numbers, requesting missing fields, checking state transitions, standardizing repeated replies, and moving records between systems. None of it looked futuristic. All of it occurred frequently.

A workflow can be examined with two initial questions: how often does the event occur, and how much judgment does it require?

  • High frequency, low judgment: a strong automation candidate.
  • High frequency, high judgment: assist the person, but preserve control.
  • Low frequency, high judgment: keep it human.
  • Low frequency, low judgment: automate only if the implementation is genuinely cheap.

The handoff is part of the system

A bounded agent needs to know where its authority ends. Conflicting records, unclear intent, or an exception to a rule should move to a person with the context intact.

Without that handoff, automation only relocates complexity. Someone still has to investigate what happened and reconstruct the previous sequence of events.

Observe the actions that disappear

A demonstration can show that a system behaves correctly in one path. A production evaluation asks whether the same workflow now requires fewer repetitive actions, produces fewer state errors, and leaves judgment-dependent decisions visible to people.

The best systems are often quiet. They make an ordinary Tuesday run better.

Written by Alexander Aluf

Programmer and software engineer. Writing about AI system design, software architecture, and production constraints.