Speed is not the first goal
A workflow that is unclear, duplicated, or approval-heavy should not be automated as-is.
The first goal is clarity: what starts the workflow, who owns it, what data matters, what exceptions exist, and what outcome proves it worked.
Automation should remove ambiguity
A strong automation layer reduces interpretation. It defines states, owners, review points, notifications, dashboards, and audit trails.
What to redesign first
Remove duplicate entry, clarify approval rules, define the source of truth, and separate normal cases from exceptions before building software around the process.