Process Cycle Efficiency
Definition
Process Cycle Efficiency
Process cycle efficiency measures how much of a process cycle is spent adding value, dividing value-adding time by total elapsed time. It is the share of a workflow that is actually working, and most real processes score far worse than anyone expects.
Single-digit results are normal rather than alarming. A figure of 5% is not a scandal — it simply means nineteen minutes of every twenty are spent waiting.
The measure exists to make waiting visible. Most improvement effort goes into speeding up the working portion, which is the smallest part of the total.
That is the insight lean practitioners keep returning to. Remove the queues — and the process gets faster without anybody working harder.
Key takeaways
- Process cycle efficiency divides value-adding time by total elapsed cycle time.
- Results in single digits are common and indicate queue time, not laziness.
- Only steps a customer would willingly pay for count as value-adding.
- Improvement comes from removing waiting, not from accelerating the working steps.
How it works
Map the process, time each step, then classify every step as value-adding or not. Divide the value-adding total by the full elapsed cycle time and express the result as a percentage of the whole.
Classification is where judgement enters. The test is whether a customer would knowingly pay for that step if they could see it happening.
| Step type | Examples | Counts as value-adding |
|---|---|---|
| Transformation | Processing a claim, writing code, packing an order | Yes |
| Inspection | Checking, approving, reviewing | No |
| Movement | Handoffs between teams or systems | No |
| Waiting | Queues, batching, overnight holds | No |
Inspection is the row that causes arguments. Checking work is necessary, but it does not change the thing being checked, so lean method places it outside the value-adding total.
The American Society for Quality defines lean as management practices that improve efficiency and effectiveness by eliminating waste, with the core principle of removing non-value-adding activity.
Support is widely available for the analysis itself. The Manufacturing Extension Partnership runs nearly 1,400 advisors across more than 450 service locations in all fifty states and Puerto Rico, offering value stream mapping among its services.
Small operations get results too — a two-week mapping exercise on a single back-office process routinely surfaces days of hidden queue time nobody had ever measured.
Examples
Efficiency figures look shocking until you see how much of a typical cycle is queue rather than work. Four cases show where the waiting actually accumulates in practice.
An invoice processing team. Active handling takes eleven minutes and the elapsed cycle runs 32 hours, giving efficiency near 0.6%. Approval queues account for almost all of the gap.
A claims assessment process. Efficiency rose from 3% to 9% after two sequential reviews were merged into one. No individual step got faster.
A software release pipeline. Build and test consume four hours while waiting for a change window consumes three days. Moving to daily windows tripled the figure.
A recruitment process. Interview time totals five hours against a 34-day elapsed cycle. Candidate drop-out tracked the waiting time far more closely than it tracked salary offers.
Related terms
Process cycle efficiency belongs to the toolkit used to find and remove waste in a workflow. The terms below cover the mapping, the analysis, and the automation that follows.
- Process Mapping: the first step in the calculation.
- Process Analysis: the discipline the measure sits inside.
- End to End Process: the boundaries of the cycle being timed.
- Business Process Improvement: the work the number justifies.
- Six Sigma: the variation-reduction half of the method.
- Efficiency Metrics: the wider measurement family.
- Robotic Process Automation (RPA): the tooling that removes handoffs dragging the figure down.
FAQ
What is a good process cycle efficiency?
Anything above 25% is strong for an office process, and many manufacturing lines target higher. Most unimproved administrative processes land below 10%.
Why are the numbers so low?
Because elapsed time counts every queue, handoff, and overnight hold. Active work is nearly always a small fraction of the total.
What counts as value-adding time?
Steps that change the product or service in a way the customer would pay for. Checking, moving, and waiting all fail that test.
Does inspection really not count?
Not under lean method, because inspection does not change the thing inspected. It may still be necessary for safety or compliance.
How is it different from cycle time?
Cycle time measures how long the whole process takes. This measure shows what proportion of that time was productive.
How do you improve the figure fastest?
Remove waiting rather than speeding up work. Merging approvals and shrinking batch sizes usually deliver the largest single gains.
See how delivery partners run process improvement work across the Outsource Accelerator BPO hubs.
Independent
