01 · Mechanics and boundaries
Mechanics and boundaries
Value analysis examines whether an activity contributes to the outcome the customer needs. Define that outcome before classifying work. For dispatch, the customer needs the correct items, in usable condition, sent to the correct destination at the promised time. An activity is not value creating merely because it is busy, costly, or mandatory.
Use three classes: value creating, necessary non-value-adding under current conditions, and avoidable non-value-adding. Necessary non-value-adding work may include regulatory records, risk controls, and checks required by the present process design. Recognizing its lack of customer transformation does not authorize removing it. Seek a safer way to meet its purpose.
02 · Construct the analysis
Construct the analysis
Break work into observable elements and record their purpose. Ask whether omitting an element without replacement would reduce the delivered outcome's value. Then ask whether the element remains required by a constraint, control, or current system. Classify with workers and the customer requirement in view. Record disagreements and the assumption underlying each classification.
Separate necessity from efficiency. A required check can still contain redundant data entry, travel, or rechecking. Examine whether its purpose can be built into the operation or satisfied upstream. Compare alternatives by outcome and risk, not by the count of steps deleted. Keep an explicit approval owner for controls governed by a policy or external requirement.
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.
For the normal trace, the team provisionally classifies five minutes of selecting correct items and three minutes of protective packing as value creating: eight minutes total. Of the remaining 12 processing minutes, order release, verification, labels, and loading include necessary work under the current dispatch arrangement. The 79 waiting minutes create no parcel transformation and require investigation of their mechanisms.
This classification is a teaching convention, not a universal verdict that all picking or all packing is value creating. The eight-minute pick activity includes travel and searching; the five-minute packing activity includes handling and labeling. Decomposing the activities prevents entire departments being labeled either valuable or wasteful. With eight value-creating minutes in 99 elapsed minutes, the provisional process cycle efficiency is 8.1%.
04 · Interpretation and decisions
Interpretation and decisions
Prioritize avoidable waits and motions while preserving the correct-order outcome. Replacing duplicate manual label entry with a controlled data transfer may remove work and reduce mismatch risk. Removing the final check without an alternative control could reduce processing time yet increase escaped errors. Evaluate both the classification and the function served.
A weak application calls inspection waste and immediately deletes it. A sound application asks why inspection is currently necessary, what defect prevention would make it unnecessary, and what evidence would establish the replacement's effectiveness. A class is a basis for investigation, not a judgment about the worth of a person's job.
05 · Sound application and adaptations
Sound application and adaptations
Use a function-cost view for complex supporting work: define the required function, compare ways to perform it, and examine their cost and risk. For customer-facing services, value may include reassurance or information, but specify the need rather than assuming every interaction adds value.
Classification is sensitive to boundary and customer perspective. A carrier handover control may be necessary for the warehouse even though it does not alter the parcel. Review changing constraints and retain the rationale for necessary work. Do not invent a universal target percentage; an improvement in the ratio is meaningful only if customer outcomes, accuracy, and working conditions remain acceptable.
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.