Value Stream Mapping: How to See Waste, Lead Time, and Flow Before You Fix Them

What a value stream map shows

A value stream map captures four types of information on a single page: process boxes (each step that transforms the product), inventory triangles (WIP and finished goods buffers between steps), information flows (the scheduling and ordering signals that tell each process what to produce), and a timeline at the bottom that separates value-added time from non-value-added time across the full lead time.

Process boxes contain the key data for each step: cycle time (how long it takes to process one unit), changeover time (time to switch between products), uptime or availability (what percentage of scheduled time the process is actually running), and the number of operators. These data points come from direct observation on the shop floor, not from ERP records, which often reflect planned rather than actual times.

Inventory triangles show the quantity of WIP or stock sitting between each pair of processes. Converting inventory to days of demand (inventory quantity ÷ daily demand rate) allows the map to show not just that inventory exists but how many days of lead time it represents.

The information flow arrows show whether each process is scheduled by push (a central MRP or scheduling system pushes work orders regardless of downstream readiness) or by pull (a kanban or similar signal from the downstream process authorizes production). Push flows are shown with straight arrows; pull flows with looped arrows. Most current-state maps are predominantly push; most future-state maps shift some of that to pull.

The timeline at the bottom of the map alternates between process time (value-added time at each step) and wait time (time sitting in inventory between steps). The sum of process times is the value-added time. The sum of all time, process plus waits, is the total lead time. The ratio is the process cycle efficiency (PCE): PCE = value-added time ÷ total lead time. A PCE of 2 to 5 percent is typical for batch manufacturing; 10 to 20 percent is achievable with focused lean improvement; world-class operations approach 50 percent or higher.

How to draw a current-state map

VSM is a team activity done by walking the actual value stream from customer back to supplier, in the direction material flows, but starting the observation from the customer end. Walking backward from customer to supplier ensures you see what demand the customer actually places, not what the schedule says it should be.

Start with the customer box (top right): document demand rate, order frequency, and packaging requirements. Then walk each process step from shipping back to receiving, collecting cycle time, changeover time, uptime, and WIP quantities by direct observation and count. Record the information flow, how each process receives its work authorization, whether from MRP, a supervisor, a kanban signal, or a production schedule posted on a board.

Draw the map the same day the data is collected. Memory degrades fast, and waiting to draw creates the temptation to clean up the data rather than show what was actually seen. The current-state map should be an honest picture of today, including the overtime, the workarounds, and the inventory that everyone knows is too high but accepts as normal.

The eight wastes

Lean identifies eight categories of waste (non-value-added activity) that VSM makes visible. The original Toyota Production System identified seven; the eighth (unused talent) was added in Western lean practice.

Transportation: moving material that does not need to move. Every move of WIP between buildings, floors, or locations adds lead time without adding value. The map shows each transport leg as a push arrow or a move icon.

Inventory: any stock beyond the minimum needed to maintain flow. Inventory between process steps appears as triangles on the map. High inventory is both a waste and a signal that something upstream is producing faster than something downstream can absorb, often a push scheduling problem.

Motion: unnecessary movement of people within a process. A worker who walks to a distant tool cabinet, turns repeatedly to access parts on the wrong side, or reaches into a poorly designed bin is experiencing motion waste. VSM at the process level (a process-level map or spaghetti diagram) makes this visible.

Waiting: people or machines idle because a preceding step has not delivered. Every inventory triangle on the VSM timeline represents waiting. Waiting is the dominant waste in most supply chains, the gap between value-added time and total lead time is almost entirely composed of waiting.

Overproduction: producing more than the downstream process needs, or producing earlier than needed. Overproduction is the most serious waste in lean thinking because it generates all other wastes: it creates inventory (transportation, storage), hides defects (a large batch of bad parts is harder to detect and stop than a small one), and masks capacity imbalances.

Over-processing: doing more work on a product than the customer requires. Extra inspection steps, unnecessary surface finishes, tolerances tighter than the customer needs, reports no one reads. VSM process boxes with disproportionately long cycle times relative to their value-added contribution are candidates for over-processing review.

Defects: production of units that must be reworked or scrapped. Defects consume process capacity without producing saleable output. They are often invisible on a standard VSM unless rework loops are explicitly mapped as separate process boxes.

Unused talent: not using the knowledge, skills, and ideas of the people doing the work. A VSM improvement project that is designed by engineers and consultants without involving operators typically misses the most actionable improvements, which operators already know about but have never been asked.

Drawing the future-state map

The future-state map is not an aspiration, it is a specific, achievable design for how the value stream should operate, typically targeting a 6 to 18 month implementation horizon. It is drawn on a separate sheet, using the current-state map as the baseline, and answers eight design questions:

What is the takt time? Takt time = available production time ÷ customer demand rate. This sets the pace the value stream must match. See the Production Planning and Scheduling post for how takt relates to capacity planning.

Where will you build to a finished goods supermarket versus build to order? Items with stable, predictable demand can be held in a finished goods supermarket and replenished by pull. Items with highly variable or custom demand are better built to order from a raw material or semi-finished buffer.

Where is the pacemaker process? The pacemaker is the single process in the value stream that receives the production schedule, all other processes operate in response to the pacemaker, either pushing material to it from upstream or pulling authorization from it downstream. Moving the pacemaker as far downstream (close to the customer) as possible reduces the amount of the supply chain that is forecast-driven.

