Automating without fixing the process is multiplying the mess.
Why the tool must come after the redesign, and how to prioritize what to automate first.
There is an understandable temptation: if a task consumes many hours, automating it seems the obvious solution. The problem is that automating a badly designed process only produces wrong results faster.
Before configuring any tool, three questions should be answered: should this activity exist? who should perform it? what controls does it need? In a high share of cases, the redesign eliminates the task entirely and automation is no longer necessary.
To prioritize, we use a simple matrix of hours saved per month against implementation complexity. What sits top-left is done first. With two or three early wins, the organization convinces itself.
The final criterion is dependency. An automation that only one person knows how to administer transfers the risk rather than removing it. Every delivery must include an administration manual and at least two trained people.

