When to Automate vs. When to Redesign Processes
Not every broken process should be automated. Here's how to decide when to automate—and when to start from scratch.
Stu Mason
Automation expert • Sony, Paddle, Pfizer • 15 years experience • AWS certified
Automation is powerful—but it's not a silver bullet. Here's how to avoid automating bad processes and focus on what really moves the needle.
When to Automate
- Process is well-defined and repeatable
- Manual steps are the main bottleneck
- ROI is clear and measurable
When to Redesign
- Process is outdated, complex, or unclear
- Multiple handoffs or unclear ownership
- Automation would just speed up bad outcomes
Case Example: Redesign Before Automate
One client tried to automate a broken onboarding process—result: more errors, not less. After redesigning, automation cut onboarding time by 70%.
Insider Insight
Never automate a process you wouldn't want to keep as-is for the next 3 years.
Pitfalls
- Automating before mapping the process
- Ignoring user feedback
Visuals
- Automate vs Redesign Decision Tree
- Before/After Process Map
- ROI Comparison Chart
Conclusion
The best automation projects start with process clarity. Redesign first, then automate for maximum impact.
Want help deciding?
Book a free process review with ArcTether.
Join 2,847 automation enthusiasts. Unsubscribe anytime.