01 · Mechanics and boundaries
Mechanics and boundaries
Process efficiency has several meanings, so every ratio needs a named numerator and denominator. Process cycle efficiency uses value-creating elapsed time divided by total elapsed lead time. Processing-time ratio uses all active processing time divided by elapsed lead time. Labor productivity uses good output per labor hour. These measures answer different questions and should not be presented as interchangeable percentages.
State the unit, boundary, period, and value classification. For parallel work, sum only time on the order's timeline for a flow ratio; sum person-time for a labor measure. A shorter lead time may improve flow efficiency even if labor content is unchanged. Higher resource utilization may worsen order waiting when variability is substantial.
02 · Construct the analysis
Construct the analysis
Define the customer outcome and classify the work elements before calculating a value-based ratio. Collect complete order traces with comparable boundaries. Reconcile processing and waiting to total elapsed time. Calculate the ratio from compatible quantities and preserve uncertainty in the classification. Show the underlying minutes beside the percentage.
For an aggregate ratio, specify whether it is total value time divided by total lead time or an average of order-level percentages. Those calculations can differ because long orders receive different weights. Separate normal and exception routes, and track correct-first-time completion so a higher efficiency figure is not purchased through escaped defects.
03 · Worked warehouse-dispatch example
Worked warehouse-dispatch example
The fictional North Quay warehouse dispatches a single parcel-order family. Its boundary starts when an order is accepted for release and ends at confirmed carrier handover. Demand is 240 orders in a 420-minute net working day. Each order contains three lines on average, but the example keeps the parcel order as the unit of flow. No number below describes a real organization or a demonstrated improvement. The purpose is to make the reasoning traceable rather than to present a success story.
A representative order spends 12 minutes awaiting release, 2 minutes being released, 18 minutes awaiting picking, 8 minutes being picked, 24 minutes awaiting packing, 5 minutes being packed, 10 minutes awaiting checking, 2 minutes being checked, 15 minutes awaiting loading, and 3 minutes being loaded. These mutually exclusive intervals total 99 minutes: 20 minutes of processing and 79 minutes of waiting. They describe one complete normal-route trace, not a statistically estimated mean for every order. A separate 100-order diagnostic sample contains 20 late orders, defined as handover more than 120 minutes after acceptance. The normal trace and late-order sample therefore answer different questions.
Three pickers, three packers, two checkers, and two loaders work in parallel within their respective stages. At the illustrated processing times, theoretical stage capacities are 157.5, 252, 420, and 280 orders per day. Picking is below the 240-order requirement even before interruptions or rework. Release has two staff and a theoretical capacity of 420. These capacities assume dedicated resources, identical order mix, and no overlapping assignments. They are not observed outputs and should never be reported as effective capacity.
The normal dispatch trace contains eight provisionally value-creating minutes in 99 elapsed minutes, so process cycle efficiency is 8/99=8.08%, approximately 8.1%. All processing occupies 20/99=20.2%. The difference is the 12 minutes of active but non-value-creating work under the example classification. Neither ratio means that workers are idle for 79% or 92% of their paid time; queues belong to the order, and staff may work on other orders.
A proposed queue reduction of 20 minutes would yield 79 minutes lead time if processing and all other waits stayed unchanged. The planned value-based ratio would be 8/79=10.1%. This is a scenario estimate, not a measured improvement. The value time has not increased; the order simply spends less time awaiting work.
04 · Order-time composition
Order-time composition
05 · Interpretation and decisions
Interpretation and decisions
Use the ratio to direct attention toward the order's experience, then investigate the delay mechanism. Do not prescribe a target solely because another organization reports a higher percentage. Necessary controls, route complexity, and boundary choices affect the figure. Show lead time and correct output with the ratio to prevent denominator manipulation.
A weak application reports “80% efficiency” using active time and implies customer value. A sound application labels it processing-time ratio, explains the value classification separately, and avoids equating it with staff utilization. A favorable ratio can coexist with poor throughput if the process serves too few orders.
06 · Sound application and adaptations
Sound application and adaptations
For multi-route processes, stratify before aggregating and report the volume mix. For parallel branches, determine the elapsed value contribution without counting simultaneous minutes twice. If the classification is disputed, calculate a transparent range rather than forcing false agreement. For example, treating one further minute as value creating would give 9/99=9.1%, exposing the sensitivity.
Efficiency metrics are vulnerable to changed boundaries, excluded holds, and omitted rework. Retain the full accepted-order population for outcome reporting, including unfinished orders. Use productivity and capacity analysis for staffing decisions, and process cycle efficiency for delay analysis. A balanced decision keeps customer value, quality, resource effort, and lead time visible together.
07 · Evidence and follow-through
Evidence and follow-through
Make the observation auditable before debating a countermeasure. Preserve an anonymous order identifier, acceptance and handover timestamps, route, line count, shift, exception flag, and the observer's definitions. A timestamp from a completed screen action may describe data entry rather than physical completion. Reconcile several records with direct observation and ask the person doing the work what each event actually means. Keep an uncertainty note when clocks differ or two actions overlap; rounding cannot repair an ambiguous boundary.
Observe ordinary work and exceptions over a period that includes opening, replenishment, breaks, and the carrier cutoff. Selecting only easily followed orders produces a clean-looking but biased picture. When an order is unfinished at observation end, keep it visible as unfinished rather than silently deleting it. For multi-line orders, establish whether timing ends at the first line or the complete order. Include all three lines in the latter case, because the customer receives the order only after its final requirement is satisfied.
Turn the analysis into a bounded decision. Describe the proposed change, the mechanism expected to alter performance, the measure that would detect the change, and the conditions under which it would be withdrawn. A small layout change might reduce walking yet increase congestion; an extra release wave might lower one queue yet overload picking. Monitor handover performance, first-pass accuracy, work in process, and staff workload together. Treat the proposed numbers as planning assumptions until a comparable observation period supplies evidence.
08 · Boundary and robustness review
Boundary and robustness review
Before implementing the selected countermeasure, check the boundary one more time. If the analysis starts after order release, an upstream acceptance hold is outside its measured lead time even though the customer experiences it. If the analysis ends at the loading bay, a parcel waiting for the carrier is still incomplete within the stated dispatch outcome. Keep those events inside the customer-facing boundary, or state exactly why a narrower operational measure is also being used.
Assess robustness across normal variation. A proposed operating rule should specify what happens when an urgent order arrives, stock is unavailable, a staff member is absent, or the carrier changes collection time. Those conditions do not invalidate the main analysis; they define where its assumptions need adaptation. Rehearse an exception through the proposed route with the people responsible for each decision. Record which assumptions remain unverified and what evidence would be sufficient to proceed.
Finish with an explicit learning statement: what the evidence currently supports, what it does not establish, and which observation is needed next. A quantified hypothesis can be useful without becoming a guaranteed result. Retain the current-state observations so a later comparison can use the same event definitions and population. When the observed outcome differs from the prediction, revisit the mechanism and resource assumptions rather than adjusting the target after the fact.
Connections
Related methods and phase use
Placed under Analyze because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.