Automate a mess, get a faster mess.
Automation does not fix a broken process. It runs it faster, at scale, with fewer chances to catch the mistake before it lands.
Automation is amplification. Point it at a clean process and you get speed and consistency. Point it at a broken one and you get the same breakage, faster, at volume, with the human who used to catch the error now removed from the loop.
Automation amplifies whatever it touches
A process is a set of steps and assumptions. Automation does not evaluate them. It executes them, exactly, thousands of times, without the small human judgements that were quietly holding the broken parts together. Whatever the process does well, it now does well at scale. Whatever it does badly, the same.
The human was the error correction
Manual processes survive their own flaws because a person is in the loop, noticing the thing that looks wrong and quietly fixing it. That correction is invisible until you automate it away. The first sign that it existed is usually the flood of errors that arrives once nobody is watching each one go by.
Faster is worse when the direction is wrong
A slow bad process leaks. A fast bad process floods. Automation shortens the distance between a mistake and its consequences, and it removes the natural friction that used to give someone time to step in. Speed is only a virtue once you are sure of the direction.
Fix the process, then automate it
The order matters. Map the process, remove the steps that only existed to fix earlier steps, and get it working reliably by hand first. Automate the version that is already good. Automating to avoid fixing the process is not a shortcut. It is a commitment to the current mess, at speed.
Before you automate, ask whether you would be happy for this process to run a thousand times unattended tonight. If the answer is no, automation is not your next step. Fixing the process is.