How to make a value stream map

Learn how to make a value stream map: walk the process, time each step and wait, draw the ladder, mark the waste and plan a better future state.

Written by
FlowDraw Team
Published
Reading time
6 min read
A FlowDraw board with a value stream map of a refund at Linden Home: five process boxes, triangles for queues, a timeline ladder and a lead time of 7 days, 40 min.

A refund at Linden Home, an online homeware store, takes 7 days and 40 minutes. Forty of those minutes are work. A value stream map is how you find that out, and it shows you which of the waits to attack first.

Quick Answer

A value stream map follows one process from request to delivery and shows the time spent working and waiting. To make one, walk the process, time each step and queue, draw the ladder that adds up the lead time, mark the waste, then plan a future state.

What is a value stream map?

It comes from lean manufacturing at Toyota, and the book Learning to See by Mike Rother and John Shook made it widely known. It also suits office work like this refund.

The first steps of the Linden Home refund map, with numbered pins on its seven kinds of part.
The parts of a value stream map
  1. Customer: who starts it and who receives the result.
  2. Information: how the request travels, shown by dashed lines here.
  3. Process box: one step of the work.
  4. Data box: the numbers for that step.
  5. Triangle: a queue where work waits. The “I” stands for inventory.
  6. Ladder: waiting on the upper level, working on the lower.
  7. Kaizen burst: an improvement idea.

Use one when a process feels slow and nobody knows why. To see who hands work to whom, use a swimlane diagram instead. For the causes of one fault, a fishbone diagram fits better.

How to make a value stream map

Walk the process

Follow one real request from start to finish, and go and look instead of asking how it should work. Keep to steps where someone adds something.

A customer sends a refund form to the help desk system, which leads to Log request, Check order and photos, and Approve refund.
Follow one request, leaving gaps for the waits

The refund has five steps: Log request, Check order and photos, Approve refund, Send payment and Email customer. Keep each box to something a person could time.

Time each step and wait

Fill in a data box for each step, and count the queue in front of it.

Data boxes and queues added: 20 requests before a 5 minute step, 40 before a 10 minute step, 80 before another 5 minute step.
Numbers for the work, and queues between steps
On the mapMeaningExample
C/TCycle time: to do the work once10 min
PeopleStaff on the step3
%C&ADone right the first time80%
QueueRequests waiting40 requests

To turn a queue into a wait, divide by demand. Demand here is 40 requests a day, so 120 waiting is 3 days. Factory maps often record changeover time and uptime as well.

Draw the ladder

The ladder puts every wait above the line and every step below it, so the two sums are easy to read.

The end of the ladder, 3 days, 15 min, 0.5 days and 5 min, beside totals: lead time 7 days, 40 min, process time 40 min, rolled %C&A 67%.
The ladder adds up to three totals
  • Lead time: all of it added together, 7 days and 40 minutes.
  • Process time: the work alone, 40 minutes.
  • Rolled %C&A: each step’s figure multiplied together, 67%.

Counting full days, under 1% of the lead time adds value. That figure usually changes the conversation.

Mark the waste

Now look for what the numbers point at. Put a kaizen burst over each place you want to change.

Two kaizen bursts above the queues: Auto-approve refunds under $50, and Pay every day, not in a weekly batch.
Bursts go over the longest waits

Start with the longest queues, not the slowest steps. Saving five minutes on Send payment does little against the 3 days in front of it.

Plan the future state

Write what each idea would change, in the same numbers. This is a forecast until you try it.

Two panels. Waste spotted lists waiting, rework and batching. Future state cuts two waits, for a lead time of 3 days, 40 min.
From the waste you found to the change you expect

Teams usually draw a second map for this, then a plan to reach it.

Drawing a value stream map in FlowDraw

The template is free, and Free can edit and copy everything on it. Its triangles are basic shapes and its bursts are images. The separate Value stream map library, with cells such as Inventory and Kaizen burst, needs Pro.

The FlowDraw Templates page with Value stream map as the one result.
Find it under Templates in the sidebar
  1. Open the template

    Search for “Value stream map” under “Templates”, open the card, then choose “Use template”.

  2. Enter your own numbers

    Double-click any label or data box and type. FlowDraw does not calculate on a board, so work out the totals yourself and type those in too.

  3. Rename the steps

    Double-click a process box. Five steps suit the template as drawn, with no redrawing.

  4. Add or remove a step

    Shift-click the triangle, its two labels, the box, the data box and the arrows, then press ⌘D (Ctrl+D on Windows) or ⌫. The arrows between steps have free ends, so they stay put if you move a box alone.

  5. Change the ladder’s length

    The ladder is one line with its corners stored. Dragging an end redraws it with fewer bends. For another length, delete it, press L and draw each part, with “Straight” and end “None” in “Line properties”.

  6. Review it with the team

    Choose “Share” and add people. On Free everyone you invite can edit. On Pro only one person can, so others press C and comment.

The Value stream map template open in the FlowDraw editor, with the waste and future state panels below the ladder.
The template open in the editor

Maps like this go stale when the process changes, so plan to redraw them rather than trust an old one. “SIPOC” and “5 whys” are free templates that pair well with it.

Value stream map mistakes to avoid

  • Mapping from memory. People remember how a process should run. Walk it and count the queues.
  • Too much at once. Pick one product or request type, with a clear start and end.
  • Timing the work and skipping the waits. The waits are usually the point.
  • Averages with no source. Note whether a time was measured or estimated.
  • Trimming fast steps first. It feels productive and barely moves the lead time.
  • Stopping at the current state. A map with no future state is only a description.

FAQ

It shows every step and wait needed to deliver something to a customer, with times, so a team can see where time goes and decide what to change first.

Continue Reading

A FlowDraw board with a state machine diagram of a document: Draft, In review, Approved, Published and Archived, joined by labeled transitions.

Guides·

How to draw a state machine diagram

Draw a state machine diagram in UML: states, transitions, guards and entry actions, with a document review example you can check against a simple table.

A FlowDraw board with a data flow diagram: Customer and Payment provider connect to Validate order, Take payment and Fulfill order, with two data stores.

Guides·

How to make a data flow diagram

How to make a data flow diagram: the four symbols, context and level 1 views, the rules that catch errors, and how to draw one in FlowDraw.

A FlowDraw board with a kanban board named Launch campaign: To do, Doing and Done columns, with cards such as Pricing page copy and Q4 launch brief.

Guides·

How to make a kanban board

Make a kanban board that keeps work moving: choose columns, write clear cards, set a WIP limit and build one in FlowDraw with tags and due dates.

Ready to create your first diagram?

Turn your ideas, notes, or documents into a clear,
editable flowchart in seconds.

Get Started Free