Business Process Management
Definition
Business Process Management
Business process management is the standing discipline of designing, running, measuring and improving an organisation’s processes as a permanent activity rather than as a project with an end date. It never finishes — which is what separates it from a single redesign.
The acronym form of this term has its own entry in this glossary. The two describe the same discipline rather than two different ones, and business process management (BPM) covers the same ground from the technology side.
The discipline assumes processes decay. Volumes shift, exceptions accumulate, workarounds harden into practice, and a process that worked well two years ago now needs three people to keep it upright.
What makes it a discipline rather than a habit is ownership. Every significant process has a named owner who holds the performance numbers, approves changes and answers for the result across whatever departments the work crosses.
Ownership is also the part that fails quietly. An owner without budget or the standing to overrule a department head has a title rather than a role — and the process reverts within two quarters.
The discipline is indifferent to how the work is sourced. An owner keeps the measures and the review cadence whether the steps run in-house, at a shared centre or at a provider.
Key takeaways
- The activity is permanent, with owners, measures and a review cadence.
- Process owners cut across departments, which is why the model meets resistance.
- Measurement precedes change; unmeasured processes cannot be managed.
- Sequence and decision logic are modelled separately, using different notations.
How it works
The cycle runs design, execute, monitor, optimise, and then back to design. Each turn is small. A quarter that produces one measured improvement to a process beats a year spent building an unused model repository.
Monitoring is where most programmes stall. Collecting cycle time, cost per transaction, exception rate and rework rate takes instrumentation that few organisations have — and estimates will not support the decisions that follow.
Sequence and decisions are modelled apart. The Object Management Group notes that its decision model and notation is “designed to be usable alongside the standard business process notation BPMN”, keeping rules out of the flow.
Public digital teams treat measurement as a standing obligation. The UK government’s measuring success guidance covers “how to use data to improve your service: measuring, reporting, analytics tools and techniques”.
| Stage | Question | Common failure |
|---|---|---|
| Design | How should the work run | Modelling the ideal, not the actual |
| Execute | Does it run that way | Undocumented local workarounds |
| Monitor | What do the numbers say | Estimates standing in for data |
| Optimise | What changes next | Improvements that are never re-measured |
The discipline covers small corrections, not only large ones. Most of its value accumulates from changes too minor to justify a project, applied steadily over several years.
Examples
The discipline looks unremarkable from outside, because its output is a slow decline in cost and error rather than a launch. Three cases show what that looks like in practice.
An insurer appoints a claims process owner across four departments. Handover delays fall once one person is accountable, before any business process automation (BPA) work begins.
A utility runs quarterly reviews on its billing process. Each cycle produces a small change, and cumulative business process improvement removes a third of the exception queue over two years.
A retailer brings in process design outsourcing to rebuild its returns flow. The provider designs it; the retailer’s own owner keeps managing it afterwards.
Related terms
Process work divides into the standing discipline, the tools it uses, and the measures it watches. The entries below sit at those different points rather than describing the discipline itself.
- Robotic process automation (RPA): one automation technique the discipline may choose.
- Workflow outsourcing: handing execution to a provider while retaining the ownership.
- Process cycle efficiency: a measure the monitoring stage collects.
- Operational efficiency ratio: a summary metric reported above process level.
FAQ
Is this the same as reengineering?
No. Reengineering tears up one process and starts again. This manages processes continuously, and most of its changes are small enough that nobody outside the team notices them.
Does it require software?
Not initially. Owners, measures and a review cadence deliver most of the early benefit. Software becomes necessary when the volume of models and rules outgrows a spreadsheet.
Who should own a process?
Whoever is accountable for its outcome, not whoever employs the most people in it. Functional ownership is the most common reason cross-department processes stay broken.
How long before results appear?
Two to three quarters for the first measured improvements. Programmes that promise savings in the first quarter are usually counting a headcount cut instead.
What is the most common failure?
Modelling everything before changing anything. Repositories of unused process models are the standard artefact of a programme that lost its purpose.
How does it relate to a framework?
A framework names the processes. This discipline runs and improves the processes the framework has named.
Find process delivery partners in the Outsource Accelerator hubs.
Independent
