Automation promises to remove tedious work, and it can. But it does exactly what it is told. If the underlying process is unclear, full of exceptions or dependent on one person’s judgement, automating it locks those problems in and makes them harder to see.
Map it first
Write down each step as it happens today — not as the manual says, but as people really do it. Note who does it, what they need and where it gets stuck. This alone often reveals steps nobody can explain.
Simplify before you automate
- Remove steps that exist only out of habit.
- Reduce approvals to those that add real protection.
- Standardise inputs — one form, one format.
- Decide how exceptions are handled, and by whom.
Then choose what to automate
Good candidates are frequent, rule-based and low-risk: sending confirmations, moving data between systems, creating routine documents, chasing overdue tasks. Leave judgement to people.
Keep someone watching
Every automation needs an owner who checks that it still does what was intended. Processes change; forgotten automations quietly produce errors for months.
Key takeaways
- Document the real process before touching tools.
- Simplify first; automate what remains.
- Give every automation a named owner.
