LeanActivity.

Value Stream Mapping

Also known as: VSM · Value stream mapLean Glossary · Tools & Methods

Definition

Value stream mapping (VSM) is a Lean method for drawing all the steps, material flows and information flows needed to deliver a product or service to the customer. The map shows where time is spent waiting and where waste occurs, and it is the basis for a future-state plan.

What value stream mapping is

Value stream mapping grew out of the material and information flow diagrams used at Toyota and became widely known through the book Learning to See by Mike Rother and John Shook. A value stream is every step, value-adding or not, that turns a customer order into a delivered product.

Unlike a simple process map, a VSM shows the material flow and the information flow together and adds data: cycle times, changeover times, stock levels and the total lead time. It is drawn for one product family, usually from the customer back to the suppliers.

Common VSM symbols

  • Process box: one process step, with a data box below it for cycle time, changeover time, uptime and number of operators.
  • Inventory triangle: stock waiting between steps, with the quantity or the days of stock.
  • Push arrow: material pushed to the next step whether it is needed or not.
  • Supermarket and pull arrow: a controlled stock that is replenished by Kanban.
  • Information flow: lines from production planning to the processes, manual or electronic.
  • Timeline: the stepped line at the bottom that adds up waiting time and processing time.

How to create a value stream map

  1. Choose a product familyPick products that go through similar steps and serve the same customer demand.
  2. Walk the processGo to the Gemba and follow the flow, collecting real data instead of system values.
  3. Draw the current stateDraw the customer, the processes, the stock, the information flow and the timeline, by hand and with the team.
  4. Calculate the lead timeConvert stock into days of demand, add the processing time of each step and compare the two.
  5. Design the future stateApply takt, flow and pull: where can steps be connected, where is a supermarket needed, which process sets the pace?
  6. Make an action planTurn the gap between current and future state into concrete Kaizen projects with owners and dates.

Example and common pitfalls

A team maps a product made in four steps. The processing time of all steps adds up to a few minutes, but between the steps the parts wait in stock for several days. The map makes clear that faster machines would hardly change the lead time, while less stock and connected steps would. In an office, a map of the order-to-invoice process shows hand-overs, approvals and queues in the inbox in the same way.

  • Mapping alone at a desk with data from the ERP system.
  • Drawing the map in too much detail and losing the overview.
  • Stopping at the current state without a future state and an action plan.
  • Mapping a single variant instead of a product family, or the whole plant at once.

Go deeper

Value Stream Mapping: questions and answers.

What is the difference between a value stream map and a process map?

A process map shows the steps of a process. A value stream map also shows the information flow, the stock between steps and data such as cycle times and lead time, for a whole product family from supplier to customer.

What are current-state and future-state maps?

The current-state map shows the value stream as it runs today. The future-state map shows how it should run after applying flow, pull and takt, and the gap between the two becomes the improvement plan.

Who should take part in value stream mapping?

A small cross-functional team: people from the processes on the map, production planning, logistics and a manager who owns the value stream and can decide on the future state.

Learn Value Stream Mapping by playing it.

Lean terms stick when a team experiences them. The LeanActivity games turn them into rounds your team plays, measures and improves.