Waiting: the Largest Hidden Loss
In most processes the majority of elapsed time is queueing. It is invisible to productivity measures and cheap to reduce.
Measure a process end to end and most of the duration is usually waiting rather than working. This is consistently true and consistently unmeasured.
The process issue in “Waiting: the Largest Hidden Loss” is easier to diagnose when effort can be connected to projects without confusing activity with value. Used for chronemics definition, see the official information can add time and workflow context, while the process outcome remains the source of truth for whether the system improved.
Where the waiting is
For approval.
For an independent perspective related to “Waiting: the Largest Hidden Loss”, consult the Microsoft WorkLab; it offers a useful external check on definitions, governance and the assumptions built into a proposed measure.
For information from somebody else.
For a system, a batch run, an overnight process.
For a specialist who is the only person who can do that step.
In a queue, because the team is at capacity.
And for a scheduled meeting at which the decision will be made.
The proportion
Organisations that measure it typically find working time is a small fraction of elapsed time.
The exact figure varies and the shape does not.
Which means improving how fast people work addresses the smaller part, and that is the finding that reorients most improvement efforts.
Why it is invisible
Productivity measures count output and effort, and waiting is neither.
Nobody is working during the wait, so it does not appear in hours.
And it is distributed across departments, so no single team sees the whole of it.
Only an end-to-end view shows it, which is why somebody has to deliberately look.
Measuring it
Walk one process and record the timestamps at each stage.
Elapsed time minus the time anybody was actually working on it.
Two days of work for a significant process, and it produces a specific list of queues with durations attached.
What it usually finds
An approval step taking days where the decision takes minutes.
A handoff where work sits in somebody's queue.
A weekly meeting that gates everything.
And a specialist bottleneck that nobody realised was one, which the constraint note covers.
Why it is cheap to fix
Removing a queue requires a decision rather than resources: a delegation limit, an auto-approval threshold, a named deputy, a shorter batch interval.
Most of these cost nothing and take effect immediately.
Which makes waiting the highest-return thing to measure, by a considerable margin.
Reporting it
As a proportion of lead time, with the largest queues named.
"Four days elapsed, of which three were waiting for approval" is a sentence that produces action.
A productivity percentage does not.
What to check
Have you measured elapsed time against working time for any process?
What is your longest queue?
How long do your common approvals take, elapsed?
And does anybody own the end-to-end duration?