Every time we enter a new project, the first question the client asks is: "How long until we have it automated?"

It's a fair question. But it's not always the first one to answer.

There's a phase before automation that often goes unseen: the process stabilisation phase. Automating a chaotic process doesn't fix it. It leaves it chaotic, but at machine speed.

One of the most common mistakes we see is automating too soon. When the workflow isn't yet stable, when the team hasn't yet internalised how the process works, when exceptions outnumber standard cases.

The informal rule we use internally is: if you couldn't explain the process to someone new on the team in under fifteen minutes, you're probably not ready to automate it.

That doesn't mean you can't automate. It means you first need to simplify, document, and repeat. Until the process works without depending on the person who does it well because they've been doing it for years.

When a process is stable, understandable, and consistently executed, automation multiplies it. When it isn't, automation freezes its flaws.

The right moment to automate isn't when you're in a hurry. It's when you understand the process well enough that you could describe it line by line.

→ The mistake that makes you better · Why we don't work with everyone · How you know when change has truly worked