What to redesign before automating a business process

The quickest way to automate a process is to take what exists and make software do it faster. It is also an easy way to spend money preserving problems. Every workaround, duplicate approval and unnecessary handover becomes a permanent feature, now with a licence fee. A short redesign pass before automation is usually time well spent.

Map the process as it really runs

Documented procedures describe how a process was meant to work. The actual process lives in inboxes, spreadsheets and the habits of a few experienced people. Walking through real cases with the people who handle them reveals the steps that matter, the ones that exist only because of an old constraint, and the ones nobody can explain.

Question every handover

Each time work moves between people or systems, it waits, it is re-keyed, and information is lost. Handover points are often where delay accumulates. Some are necessary for control or expertise. Many exist because of how teams were organised years ago. Removing or merging a handover often improves a process more than automating both sides of it.

Decide what the data should be

• Which fields are genuinely required to complete the work, and which are collected out of habit.
• Where each piece of information should be captured once, and which system holds the master copy.
• What validation should happen at the point of entry, so errors are caught early.
• What the process should produce for reporting, so visibility does not require a separate effort.

Separate the standard path from the exceptions

Most processes have a high-volume standard path and a smaller set of exceptions that consume a disproportionate amount of attention. Automation should target the standard path with confidence, while exceptions get a clear, human route with the right information attached. Trying to automate everything at once tends to produce a system that is rigid where it should be flexible and slow where it should be fast.

Assign ownership before building

A process without an owner drifts. Before automation, agree who owns the process end to end, who can change it, and how performance will be reviewed. Then the software has a customer who will keep it aligned with the business as things change.

Automation is a decision to keep a process the way it is for a long time. Make sure it is worth keeping.

This does not need to be a long exercise. For many operational processes, a focused discovery and redesign phase is enough to produce a cleaner target design, a shortlist of automation candidates and a realistic estimate of the benefit. The build that follows is smaller, faster and far more likely to be used.