13.2 Value Stream Mapping

Value Stream Mapping in Lean Manufacturing

Concept and Purpose of Value Stream Mapping

Value stream mapping (VSM) is a lean tool that visualizes the entire flow of materials and information required to bring a product or service from raw materials to the customer's hands. It gives you a bird's-eye view of a production process so you can spot waste, bottlenecks, and inefficiencies that aren't obvious when you're only looking at individual steps.

VSM uses standardized symbols to represent different process elements:

• Rectangles for process steps
• Triangles for inventory points
• Solid arrows for material flow
• Dashed or lightning-bolt arrows for information flow

This common visual language makes it much easier for people across departments to look at the same map and have a shared understanding of what's happening.

The primary goals of VSM are to:

• Identify and eliminate waste (muda) in the production process
• Reduce lead times and improve throughput
• Support data-driven decisions by quantifying metrics like cycle time, lead time, and value-added time
• Help teams understand where they are now (current state) and where they want to be (future state)

VSM fits directly into lean principles like continuous improvement and just-in-time production. Rather than guessing where problems are, you map them out with real data.

Applications and Benefits

VSM isn't limited to factory floors. It's used across manufacturing, healthcare, software development, and service industries wherever there's a process that can be mapped and improved.

Key benefits include:

• Shorter lead times and better quality, which directly improve customer satisfaction
• Cost reduction through identifying redundant steps and wasted resources
• Supply chain visibility by mapping relationships with suppliers and customers, not just internal steps
• Employee engagement, since workers closest to the process are involved in observation and improvement
• Compliance support for quality management systems like ISO 9001, because VSM documents and standardizes processes

Current vs. Future State Value Stream Maps

Creating Current State Maps

A current state map captures the process exactly as it exists today, including all the delays, workarounds, and inefficiencies. The goal is an honest picture, not an idealized one.

Here's how you build one:

1. Define the scope. Pick the product family or process you're mapping, from a specific starting point (e.g., raw material receipt) to an endpoint (e.g., shipment to customer).
2. Walk the process (gemba walk). Go to the actual workplace and observe the flow firsthand. Talk to operators and process owners. Don't rely on what a procedure manual says happens; record what actually happens.
3. Map each process step using standard VSM symbols. Record key metrics at each step: cycle time, changeover time, uptime, and number of operators.
4. Map the material flow. Show how physical materials move between steps, including any inventory buffers (represented by triangles with quantities noted).
5. Map the information flow. Show how each step knows what to produce and when. This includes production schedules, electronic signals (like ERP system triggers), and manual communications.
6. Add customer and supplier data. Note the customer's takt time (the rate at which you need to produce to meet demand) and supplier delivery frequency.
7. Draw the timeline. At the bottom of the map, add a stepped timeline showing lead time (total elapsed time) and value-added time (time spent actually transforming the product).

Takt time deserves a quick definition since it shows up constantly in VSM. It's calculated as:

$\text{Takt Time} = \frac{\text{Available Production Time}}{\text{Customer Demand}}$

For example, if you have 480 minutes of production time per day and the customer needs 240 units, your takt time is 2 minutes per unit. Every process step on your map gets compared against this number to find where the flow breaks down.

Developing Future State Maps

The future state map represents what the process should look like after improvements are made. You build it by analyzing the current state map and asking where waste can be removed.

Future state maps typically incorporate lean principles such as:

• Pull systems (producing only what the next step needs, rather than pushing inventory forward)
• Continuous flow (eliminating waiting between steps where possible)
• Load leveling (heijunka) (smoothing out production volume to avoid spikes and idle periods)

The future state map includes target metrics for each process step, such as reduced cycle times or smaller inventory buffers. It may also propose changes to physical layout, equipment, or information systems.

Think of the future state map as a roadmap. It doesn't just show the destination; it highlights exactly which parts of the process need to change and by how much. On the map itself, you'll often see kaizen burst symbols (jagged starbursts) placed at specific steps to flag where improvement actions are needed.

Value-Added vs. Non-Value-Added Activities

