Skip to content
Business automation

Before you automate, decide what should happen

Automation works best when the process is understood first. Define the decision, the owner and the exception route before you choose a tool.

Equinox Consulting editorialPublished 5 November 20264 min read
A consultant mapping a process on a wall of sticky notes

If a team automates a process it has not agreed on, the same problems happen faster. Before anyone opens a tool, the team needs to agree what should happen, who decides and what to do when something goes wrong.

Write the process as it runs today

Sit with the people who do the work and record each step as it actually happens, including the spreadsheets, emails and checks that never made it into a procedure. Note where work waits, where it is re-keyed and where someone has to chase for an answer.

This often shows that part of the delay comes from unclear ownership or missing information, and less from manual effort. Fixing those first can remove steps that would otherwise have been automated.

Agree the rules before the tool

A rule a person applies by judgement has to be written down before a system can follow it. For each step you plan to automate, agree the following.

  • What input does the step need, and where does it come from?
  • What rule decides the outcome?
  • Which cases should go to a person instead?
  • Who owns the rule and approves changes to it?

Design the exception route

Every automated step will meet cases it cannot handle. Decide in advance where those cases go, who picks them up and how quickly. A well-run exception queue keeps people trusting the automation as volumes rise.

Choose one process and measure it

Start with a process that matters, runs often and has one accountable owner. Before you change it, measure how long it takes, how often it fails and how much rework it creates. Measure the same things afterwards. That gives you a clear case for the next process and a baseline if results slip.

Plan the handover too. Someone in the business needs to own the automated process, watch the exceptions and approve changes once the project team has moved on.

This is general operational guidance. Where automation touches compliance, AML or KYC processes, confirm the requirements with your qualified advisers.

Explore the related consulting serviceBusiness Automation
Start a conversation

What needs to work better in your business?

Tell us what you are working on. We will agree the scope, priorities and next steps with you.

Discuss your priorities