When not to automate a business process
The warning signs that a process needs clarification, ownership or simplification before automation can help.
Automation can preserve the wrong behaviour
A repeated task may look like an obvious automation candidate, but repetition alone is not enough. If the team disagrees about the rule or the information is unreliable, automation can make the wrong result happen more consistently.
The responsible decision is sometimes to pause, simplify the process and clarify ownership first.
Four reasons to wait
A short delay before implementation can prevent a much larger correction later. Treat these signals as design work, not as failure.
- The process changes every time because nobody owns the rule.
- Required data is missing, duplicated or not trusted.
- Exceptions are more common than the normal path.
- The task happens too rarely for ongoing automation maintenance to be sensible.
A better first response
Write the normal path, assign one owner and remove steps that exist only because of an old limitation. Then observe whether the remaining work is stable enough to support a reliable rule.
If the improved manual process is already fast and low risk, further automation may not be necessary.