What is value in lean? From customer needs to work steps

Why it matters

A protective cover does its job when it fits its mounting point and does not cut the user's hand. What matters to the buyer is not how many workstations the cover passes through or which expensive equipment the manufacturer uses. It is providing the required features, in the required quantity, at the required time. Value in lean manufacturing is defined from this need. Calling every production activity equally valuable confuses work that transforms the product with waiting. To define value, first explain the product's use and acceptance criteria. The purpose of improvement then goes beyond simply making work faster: it becomes reliably providing the result the customer expects with less waste.

A customer need may be stated as a specific dimension, a function or a delivery requirement. These are not all met by the same kind of activity. Forming may make the cover fit the connection. Deburring that creates the required edge condition may contribute to safe use. Inspection checks whether that feature has been achieved; it does not create the feature itself. The fact that inspection does not change the product does not show that it is unnecessary. This distinction prevents the mistake of immediately removing all non-value-added work. Necessary support work and safety measures are maintained while the conditions that make them necessary are examined. The definition of value is the starting point that determines which result the improvement must preserve.

An operation does not automatically add value because it is expensive, keeps a worker busy for a long time or looks important in a production report. Processing to achieve an unwanted extra shine is an example. The operation may be technically successful; yet no claim of value can be made if it does not contribute to an agreed customer need. At the same time, customers cannot be expected to know every technical detail of a product. The manufacturer is responsible for translating the need into a safe, suitable product. Assessment therefore involves more than simply asking the customer whether they want the operation. Conditions of use, the agreed product definition and verified requirements are considered together.

In lean thinking, once value is defined, the product's entire route, the value stream, is examined. Reducing interruptions between tasks supports flow. Starting production in response to the next process's verified need is the basis of pull. Continuous improvement is sustained by monitoring results. These principles are not applied as separate slogans; they are linked to the same customer requirement. A single workstation running faster may not speed delivery by the same amount if the product waits at the next stage. The value-added ratio calculated in this lesson also describes only the defined observation scope. It is not interpreted as plant-wide efficiency, worker performance or a direct financial gain.

Formula

How to do it

1. 1

   Define the product, customer and conditions of use

   Choose a product family and the need this product meets. In the cover example, fitting the connection and having no sharp edges are acceptance criteria. Record delivery time and quantity separately too. Do not confuse the next station's habits with the final need; investigate how a requested intermediate feature contributes to the product. If a technical requirement is unknown, record it as a matter requiring verification rather than assigning a definite class. Listen to why the worker prepares the product this way. Do not judge value from visible movements alone without knowing how the product is used. The definition must be clear enough for another observer to explain which acceptance criterion the same task meets. This definition also provides a shared basis for later speed comparisons.

2. 2

   Fix the start and end boundaries

   Follow the same product from entry into the first operation to the selected exit point. Record the starting condition and the condition for completion. This scope may be part of production; it is not assumed to cover the entire time from order to delivery. Transportation and waiting between tasks are recorded if they fall within the boundary. Do not add work on another product as processing time for the product being followed. Keep human working time separate from the part's elapsed time. When a worker moves to another task while the machine runs, there are two different timelines. This calculation uses the product's timeline. Keep the same boundary for the proposal being compared; moving the endpoint earlier and hiding the remaining work is not a gain.

3. 3

   Ask which feature the activity creates

   Write each row with a concrete verb and add the product feature it provides. If forming creates the connection geometry, show this relationship. If deburring achieves the accepted edge condition right first time, it is value-added work in this example. Another activity with the same name does not automatically enter the same class if it is needed to correct an earlier error. The reason for doing an activity matters as much as its name. Separately question what change inspection, transportation and waiting make to the product. Do not fill in the duration of an unmeasured or invisible section with an estimate. If the reason for classification remains unresolved, state what information is missing; filling the gap with an easy value label does not make the calculation reliable.

4. 4

   Separate necessary support work from loss

   Investigate why each task that does not change the product is performed. Explain how inspection verifies the acceptance criterion and what assurance would be lost if it were removed. Transportation may be necessary in the current layout; this does not mean the layout can never change. Waiting is also examined according to its cause, rather than blamed on the worker. Overproduction at the previous stage or a material supply problem may appear as waiting at the next stage. Verify the reason for an activity considered necessary with the responsible function. Having always done it is not sufficient justification. However, do not remove an inspection or protective arrangement before its necessity is understood. The improvement list must distinguish work proven removable from work that has not yet been explained.

5. 5

   Reconcile the time total and calculate the ratio

   Convert all times to the same unit and count each interval only once. Add value-added work first, then other work; verify that the two totals equal the observed elapsed time. When calculating the ratio, do not use only manual work time as the denominator; use the selected total lead time. Numerator and denominator must refer to the same product and boundary. Round after converting the division result to a percentage. Keep raw times rather than generating a new result by adding rounded intermediate ratios. The figure's segments visualize how the times reconcile. A segment's color does not determine whether work should be removed; the necessity of inspection is assessed independently of its numerical share.

6. 6

   Compare options that preserve the same result

   Develop feasible proposals to reduce waiting, bring material closer safely or remove unnecessary extra processing. State clearly what each proposal changes and what it must preserve. Include any new transportation, preparation or inspection work in the overall comparison. Reconsider a proposal that forces workers to move faster but does not change the cause of the loss. Do not select a time saving before safety and product conformity requirements are met. Distinguish estimated results from measured results. A new total calculated by assuming an interval will become shorter is an expectation before the trial. In the actual trial, follow the product's entire route again to see whether the loss has moved elsewhere.

7. 7

   Measure the trial and record the limits of validity

   Measure the new time with a similar product and working conditions. Check conformity, remaining waiting and safe access together. Do not declare a lasting result from one successful observation. Record the conditions of comparison and the situations that require new measurements. Reject a proposal if the value-added ratio rises while the customer requirement deteriorates. Reducing total time may be useful even if the ratio stays the same; the ratio is not the only measure of success. Assess with the worker whether the practice can be sustained under daily conditions. The decision record must include the reason for the selected change and the question still open. This prevents the next observer from reading the same numbers and assuming a different work scope.

Worked example

When the method misleads

Common mistakes

• Confusing cost with value: Expensive equipment or long processing time does not prove a contribution to customer need; explicitly state the accepted feature provided.
• Deleting inspection: Necessary inspection that does not change the product must not be removed before alternative assurance is verified; a class name alone is not an implementation decision.
• Narrowing the denominator: Excluding waiting from the total and comparing it with the baseline artificially raises the ratio; keep the same boundary and timeline in both cases.
• Generalizing a local result: Do not directly convert a reduction in one part's lead time into shift output or cash savings; measure the relevant outcome separately.
• Counting correction as value: Even if it touches the product, an activity correcting an earlier nonconformity is not right-first-time production; record its reason separately.