01 · Mechanics and boundaries
Mechanics and boundaries
Process analysis is the disciplined examination of an operating system rather than a single drawing technique. It integrates sequence, time, movement, quality, capacity, and decision rules to explain why the system produces its observed results. Start with a question such as why orders miss the carrier cutoff, not with a preferred tool or a request to make every activity faster.
The unit of analysis matters. An order experiences elapsed time; a worker expends labor time; a station has capacity; a warehouse has throughput. Those quantities interact but are not interchangeable. A process can contain fast individual activities and still be slow because queues, synchronization, and rework dominate the customer experience.
02 · Construct the analysis
Construct the analysis
Set the boundary, family, outcome, and comparison period. Walk the actual route with workers and record normal and exception paths. Build a sequence map before adding quantitative layers. Measure processing, waiting, movement, quality escapes, and resource constraints with explicit definitions. Test whether totals reconcile with complete order traces.
Form competing explanations. Insufficient capacity predicts persistent queues at the constrained stage; batching predicts waves of work and alternating starvation and overload; stock holds predict interrupted routes. Compare those predictions with observations. Use targeted tools for the unresolved question: a swimlane map for handovers, spaghetti diagram for distance, and stratification for differences between conditions.
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 trace contains 20 processing minutes and 79 waiting minutes, giving 99 minutes elapsed. Picking needs 240×8=1,920 labor minutes per day, while three pickers supply only 1,260 net minutes. That 660-minute theoretical deficit cannot be repaired solely by moving a label printer. Packing requires 1,200 labor minutes against 1,260 available, leaving little nominal margin.
Meanwhile, the 100-order sample shows replenishment holds in 12 orders, with 8 late. This suggests an interruption mechanism in addition to the structural capacity issue. A dispatch analyst should investigate both. Adding picking capacity might reduce the persistent queue but leave stock exceptions unresolved; fixing replenishment might reduce interruptions but still leave the 1,920-minute workload.
04 · Interpretation and decisions
Interpretation and decisions
Separate demand balancing, task redesign, and interruption reduction. A proposed shorter pick route changes task time; cross-training changes resource availability; earlier replenishment changes interruption exposure. Estimate each mechanism independently before combining them. If a redesign proposes a six-minute pick time, four pickers would theoretically supply 280 orders per day, but effective output still depends on availability and mix.
A weak analysis produces a long list of wastes with no explanation of the outcome. A sound analysis reconciles the order trace, resource arithmetic, and exception evidence, then identifies which hypothesis each countermeasure addresses. It also checks whether a local change shifts delay into packing or loading.
05 · Sound application and adaptations
Sound application and adaptations
Use nested boundaries to move from the value stream to a problem stage and back again. Map a pick subcycle in detail without losing sight of handover performance. For variable demand, study time-of-day arrivals, shared resources, and the cutoff rather than relying only on a daily average.
Complex systems may require queueing models or simulation, but those models need validated routing and service-time data. Sophisticated modeling cannot rescue an incorrect map. Document what the current explanation cannot account for and what new evidence would resolve it. The final analysis should let another person reproduce the reasoning from the observations, not merely agree with the analyst's experience.
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.