Should you automate or redesign first?
Organizations often reach for automation when the real problem is an unclear or unnecessarily complex process. The right sequence is to understand the current state, remove avoidable work, standardise repeatable decisions, and then automate where technology can improve speed, quality, or control.
Signs that redesign should come first
- Different teams perform the same process in different ways.
- Approvals exist because ownership or decision criteria are unclear.
- Users re-enter the same information across several systems.
- Exceptions are common but not documented or measured.
- No one agrees on the outcome or the process success measures.
Where automation creates value
Automation is effective for high-volume, repeatable work with clear rules. It can route requests, validate required information, send notifications, calculate straightforward decisions, and create an auditable record. The best targets are tasks where manual effort is predictable and the expected result is well defined.
A practical decision framework
Map the process, measure volume and cycle time, identify rework, and separate rules from judgement. Redesign the unnecessary steps. Then compare the expected benefit of automation with implementation, training, support, and change costs. This keeps the business case grounded in outcomes.
Closing perspective
Automation is a capability, not a strategy. When process design comes first, automation can reinforce a simpler and more reliable way of working instead of making existing friction harder to change.