01 · Mechanics and boundaries
Mechanics and boundaries
A value-stream map describes the end-to-end flow for a product or service family, including information that authorizes or schedules work. It supports Define by clarifying boundaries and customer needs, Measure by establishing a current state, Analyze by exposing system constraints, and Improve by designing a future state. It is not exclusive to one DMAIC phase.
A current map records the observed operating pattern, while a future map states an intended pattern with assumptions and implementation work. Distinguish operator cycle time, elapsed order lead time, availability, first-pass quality, and queue inventory. A process data box should tell the reader which quantity was measured and for what unit.
02 · Construct the analysis
Construct the analysis
Choose a family with sufficiently similar routes and work content. Establish customer demand, working time, and dispatch requirements. Walk backward from carrier handover to acceptance to see the flow and then document it in the operating direction. Draw process blocks where flow is disconnected rather than drawing every small action. Add inventory and queues between blocks.
Map the information path separately: who releases orders, at what cadence, using what demand signal, and with what override rules. Record processing and availability data with dates and uncertainty. Build a timeline from observed intervals. Where queue counts are converted to time, state throughput and stability assumptions; a snapshot divided by daily demand is an estimate, not a direct observation of an order's wait.
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.
Customer demand is 240 orders over 420 net minutes, giving a demand interval of 1.75 minutes per order. The normal trace totals 99 minutes elapsed and 20 processing minutes. Picking has three parallel resources and an eight-minute activity time, giving a nominal output interval of 8/3=2.67 minutes per order, already slower than demand. Its operator activity time must not be labeled as the whole value-stream lead time.
A proposed future map might level release in small intervals, establish visible queue limits, replenish forward locations before release, and redesign picking. Those proposals need feasibility checks. Lowering the pick activity to six minutes and providing four dedicated pickers would yield a theoretical interval of 1.5 minutes per order. That is a design assumption, not evidence that the future state can sustain demand.
04 · Interpretation and decisions
Interpretation and decisions
Read the map as a connected system. A packing bench may appear efficient while released orders accumulate before picking. Improving packing alone will not increase the system's maximum output when picking remains constrained. Information waves can create queues even if daily average capacity seems sufficient; examine when the work arrives.
A weak map is a flow chart with attractive icons and invented data boxes. A sound map identifies material and information paths, distinguishes measured from estimated time, and makes future-state assumptions visible. Use a map to organize the investigation, then zoom into the problematic stage with more detailed tools.
05 · Sound application and adaptations
Sound application and adaptations
For service operations, substitute cases and requests for physical inventory while retaining routing, authorization, and completion conditions. For mixed families, use separate maps or explicit workload equivalents. In shared-resource environments, capture what other flows consume the same resources; a map of one family cannot assume exclusive availability.
Keep current-state date and future-state target conditions visible. Assess quality, safety, and workload alongside flow, and identify a practical sequence of changes rather than drawing an ideal state without a route to it. Update the current map after a verified change. A mapping workshop is not itself proof of shorter lead time or higher throughput.
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.