You have probably been pitched automation more than once, and quietly wondered whether your own processes were too messy for it to work. That instinct is worth trusting. Business automation multiplies whatever you give it. It saves hours on a clean process, but it repeats the same mistakes faster and at more cost on a broken one.
So the answer to whether a business should simplify a process before automating it is usually yes. This piece explains why, sets out the five signs a process is not ready, shows a one-afternoon way to map it, and ends with the honest call.
Why Automating A Broken Process Makes It Fail Faster
A manual process has one quiet advantage: a person notices when something looks wrong and stops. With automation, that check disappears and the flaw now runs at machine speed, many times a day, with nobody watching the middle. Reports may still look fine, but errors are building up underneath.
McKinsey found that when processes are not reconfigured before automation, the savings often prove elusive. In their work, one professional-services firm automated a process carrying hundreds of customer variations across five input systems. The build turned hypercomplex, needed manual intervention at several points, and was eventually abandoned. In other words, for business process automation to be valuable, a tidy process is needed.
Take invoicing, for instance. A person keying supplier invoices spots a duplicate and pauses. An automation without that check pays it, files it, and moves on, and the error only surfaces at month-end when the numbers do not reconcile. A task that scores on all four is worth automating. However, one that fails on cost of error or that touches personal data should still stay on a person’s desk.
Five Signs A Process Is Too Messy To Automate Yet
Check the process against these five signs before you shortlist a tool. Two or three of them, and simplification comes first.
- Too many hand-offs: the work passes between five or six people before it is done, and each hand-off is a place it can stall.
- Stacked approval loops: a single request needs three sign-offs.
- The same data keyed twice: someone types the same figures into two systems because the two do not talk.
- Exceptions outnumber the rule: the process has so many special cases that the standard path is the rare one.
- Nobody can draw it end to end: ask three people how it works and you get three different diagrams.
The last one matters most. A process no single person can draw is a process no tool can automate cleanly, because there is no agreed version to build against.
How To Map The Process In One Afternoon
You do not need a consultant or a fortnight, but you do need a whiteboard and the people who do the work. Draw a swimlane: one row per person or system, the steps left to right in the order they happen. This is BPMN-lite, the plain form of the Business Process Model and Notation standard, and it is enough.
Take a purchase-to-pay process. On paper it is six clean steps, but map what actually happens and the same few problems show up every time:
- Missing purchase orders: half the orders skip the PO step and go straight to buying.
- Stalled approvals: the sign-off bounces back because the budget code was left off.
- Double-keyed invoices: procurement enters the invoice once, then finance enters it again.
Now count the hand-offs and the points where work waits. Most of the six steps are fine. These three are where the time and the errors go, and that is your shortlist for simplifying.
What Simplification Looks Like In Practice
Once the map is on the wall, three moves clear most of the mess.
- Remove steps: cut the checks and copies that survive out of habit.
- Merge approvals: collapse three sign-offs into one where the other two add no real control.
- Settle on one source of data: pick the system that owns each figure, so nothing gets keyed twice.
Run purchase-to-pay through those three moves and the double-keying goes, the approval shrinks to one gate, and every order follows the same path. Now there is a clean process worth automating, and fewer branches mean a cheaper, steadier build for business process automation services to work with.
Automate Now, Simplify First, Or Leave It Manual?
Every process lands in one of three buckets, and naming the bucket saves money.
- Automate now: the process is clean, high-volume, and rule-driven. Go ahead.
- Simplify first: the process matters but scored on two or three of the five signs. Fix it, then automate.
- Leave it manual: low volume or genuinely judgement-heavy. A person is still the cheapest and safest option.
Most processes pitched for automation sit in the middle. That is not a reason to stall, but just the order of work: simplify, then automate.
Start Simplifying Your Business Processes with Net Onboard
A messy process does not get better by running faster. It gets more expensive, more often, with fewer people watching the middle. Simplification is the step that makes the rest work, and it is the one most automation projects skip. If a process in your business scores on two or three of the five signs, the tool is not the next step. The map is.
At Net Onboard, simplification is the second step of the AmplifyChampion journey, which runs digitisation, simplification, automation, then AI. Our team maps the process with the people who run it, strips out the steps and duplicated data that make it messy, and only then builds the automation on top.
Have a process that might be too messy to automate? Book a process review with our team and we will map it, name the fixes, and tell you whether to automate now, simplify first, or leave it manual with our cloud transformation services in Malaysia.