Automation Does Not Fix a Broken Process - Do It Manually First
Automation Does Not Fix a Broken Process - Do It Manually First
I learned this the hard way building desktop automation. I spent weeks building elaborate workflows to automate browser tasks before I even knew if the actual task was worth doing repeatedly. Turns out half of them I only needed to do twice a month.
The Premature Automation Trap
It is tempting to automate everything the moment you have the tools. You see a repetitive task, and your brain immediately jumps to "I should build a workflow for this." But building automation has a real cost - setup time, debugging, maintenance when the target app updates its UI.
If you automate a task you only do twice a month, and it takes 5 minutes each time, you have saved 10 minutes per month. If the automation took 4 hours to build, you are looking at 24 months before it breaks even. And that is assuming the automation never breaks.
The Manual-First Rule
Now I do everything manually first for at least a week. I track how much time each task actually takes - not how much time I think it takes, but actual logged minutes. The difference is usually surprising.
Tasks I thought were eating hours per day turned out to be 15-minute jobs. Other tasks I barely noticed were quietly consuming 45 minutes every morning.
The 30-Minute Threshold
Only automate the stuff where you are losing 30 or more minutes a day. That gives you a real ROI within a week or two of building the automation. Anything below that threshold - just do it manually. It is faster, more reliable, and you do not have to maintain it.
The Right Order
- Do the task manually for a week
- Log actual time spent per occurrence
- Calculate daily total
- If it is over 30 minutes, build the automation
- If not, keep doing it manually and revisit in a month
The best automation is the automation you do not build for tasks that do not need it.
Fazm is an open source macOS AI agent. Open source on GitHub.