Business Process Reengineering

Business process reengineering for radical redesign

Business process reengineering (BPR) is the radical-redesign cousin of incremental process improvement. Michael Hammer framed it in his 1990 HBR article "Reengineering Work: Don't Automate, Obliterate" - start with a blank sheet rather than edit the existing process - and Hammer and Champy expanded it in their 1993 book. This page covers the BPR programme as a BPMN process map, when to choose BPR over incremental BPI, and how to avoid the failure modes the 1990s BPR wave was famous for.

By Jack Finnegan · Updated 21 May 2026

Map the redesigned process Business process improvement

What it is

What business process reengineering actually is

Business process reengineering (BPR) is the radical redesign of business processes to achieve dramatic improvements in cost, quality, service, and speed. Michael Hammer introduced the concept in his July-August 1990 Harvard Business Review article "Reengineering Work: Don't Automate, Obliterate", and Hammer and James Champy popularized it in their 1993 book *Reengineering the Corporation*; the key distinguishing idea was that BPR starts with a blank sheet rather than editing the existing process - it questions whether the process should exist at all and designs the answer from first principles.

BPR went out of fashion in the late 1990s after a wave of failed implementations and was eclipsed by the gentler language of Lean, Six Sigma, and business process improvement. The discipline has since matured into a more disciplined practice: BPR is appropriate where incremental BPI has hit a ceiling, where the process is fundamentally wrong, or where digital transformation makes the old process obsolete.

The problem today

BPR's bad reputation comes from skipping the as-is

The classic 1990s BPR failure mode: a senior executive declares the existing process is broken, hires a consultancy to redesign from scratch, the consultancy delivers a beautiful blank-sheet design, and the team trying to implement it discovers that all the awkward variants and exceptions the existing process handled were the entire reason the existing process looked so messy. The redesign breaks half the things the as-is was quietly handling correctly.

The fix is keeping the as-is in scope. The point of BPR is to redesign on first principles, but you cannot redesign honestly if you do not know what the existing process is actually doing. Modern BPR pairs blank-sheet design with rigorous discovery - capture the as-is including the workarounds, then design the to-be from first principles knowing what you are replacing.

Four pillars

Four pillars of a modern BPR programme

Question the fundamentals

Why does this process exist? Who is it for? What would happen if it disappeared tomorrow? The questions that incremental improvement is not allowed to ask.

Honest as-is discovery

You cannot redesign what you do not understand. Discovery captures the workarounds and exceptions that the existing process handles - the bits the blank-sheet design needs to replace.

Blank-sheet design

Design the to-be without anchoring on the as-is shape. The disciplined version of "what would a brand-new firm build?".

Pilot before scale

Pilots prevent the 1990s failure mode. A controlled rollout catches the variants the design missed before they break the full population.

Process Map

A BPR programme as a process map

The canonical flow - identify, question, design, pilot, scale, decommission - with the viable gateway routing failed pilots to refine-or-abandon.

Open in editor

A business process reengineering programme as a process map

A Hammer-and-Champy-style business process reengineering (BPR) programme rendered as a BPMN 2.0 process. Identify the candidate, question the fundamentals, design from a blank sheet, pilot, scale, and decommission the old process.

Identify a candidate process - usually one where incremental improvement has hit a ceiling.
Question the fundamental assumptions: why does this process exist at all, who is it serving, what would happen if it did not exist.
Design the redesigned process from a blank sheet, not as an edit of the as-is.
Pilot the redesign with a controlled cohort.
If the pilot is not viable, loop back and refine the blank-sheet design (or abandon the redesign).
If the pilot is viable, run the full rollout and decommission the legacy process.

What this diagram shows: The programme starts when a reengineering candidate is identified - usually a process where incremental improvement has hit a ceiling. The question-fundamentals task is where BPR diverges from BPI: blank-sheet design follows, not edit-the-existing. Piloting is non-negotiable; the viable gateway routes failed pilots back to refine-or-abandon rather than letting a flawed design hit full population. Successful pilots flow to full rollout and legacy decommissioning.

FAQ

Frequently asked questions

What is business process reengineering?

Business process reengineering (BPR) is the radical redesign of business processes - starting with a blank sheet rather than editing the existing process - to achieve dramatic improvements in cost, quality, service, and speed. Michael Hammer introduced the concept in his 1990 Harvard Business Review article "Reengineering Work: Don't Automate, Obliterate"; Hammer and James Champy popularized it in their 1993 book *Reengineering the Corporation*.

What is the difference between BPR and BPI?

BPI is incremental - it improves the existing process within its current shape. BPR is radical - it asks whether the process should exist at all and redesigns from a blank sheet. Most programmes are BPI; BPR is reserved for when incremental improvement has hit a ceiling.

When should you choose BPR?

When incremental BPI has hit a ceiling, when digital transformation makes the existing process obsolete, when a regulatory or competitive shift changes the question the process is answering, or when the existing process is fundamentally wrong - serving the wrong outcome, run by the wrong roles, or built on assumptions that no longer hold.

Why did 1990s BPR fail so often?

The classic failure mode was skipping the as-is discovery. Blank-sheet redesigns shipped by consultancies broke the workarounds and exceptions the existing process was quietly handling. Modern BPR pairs blank-sheet design with rigorous discovery.

How does BA Copilot fit into BPR?

BA Copilot accelerates both halves: the discovery (turning interviews and transcripts into as-is BPMN in seconds) and the blank-sheet design (producing the to-be BPMN as a working diagram, not a slide). The to-be diagram then drives implementation rather than living as a strategy artefact.

Jack Finnegan, Founder & CEO, BA Copilot

From the founder

14 Years in BPMN

I'm Jack Finnegan. I've spent fourteen years working hands-on with BPMN, as an analyst, an engineer, and a product director, where I felt every sharp edge of legacy business process platforms.

BA Copilot is the platform I wanted on every one of these projects: AI-first process management, which treats BPMN as a first-class output rather than an export afterthought.

Jack Finnegan on LinkedIn

Redesign without breaking the workarounds

Open BA Copilot, capture the as-is fast with AI-assisted modelling, then design the to-be on a blank canvas with the existing variants in view.