Fixing a broken process first vs Automating the process as it is today
A process either has a shape worth keeping or it doesn't. Fixing it first means mapping how the work actually happens, admitting what a system can and cannot take over, then building against that corrected picture. Automating as-is means taking the process exactly as people run it now and putting a system underneath it, warts included, which is faster but inherits whatever was already wrong.
By Precipitate · Updated 25 July 2026
| Fixing a broken process first | Automating the process as it is today | |
|---|---|---|
| Effort it asks of you up front | Someone has to walk through the current process with you and be honest about what's inconsistent or undocumented before any building starts. That takes real time from you: answering questions and showing how the work actually happens rather than how it's supposed to happen. | Less negotiation at the start. You describe the steps, hand over access to the tools involved, and the system copies what already happens. That's lighter on you initially, but only because nobody is checking whether the process was sound in the first place. |
| Speed to get running | Slower out of the gate. Mapping the real process and agreeing what a system can honestly own takes time before anything ships. | Faster. If the steps are already clear and stable, wrapping them in automation can go live without a redesign step first. |
| The unusual case | A system built after the exceptions were mapped has a better chance of recognizing when something falls outside the normal pattern, and escalating it to a person instead of guessing. | A system built on top of an unexamined process usually only knows the version it was shown. An unusual case either gets forced through the normal path, giving a wrong result, or it stalls quietly, and you find out later from a customer or a report. |
| When it breaks | Because the system was built against a documented version of the process and is operated rather than handed off, a failure shows up as a clear deviation from something known and can be diagnosed against it. | The automation inherits whatever ambiguity the process already had. If there was no single correct way to do the task before, a failure is harder to trace, since there's no clean version to compare it against, only what usually happens. |
| What you own at the end | A documented, working version of the process, plus a system built to match it. If you ever move the work elsewhere, there's a clear reference for what the process actually is. | Automation of whatever existed, including its quirks. Fine if the process was already sound. If it wasn't, you now have a faster, less visible version of the same problem, running with less oversight than before. |
| When it stops making sense | Overkill for a process that's simple and already working well. Mapping something that isn't broken just spends time you didn't need to spend. | Weak fit for a process that leans on one person's judgment or has no agreed version at all. Automating that locks in the inconsistency and makes it harder to see, since it now runs quietly instead of visibly. |
Choose fixing the process first if exceptions come up often enough to matter, or if you're not sure the process people describe matches what they actually do when nobody's watching.
Choose automating as-is if the process is simple and already works well, and what you want is mainly to stop doing it by hand rather than to redesign it.
Related questions
How do I know whether my process needs fixing or just automating?
Look at what happens right now when something unusual comes up. If the answer is someone figures it out on the spot rather than here's what we do, the process has gaps that automation will copy rather than close.
Can I automate as-is now and fix the process later?
Yes, and it's a reasonable way to test whether automation is worth it before committing to a redesign. The catch is that once the automation is running quietly, the pain that used to prompt someone to fix the process disappears too, along with the pressure to ever go back to it.
Not sure which side you are on? Tell us what the manual work is, and we will tell you honestly what a machine can take off your plate and what still needs a person.
Start a conversation →