Do not automate dysfunction

Most automation requests arrive fully formed. "We spend six hours a week copying orders from email into our system — can you automate that?"

Usually the honest answer is yes. Software can read the email, extract the fields and create the record. The six hours disappear, the project looks like a success, and everyone moves on.

But it's worth asking a less comfortable question first: why are orders arriving by email in the first place?

Faster is not the same as better

When a process contains unnecessary steps, unclear ownership or outdated rules, automation doesn't remove those problems. It runs them faster and makes them harder to see.

A few patterns come up again and again:

• Approvals that no longer protect anything. An approval step introduced after a one-off mistake years ago is still there. Automating the routing makes the wait shorter, but the step itself still adds nothing.
• Duplicate data entry between systems. The same customer details live in three tools. Automating the copying hides the fact that two of those copies shouldn't exist.
• Workarounds that became the process. A spreadsheet started as a temporary fix and is now the source of truth. Automating around it locks it in.
• Unclear responsibility. Nobody quite owns the handoff between two teams, so work stalls there. A bot can move the task, but it can't decide who is accountable.

In each case, technology makes the existing arrangement more permanent. Changing it later becomes more expensive, not less.

Five questions before any automation

Before we recommend automating anything, we work through five questions with the people who actually do the work:

1. Should this step exist? If it were removed tomorrow, what would actually go wrong?
2. Can this process be simplified? Fewer handoffs, fewer formats, fewer exceptions.
3. Does this approval add value? Who is protected by it, and from what?
4. Are responsibilities clear? Every step should have one owner who knows they own it.
5. Does this system actually support the business? Or is the business working around the system?

Sometimes the answers confirm the process is sound and automation is exactly right. Often, though, a step or two can be removed entirely. The remaining work is smaller, simpler and cheaper to automate — and sometimes it no longer needs automating at all.

What this looks like in practice

Take the email orders. Working through the questions might show that customers email orders because the ordering form is hard to find, and staff re-key them because the form doesn't feed the order system. The better fix might be a simpler form connected directly to the system, with email automation kept only for the customers who will always email.

That's still a technology project, but it's aimed at the cause rather than the symptom.

The principle

Digital transformation isn't the same thing as installing software. It's the coordinated redesign of people, process, technology, data, governance and the operating model, so the technology has something sound to support.

Automation is one of the most useful tools available to a growing business. It just shouldn't be the first one you pick up.