Value Stream Mapping Steps

Why This Matters

Value Stream Mapping (VSM) isn't just a flowcharting exercise—it's the diagnostic tool that separates process improvement guesswork from data-driven transformation. You're being tested on your ability to understand how organizations systematically identify waste, quantify inefficiencies, and design leaner workflows. The steps in VSM represent a structured methodology rooted in Lean manufacturing principles, and exam questions will probe whether you understand the logical sequence and purpose behind each phase.

Don't just memorize the steps in order. Know why each step exists, what data it generates, and how it connects to the broader goal of eliminating the eight wastes (TIMWOODS). When you can explain the difference between current state analysis and future state design—or why information flow matters as much as process flow—you're thinking like a process engineer, not just a test-taker.

---

Scoping and Preparation

Before any mapping begins, teams must establish clear boundaries. Without proper scoping, VSM projects expand uncontrollably or focus on the wrong processes entirely.

Define the Product Family or Process to Map

• Scope selection determines project success—choose a process that's strategically important and has measurable inefficiencies
• Product families group items with similar processing steps, allowing you to map representative workflows rather than every variation
• Stakeholder alignment at this stage prevents scope creep and ensures cross-functional buy-in before resources are committed

Identify the Current State

• Baseline documentation captures how work actually flows today, not how procedures say it should flow
• Gemba observation (going to the actual workplace) reveals informal workarounds and tribal knowledge that formal documentation misses
• Frontline involvement is critical—operators and process workers provide ground-truth insights that managers often lack

---

Visual Documentation

The core of VSM is creating standardized visual representations that anyone can interpret. Consistent notation transforms complex workflows into shareable, analyzable artifacts.

Map the Process Flow

• Standardized symbols (process boxes, inventory triangles, push/pull arrows) create a universal language across departments and organizations
• Sequential flow shows the order of activities, decision points, and handoffs between roles or departments
• Simplicity over detail—the map should communicate at a glance; overly complex maps defeat the purpose of visual management

Collect and Add Process Data

• Cycle time, takt time, and changeover time are the core metrics that quantify each process step's performance
• Data collection methods include time studies, system reports, and direct observation—triangulating sources improves accuracy
• Contextual integration means placing data directly on the map (in data boxes beneath process steps) so analysis happens visually

Add Information Flow

• Information triggers action—documenting how orders, schedules, and signals move reveals coordination bottlenecks
• Electronic vs. manual flows are distinguished visually (lightning bolt vs. straight arrow) to highlight automation opportunities
• Misaligned information flow often causes more waste than physical process problems; orders arriving late or inaccurately cascade into delays

---

Quantitative Analysis

Numbers transform observations into actionable insights. Calculating time metrics reveals the gap between value-added work and total elapsed time.

Calculate Lead Time and Process Time

• Lead time measures total elapsed time from process start to finish, including all waiting and delays
• Process time (or value-added time) counts only the moments when the product is actively being transformed
• Process cycle efficiency ($\text{PCE} = \frac{\text{Process Time}}{\text{Lead Time}} \times 100$) quantifies how much of the total time actually adds value—most processes score below 10%

Identify Waste and Improvement Opportunities

• Eight wastes (TIMWOODS)—Transportation, Inventory, Motion, Waiting, Overproduction, Overprocessing, Defects, Skills underutilization—provide a systematic checklist
• Root cause analysis distinguishes symptoms from sources; a delay might stem from upstream overproduction or information flow failures
• Impact prioritization ranks improvement opportunities by effort required versus benefit gained, focusing resources on high-leverage changes

---

Future State Design and Execution

Analysis without action is just expensive documentation. The transition from current state to future state is where VSM delivers actual business value.

Create the Future State Map

• Ideal flow visualization removes identified wastes and shows how the process should operate with implemented improvements
• Pull systems and flow replace batch-and-queue thinking, reducing inventory and wait times between steps
• Strategic alignment ensures the redesigned process supports organizational goals, not just local optimization

Develop an Implementation Plan

• Action items with owners translate map changes into specific tasks, deadlines, and accountable individuals
• Risk mitigation anticipates resistance, resource constraints, and technical challenges before they derail implementation
• Kaizen events (rapid improvement workshops) often execute discrete portions of the plan in focused 3-5 day bursts

Implement Changes and Monitor Progress

• KPI tracking measures whether changes actually improve lead time, quality, and cost—not just whether activities were completed
• PDCA cycles (Plan-Do-Check-Act) structure ongoing refinement as initial implementations reveal new issues
• Sustained improvement requires embedding new practices into standard work; otherwise, processes drift back to old habits

---

Quick Reference Table

---

Self-Check Questions

1. Which two steps both occur before any visual mapping begins, and what distinguishes their purpose?

2. If a company's process cycle efficiency is 5%, what does this tell you about the relationship between lead time and process time—and which VSM step would reveal this?

3. Compare and contrast process flow and information flow: How are they documented differently on a VSM, and what types of waste does each help identify?

4. A team creates an excellent future state map but sees no improvement six months later. Which step did they likely underperform, and what elements should that step have included?

5. You're asked to reduce lead time by 30%. Which three VSM steps would provide the data and analysis needed to identify where that reduction could come from?