Methods & Guides
How to Create a Value Stream Map: A Step-by-Step Guide
A practical VSM guide covering symbols, metrics, current state mapping, future state design, and kaizen planning.
A practical VSM guide covering symbols, metrics, current state mapping, future state design, and kaizen planning.
You know something is wrong. Orders take three weeks when they should take three days. Work piles up between departments. Nobody can explain why. The symptoms are visible everywhere. The cause is not.
That is exactly the problem Value Stream Mapping (VSM) was designed to solve.
VSM is a Lean diagnostic tool that draws the complete flow of materials and information required to deliver a product or service to the customer, onto a single page. Not how the process is supposed to work. How it actually works. Every step, every wait, every handover, every inventory pile, laid out so the waste becomes impossible to ignore.
The typical starting point: most organisations find that only 2 to 15 percent of total lead time is genuinely value-adding. The rest is waiting, batching, rework, and unnecessary movement.
VSM gives you the evidence to change that. This guide walks you through every stage of the process, from selecting the right product family to publishing a kaizen plan your team will actually execute.
Value Stream Mapping originated within the Toyota Production System and was formalised for Western practitioners by Mike Rother and John Shook in their 1998 book Learning to See. The term "value stream" refers to every action, both value-adding and non-value-adding, required to bring a product from raw material to the hands of the customer.
VSM is not a flowchart. It is not a process map. It is a specific diagnostic with a defined symbol language, a defined set of metrics, and a defined sequence: current state, future state, implementation plan.
A completed map captures three things simultaneously:
Material flow — the physical movement of the product or work item through each process step
Information flow — the signals that tell each process what to make, when to make it, and how much
Time data — the split between value-added time (when work is actually being done) and non-value-added time (when it is waiting)
The combination of all three on one page is what makes VSM uniquely powerful. You can see, at a glance, whether your scheduling system is pushing work into queues that nobody downstream has asked for yet. That is something a standard process map cannot show you.
VSM was developed in manufacturing, but the method applies to any repeatable process. In 2026, VSM workshops are common across healthcare patient pathways, financial services case processing, NHS administrative flows, and software development pipelines. The symbols translate cleanly. The principle is identical: make the waste visible, then design it out.
Before you draw anything, you need to understand the icons. VSM uses a standardised symbol set so that any Lean practitioner can read any map, regardless of who drew it or which industry it covers. There are roughly thirty symbols in the full library. The twelve below cover 90 percent of what you will encounter.
| Symbol | Name | What it represents |
|---|---|---|
| Rectangle | Process box | A single process step: a machine, workstation, or team |
| Box below process | Data box | Key metrics for that step: cycle time, changeover time, uptime, operator count |
| Triangle with "I" | Inventory triangle | Stock or work-in-process between two steps; labelled with quantity and days |
| Factory icon | Customer / Supplier | The external customer (right) or supplier (left) |
| Striped arrow | Push arrow | Material pushed to the next process regardless of downstream demand |
| Bin icon | Supermarket / Pull | A controlled inventory buffer replenished only when downstream pulls |
| Arrow with "FIFO" | FIFO lane | First-in-first-out sequence between two processes |
| Card icon | Kanban | A pull signal: downstream triggers upstream replenishment |
| Straight thin arrow | Manual information flow | Paper schedules, verbal instructions, printed work orders |
| Lightning-bolt arrow | Electronic information flow | ERP signals, MRP releases, EDI orders |
| Stepped line at bottom | Timeline rail | Valleys = value-added time; peaks = wait / lead time |
| Starburst | Kaizen burst | A targeted improvement point on the future-state map |
The timeline rail at the bottom of the map is where the headline numbers live. The sum of the valley depths gives you your total value-added time. The sum of the peak heights gives you your total lead time. The ratio between the two is your Process Cycle Efficiency (PCE). Most organisations start with a PCE below 10 percent. That is not unusual. It is the baseline you are trying to improve.
A value stream map without data is just a diagram. The data boxes beneath each process step are what transform a sketch into a diagnostic tool. Before you go to the floor, know exactly what you are measuring.
Collect these at every process step:
| Metric | Definition | Why it matters |
|---|---|---|
| Cycle time (C/T) | Time between one completed unit and the next at this step | If C/T exceeds takt time, this step is the bottleneck |
| Changeover time (C/O) | Time to switch from one product or variant to another | Drives batch size decisions; the target for SMED improvement |
| Uptime (%) | Actual availability as a proportion of scheduled time | Effective capacity, not theoretical capacity |
| First pass yield (FPY) | Percentage of units completed correctly first time | Reveals hidden rework loops that inflate lead time |
| Number of operators | Headcount required to run the step | Labour component of value-added time |
| WIP / inventory | Units or days of stock held before this step | The dominant driver of lead time between processes |
Once you have the process data, calculate these across the whole map:
Takt time — available production time divided by customer demand. This is the pace the value stream must match. It is the single most important number on the map. Use the SimplicityHub cycle time calculator to compare your process cycle times against takt.
Total lead time — the sum of all inventory peaks on the timeline rail. Use the lead time calculator to work this out precisely.
Total value-added time — the sum of all cycle time valleys on the timeline rail.
Process Cycle Efficiency (PCE) — value-added time divided by total lead time, expressed as a percentage.
VSM follows a fixed sequence. Do not skip steps. Do not reorder them. Each stage builds on the last.
Do not try to map an entire factory, department, or service line at once. The scope will collapse the exercise. Pick one product family.
A product family is a group of products or services that pass through similar process steps using similar resources. The simplest way to identify one is to build a product-process matrix: list your products down the rows and your process steps across the columns, then mark which products use which steps. Products that share the most steps belong to the same family.
Choose the family with the highest volume, the highest strategic importance, or the longest lead time. That is where the biggest improvement potential sits.
This is a snapshot of reality. Not what the standard operating procedure says. Not what the process was designed to do. What is actually happening today.
The single biggest mistake teams make is drawing the current state from memory in a conference room. Do not do it. Walk the process instead.
Start at the customer end (shipping or final delivery) and walk upstream to the supplier or raw material intake. Walking backwards forces you to see what is genuinely being pulled by customer demand versus what is being pushed by internal scheduling.
Bring a stopwatch. Time actual cycle times yourself. Do not use standard times from the ERP system.
Count the inventory. Walk to each queue, count the units or estimate the days of supply.
Sketch on paper as you go. A pencil and A3 paper is the right tool. Do not open a laptop until the walk is complete.
Talk to the operators. They know where the rework happens, where the machine breaks down, and where work sits waiting for approval.
Use the SimplicityHub Gemba Walk Checklist to structure your observations before you go.
Draw from left to right. Supplier on the far left, customer on the far right. Process boxes in the middle, connected by push arrows or pull signals. Inventory triangles between every disconnected pair of processes. Information flows across the top. Timeline rail at the bottom.
Fill in every data box. A process box without a data box is incomplete. If you do not have a data point, go back and measure it.
Before designing the future state, analyse what you have drawn. Look for:
Inventory mountains — large inventory triangles, especially those measured in days rather than hours. These are the primary cause of long lead times.
Bottlenecks — process steps where cycle time exceeds takt time. These constrain the entire value stream.
Push arrows — every push arrow is a potential overproduction point. Production is being scheduled regardless of whether the next process is ready.
Information complexity — if the Production Control box sends individual schedules to every process step, you have a push system. That is the visual signature of a system that creates queues.
Low FPY — first pass yield below 95 percent at any step means rework is happening. Rework consumes capacity and inflates lead time invisibly.
Cross-reference your findings against the 8 Wastes. Every inventory triangle, push arrow, and rework loop maps to at least one of the eight waste categories.
The future-state map is not a wish list. It is a specific, achievable design for how the value stream should operate, grounded in the data you collected.
Rother and Shook's eight design questions are the structured method for building it:
What is the takt time?
Will you build to a finished-goods supermarket or directly to shipping?
Where can you introduce continuous flow?
Where will a supermarket pull system be required?
Which single process sets the pace for the whole value stream (the pacemaker)?
How will you level the production mix at the pacemaker?
What increment of work will you release consistently (the pitch)?
What process improvements are needed to achieve the future state?
Work through these questions in order. Each answer shapes the design of the next.
Mark every improvement point on the future-state map with a kaizen burst symbol. The gap between the current state and the future state becomes your project list.
The map is not the goal. The map is the blueprint. A VSM exercise that ends with a diagram on the wall and no implementation plan has produced nothing.
Every kaizen burst on your future-state map needs to become a concrete action. Convert them into a structured plan with four fields for each improvement:
What — the specific change to be made
Who — a named owner, not a department
When — a deadline, not a quarter
Measure — the KPI that will confirm the improvement has been achieved
The implementation plan prevents this. Review it weekly for the first twelve weeks. Monthly after that. Redraw the current-state map after each significant kaizen event to track progress against the baseline.
Not all improvements are equal. Use an impact vs effort matrix to sequence them. Tackle the high-impact, low-effort items first. These deliver visible results quickly, build team confidence, and demonstrate to leadership that the VSM investment was worthwhile.
A typical VSM implementation runs over six to twelve months. The first kaizen events address the biggest inventory queues and the most obvious bottlenecks. Later events tackle the structural changes: converting push systems to pull, introducing continuous flow between linked processes, and levelling the production mix at the pacemaker.
| Phase | Activity | Duration |
|---|---|---|
| Preparation | Product family selection, gemba prep, data collection plan | 0.5 days |
| Current-state mapping | Gemba walk, data collection, drawing the map | 1 to 2 days |
| Analysis | Waste identification, PCE calculation, bottleneck review | 0.5 days |
| Future-state design | Applying Rother and Shook's eight questions, drawing the map | 1 day |
| Implementation planning | Kaizen burst conversion, owner assignment, timeline | 0.5 days |
| Total | 3.5 to 5 days |
Most VSM exercises fail for the same reasons. None of them are technical.
Attempting to map an entire factory, service division, or end-to-end supply chain in a single exercise produces a map so complex it cannot be acted upon. Start with one product family. One process flow. One map. Expand scope only after you have completed your first implementation cycle.
This is the most common and most damaging mistake. A current-state map drawn in a conference room reflects how managers believe the process works. It rarely reflects how it actually works. The inventory counts will be wrong. The cycle times will be wrong. The rework loops will be invisible. Walk the floor first. Draw second.
A VSM workshop that ends with a finished map and no implementation plan has produced a poster, not an improvement. The map is a means to an end. The end is a shorter lead time, lower WIP, and a more reliable process.
This is a counterintuitive one. Most managers instinctively want to make each process step faster. But if a process step takes 10 minutes and the work then sits in a queue for three days, making the step take 8 minutes saves nothing. Focus on eliminating the queue. That is where the lead time lives.
VSM workshops generate energy. That energy dissipates quickly without a structured follow-up cadence. Assign owners before the workshop ends. Schedule the first implementation review before people leave the room. A weekly rhythm for the first twelve weeks is the minimum required to sustain progress.
Value Stream Mapping is one of the most powerful tools in Lean. It is also one of the most straightforward to begin. You do not need specialist software. You do not need a consultant. You need a product family, a stopwatch, a pencil, and the willingness to walk the process rather than imagine it.
The first map will not be perfect. That is fine. A rough map drawn from real data is worth more than a polished diagram drawn from assumption.
Start here:
Download the free VSM template and supporting templates from the SimplicityHub library
Use the Gemba Walk Checklist to prepare your observation before you go to the floor
Calculate your takt time and compare process cycle times using the cycle time calculator
Track total lead time and PCE with the lead time calculator
If you want to build the skills to lead VSM workshops and full Lean transformation projects, the SimplicityHub Lean Practitioner course covers value stream mapping in depth alongside A3 thinking, standard work, kaizen event facilitation, and more.
The map is waiting to be drawn. The waste is already there.
A value stream map shows the full flow of materials and information needed to deliver a product or service. It highlights every process step, queue, handover, and delay so you can see where time is lost and where improvement will have the biggest effect.
A process map shows the order of steps. A value stream map adds timing, inventory, and information flow. That makes VSM a diagnostic tool, not just a diagram, because it shows where lead time, waste, and bottlenecks are actually coming from.
The core metrics are cycle time, changeover time, uptime, first pass yield, number of operators, and inventory or WIP. At the value stream level, calculate takt time, total lead time, total value-added time, and process cycle efficiency.
Start at the customer end and walk upstream through the real process. Time the work, count the inventory, capture the information flow, and draw the map from observation, not memory. Use the data to show how the process actually runs today.
The future-state map is the target design for a better process. It removes obvious waste, reduces queues, sets the pacemaker, and shows where pull, flow, and kaizen actions are needed to move from the current state to the desired state.
Current-state and future-state VSM templates with symbols and metrics built in.