
Business Process Redesign: What It Is, When You Need It, and How to Do It Right
Business process redesign is one of the most misunderstood concepts in operational improvement. It gets confused with process optimisation, with digital transformation, and with ERP implementation. It’s related to all three, but it’s not the same as any of them.
This matters because businesses that implement ERP without redesigning broken processes automate those broken processes. Faster, more expensive, equally broken.
What Business Process Redesign Actually Is
Process redesign is the fundamental rethinking of how work gets done to achieve significant improvements in cost, quality, speed, or service. The key word is fundamental. Not tweaking a form, not adding an approval step, not moving a task from one team to another. Asking “why does this process exist in this form” and being willing to answer “it doesn’t need to.”
Process optimisation, by contrast, takes an existing process and makes it more efficient. You’re improving the current design, not questioning it. Both are valuable. The confusion comes when businesses apply optimisation thinking to processes that need redesign, they make a dysfunctional process slightly less dysfunctional.
When You Need Redesign vs Optimisation
Three conditions indicate redesign rather than optimisation:
The process has fundamental structural problems. If a process requires multiple handoffs between departments to accomplish something that could logically be done by one person or team, optimising the handoffs doesn’t fix the structure. Redesign eliminates the handoffs.
The process was designed for a different business context. Many Singapore SMEs are running processes that were designed when the business was half its current size, before they had their current product range, or before the market they serve changed. The process made sense then. It doesn’t now.
The process relies on workarounds. When the normal process doesn’t handle exceptions well, people build workarounds. Over time, the workarounds become the process. When you see a process that’s held together by people’s tribal knowledge of “how we actually do it,” you’re looking at a candidate for redesign.
The Business Process Redesign Framework
Phase 1: Document the Current State (As-Is)
You cannot redesign what you haven’t mapped. The as-is process documentation captures how work actually flows through the business today, not how the procedures manual says it should flow, but how it actually happens.
For each process, document: who initiates it, what information they need to start, what happens at each step, who makes each decision, what can go wrong at each step, and what the output is. Include the workarounds. Include the exceptions. The gaps between the official process and the actual process are where the redesign opportunities live.
Phase 2: Measure the Current State
Document the measurable costs of the current process: time to complete end-to-end, error rate, rework rate, staff hours consumed per transaction, and the frequency of exceptions. These numbers serve two purposes: they tell you where the biggest improvement opportunities are, and they give you the baseline against which you’ll measure the redesigned process.
If you don’t measure the current state before redesign, you can’t demonstrate the value of the change. This matters for getting buy-in and for validating that the redesign achieved its goals.
Phase 3: Design the Future State (To-Be)
The to-be design starts with the output, not the current process. What result does this process need to deliver? Work backward from the desired output to the simplest process that reliably delivers it.
Challenge every step. For each step in the current process, ask: Is this step necessary to produce the output? Does it add value for the customer or the business? Could it be automated? Could it be eliminated if we changed how an upstream step works? Could two separate steps be combined?
The redesigned process should be simpler than the current one, not more complex. Complexity is usually a sign of accumulated workarounds, not genuine business requirements.
Phase 4: Identify Technology Requirements
Only after the to-be process is designed should you ask what technology is required to support it. This is where most businesses get the sequence wrong. They buy the technology first, then try to fit their processes to the system. The result is a system that doesn’t fit the business and a business that’s constrained by the system’s logic.
The technology assessment question is: what does the redesigned process require from a system? Not “what does the system do?” but “what does our process need?” These are different questions that lead to very different outcomes.
Phase 5: Change Management
Process redesign fails in implementation far more often than it fails in design. The reason is almost always people, not technology. Staff who have built their expertise around the current process see redesign as a threat. Their knowledge of the workarounds and exceptions becomes less valuable. Their informal authority over parts of the process disappears.
Getting buy-in for process redesign requires involving the people who do the work in the redesign itself. They know where the current process breaks down better than any consultant does. When they’re involved in designing the replacement, they own it. When it’s imposed on them, they resist it.
Common Business Processes That Need Redesign in Singapore SMEs
Order fulfilment: From customer order confirmation to invoice. The most common failure is a process that requires manual handoffs between sales, operations, warehouse, and finance, each handoff adding delay and error risk.
Procurement: From identifying a need to goods received and payment. The most common failure is a process where purchase orders are raised without real-time inventory visibility, approved through email chains with no audit trail, and received without systematic matching to the original order.
Customer onboarding: From a new account request to the customer being active in the system with correct credit terms, pricing, and contacts. The most common failure is a process that takes two weeks because it requires seven people to do seven things sequentially that could be done in parallel or eliminated entirely.
Month-end close: From the last day of the month to published management accounts. The most common failure is a process built around reconciling data that shouldn’t need reconciliation if the source systems were connected.
The Outcome to Expect
Well-executed process redesign typically delivers 30–60% reduction in process time, significant error rate reduction, and measurable headcount efficiency improvement. These aren’t theoretical numbers, they’re what happens when you stop automating broken processes and start redesigning them first.
The businesses that get the most from ERP implementation are the ones that redesign their processes before they implement the system. The system then supports a process that’s been designed to work. That’s a fundamentally different outcome from fitting a new system around an old process.


