Value Stream Mapping

Thinking Tools3.3 Mapping the System Around the ProblemAlso known as VSM

Developed by Mike Rother and John Shook (Learning to See, 1999).

Draws the whole flow of material and information from customer order back to raw input, separating time that adds value from waiting, moving, and rework.

A spare-parts order with 40 minutes of work and nine days of waiting

Each box is one step and its hands-on work; the number is the days the order waits before that step starts. The total is the lead time the customer feels. Find the two biggest waits and cut them, as the distributor did, and watch the lead time fall while the 40 minutes of work stays put. Illustrative.

Days waiting before the step

Order entry1.5
Credit check2.5
Pick2.0
Pack1.0
Ship2.0

Lead time, in days9.0

Select a stage to read it, or play the sequence.Order entry. The emailed order waits in a shared inbox that is cleared twice a day, often later. A web form that feeds the system directly would cut most of this wait.Credit check. Every order waits for the one credit analyst, though nine in ten come from accounts in good standing. Approving those automatically takes this wait to zero.Pick. Orders are released to the warehouse in one batch every other morning. Releasing them every hour takes the wait to half a day.Pack. Picked orders sit on a staging rack until the packing team clears the morning's batch.Ship. The carrier collects twice a week. A daily pickup costs more and halves this wait; the team left it for a second pass.
  1. Order entry. The emailed order waits in a shared inbox that is cleared twice a day, often later. A web form that feeds the system directly would cut most of this wait.
  2. Credit check. Every order waits for the one credit analyst, though nine in ten come from accounts in good standing. Approving those automatically takes this wait to zero.
  3. Pick. Orders are released to the warehouse in one batch every other morning. Releasing them every hour takes the wait to half a day.
  4. Pack. Picked orders sit on a staging rack until the packing team clears the morning's batch.
  5. Ship. The carrier collects twice a week. A daily pickup costs more and halves this wait; the team left it for a second pass.

An example

An industrial parts distributor promised next-week delivery on spare parts and kept missing it. Each department had tuned its own step: the warehouse had cut its pick time, and customer service had added a second person to order entry.

The operations manager followed one order from the customer's email to the truck, timing the work and the waiting separately. The work added up to 40 minutes across five steps. The order spent nine days waiting: in a shared inbox, in the queue for the one credit analyst, for the warehouse's every-other-day batch release, on a staging rack before packing, and for a carrier that came twice a week. The future-state map removed the two biggest waits. Accounts in good standing were approved automatically, and orders went to the warehouse every hour. Lead time fell to five days with no change to the 40 minutes of work.

Why it works

Departments measure what they control, which is the time they spend working, so improvement goes into steps that were already quick. The customer feels the lead time, and in most processes the work is a small fraction of it; the rest is the order sitting between steps. Drawing the whole flow on one page, with processing time and waiting time on separate lines, makes that ratio impossible to miss.

The map also shows why the waits exist: batches, queues for a single approver, information that moves on a schedule. Those are design choices, and a future-state map changes them on paper first, so the team can see the lead time it would get before anyone rearranges a warehouse.

The thinking behind it

Mike Rother Mike Rother is a researcher of the Toyota production system who, with John Shook, introduced value stream mapping to Western industry. Their workbook, Learning to See: Value Stream Mapping to Add Value and Eliminate Muda (Lean Enterprise Institute, 1999), taught the mapping of material and information flow through a process. Rother later described the improvement kata and the coaching kata in Toyota Kata (2009).

John Shook John Shook, a lean management author, wrote Learning to See with Mike Rother, the workbook that taught value stream mapping of material and information flow. In Managing to Learn: Using the A3 Management Process (2008) he described Toyota's A3 process, which puts a problem, its analysis, the countermeasures, and the plan on one large sheet of paper, as a way of developing people as well as solving problems.

How to run it

  1. Pick one product family. Choose one line of products or services that share most of their steps, and follow only that.
  2. Walk the flow yourself. Start where the customer's request arrives and follow it step by step to delivery, with a stopwatch and a notebook.
  3. Record work and waiting separately. For each step note the hands-on time, then how long the item waits before the step begins.
  4. Draw the information flow too. Show how each step learns what to do next: a schedule, an email, a batch release.
  5. Total the two timelines. Put the sum of the work beside the lead time, in the same units.
  6. Draw the future state. Remove the largest waits on paper, by smaller batches, automatic approvals, or steps that pull work when ready.
  7. Plan the changes in order. Sequence the moves that get from the current map to the future one, and remap after each.

Where it goes wrong

The map is drawn in a conference room. Memory and the process manual leave out the queues, so the waiting looks small. Walk the floor and time a real order.

The map covers every product. Mixing families with different routes produces an average flow that nobody's order follows. Map one family at a time.

The map is the end of it. Teams admire the current state, frame it, and change nothing. Set a date for the future state and a person for each change before the session ends, and redraw the map once the first changes are in.

When to use something else

  • Theory of Constraints. When one step's capacity limits the whole flow and the question is how to work around that step.
  • Service Blueprint. When the process is a service the customer takes part in, and what they see matters as much as the time.
  • Queueing Theory. When the waits come from variable arrivals at a busy step, and you need to predict how long the line gets.

Where it sits in SOLVE eX

Go to the source

  • Learning to See: Value-Stream Mapping to Add Value and Eliminate Muda, Lean Enterprise Institute, 1999

Back to the catalog