How to do value stream mapping, step by step

To do value stream mapping, walk the process, record data at each step and draw the current state by hand.

Value stream mapping is a widely used lean tool, and an easy one to misuse. Teams often draw it in a meeting room as they believe the process works. The result looks tidy but can be far from reality.

Mike Rother and John Shook's book Learning to See describes walking the process and drawing the first map by hand. This guide follows that approach.

Step 1: walk the process

Choose one product family and walk its path from the customer back to the supplier on a gemba walk. A clipboard, a pencil and a stopwatch are all you need.

Walking backwards, from shipping to receiving, keeps attention on what the customer pulls rather than what each department pushes.

Step 2: collect data at each step

Record cycle time, changeover time, uptime and the number of people at each step. Count the inventory waiting between steps, and convert it into days of demand.

Note how each step learns what to make next, such as a schedule, a forecast or a kanban signal.

Step 3: draw the current state

Sketch the map on a large sheet with the people who do the work. Add the information flow, such as orders and schedules, above the material flow.

Then add the timeline at the bottom: value-added time against total lead time. The difference shows how much of the lead time is waiting.

Step 4: design the future state

A current-state map is only useful if it leads to a future state and a plan. Learning to See offers a set of questions for this.

Ask where you can create continuous flow and where you need a pull system with kanban. Ask which single point to schedule, and how to level the mix with heijunka.

Turn the ideas into improvement loops with owners. Long changeovers on the map often point to SMED, and takt from the takt time calculator sets the pace.

Mapping office and service work

The same method works for requests, approvals and handoffs. Inventory becomes items waiting in queues or inboxes, and the timeline still compares working time with waiting time.

Where software helps

Software earns its place after the walk. It keeps maps current, calculates lead times, shares maps across sites and compares versions over time.

Some tools add simulation to test a future state, or process mining to rebuild the flow from system data. See value stream mapping software. Software cannot do the observing.

Frequently asked questions