What it means
Most processes in a business were never designed; they accumulated. Someone added an approval after a mistake, a system migration added a rekeying step, and a departed manager left behind a report nobody reads.
Redesign treats that accumulation as the problem rather than as the constraint. The distinction from continuous improvement matters.
Continuous improvement shaves time off existing steps, while redesign asks whether the step should exist at all. A purchase approval that takes three days is improved by chasing approvers faster and redesigned by removing approval below a threshold entirely.
Finance cares because process cost is real cost that rarely appears as a line in the accounts. The salary of the people doing the rekeying sits in payroll, the error rework sits in overheads, and the working capital tied up by a slow invoicing cycle sits on the balance sheet.
Putting a cost per transaction on a process is what turns a vague complaint into a business case. A workable method is to map the current process with real timings, count the handoffs and the rework loops, then design the target process around the few steps that actually add value.
The test of a genuine redesign is that at least one role, system or document disappears. If nothing disappears, what you have is a tidy up.
The common nuance is that redesign fails on people, not on logic. Steps exist because someone was once blamed for an error, and removing a control without replacing the assurance it provided is how redesigns get quietly reversed.
Pair every removed step with either a system control or an agreed tolerance for the risk.
In practice
Real-world examples.
Example
An insurance broker's renewal process required clients to re-enter details the broker already held, then wait for a manual quote. The redesign pre-fills the form from the policy record and auto-quotes anything under $5,000 of premium. Renewal turnaround fell from six days to one, and retention improved because clients stopped shopping around while they waited.
Example
A manufacturer's month end close took 14 working days, largely because three teams reconciled the same intercompany balances in different spreadsheets. The redesign made one team the single owner, moved the reconciliation into the ledger and removed two sign-off memos. The close now lands on day six with the same audit evidence.
Example
A university's student refund process involved four signatures for any amount. After redesign, refunds below $500 are approved by system rule with a monthly exception report, and only larger refunds go to a human. Processing cost per refund fell from about $26 to about $4.
Formula
Calculation
The business case usually runs on cost per transaction: Cost per Transaction = (Minutes per Transaction / 60) x Fully Loaded Hourly Cost, and Annual Saving = (Old Cost per Transaction - New Cost per Transaction) x Annual Volume.
A shared services team processes 2,000 supplier invoices a month at 40 minutes each, with a fully loaded cost of $30 an hour. Old cost per invoice = (40 / 60) x $30 = $20, so the monthly cost is 2,000 x $20 = $40,000. The redesign removes two approval steps and one rekeying step, cutting handling to 10 minutes, so the new cost per invoice = (10 / 60) x $30 = $5, or $10,000 a month. The annual saving is ($20 - $5) x 24,000 invoices = $360,000, so a $600,000 redesign project pays back in $600,000 / $360,000 = 1.67 years, or about 20 months.Case study
Seen in the real world.
Meridian Fasteners is an illustrative, fictional industrial distributor used here to show a redesign rather than to describe a real company. Its order to cash cycle took 11 days from order to invoice, because orders arrived by email, were typed into the warehouse system, picked, then typed again into the accounting system by a separate clerk.
The finance director costed the process instead of complaining about it: 3,600 orders a month at 25 minutes of admin each, at $28 an hour, came to 3,600 x (25 / 60) x $28 = $42,000 a month. The redesign removed the second data entry by integrating the two systems, moved order capture to a customer portal, and invoiced automatically on dispatch.
Admin time fell to 6 minutes an order, or 3,600 x (6 / 60) x $28 = $10,080 a month, and invoicing moved from 11 days after the order to the same day. In this illustrative case the faster invoicing released roughly $740,000 of working capital, which was worth more to Meridian than the labour saving itself.
Watch out
Common mistakes.
- Automating the existing process instead of redesigning it, which locks the accumulated waste into software and makes it harder to remove later.
- Measuring the new process on activity, such as tickets closed, rather than on cost per transaction and cycle time, which is what the business case promised.
- Removing controls without agreeing who now owns the risk, so the first error reinstates every step the redesign took out.
Questions
People also ask.
How is business process redesign different from reengineering?
Reengineering is the older and more drastic label for the same idea, usually applied across a whole value chain rather than to one process.
How do I know a process is worth redesigning?
Look for high volume, many handoffs, repeated data entry and a rework rate above roughly one in ten, because those four together almost always hide real money.
Who should lead a redesign?
Someone who owns the outcome end to end rather than a single department head, because redesigns mostly fail at the boundaries between teams.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%