If work takes minutes but delivery takes days, the gap is often time spent waiting between steps. Flow efficiency makes that gap visible: it is value-adding work time divided by total elapsed lead time, expressed as a percentage. The word “most” in this title is a useful question to investigate—not a universal statistic. Whether waiting dominates depends on the process, its boundaries and how value-adding time is defined.
What flow efficiency measures
Flow efficiency compares time spent doing work that creates value for the customer with the total elapsed time from the start to the finish of a defined process. The calculation is:
Flow efficiency = value-adding work time ÷ total elapsed lead time × 100
For example, if a particular order spends 30 minutes in value-adding work and takes 10 hours from receipt to delivery, its flow efficiency is 5% when both figures use the same elapsed-time convention. The other 95% is time outside the counted value-adding work; it may include queues, handoffs, approvals or other pauses. This calculation describes that order and those definitions, not every order in the process.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
Lead time is the elapsed time for one item to move through a defined process or value stream from start to finish. A value stream includes all the actions—both value-creating and non-value-creating—needed to bring a product from raw material to the customer, as the Lean Enterprise Institute explains.
Decide what counts as value-adding
Use the customer’s perspective, not whether a task keeps a person or machine busy. The Lean Enterprise Institute’s test is whether omitting a task, without affecting the product, would make the customer judge it less valuable. Classification therefore depends on the particular product or service and what its customer values.
Machine run time and employee utilization are not automatic substitutes for value-adding time. A task may be necessary for internal control or compliance without directly increasing customer-perceived value; define and report such work clearly rather than silently treating all active time as value-adding.
Keep lead time and cycle time distinct
Lead time covers the end-to-end elapsed interval. Cycle time describes the time to complete a process cycle or individual step. A process can have short cycle times yet deliver slowly when work waits between steps. A value-stream map can record process data such as cycle time, uptime, changeover time and percentage complete and accurate alongside lead time; these measures answer different questions.
Rank #3
- book
- A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition and The Standard for Project Management (ENGLISH)
Where the rest of the time goes
Waiting is elapsed time when the item, request or case is not receiving the value-adding work counted in the numerator. On a map, it can appear between process steps, in a queue or inventory, or during a handoff or approval. The Lean Enterprise Institute describes flow as material and information moving through a value stream without stopping, making pauses an important part of the improvement picture (Lean operations).
Do not assume every pause has the same cause. A queue may reflect batching, scheduling, capacity mismatch, an approval rule, missing information or defects that require rework. Those are possible explanations to investigate, not diagnoses you can infer from a low ratio alone. Map where the time accumulates, then find out what is happening there.
Rank #4
- Harvard Business Review Project Management Handbook: How to Launch, Lead, and Sponsor Successful Projects
- Harvard Business Review Press
- BLANK BOOK
Examples are not industry benchmarks
Published illustrations show how dramatic the difference between work time and lead time can be, but they do not establish a typical flow-efficiency percentage:
| Illustration | What it reports | How to interpret it |
|---|---|---|
| U.S. Environmental Protection Agency Lean and Environment Toolkit slide deck (2006) | 68 days of total lead time and 15 minutes of value-added time | A particular training example, not a population estimate. EPA slide deck |
| International Society for Pharmaceutical Engineering article (2008) | 5.9% value-adding time | A figure for the specific process example discussed in “Lean Manufacturing Techniques,” not a cross-industry benchmark. ISPE article |
These examples support investigating the balance of work and waiting; they do not support a single current, representative percentage for processes generally. Treat rules of thumb about a “typical” ratio cautiously unless their original study, population and measurement method are clear.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Best Value
How to measure your own process
- Choose one kind of work. Define the product, service, request type or customer journey you want to understand. State exactly when the clock starts and stops, and whether you measure calendar time or working time.
- Observe the current process. Walk the work as it actually happens. Record its steps, information flow, handoffs, queues or inventory, and relevant process data. Ask the people doing the work to validate the map. A current-state value-stream map describes the present flow; it is not the same as a future-state target. See the Lean Enterprise Institute’s mapping overview.
- Set a consistent numerator and denominator. Add the value-adding work time for the same item or case whose end-to-end lead time you measure. Keep units and clock conventions consistent. State whether your result is per item, order, case or cohort.
- Account for variation. If cases differ, measure multiple cases and state the observation period and summary statistic you use. One unusually fast or slow case should not stand in for the whole process.
- Locate the largest delays. Break waiting down by where it occurs and investigate the conditions behind it. A single total may reveal that time is not spent on counted work, but it will not explain why.
- Test a future-state change and remeasure. Use the current-state map to design countermeasures, then check lead time, quality and customer outcomes after testing. The Lean Enterprise Institute describes value-stream improvement workshops as moving from current-state analysis to a future-state map; it frames countermeasures as invitations to continued learning, not proof of a permanent fix (value-stream improvement).
Improve flow without shifting the cost elsewhere
Reducing a queue or handoff can shorten elapsed time, but a faster process is not automatically a better one. Check whether the change creates defects, unsafe work, excess workload, unwanted inventory or less reliable service elsewhere. Compare like with like: use matching start and finish definitions, similar case mix and the same value-adding-time rules when assessing before-and-after results or comparing processes.
Use flow efficiency as a diagnostic, not a team score. A raw percentage cannot fairly rank teams whose work, customer needs, definitions or service requirements differ. Pair it with the causes of waiting, quality and completeness—including rework and first-pass completion—and the customer outcome.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
