Value Stream Mapping

VSM emerged from the Toyota Production System (TPS), developed across the 1950s through the 1970s under engineers Taiichi Ohno and Shigeo Shingo. Toyota’s internal methodology included a practice called “material and information flow mapping” — a systematic visual technique for documenting how product moved through a factory and how decisions drove that movement[fn]Learning to See; Lean Enterprise Institute[/fn]. The approach was not proprietary to any single Toyota facility — it reflected a systemic philosophy that waste elimination requires whole-system visibility before any component-level intervention.

Shook became Toyota’s first American manager in Japan and subsequently its senior American manager at the Toyota Supplier Support Center in Lexington, Kentucky, helping North American companies adopt the TPS. In 1998, he partnered with Mike Rother of the University of Michigan — who had introduced the concept of Toyota Kata and continuous improvement coaching — to document Toyota’s mapping methodology in written, teachable form for the first time. Their workbook, Learning to See, published plain-language guidance supported by detailed technical drawings and a case study following the fictional Acme Stamping Company through a full current-state to future-state mapping cycle.

The title Learning to See is not incidental. Rother and Shook’s central argument is that VSM is not primarily a documentation technique — it is a perceptual discipline. Practitioners who draw value stream maps learn to see the shop floor, office or service operation “in a way that supports lean” — recognizing waste, flow interruptions and information disconnects that are invisible without the map’s systematic perspective.

The Two Pillars: Material Flow and Information Flow

VSM’s distinctive analytical contribution is its simultaneous mapping of two flows that most process documentation treats independently: the material flow — how product or service work physically moves through the process — and the information flow — how decisions, instructions and schedules drive that movement.

Most process improvement efforts focus on material flow. They identify where bottlenecks slow throughput, where buffers accumulate excess inventory and where steps take longer than their designed standard. These are the visible symptoms of process dysfunction. VSM identifies them, but it goes further. The information flow maps how production orders, forecasts, schedules and customer signals move from the customer back through the organization to the supplier. When information flow is misaligned — when a production system responds to internal schedules rather than actual customer demand — it generates the overproduction, waiting and excess inventory that appear as waste in the material flow, regardless of how efficiently each individual process step executes.

Toyota’s principle of “seeing both flows simultaneously” is what distinguishes VSM from conventional process mapping. A process flowchart shows steps and their sequence. A value stream map shows steps, their sequence, the time and inventory between them, the information triggers that drive each step and the metrics that characterize the performance of each process box — cycle time, changeover time, uptime and operator requirements. This density of operational data, organized into a single visual, is what enables the design of a future state rather than merely the documentation of a current one.

The Current State Map

The current state map is the starting point for every VSM engagement. It documents the value stream as it actually operates — not as it was designed to operate, not as it appears in standard operating procedures (SOPs), but as it functions in current, observed practice. Rother and Shook are explicit:

the current state map must be built through direct observation at the process level, walking the value stream from the shipping dock back to the raw material supplier — never from behind a desk or from existing documentation

The current state map captures seven categories of data for each process step: the process name and description, the number of operators, machine cycle time, changeover time, uptime or reliability rate and the inventory count upstream and downstream of each step. Combined, these data points reveal the total production lead time — the time from raw material to finished product — and the value-added time — the time within that lead time during which work that changes the product is actually occurring. The ratio of value-added time to total lead time is, for most organizations encountering VSM for the first time, a confronting number — typically below 10 percent in manufacturing contexts and often below 5 percent in service operations.

The Future State Map and Takt Time

The future state map is not an aspiration — it is a design. Rother and Shook provide specific design questions that the future state map must answer before it can be considered complete. These questions begin with takt time: the rate of customer demand expressed as available production time divided by units required per period. Takt time is the heartbeat of the future state. Every process in the future state should be designed to produce at takt time — no faster, which creates overproduction and inventory and no slower, which creates downstream starvation and delivery failure.

