Process re-design is rethinking how a workflow should work from first principles, not just speeding up the existing steps. Automation, by contrast, takes an existing process and removes manual effort from it, even if the process itself is inefficient.
Rethinking a process versus speeding it up
Process re-design is the practice of rethinking how a workflow should work from first principles, rather than simply making the existing steps run faster. Automation, in contrast, takes an existing process as it currently stands and removes manual effort from it — even if that process is fundamentally inefficient to begin with. The distinction matters more than it might first appear, because automating a flawed process doesn’t fix the flaw, it just makes it happen more quickly and with less visibility into what’s actually going wrong.
A simple way to picture the difference: automation asks “how do we do this current thing faster, with less manual effort?” Re-design asks a different, more fundamental question — “should we even be doing this in the current form at all, or is there a better way to achieve the same outcome?”
Why the order matters
Generally, re-design should come before automation, not the other way around. Automating a process that’s carrying unnecessary steps, redundant approvals, or outdated logic just means those inefficiencies now run on autopilot, often making them harder to notice and fix later, since nobody’s actively performing the wasteful steps by hand anymore to notice how wasteful they are.
Does re-design always mean a big project?
No. One of the more common misconceptions is that process re-design implies a large, disruptive initiative spanning an entire department. In reality, it applies just as usefully to a single workflow: how invoices get approved, how a new client gets onboarded, how a support request moves from received to resolved. Small, well-scoped re-design projects are often the best place to start, both because they’re lower risk and because they demonstrate value quickly enough to justify tackling larger processes afterward.
Will every process eventually need this?
Most will, eventually processes tend to be built for the scale and complexity a business had at the time, and they rarely get revisited unless something forces the issue. As a business grows, the assumptions baked into an old process quietly stop matching reality, and what was once a sensible workflow starts generating friction nobody’s stopped to question. Recognising this as a normal part of growth, rather than a failure, makes it easier to treat process review as a routine activity rather than a last resort.
What this looks like in a real business
Consider an invoice approval process that’s grown three extra sign-off steps over the years, each added in response to a specific past problem that may no longer even apply. Automating that five-step approval just makes the redundant steps happen faster. The redesign question asks whether all five are still needed at all, or whether the original problem they were solving has since been fixed some other way, making several of them dead weight nobody’s thought to remove.
Quick facts
- Automation speeds up an existing process, flaws included.
- Re-design questions whether the process should exist in its current form at all.
- The two are often combined — redesign first, then automate what remains.