How to implement automation without creating chaos

Automating processes sounds promising until you realise you’ve automated the wrong one. The most common mistake is rushing — deploying a tool before the team understands what they’re actually doing manually and why.

Start with an audit, not a tool

Before choosing any solution, map the processes you want to automate. Questions worth asking:

• How much time does this process take each week?
• Who does it, and what are the most common mistakes?
• Is the process stable, or does it change every few months?
• What data comes in and goes out?

Unstable or poorly defined processes are bad automation candidates. Stabilise first, then automate.

Pilot on a single process

Rather than automating everything at once, pick one process — ideally repetitive, well-defined, and with a measurable impact on time or cost. Deploy, measure results, and draw conclusions.

A successful pilot builds team confidence in new tools and provides arguments for further investment. Failing at small scale is acceptable; failing at the scale of the whole organisation is not.

What to avoid

Automating a bad process. If a process is inefficient, automation will make it faster at being inefficient.

Tools without an owner. Every automation needs someone responsible for maintaining and updating it.

Ignoring edge cases. Every process has exceptions. Automation that doesn’t handle exceptions creates chaos where a human used to simply solve the problem on the spot.

A practical first step

Pick one process that takes the team more than three hours per week and is performed the same way every time. Write it out step by step. Only then start looking for a tool — or commission its automation.