Skip to content

Value Stream Mapping

Definition

Value Stream Mapping is a visual diagramming technique that represents all major tasks in a process and explicitly categorizes each as value-added (creates value in the customer's eyes, produces good results, causes no delays), non-value-added (delays, errors, extra steps, waste), or business requirement (necessary for legal, regulatory, safety, or compliance reasons but not customer-valued). The approach begins with a current-state map showing how the process actually flows, then designs a future-state map with waste and delays removed. By making the invisible visible—showing wait times, handoffs, and rework cycles—Value Stream Mapping exposes the gap between ideal and actual process flows.

In the Book

Slides 137-142 define and illustrate Value Stream Mapping. Slide 138 states: "A Value Stream Map (VSM) is a graphic representation of the process being studied. It's used to identify value and lead time." The color-coding system assigns each process step:

  • Value Added (Green): Good results, no mistakes, safe and timely, valued by patient.
  • Non-Value Added (Red): Delays, errors, extra steps, waste.
  • Business Requirement (Yellow): Accreditation, legal compliance, regulatory requirements, safety standards.

Slides 139-141 show current-state and future-state examples from Emergency Department patient registration and triage. The current state maps actual flows with measured lead time and wait periods; the future state removes waiting time and excess steps while preserving value-added and required activities. Slide 148 emphasizes using VSM to "identify waste within the current process" and then designing the ideal "future state."

Why It Matters

Value Stream Mapping translates abstract process thinking into concrete geography. By literally drawing where work sits, waits, and flows, it makes delay visible to people doing the work—not as individual slowness but as system design. The color coding prevents a common error: eliminating business-requirement steps (like safety checks or compliance documentation) that must remain. The future-state design then forces explicit trade-off conversation: removing a delay means either redesigning the step, relocating it, or accepting longer overall time. This method is exportable to any repeatable process: software delivery pipelines, loan approvals, manufacturing, content publishing—wherever value flows through sequential steps and waste accumulates in invisible queues.