top of page

Automation is NOT the real goal

Oct 9
5 min read

A broken process does not become healthy because software runs it faster. It usually becomes a faster broken process.


That is the trap many teams fall into. They feel the pain of repeated work, missed steps, unclear handoffs, and slow approvals. Automation looks like the cure. So they buy a tool, build a workflow, or connect systems together. For a short time, things feel better. Then the same confusion returns, only now it is hidden inside the automation.


The better path climbs in order:


4. Process improvement

------------------------

3. Process automation

------------------------

2. Process standardisation

------------------------

1. No clear process


Each step matters. Skip one, and the ladder becomes shaky.


Wide-angle view of a wooden ladder leaning against a workshop wall with labelled steps.
Every stable improvement starts with the step below it.

When there is no process, every result depends on memory


A team without a clear process may still get work done. People use experience, reminders, chat messages, and personal notes. The problem is that the work lives in people’s heads.


That creates risk.


If one person is absent, the next person may not know what to do. If volume increases, small gaps become larger. If a customer asks for an update, the answer may depend on who last handled the task.


This stage often feels busy, not broken. The pain shows up through small signals:


  • The same question gets asked again and again.

  • Different people complete the same task in different ways.

  • Work gets checked late because no one knows who owns the next step.

  • Fixing errors takes longer than doing the original work.

  • New team members learn by guessing, watching, or interrupting others.


At this point, automation is tempting because it promises speed. But speed is not the first need. Clarity is the first need.


Before a team can automate, it must agree on what should happen.


Standardisation turns hidden habits into visible work


Standardisation means defining the best known way to do a task right now. It does not mean creating heavy rules for every small action. It means making the work clear enough that people can follow it, measure it, and improve it.


A standard process usually answers five simple questions:


Question

Why it matters

What starts the work?

Prevents confusion about when the process begins.

Who does each step?

Removes hidden ownership gaps.

What information is needed?

Reduces rework and follow-up questions.

What does “done” mean?

Keeps quality consistent.

What happens when there is an exception?

Stops unusual cases from breaking the flow.


Think of a restaurant kitchen. Before machines or ordering systems matter, the kitchen needs a standard way to prepare each dish. Ingredients, portions, timing, plating, and checks must be clear. Without that, faster equipment only helps people make inconsistent food faster.


Close-up of handwritten process cards clipped above labelled kitchen containers.
Standard work makes the invisible parts of the process easier to see.

The same idea applies to approvals, customer support, warehouse picking, maintenance checks, invoice handling, hiring steps, and almost any repeated work.


Standardisation should be practical. A one-page checklist may be better than a long manual. A simple flow diagram may be better than a complex system map. The goal is not to write perfect documents. The goal is to make the current best way easy to understand and easy to repeat.


This is why Standardize First, Automate Second, Improve Always is more than a catchy principle. It is a safety rule for change.


Automation should carry a good process, not hide a bad one


Once the process is standard, automation becomes far more useful.


Automation works best when the rules are clear. If a request has all required information, send it to the right person. If stock falls below a set level, create a reorder task. If a form is submitted, record the data and notify the next step.


These are strong uses of automation because the path is already known.


Problems begin when automation tries to solve unclear judgement, unclear ownership, or unclear quality. A tool cannot decide what the team has not agreed on. It only follows the rules it is given.


Before automating a process, ask:


  • Can we describe the process in plain language?

  • Do people follow it in roughly the same way?

  • Do we know which steps add value and which steps only create delay?

  • Do we know what exceptions should bypass the normal path?

  • Can we measure whether the new automated flow is better?


If the answer is no, automation may still be possible, but it will likely create extra work later.


There is another risk. Once a bad process is automated, people may stop questioning it. The tool gives the process a false sense of authority. People say, “That is how the system works,” even when the system is only copying an old mistake.


Eye-level view of a small mechanical conveyor moving identical wooden blocks in a workshop.
Automation works best when the path is already clear.

Automation is powerful. It can reduce manual work, lower missed steps, and make handoffs smoother. But it is not the finish line. It is a way to protect a standard process from unnecessary effort.


Improvement is the real goal


The highest step on the ladder is improvement.


This matters because even a standard, automated process can become outdated. Customer needs change. Team size changes. Regulations, suppliers, software, and costs change. A process that worked last year may slow people down this year.


Improvement asks a different question. Not “Can we automate this?” but “Is this still the best way to get the right result?”


That question keeps teams honest.


A useful improvement habit can be simple:


  1. Watch the process in real use.

  2. Find the friction.

  3. Change one thing.

  4. Measure the effect.

  5. Update the standard.

  6. Automate only when the new standard is stable.


This creates a loop. Standardisation is not a one-time document. Automation is not a one-time project. Improvement is the ongoing discipline that keeps both of them useful.


For example, a team may standardise customer request handling by using one intake form. Then it may automate routing based on request type. After a few weeks, the team may notice that many requests are being sent to the wrong queue because customers misunderstand one field. The right improvement may not be more automation. It may be rewriting the form question.


That is the point. Better work often comes from removing confusion before adding technology.


Use the ladder before choosing the tool


When a process feels slow or painful, start by locating it on the ladder.


If there is no clear process, document how work happens today. If the process varies by person, standardise the best known way. If the process is stable and repeated, automate the parts that do not require judgement. If the process is already standard and automated, look for the next improvement.


Top-down view of four paper cards arranged like ladder steps on a wooden workbench.
The ladder helps decide what kind of change the process needs next.

The sequence is simple, but it prevents expensive mistakes:


No process

↓

Standardise the work

↓

Automate the stable parts

↓

Improve the result

↓

Update the standard and repeat


Automation is not the end. It is one step in a larger practice of making work better.


The best teams do not ask, “What can we automate?” first. They ask, “What result are we trying to improve, and what step are we on now?” That question leads to better tools, cleaner processes, and changes that last.


bottom of page