Identifying and Categorizing Activities

Every activity in a process falls into one of three categories:

• Value-added (VA): The activity transforms the product or service in a way the customer cares about and would pay for. Example: machining a part to specification, or assembling components into a finished product.
• Non-value-added but necessary (NVA-N): The activity doesn't add customer value but can't be eliminated right now due to regulations, technology limits, or current process design. Example: mandatory quality inspections required by industry standards.
• Pure waste (NVA): The activity adds no value and can be eliminated. Example: moving parts back and forth between distant workstations because of poor layout.

Common forms of pure waste identified through VSM include:

• Excessive inventory sitting between process steps (tying up capital and hiding problems)
• Unnecessary transportation of materials
• Waiting times where nothing is happening to the product
• Overproduction (making more than the customer needs, which is often considered the worst form of waste because it triggers other wastes like excess inventory and transportation)

To quantify efficiency, calculate the value-added ratio:

$\text{Value-Added Ratio} = \frac{\text{Value-Added Time}}{\text{Total Lead Time}} \times 100\%$

For example, if your timeline shows 15 minutes of value-added time across all process steps but a total lead time of 10 days (14,400 minutes), your value-added ratio is about 0.1%. That number makes the improvement opportunity very concrete.

Analyzing and Improving the Activity Mix

Once you've categorized activities, the work shifts to maximizing VA time and shrinking everything else. Several techniques help:

• 5 Whys: Ask "why" repeatedly to drill down to the root cause of a non-value-added activity. If parts are always waiting, why? Because the upstream machine has long changeovers. Why? Because tooling isn't standardized. Keep going until you reach a cause you can act on.
• Fishbone (Ishikawa) diagrams: Map out all possible causes of a problem across categories like materials, methods, machines, and manpower. This helps you avoid jumping to conclusions about a single cause.
• SMED (Single Minute Exchange of Die): A structured method for reducing changeover times, often from hours to under 10 minutes, which directly cuts waiting waste.

You should also analyze the information flow. Delays in scheduling, approvals, or communication between steps often cause as much waste as physical bottlenecks. Visual management tools like kanban boards and andon signals make non-value-added activities more visible so teams can address them quickly.

Always evaluate the value stream from the customer's perspective. If the customer doesn't care about a step, it's a candidate for elimination or reduction.

Improvement Plans from Value Stream Mapping

Developing Targeted Improvement Strategies

The gap between your current state and future state maps is your improvement plan. Turning that gap into action involves a few layers:

Short-term (quick wins):

• Organize kaizen events, which are focused, short-duration workshops (typically 3-5 days) targeting a specific problem identified on the map
• Rearrange workstations to reduce transportation waste
• Implement visual controls like floor markings or shadow boards

Long-term (structural changes):

• Redesign facility layouts to support continuous flow
• Implement pull systems with kanban signals
• Introduce new technologies or automation for repetitive, non-value-added tasks

Every improvement action should have:

• A specific, measurable goal (e.g., reduce lead time from 12 days to 7 days)
• A timeline for implementation
• An assigned owner responsible for execution

Develop standardized work procedures for improved processes. Without standardization, improvements tend to drift back toward old habits.

Implementing and Sustaining Improvements

Making changes stick is often harder than identifying them. A few practices help:

• Change management: Communicate the "why" behind changes clearly. People resist what they don't understand.
• Training: Build employee skills to match the new processes. A pull system won't work if operators don't understand how to respond to kanban signals.
• KPIs (Key Performance Indicators): Track metrics like lead time, inventory levels, and defect rates before and after changes. If you can't measure it, you can't confirm it improved.
• Feedback loops: Regularly gather input from operators and customers. The people doing the work will spot problems with new processes fastest.

Integrate improvements into your existing quality management systems and standard operating procedures so they become the new baseline, not a one-time project.

Finally, update your value stream map regularly. Today's future state becomes tomorrow's current state. Continuous improvement means the mapping cycle repeats: map, analyze, improve, re-map. That ongoing cycle is what separates organizations that sustain gains from those that slide back.