1. Method Name

Value Stream Mapping (VSM) / Value Stream Mapping

2. Alternative Names

Mapping Material and Information Flows

3. Brief Description

VSM is a Lean management tool used to visualize, analyze, and improve all steps—both value-adding and non-value-adding—required to deliver a product or service to the customer. It depicts not only the flow of materials but also the flow of information.

4. Purpose / When to Use

It is used to gain an overall view of the process (“from a helicopter perspective”), identify waste (particularly overproduction, waiting, and unnecessary inventory), and define future, leaner processes. It is a strategic tool that helps determine where to focus improvement activities (Kaizen).

5. Procedure / How to Apply It

1. Select a product family: Choose a group of products that go through similar process steps.
2. Create a Current State Map:
a. Take a Gemba Walk: Collect data on-site, starting at the end of the process (the customer) and moving toward the beginning (the supplier).
b. Map the information flow: How does the customer place an order? How is production planned?
c. Map the material flow: Map all process steps, from material receipt to shipping.
d. Record data: For each step, identify key metrics (cycle time C/T, changeover time C/O, number of operators, batch size, defect rate).
e. Create a timeline: At the bottom of the map, distinguish between value-adding time (Process Time – P/T) and non-value-adding time (Lead Time – L/T).
3. Analyze the current state: Identify the main sources of waste in the map and mark “Kaizen bursts” (quick improvements) indicating opportunities for improvement.
4. Design a Future State Map:
a. What should the process look like to be leaner? Consider the following questions: How can you create a smooth flow? Where should you implement a pull system (Kanban)? How can you level production (Heijunka)?
b. Sketch out an ideal but achievable state (typically within a 6- to 12-month timeframe).
5. Create and implement an action plan: Define the specific steps and projects (Kaizen events) needed to transition from the current state to the future state. Monitor the implementation process.

6. A Real-World Example

A furniture manufacturer was facing long lead times (8 weeks). The team created a VSM for the main product family (chairs). The current state map showed that the total value-added time (cutting, welding, painting, assembly) was only 4 hours, but the total lead time was 42 days. A huge amount of time was lost waiting between operations in the form of inventory. The team designed a future state by linking operations into a continuous flow, implementing a Kanban system between the paint shop and assembly, and reducing batch sizes. The action plan led to a reduction in lead time to 10 days.

7. Benefits

- Visibility of the entire flow: Helps you see the “big picture,” not just individual trees (processes).
- Identification of sources of waste: Highlights problems that remain hidden when looking at individual departments.
- Common language: Provides a shared view of reality for everyone (production, logistics, planning, management).
- Strategic tool: Helps prioritize improvement activities so they have the greatest possible impact on the entire value stream.

8. Risks / Limits

- "Mapping for the sake of mapping": The team spends weeks creating the perfect map but never moves on to implementing the improvements.
- Excessive complexity: The effort to map every detail can lead to a confusing and unusable map.
- Missing data from the Gemba: Using estimates or data from a system instead of actual observations leads to incorrect conclusions.
- Focusing only on manufacturing: VSM is an equally powerful tool in administration, services, healthcare, or software development, but it is often mistakenly limited to manufacturing.

9. Practical Tips

- Start with paper and pencil: Draw the first version of the map by hand together with your team. It’s faster and promotes collaboration. Only transfer the final version to software (e.g., Visio).
- Focus on a single specific product or part: Don’t try to track everything at once. Track the “life cycle” of a single product from start to finish.
- Calculate flow efficiency: Calculate the ratio of value-adding time to total elapsed time (V/T). This metric (often less than 1%) is a strong argument for change.
- The future state map is not a fantasy: It must be realistic and achievable within a reasonable time frame.