Customer Value, Waste, and the Value Stream

Value starts with the recipient

If you make an internal step faster when the customer does not need that step at all, you may simply make waste faster. Lean thinking starts by asking what outcome the recipient values and which activities transform an input into that outcome. The “customer” may be an external buyer, an internal user, or the recipient of a process output. The important point is not to confuse what we have always done with what actually creates value.

Three useful categories when examining a step are: (1) value-adding — it changes the output in a way the recipient needs and is done correctly; (2) non-value-adding but currently necessary — for example, some safety, compliance, or enabling controls; and (3) waste — it adds no value and is not necessary, such as entering the same data twice without a reason. The classification is a questioning tool, not a permanent label; it can change when the process design or requirements change.

Waste appears in time, movement, and information too

Waste is not limited to damaged material. In services and offices it may appear as a request waiting for days, a file handed from person to person without need, work started before capacity exists to process it and therefore accumulating, a report containing details no one uses, or repeated correction after incorrect entry. Waste categories help observation, but the objective is not memorizing a list; it is seeing where the system consumes time and effort without improving the output.

The value stream: look from end to end

The value stream is the activities and information needed to move a product or service from request to delivery. The end-to-end view matters because the largest opportunity may sit between departments rather than inside one step. A fast department can send large batches to a slower one, making the first department look productive while work accumulates across the whole system. Measuring each department in isolation is therefore insufficient; we need to see waiting, handoffs, rework, and information flow across the process.

Reading the map above: submit request — starts the flow; data check — currently necessary if it prevents unusable inputs; duplicate entry — strong waste candidate; wait for meeting — non-value-adding waiting; make decision — necessary for the output; send result — completes delivery. This is an initial reading that must be confirmed in the actual process, not an automatic judgment for every similar process.

When drawing a simple value stream, record what actually happens rather than only what the written procedure says should happen. Ask: how long does a case wait before each step, how often does it move backward, how many cases are teams working on at once, and where does missing information create correction? Even before using a formal map, these questions expose the difference between active processing time and the time experienced by the customer.

Flow and pull, explored in the next lesson, build on this view. Once we see the whole stream, we can ask how a case can move without unnecessary stopping and when new work should begin in response to real need and capacity rather than being pushed into growing queues.