Value stream mapping (VSM) is a lean method for drawing every step that gets one product family from raw material to the customer, with the material flow, the information flow and a lead-time timeline on one page. You draw the current state from a walk of the floor, then a future state, then the plan between them. The eight steps:
- Pick one product family
- Set customer demand and takt time
- Walk the process from shipping back to receiving
- Fill in a data box for each process
- Count the inventory and convert it to days
- Draw the information flow
- Add the timeline and total it
- Design the future state and an action plan
Free value stream map template The steps in detail VSM symbols chart Worked example with numbers VSM software
What Is Value Stream Mapping?
Value stream mapping (VSM) is a lean method for drawing every step, value-adding or not, that it takes to get one product family from raw material to the customer, with both the material flow and the information flow on one page. The Lean Enterprise Institute defines it as diagramming "all the actions (value-creating and nonvalue-creating) needed to move a product or service from raw material to the arms of the customer." You draw the current state as it really runs today, then a future state that shows how it should flow, then a plan to get there.
A value stream is the whole set of actions for one product family; a value stream map (the drawing itself) is different from an ordinary flowchart in three ways: it puts numbers on every step (cycle time, changeover, uptime, inventory), it shows how each step learns what to build next, and it ends in a timeline that adds up the total lead time against the minutes of actual work.
Why VSM Matters
Most managers know their individual process times. VSM shows what happens between processes (the waiting, the batching, the handoffs), which on most maps is most of the lead time. In the worked example below, a part spends 20 days in the building to get 154 seconds of work.
Mapping for the first time?
Start with one product family and one walk. The short floor guide Value Stream Mapping: Where to Start covers scope, what to record, and how to turn the map into actions with owners and dates.
Ready to model it?
VSM Pro is value stream mapping software that builds current and future state maps offline and does the takt, lead-time and WIP math for you, with what-if for the future state. Free 2-day trial.
How to Draw a Value Stream Map: 8 Steps
Steps 1 to 7 produce the current-state map, in the order you do them on the floor; step 8 turns it into a future state. Public guides from NIST MEP and AHRQ use the same sequence: choose the family, draw the process and material flow, add the information flow, collect the data, add the timeline, then design the future state.
A family is a group of products that pass through similar steps and over common equipment in your downstream processes. Learning to See (Rother and Shook) is blunt about it: unless you have a small, one-product plant, drawing all your flows on one map is too complicated. Write down the family, how many part numbers are in it, and how much the customer wants, how often.
Put the customer in the top right with daily demand. Work out takt time: available time per day divided by units per day. Every cycle time on the map gets compared against this number.
Start at shipping and walk upstream to receiving. This follows the flow of customer value. Bring a pencil, stopwatch, and clipboard. Go to the gemba (actual workplace), don't map from a conference room.
Draw one process box wherever the material flow stops. Under it, a data box: cycle time (how long one unit takes), changeover time, uptime %, batch size, number of operators, and available time per shift.
Count WIP at every queue, buffer, and staging area. Convert it to time by dividing by daily demand: 900 parts in front of a step, with customers taking 450 a day, is 2 days of wait.
How does each step know what to work on next? Is it a schedule push, a kanban pull, or "whoever yells loudest"? Draw information flows across the top of the map: straight arrows for paper and verbal, zigzag arrows for electronic.
Draw a timeline at the bottom: wait time (days of inventory) on the upper level, processing time on the lower level. Total each row. The top row is your lead time, the bottom row your value-add time, and the ratio between them is what the map is for.
Mark each problem with a kaizen burst, answer the future-state questions (takt, finished goods, flow, pull, pacemaker, levelling), draw the target map, and turn every burst into an action with an owner and a date. Without this step the map is a poster.
CT: 2 min
CT: 8 min
CT: 3 min
CT: 5 min
Total lead time: 12h 18min → Value-add time: 18 min → Value-add ratio: 2.4%
VSM Symbols Chart
Value stream maps use a standard set of icons so anyone trained in lean can read anyone else's map. The set below follows the one popularized by Learning to See and taught in courses such as the University of Washington's IE 337. You need about a dozen of them for a typical first map.
Customer / Supplier
Factory outline. Supplier top left, customer top right, with demand written underneath.
Process box
One area where material flows. A new box starts wherever the flow stops and parts pile up.
Data box
Sits under a process: cycle time, changeover, uptime, operators, shifts, batch size.
Inventory
Triangle with an I. Write the count and the days it represents underneath.
Push arrow
Striped arrow. Material is made to a schedule and pushed on, whether the next step needs it or not.
Truck shipment
Deliveries in from suppliers and out to customers. Write the frequency: daily, 2x week.
Supermarket
A small, controlled stock the downstream process pulls from. Open side faces the supplying process.
Withdrawal (pull)
Curved arrow. The downstream process takes what it needs from a supermarket.
FIFO lane
First in, first out with a cap on how many parts can sit in the lane. When it is full, upstream stops.
Kanban card
Production kanban tells a process to make; withdrawal kanban tells a material handler to move parts.
Signal kanban
Upside-down triangle. Used where a batch process makes a lot when stock falls to a trigger point.
Load leveling
Heijunka box. Spreads the mix and volume evenly over the day instead of in big runs.
Manual information
Thin straight arrow: paper schedules, hot lists, phone calls, the supervisor's walk.
Electronic information
Zigzag arrow: ERP or MRP schedules, EDI orders, emailed forecasts.
Go see
Glasses. Someone adjusts the schedule by walking out and looking at what is on the floor.
Operator
Drawn in the process box with the head count next to it.
Kaizen burst
Starburst on the current-state map marking a problem the future state has to fix. Find its cause with root cause analysis (RCCA) before you pick the fix, and scope a burst big enough for an event with a kaizen charter template.
Timeline
Stepped line along the bottom. Upper steps are waiting (days), lower steps are processing (seconds).
VSM symbols table
The same symbols grouped the way most references group them: process, material, information and general. If you only learn five, learn the process box, data box, inventory triangle, push arrow and timeline.
| Group | Symbol | What it means on the map |
|---|---|---|
| Process | Customer / supplier | Outside company or site; write demand or delivery frequency under it |
| Process | Process box | One area where material flows continuously; a new box starts where the flow stops |
| Process | Data box | C/T, C/O, uptime, operators, shifts, batch size for the process above it |
| Process | Operator | Head count working in the process |
| Material | Inventory triangle | Parts waiting; count them and convert to days of demand |
| Material | Push arrow | Material made to a schedule and sent on whether or not the next step needs it |
| Material | Truck shipment | Inbound or outbound delivery, with its frequency |
| Material | Supermarket | A small controlled stock that the downstream process pulls from |
| Material | Withdrawal arrow | The downstream process takes parts from a supermarket (pull) |
| Material | FIFO lane | First in, first out queue with a maximum; full lane stops upstream |
| Information | Manual information arrow | Paper schedules, phone calls, hot lists |
| Information | Electronic information arrow | ERP or MRP schedules, EDI orders, emailed forecasts |
| Information | Production / withdrawal kanban | Card that tells a process to make, or a handler to move, a fixed quantity |
| Information | Signal kanban | Triggers a batch when stock falls to a reorder point |
| Information | Load leveling (heijunka) box | Spreads mix and volume evenly over the day |
| Information | Go see | Schedule adjusted by walking out to look |
| General | Kaizen burst | A problem the future state has to fix |
| General | Timeline | Waiting days on the upper steps, processing time on the lower steps |
Worked Example: A Current-State Map With Real Numbers
This is an illustrative example, not a client case. The numbers are made up but typical, and every one of them is shown with its math so you can check it and swap in your own. The product family is a line of painted steel brackets, made in four steps and shipped by truck every day.
Swipe the map sideways to see all of it.
The lead-time math
Inventory on a map is converted into time by dividing it by daily customer demand. A Rolls-Royce supplier guide to completing a value stream map shows the same method: 174 pieces of in-process inventory against a requirement of 100 a day is 1.74 days. It is Little's Law (lead time = WIP ÷ throughput) applied one pile at a time.
| Where the parts sit | Pieces counted | Math | Days of lead time |
|---|---|---|---|
| Raw coil (enough for) | 2,250 | 2,250 ÷ 450 | 5.0 |
| Stamped, waiting for welding | 2,700 | 2,700 ÷ 450 | 6.0 |
| Welded, waiting for paint | 1,350 | 1,350 ÷ 450 | 3.0 |
| Painted, waiting for assembly | 900 | 900 ÷ 450 | 2.0 |
| Finished goods, waiting for the truck | 1,800 | 1,800 ÷ 450 | 4.0 |
| Production lead time | 9,000 | 5 + 6 + 3 + 2 + 4 | 20.0 days |
Processing (value-add) time = 4 + 45 + 50 + 55 = 154 s, about 2.6 minutes.
Value-add ratio = processing time ÷ lead time = 154 s ÷ (20 days × 27,000 s) = 154 ÷ 540,000 = 0.029%.
Takt check: effective cycle time = C/T ÷ uptime. Stamping 4 ÷ 0.85 = 4.7 s, welding 45 ÷ 0.90 = 50 s, painting 50 ÷ 0.80 = 62.5 s, assembly 55 ÷ 1.00 = 55 s. Painting is the only step slower than the 60 s takt, which is why the burst goes there.
Two things jump out. First, a bracket waits 20 days to receive under three minutes of work, and none of that waiting is anyone working slowly. Second, the map points at the constraint without anyone arguing about it: painting cannot keep up with takt on an 80% uptime, so the plant makes up the gap with overtime and stock. If the cycle times on your own map need checking, the Cycle Time Calculator and WIP and Little's Law Calculator do the same math, alongside the other free manufacturing calculators.
VSM Pro takes your demand, data boxes and inventory counts and builds this map, the timeline and the takt check for you, then lets you try the future state before you move anything.
Reading a VSM: What to Look For
| Symptom on Map | What It Means | Action |
|---|---|---|
| Large inventory triangles between steps | Batching or unbalanced processes | Reduce batch sizes, balance line |
| Information flows going to every step separately | Push scheduling: no flow | Implement pull signals (kanban) |
| One step with much longer CT than others | Bottleneck constraining the system | Apply Theory of Constraints |
| Effective C/T (C/T ÷ uptime) above takt | The step cannot keep up without overtime or stock | Raise uptime, offload work, or add capacity |
| High changeover time at one step | Long setup blocking flow | SMED (Single Minute Exchange of Die) |
| Low uptime % at a step | Equipment reliability issue | TPM (Total Productive Maintenance) |
Current State vs Future State Map
The current-state map is a diagnosis: what really happens today, drawn from the walk. The future-state map is the target design: how material and information should flow in, say, six to twelve months, using the same symbols. LEI describes it as "a target image of how the material and information should flow through the value stream." The improvement plan connects the two, one kaizen burst at a time.
The future state is built by answering a fixed set of design questions in order, the approach laid out in Learning to See:
- What is the takt time?
- Will you build to a finished-goods supermarket or straight to shipping?
- Where can you use continuous flow?
- Where do you need supermarket pull to control upstream production?
- At what single point (the pacemaker) will you schedule production?
- How will you level the production mix at the pacemaker?
- What increment of work will you release and take away at the pacemaker?
- What process improvements are needed to make all of this work?
Applied to the bracket example (still illustrative), the answers give this future state:
| Item | Current state | Future state |
|---|---|---|
| Raw coil | Weekly truck, 5.0 days | Twice-weekly delivery, 2.0 days |
| Stamping to welding | Push, 2,700 pcs, 6.0 days | Supermarket with kanban, 450 pcs, 1.0 day. Stamping changeover cut from 60 to 20 min (SMED) so it can run smaller lots |
| Welding to painting | Push, 1,350 pcs, 3.0 days | FIFO lane, max 225 pcs, 0.5 day |
| Painting | 80% uptime, 62.5 s effective, above takt | 95% uptime through TPM: 50 ÷ 0.95 = 52.6 s, under takt |
| Painting to assembly | Push, 900 pcs, 2.0 days | FIFO lane, max 225 pcs, 0.5 day |
| Finished goods | 1,800 pcs, 4.0 days | Finished-goods supermarket, 675 pcs, 1.5 days |
| Scheduling | Weekly MRP schedule to all four processes | One schedule point: welding is the pacemaker, pulled by kanban from finished goods and levelled in a heijunka box |
| Lead time | 20.0 days | 2 + 1 + 0.5 + 0.5 + 1.5 = 5.5 days |
| Processing time | 154 s | 154 s (unchanged) |
| Value-add ratio | 0.029% | 154 ÷ (5.5 × 27,000) = 0.10% |
Lead time falls by (20 − 5.5) ÷ 20 = 72.5% without anyone working faster. That is the usual pattern: the future state changes the valleys of the timeline, not the peaks.
Current state: 14-day lead time from raw material to shipped product. Only 47 minutes of actual processing time. Value-add ratio: 0.23%.
Future state changes: Replaced batch scheduling with FIFO lanes, added supermarket pull between cutting and assembly, reduced changeover from 45min to 12min.
Result: Lead time dropped to 3.5 days. Same 47 minutes of processing, but 75% less waiting. On-time delivery went from 82% to 97%.
Value Stream Mapping vs Process Mapping
Both are flow diagrams, and teams often need both. The difference is altitude. A value stream map looks at a whole product family door to door and asks where the time goes; a process map (flowchart or swimlane) zooms into one process and shows every task, decision and handoff. Learning to See puts it as flow kaizen versus process kaizen: flow kaizen "focuses on material and information flow (which require a high vantage point to see) and process kaizen focuses on people and process flow."
| Value stream map | Process map | |
|---|---|---|
| Scope | One product family, receiving to shipping, many processes | One process or procedure |
| Level of detail | One box per area where flow stops | Every task, decision and handoff |
| Shows | Material flow, information flow, inventory, timeline | Sequence, decisions, who does what |
| Numbers | C/T, C/O, uptime, WIP in days, lead time, takt | Often none, sometimes step times |
| Main question | Where does the lead time go, and how should it flow? | How exactly is this step done, and where does it go wrong? |
| Output | Future-state map and an improvement plan | A better procedure, standard work or SOP |
A practical rule: map the value stream first to find the step that matters, then process-map that one step. If the team cannot yet agree where the stream starts and ends, a one-page SIPOC settles the boundaries before the walk.
High Level Value Stream Map
A high level value stream map shows the whole order-to-delivery stream with one box per department or site and the days each one adds. It comes before the detailed map: it tells you which part of the stream holds the lead time, so you know where the walk with a stopwatch is worth doing. Some teams call it an extended or door-to-door-plus map when it crosses company boundaries.
Continuing the bracket example (still illustrative), the plant is one box among five:
| Box on the high level map | Lead time | Work time |
|---|---|---|
| Order entry (customer service) | 1.5 days | 20 min |
| Planning and MRP run | 3.0 days | 15 min |
| Plant: stamping to finished goods (the detailed map above) | 20.0 days | 154 s (2.6 min) |
| Regional warehouse | 6.0 days | 5 min |
| Truck to customer | 2.0 days | none (transit) |
| Order to delivery | 32.5 days | about 43 min |
The plant holds 20 ÷ 32.5 = 62% of the lead time, so the detailed map belongs there first. The 4.5 days in order entry and planning are the next target, and they need an office map (touch time against queue time), not a shop floor one. The lean office guide covers that kind of stream.
Value Stream Mapping Examples by Setting
The method is the same everywhere; what changes is what sits in the queues and what counts as a process box.
| Setting | Process boxes | What the inventory is | Typical finding |
|---|---|---|---|
| Fabrication and assembly | Stamping, welding, paint, assembly | Parts between machines | Batch sizes set by long changeovers (SMED) |
| Office and order-to-cash | Order entry, credit check, scheduling, invoicing | Orders, emails, files in queues | Minutes of touch time against days in inboxes (lean office) |
| Warehouse | Receiving, putaway, pick, pack, ship | Pallets on the dock, orders waiting for a wave | Dock-to-stock time and wave release batching (lean warehousing) |
| Aerospace and long-cycle builds | Machining, outside processing, sub-assembly, final assembly | Kits and parts waiting at outside vendors | Outside processing loops dominate lead time (aerospace VSM) |
Value Stream Mapping Software and Templates
Draw the first map by hand. Once the map is drawn, a tool earns its place by doing the arithmetic (days of inventory, lead time, value-add ratio, the takt check) and by letting you test a future state before you move a machine. The options, from simplest:
| Option | Good for | Does the lead-time math? | Limits |
|---|---|---|---|
| Pencil and A3 paper | The first map, drawn during the walk | No, by hand | Hard to share and to redo |
| Excel or Google Sheets | The data: one row per process, formulas for days and lead time | Yes, if you build the formulas | Poor for drawing the map itself |
| Diagram tools (Visio, Lucidchart, Miro) | A clean drawing with standard VSM shapes | Generally no: the numbers are typed text | Change a number and the totals do not follow |
| Dedicated VSM software (for example eVSM, VSM Pro) | Maps where the numbers drive the timeline, plus what-if | Yes | Another tool to learn |
The free value stream map template takes your process and data boxes in the browser and works out lead time and the value-add ratio. VSM Pro is the offline value stream mapping software from SymplProcess: current and future state, takt and lead-time math, what-if, and maps saved as files on your own machine ($99, one-time, single user, with a free 2-day trial). For a class, the VSM Class Workbook walks a stream stage by stage. To check one pile at a time, the WIP and Little's Law calculator does the same math as the timeline.
Build Your Own VSM
Try mapping a simple value stream. Edit the process times and wait times to see how they affect total lead time and Process Cycle Efficiency.
Mini Value Stream Map
Edit process times and wait times for each step. Watch how wait time dominates lead time — and how Process Cycle Efficiency (PCE) reveals the truth about your value stream.
Ready for the full knowledge check? Guided scenarios and data export. Included with every plan.
PlanTake the advanced knowledge checkTake the workbook to the floor
The Value Stream Mapping Workbook is a single self-contained file: build the stream stage by stage, put your own times and piles in, and it works out the metrics, the biggest opportunities, area capacity against a target, shared-resource load and a modelled future state as you go. It exports your data as CSV and a summary you can paste into a report. Works offline, on a laptop in a meeting room, with nothing to install.
Value Stream Mapping FAQ
What is value stream mapping?
Value stream mapping (VSM) is a lean method for drawing every step needed to get one product family from raw material to the customer, with the material flow, the information flow and a timeline on one page. Teams draw the current state as it runs today, then a future state showing how it should flow, then a plan to get there.
What are the steps of value stream mapping?
There are eight: (1) pick one product family, (2) set customer demand and takt time, (3) walk the process from shipping back to receiving, (4) record a data box for each process (cycle time, changeover, uptime, operators), (5) count the inventory between steps and convert it to days, (6) draw the information flow, (7) add the timeline and total it, (8) design the future state and an action plan.
How do you calculate lead time on a value stream map?
Convert each inventory pile to days by dividing the pieces by daily customer demand, then add the days. For example, 900 parts in front of a step with demand of 450 a day is 2 days. Add every pile on the map for the production lead time, and add the cycle times for the processing time. Processing time divided by lead time is the value-add ratio.
What is the difference between a value stream map and a process map?
A value stream map covers a whole product family door to door at a high level, with inventory, information flow and a lead-time timeline. A process map zooms into one process and shows every task, decision and handoff. Map the value stream first to find the step that matters, then process-map that step.
What is the difference between a current state and a future state map?
The current-state map shows how material and information flow today, drawn from what you saw on the floor. The future-state map is the target design, usually six to twelve months out, built by answering questions about takt, continuous flow, supermarkets, the pacemaker and levelling. The improvement plan is the list of changes that gets you from one to the other.
What symbols are used in value stream mapping?
The common ones are the customer and supplier factory icon, process box, data box, inventory triangle, push arrow, truck shipment, supermarket, withdrawal arrow, FIFO lane, kanban cards, load-levelling box, manual and electronic information arrows, go-see glasses, operator, kaizen burst and the timeline. About a dozen cover most first maps.
How long does value stream mapping take?
For one product family, a walk and a draft current state can be done in a day. Learning to See suggests that in about two days a team should have a future-state map drawn to the point where implementation can begin. Do not wait for perfect data; note what you estimated and check it on the next walk.
What is a high level value stream map?
A high level value stream map shows the whole order-to-delivery stream with one box per department or site (order entry, planning, production, warehouse, delivery) and the days each one adds. It is used to choose which stream to map in detail and to show where the lead time sits before anyone draws process boxes and data boxes.
Can I make a value stream map in Excel?
Yes. Excel works for the data: one row per process with cycle time, changeover, uptime and inventory, and formulas for days of inventory, lead time and value-add ratio. It is clumsy for the drawing itself, so most teams sketch the map on paper and keep the numbers in a sheet, or use a tool that does both.
Do you need software for value stream mapping?
No. The first map should be drawn in pencil on the walk, so the team sees the floor rather than a screen. Software helps afterwards, when you want the takt, lead-time and WIP math done for you, a clean copy to share, and a way to test the future state before changing the floor. VSM Pro from SymplProcess does this offline.
Sources
- Lean Enterprise Institute, Understanding the Fundamentals of Value-Stream Mapping (definition, map layout, data box terms, future state).
- Mike Rother and John Shook, Learning to See, introduction (Lean Enterprise Institute) (product families, door-to-door scope, flow vs process kaizen, time to a future state).
- NIST Manufacturing Extension Partnership, Value Stream Mapping (the four-stage approach).
- AHRQ, Value Stream Mapping workflow tool (mapping steps).
- Rolls-Royce, How to Understand and Complete a Value Stream Map (converting inventory to days of demand).
- University of Washington IE 337, Value Stream Mapping (icon definitions).
The bracket and packaging-line examples on this page are illustrative, not client data.