How will you level the production mix and volume? Heijunka (production leveling) distributes product mix and volume evenly across the schedule rather than batching by product type. Leveled production reduces WIP and makes the supply rate predictable for upstream processes.

What process improvements are required to achieve the future state? The gap between the current-state cycle times and the takt time requirement identifies where capacity must be freed. The inventory buffers on the current-state map that exceed the kanban sizing calculation identify where excess inventory can be reduced.

Kaizen bursts are drawn on the future-state map at the points where improvement is needed, they are starburst symbols that mark where a focused improvement project must occur to close the gap between current and future state.

VSM for supply chains beyond the factory

VSM originated in manufacturing but applies directly to any value stream with sequential processes, queues, and information flows, including distribution, procurement, order management, and service delivery. A procurement VSM might map the flow from purchase requisition through supplier selection, PO issuance, goods receipt, and invoice processing, showing wait times at each approval step and the information flows that trigger each action. The principles are identical: find the ratio of value-added to total lead time, identify where waiting and inventory dominate, and design a future state that eliminates or reduces those buffers.

Common mistakes

• Mapping too broad a scope. A VSM for a product family is actionable. A VSM for an entire factory, or for a supply chain spanning multiple tiers of suppliers, becomes too complex to use as a planning tool. Start with one product family, a group of products that share the same major process steps, and map that flow end to end.
• Skipping the information flow. The material flow arrows are the easy part of a VSM. The information flow, how each process knows what to produce, is harder to map but often more important. Most overproduction and inventory accumulation problems trace back to information flow design: the wrong scheduling system, the wrong signal frequency, or a push system where a pull system would work.
• Drawing the future state before understanding the current state. Teams that jump to the future state before thoroughly understanding the current state design improvements based on assumptions rather than facts. Spend at least as long on the current-state map as on the future-state design.
• Creating a future-state map without an implementation plan. A future-state map that is drawn, reviewed, and filed is a completed exercise, not a completed improvement. The future-state map should come with a specific implementation plan: which kaizen projects, who owns each, and by when. Without implementation, VSM is an expensive form of documentation.

Frequently asked questions

What is value stream mapping and why is it used?

Value stream mapping (VSM) is a lean planning tool that draws the complete flow of material and information required to deliver a product from raw material to customer on a single diagram. It shows every process step, every inventory buffer, and the time each takes, distinguishing value-added time (when the product is actually being transformed) from non-value-added time (when it is waiting, moving, or being inspected). VSM is used to make the ratio of value-added time to total lead time visible, to identify where waste is concentrated, and to design a future state with less inventory, shorter lead times, and fewer non-value-added steps.

What is process cycle efficiency (PCE) in VSM?

Process cycle efficiency (PCE) is the ratio of value-added time to total lead time in a value stream: PCE = value-added time ÷ total lead time. A PCE of 2 to 5 percent is typical for batch manufacturing, meaning 95 to 98 percent of the time a product spends in the factory is non-value-added (waiting, moving, being counted). A PCE of 10 to 20 percent is achievable with focused lean improvement. The PCE calculation uses the VSM timeline: add up all the process times (value-added) and all the wait times between processes (non-value-added) to calculate the ratio.

What is the difference between current-state and future-state VSM?

The current-state map documents how the value stream actually operates today, collected from direct observation on the floor, not from ERP records or standard work documentation. It shows where WIP accumulates, where push scheduling creates overproduction, and where the total lead time is dominated by waiting rather than processing. The future-state map is a specific design for how the value stream should operate within a defined improvement horizon (typically 6 to 18 months), answering design questions about takt time, pacemaker process, pull system design, and production leveling. Kaizen bursts on the future-state map mark where improvement projects must occur to close the gap.

What are the eight wastes in lean?

The eight wastes (sometimes remembered as TIMWOODU or DOWNTIME) are: Transportation (moving material unnecessarily), Inventory (stock beyond what is needed to maintain flow), Motion (unnecessary movement of people within a process), Waiting (people or machines idle because a preceding step has not delivered), Overproduction (producing more or earlier than needed), Over-processing (doing more work than the customer requires), Defects (units that must be reworked or scrapped), and Unused talent (not using the knowledge and ideas of the people doing the work). VSM makes Transportation, Inventory, Waiting, and Overproduction directly visible on the map. The others require deeper analysis at the process level.

What is a pacemaker process in VSM?

The pacemaker process is the single step in the value stream that receives the production schedule, the heartbeat of the flow. All processes upstream of the pacemaker respond to its pull; all processes downstream of the pacemaker are directly connected to customer demand. In a future-state design, placing the pacemaker as far downstream as possible (close to the customer) minimizes the forecast-driven portion of the supply chain and reduces the risk of overproduction in response to inaccurate forecasts. Upstream of the pacemaker, production is typically controlled by kanban supermarkets.

Can VSM be applied outside of manufacturing?

Yes. VSM applies to any process with sequential steps, queues, and information flows, including procurement, order management, distribution, healthcare, financial services, and software development. The principles are identical: map the flow from trigger (customer order, purchase requisition, patient admission) to completion, measure cycle time and wait time at each step, calculate the ratio of value-added to total lead time, identify where waiting and rework dominate, and design a future state that reduces those wastes. In service and administrative processes, the dominant waste is almost always waiting at approval steps or handoffs between departments.