Value Stream Mapping

Value stream mapping differs from standard process mapping in several ways:

• Scope: A value stream map typically encompasses the entire fulfillment path for one product family rather than an isolated departmental procedure. A product family consists of items that pass through similar downstream processing steps and share common equipment.
• Single-sheet constraint: The entire end-to-end stream is documented on a single sheet of paper or whiteboard to ensure all stakeholders view system-level interactions simultaneously. Practitioners often start with a Blank map template (PPTX) or use a digital Value stream map builder for long-term documentation.
• Integrated flows: The map explicitly displays the dual relationship between material movement and information scheduling, showing how production control triggers each process.
• Quantitative timeline: The bottom of the map quantifies both production lead time and active processing time, directly establishing the flow efficiency of the system.

For step-by-step drafting instructions, see the guide on how to Draw a map, scene by scene.

The whole plant as four process boxes and the stores between them.

Open the simulation on this term →

To convert physical inventory counts into equivalent days of lead time, divide the quantity of units in a buffer by the average daily customer demand. For an in-depth explanation of these metrics, review the guide on Cycle, takt and lead time.

Consider a manufacturing plant producing steel brackets:

• The customer demands 18,400 brackets over 20 working days per month, yielding an average daily demand of 920 units.
• Available operating time is two 8-hour shifts per day, totaling 16 hours or 57,600 gross seconds. Subtracting one 20-minute break in each shift yields 55,200 net available seconds per working day.
• Dividing 55,200 available seconds by 920 units gives a takt time of exactly 60 seconds per piece.

The bracket passes through four sequential processes: stamping, welding, assembly, and packaging. Direct measurements recorded during a floor walkthrough show the following inventory buffers and active processing times:

• Raw material storage holds 5,520 pieces of raw coil stock, which equals 6 days of supply at 920 pieces per day.
• Stamping operates with a cycle time of 12 seconds per piece and a changeover time of 45 minutes. Stamped work-in-process storage holds 4,600 pieces, which equals 5 days of supply.
• Welding operates with a cycle time of 24 seconds per piece. Welded work-in-process storage holds 2,760 pieces, which equals 3 days of supply.
• Assembly operates with a cycle time of 62 seconds per piece.
• Packaging operates with a cycle time of 6 seconds per piece. Finished goods storage holds 1,840 completed brackets, which equals 2 days of supply.

Summing the inventory storage times across the timeline layer yields total lead time: 6 days in raw materials, plus 5 days after stamping, plus 3 days after welding, plus 2 days in finished goods, for a total lead time of 16 working days. Over those 16 days, the total work-in-process across the facility stands at 14,720 units.

Summing the active processing times across all four operational steps yields total processing time: 12 seconds in stamping, plus 24 seconds in welding, plus 62 seconds in assembly, plus 6 seconds in packaging, for a total work time of 104 seconds.

To calculate flow efficiency, convert total lead time into seconds. Operating 16 working days is equivalent to 883,200 seconds of plant operating time (16 multiplied by 55,200). Dividing 104 seconds of active processing time by 883,200 seconds of total lead time, and multiplying by 100, yields a flow efficiency of 0.012%.

This ratio demonstrates that a part receives active processing for only one out of every 8,492 seconds it spends inside the facility. The remaining time is spent waiting in stationary inventory batches. The reasons why large production lots create these extended queues are examined in the guide on Why batches stretch lead time.

Mapping these streams requires two key methodological adaptations:

1. Redefining units of work: Items in process are tracked as discrete claims, tickets, orders, or patient visits rather than physical parts.
2. Accounting for knowledge work variability: Information tasks often exhibit wide variance in processing duration, requiring practitioners to measure both median task time and total queue delay between handoffs.

In the financial and insurance sectors, teams apply these methods to eliminate handoff delays and reduce policy underwriting or claims settlement durations. Specific approaches for these environments are detailed in the guide on Mapping a claims stream. For example, an insurance claims review process might require 2 hours of active analysis spread across an 11-day overall processing window (equivalent to 88 operating hours), resulting in a flow efficiency of 2.3%.

In clinical healthcare systems, value stream maps follow the patient pathway through triage, diagnostics, clinical review, and discharge to reduce emergency department crowding and surgical prep delays. Practical healthcare applications are covered in the guide on Mapping a hospital stream.

How does value stream mapping differ from standard process mapping?

Value stream mapping evaluates the end-to-end fulfillment path of an entire product family rather than an isolated departmental procedure. It captures both physical material handling and the information flows that schedule production together on a single sheet. Unlike standard flowcharts, a value stream map also includes a timeline along the bottom that measures production lead time against active processing time.

What are the core structural layers shown on a value stream map?

A standard value stream map integrates three horizontal sections: an information layer, a material layer, and a timeline layer. The information layer across the top displays how customer demand and production control schedule internal steps and suppliers. The material layer across the middle documents operational steps, process data boxes, and inventory buffers, while the bottom timeline compares waiting times against active processing times.

How is flow efficiency calculated on a value stream map?

Flow efficiency is calculated by dividing total active processing time by total production lead time and multiplying by 100. Both measures must use the same unit of time, which requires converting inventory buffer quantities into net operating seconds based on daily customer demand. The resulting percentage reveals how much of the total lead time is spent actively adding value versus waiting in storage queues.

Why do mapping teams walk the process pathway in reverse when gathering data?

Practitioners walk the gemba backward from the shipping dock toward receiving to view the operational sequence from the perspective of the customer. Moving upstream reveals how downstream operations pull work from preceding stations rather than how parts are pushed through. This orientation helps the team observe actual inventory accumulation, batch sizes, and scheduling disconnects at each handover point.

How is value stream mapping applied to service and administrative processes?

In transactional environments, the material layer is adapted to track the flow of digital files, requests, or paperwork, while physical inventory is replaced by queues like shared inboxes and backlogs. Items in process are measured as discrete units such as claims, tickets, or patient visits rather than manufactured parts. Because knowledge work duration varies, practitioners record both median task times and waiting durations between handoffs.