When to Automate and When to Redesign
Decide between automation and redesign by testing whether the outcome, steps, decisions, inputs, and controls still make sense.
Updated: September 6, 2026
Direct Answer
Automate a process only when its purpose and logic remain sound; redesign when AI changes the necessary steps, decisions, or customer outcome.
Challenge the outcome and constraints
Ask whether the process still serves a necessary outcome and which constraints are real. Steps created for old system limitations, manual information transfer, or historical approvals should not automatically survive.
Assess variation and consequence
Stable, observable work with clear exceptions may suit automation. Ambiguous work with consequential errors needs redesigned decision support, stronger context, and deliberate human authority rather than unattended execution.
Remove before accelerating
Eliminate unnecessary steps, combine related decisions, improve inputs, and clarify policy before adding automation. Speed magnifies both sound design and structural waste.
Common Mistakes
- Automating every visible task
- Treating all variation as noise
- Ignoring downstream exception work
Market Signals
- Automation increases exception volume
- The process exists to reconcile disconnected systems
- Teams cannot explain why approvals occur
Questions for Leaders
"Would we create this process today?"
"Which errors are reversible?"
"What can be eliminated before automation?"