Process Reengineering Outsourcing
Definition
Process Reengineering Outsourcing
Process reengineering outsourcing is contracting a specialist to rebuild a business process from scratch rather than to improve the one that you already have. The aim is a step change in cost, speed, or quality, not an incremental gain.
The distinction from improvement is the starting point — reengineering asks what this process would look like if nobody had ever built the current one.
Ambition is also the failure mode — a rebuild that touches four departments and three systems at once has more ways to fail than it has to succeed.
Most successful programmes are narrower than the label suggests — one process, one clear outcome, and a scope small enough that somebody can hold the whole thing in their head.
Key takeaways
- Reengineering rebuilds; improvement refines what already exists.
- Narrow scope succeeds far more often than enterprise-wide ambition.
- Executive sponsorship is required because departmental boundaries move.
- Adoption planning must be funded as part of the programme itself.
How it works
The specialist establishes what the process is for, measures current performance, and designs a new flow from the outcome backwards. The design is prototyped, tested against real volumes, and rolled out with training, new measures, and revised system configuration.
Sponsorship has to be senior. Reengineering moves work between departments, and only someone above those departments can settle the argument that follows.
Public bodies apply the same logic to shared functions. The Quality Service Management Offices model standardises common administrative services rather than letting each agency rebuild its own.
| Approach | Starting point | Typical gain |
|---|---|---|
| Improvement | The current process | 10% to 20% |
| Redesign | The current outcome | 20% to 40% |
| Reengineering | A blank sheet | Step change |
| Automation only | The current steps | Speed, not simplification |
| Doing nothing | Status quo | Gradual decay |
Service transformation has published evidence. Performance.gov documents federal work on redesigning services around what people actually need from them.
Scope discipline is the strongest predictor of success. One process, one owner, one measurable outcome beats an enterprise programme with a steering committee of fourteen.
Adoption is the second half of the budget. A redesign nobody was trained to run reverts to the old way within two quarters, and the money is simply gone.
Examples
Reengineering is contracted where incremental change has stopped delivering and where the process genuinely needs rebuilding. Four cases show the range of scope that actually worked.
An insurer. Claims intake was rebuilt around straight-through processing, cutting handovers from seven to two and shortening settlement times materially.
A council. Housing repair scheduling was redesigned from the tenant’s experience backwards rather than from the depot rota outwards.
A manufacturer. Order-to-delivery was reengineered as one flow after a merger left two incompatible processes running side by side.
A bank. Mortgage application handling was rebuilt around a single case owner, replacing a queue-based model that passed files between five teams.
The common factor in all four was narrowness. Each programme took one process with one accountable owner, and each avoided the enterprise-wide ambition that sinks most attempts.
Related terms
Process reengineering outsourcing sits at the most ambitious end of the process disciplines, bordered by the gentler methods and the delivery lanes that follow. The list below marks the boundaries.
- Business Process Improvement: incremental refinement of an existing process.
- Business Process Management (BPM): the ongoing discipline of running and improving processes.
- Six Sigma: a structured method for reducing variation and defects.
- Business Process Analyst: the role mapping and analysing the current state.
- Digital Transformation: the wider change programme this often sits inside.
- Business Process Automation (BPA): automating the flow once it has been redesigned.
- Operations Management: running the process after the rebuild lands.
FAQ
How is reengineering different from improvement?
Improvement refines the process you have. Reengineering starts from the outcome and designs a new process, which is why the gains and the risks are both larger.
Is enterprise-wide reengineering realistic?
Rarely. Narrow programmes with one process and one owner succeed far more often than broad ones with committees and multiple sponsors.
Who needs to sponsor it?
An executive above the departments involved. Reengineering moves work across boundaries, and only that level can settle the resulting disputes.
How long does a programme take?
Six to eighteen months for a single significant process, including adoption. Design alone is much faster and delivers nothing on its own.
What should be measured?
Cycle time, cost per transaction, error rate, and handovers removed. Baseline them before the redesign or the improvement cannot be evidenced.
Why do these programmes fail?
Overreach and unfunded adoption. Too broad a scope, or a design delivered without training and system changes, and the old process quietly returns.
Compare vetted transformation partners in the Outsource Accelerator directory.
Independent
