Process management
that steers
Process management usually gets introduced as a documentation exercise, and fails for that reason. What makes it steerable is numbers, ownership and a cadence for measuring again.
What process management is
Process management is the continuous steering of the flows a company uses to produce its result: describing them, measuring them, changing them and proving the change.
The term Business Process Management, or BPM, means the same thing. The decisive word is continuous. A one-off mapping produces a snapshot that goes out of date the moment the first flow changes.
In practice process management has three components, and all three have to be present. First, a description that shows the actual flow rather than the intended one. Second, numbers that state what the flow costs and how long it takes.
Third, ownership with authority to decide. Without the description, people talk past each other. Without the numbers, the loudest voice decides.
Without the ownership, nothing changes, however good the first two parts are.
Why rollouts end up in a binder
The usual course of events is well documented and always the same.
A project spends months mapping every process, produces a map and hands it to the organization. After that nothing happens, because nobody is authorized to decide on its basis and because no number is attached that would create pressure to act. Two years later a new mapping exercise starts, because the old one no longer matches reality.
The cause lies in the order of work. Completeness is put ahead of effect: describe everything first, improve afterwards. That takes so long that the earliest descriptions are stale before the last ones are finished — and in the meantime the initiative has nothing to show that would justify it internally.
The reverse order is less comfortable and lasts longer: take one process all the way through until there is a before-and-after in euros, and only then map the next. One proven case shifts the internal discussion more than a complete map, because it has already answered the question about benefit.
The process management cycle
Identify
Name and bound the processes: trigger, result, customer. Without a clear boundary there is no measurable object.
Document
Map the actual flow, variants included. Write down only the normal case and you have documented the exception away.
Analyse
Collect durations, volumes and costs — as ranges. Only across many runs does it show which step sets the pace.
Optimize
Pick one intervention and justify it. Exactly one, otherwise there is no way to attribute what worked.
Implement
Anchor the change in daily work with named ownership. A change without an owner survives until the first crunch.
Monitor
Repeat the same measurement on a fixed cadence. Without the second data point, any claim of benefit stays an assertion.
Three roles that have to be filled
Not three positions — in smaller companies one person often covers two. What must stay separate is deciding and analysing.
Process Owner
Owns the result and the metrics of a process across department lines and decides on changes. The role only works with budget and authority; without both it is a title.
Process Manager
Runs the process day to day, coordinates the people involved and reports deviations. Sees first when reality diverges from the described flow — and that report is worth more than any quarterly review.
Process Analyst
Collects durations and costs, simulates and presents findings. Deliberately separate from the owner: whoever decides on a measure should not also calculate its benefit.
Four metrics that actually steer
Each needs an owner and a threshold at which something happens. Without both it is a report.
Lead time
From trigger to result, waiting time included. Not handling time — the gap between the two is the actual finding.
Error and rework rate
Share of cases that have to go back a step. Rework costs twice: the work itself and the place it takes in the queue.
Cost per run
Labour, systems and rework attributed to one case. As a range, because an exception costs a multiple of the normal case.
On-time delivery
Share of cases finished by the date promised. Harder than a satisfaction survey and available without a survey effort.
Common questions about process management
Not above a certain size, but above a certain number of handovers. As soon as a case routinely passes through three or more pairs of hands and changes systems on the way, waiting times appear that nobody can see end to end. Other triggers are recurring errors in the same place, audit obligations, and any planned digitization — because a flow nobody understands does not get better through software, it gets wrong faster.
To start, a modelling tool for BPMN and a spreadsheet for the numbers. As soon as the question becomes where the bottleneck sits, you need simulation rather than averages, because only varying durations show which step actually blocks. A BPM suite is a decision for later — it answers questions you do not yet have at the beginning.
It depends what is being rolled out. Measuring a single process, changing it and proving the effect is a matter of weeks. Company-wide process management with ownership and a fixed measuring cadence takes longer — though it sensibly grows out of the first proven case rather than being decided as a programme up front.
Optimization is the individual intervention: a process gets examined, changed and the benefit proven. Process management is the frame in which that happens repeatedly — with roles, metrics and a cadence. Without the frame the optimization fades within a year; without optimization the frame only produces documentation.
By the same yardstick as before. If lead time as a range and cost per run were collected at the start, the same measurement can be repeated after the intervention and the difference stated. Without that first data point, any later claim about benefit stays an assertion — and that is precisely where most programmes fail to justify themselves.
If you want to know what your process costs: measure it.
Start with the free diagnosis or download FlowVisual. If you want to speak to someone afterwards, we're reachable.