The future state map then addresses where to establish continuous flow — the elimination of inventory and waiting between sequential process steps — and where pull systems are required at points where continuous flow is not yet achievable. It identifies a single pacemaker process: the one point in the value stream where production is scheduled and from which the entire upstream value stream is pulled. The future state map converts these design decisions into a visual target — specific enough to drive a concrete implementation plan, but flexible enough to accommodate the iterative improvement that VSM treats as continuous rather than episodic.

The Value Stream Manager

Rother and Shook introduce a role that most organizations lack before their first VSM engagement: the Value Stream Manager. This person holds accountability for the value stream as an end-to-end system — not for the performance of individual processes within it. This role distinction is structurally important. Most organizations are managed vertically — functional leaders are accountable for their own departments. Value streams run horizontally, crossing departmental boundaries. Without a value stream owner who can make trade-off decisions across those boundaries, improvements in one department routinely create new bottlenecks in the next and the system-level gains that VSM identifies remain unrealized.

The Value Stream Manager is responsible for both the current state map and the future state map and for the implementation plan that connects them. Rother and Shook structure this plan as a series of “loops” — segments of the value stream that can be improved in sequence, each loop improving the conditions for the next. This sequencing discipline prevents the common lean implementation failure mode: organizations that attempt to implement all future-state improvements simultaneously, overwhelming their change capacity and producing partial, unstable results.

VSM in Service, Healthcare and Technology

VSM originated in manufacturing but the methodology’s underlying logic — map the full flow from customer demand to value delivery, measure waste in that flow and design a future state that reduces it — applies to any process with identifiable steps, measurable time and a definable customer. Applications in healthcare, professional services and information technology are now well-documented.

In healthcare, a 2021 systematic review published in PMC examined VSM applications across healthcare service settings. The review confirmed that VSM effectively identifies waste in clinical and administrative processes — including waiting times, unnecessary patient handoffs and redundant documentation steps — and that it provides a structured platform for designing future-state improvements in patient flow and care delivery. Emergency department throughput, surgical scheduling, discharge planning and pharmaceutical supply chains have all been mapped and improved using VSM methodology in documented clinical settings.

In information technology (IT), VSM has become a foundational tool in Value Stream Management — the extension of lean principles to software development and delivery pipelines. ITSM Group[fn]Increasing the Business Value of IT Through Value Stream Mapping[/fn] documents VSM’s direct application to IT value chains:

Value Stream Mapping analyzes the steps from customer need to value delivery… in IT, throughput and waiting times as well as cycle time are indicators of efficiency

The application maps software development cycles, identifies stages where code sits waiting for testing, review or deployment and designs future states with reduced lead times and higher deployment frequency. SAFe (Scaled Agile Framework) incorporates value stream identification as a fundamental organizational design principle, using VSM logic to align organizational structure with actual delivery flows rather than inherited functional hierarchies.

A 2024 study in Production Planning and Control integrated sustainability metrics into VSM, developing an approach that adds environmental data — energy consumption, emissions and material waste — alongside the traditional time and inventory metrics. This extension, which the authors validate against a manufacturing case study, reflects VSM’s adaptability to the evolving demands of environmental, social and governance (ESG) performance reporting — where the same systematic whole-system visualization that identifies operational waste can also quantify environmental waste.

Deploying VSM Effectively

Organizations deploy VSM most effectively when they treat the mapping exercise as a cross-functional, direct-observation activity — not a desk exercise delegated to a process analyst. Rother and Shook prescribe that the person drawing the map should personally walk the entire value stream, gathering data at each process step through direct observation rather than relying on historical records. This prescription is not ceremonial — direct observation reveals the gap between how a process was designed and how it actually operates, a gap that existing documentation systematically obscures.

The ITSM Group’s implementation guidance for VSM in complex IT environments emphasizes that a successful deployment requires an external facilitator at the outset — not because the methodology is technically inaccessible, but because organizational insiders carry the perceptual blind spots that VSM is designed to overcome. The external perspective creates the conditions under which current-state waste becomes legible to the people closest to it. Once legible, it becomes motivating — teams that see, in a single page, the ratio of value-added time to total lead time rarely need to be persuaded that improvement is necessary. The map makes the case more effectively than any management presentation.