01 · Mechanics and boundaries
Mechanics and boundaries
Process flow analysis studies how units enter, move through, wait within, and leave a system. It connects rate, work in process, lead time, and release rules. A process flow chart shows route; flow analysis adds what happens to volumes over time. Define the flow unit carefully: an order, line, tote, and parcel can have different counts and synchronization requirements.
Work in process includes accepted units inside the chosen boundary that are not yet completed, including held units. Throughput is the completion rate for that same boundary. For a stable system with consistent units and long-run averages, Little's relationship connects average work in process, throughput, and average flow time. It should not be applied casually to a growing backlog or a single inventory snapshot.
02 · Construct the analysis
Construct the analysis
Record arrivals and departures in time order. Count work in process by location and status, including exceptions. Reconcile beginning WIP plus arrivals minus departures with ending WIP. Plot cumulative accepted and completed units to expose backlog growth and release waves. Observe whether queues are FIFO, prioritized, or repeatedly resequenced.
Measure complete order lead times and stage waits. Investigate batching and transfer cadence separately from processing times. Check whether throughput is demand-limited or capacity-limited. Before using queue formulas, examine stability, boundary consistency, and whether unfinished work is represented. A daily average can conceal severe peaks before the carrier cutoff.
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.
Demand of 240 orders per 420 minutes is 0.571 orders per minute, while theoretical picking capability is 157.5/420=0.375. If 240 orders enter and only 157.5 equivalent orders can pass the constraint, WIP increases by about 82.5 orders per day in a continuous approximation. Actual daily counts are integers and vary, but the mismatch shows why a stable demand-rate calculation is inappropriate for the current design.
If a redesigned stable flow truly completed 240 daily and its measured average lead time were 99 minutes, expected average WIP would be 0.571×99=56.6 orders. That is a conditional illustration, not a baseline estimate: the 99-minute trace is a single normal-route observation and the current capacity is insufficient for that throughput.
04 · Interpretation and decisions
Interpretation and decisions
Use the conservation equation to check data completeness before interpreting trends. If accepted orders apparently disappear, search for cancellations, reclassification, duplicate records, and missing handovers. Separate legitimate cancellations from completed customer demand. The gap between arrival and departure curves represents accumulation, but explaining it still requires the route and capacity evidence.
A weak application divides one queue count by daily demand and labels the result measured waiting time. A sound application identifies the queue's effective departure rate, variability, and period, and either measures wait directly or labels the calculation as an estimate. Work in process is not automatically harmful; some is needed for normal operation, but uncontrolled accumulation hides delay.
05 · Sound application and adaptations
Sound application and adaptations
Analyze release control and local priorities together. An urgent-order rule can improve one subgroup while repeatedly delaying ordinary orders. Evaluate lead-time distributions for both, not merely overall completion. For parallel branches, account for joining and order completeness: a tote with two of three lines is still unfinished.
For advanced work, combine cumulative-flow views with discrete-event simulation and explicit routing. Test smaller release batches, queue limits, and replenishment scheduling as operating scenarios. Ensure the model preserves the conservation of orders and the resources they consume. Verify the proposed flow under realistic variation; a smooth average-rate diagram can conceal a fragile system.
06 · 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.
07 · 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.