What to fix before automating a business process

Automation can remove repetitive work, reduce delays and improve consistency. It can also make a confused process fail faster.

Define the start and finish

Automation needs clear boundaries. What event starts the process? What conditions prove it is complete?

If completion is based on somebody feeling that the work is done, the automation has nothing reliable to check.

Identify the required information

List the information needed before each stage can progress.

Missing data should create a visible exception rather than allowing the process to continue and fail later.

Separate status from action

A status describes where the work is. An action describes what needs to happen next.

Automating status changes without clear actions can create a process that looks active while nothing useful is happening.

Name the owner

Every manual action needs an owner. Every automated action needs a clear exception owner.

When automation fails, somebody must know that it failed and what to do next.

Remove unnecessary repetition

Do not automate duplicate entry simply because it already happens.

First ask whether the repeated step is needed at all, whether the information can be captured once, or whether two records should be combined.

Keep judgement where it belongs

Not every decision should be automated. Exceptions, disputes, unusual customer needs and commercial judgement may still require a person.

The goal is not to remove people from the process. It is to remove unnecessary effort and make responsibility clearer.