Business Process Expert·9 min read
What is value stream mapping?
Value stream mapping (VSM) is a lean technique for drawing the complete flow of material and information required to deliver a product or service to a customer, so you can see where value is created and where time is wasted.
It comes from the Toyota Production System, where it was called "material and information flow mapping." Unlike a standard process map, a VSM does not just show the sequence of steps. It overlays the numbers - how long each step takes, how long work waits between steps, and how much of that time actually adds value. The result is a single diagram that exposes the gap between how long a job really takes and how long the work itself takes.
What a value stream map shows
A VSM has a distinctive layout. Once you know the four building blocks, you can read any value stream map in seconds.
- -Process boxes - each major step in the flow, drawn left to right in the order work moves through them.
- -Data boxes - a small table under each process box holding its metrics: cycle time (C/T), changeover time (C/O), uptime, and often %C&A (percent complete and accurate).
- -Material and information flow - arrows across the top show how orders and schedules travel; arrows along the bottom show how the physical work or product moves.
- -The timeline ladder - a sawtooth line along the bottom. The low steps are processing time (value-add); the high steps are waiting time (non-value-add). Summed up, they give you lead time versus value-add time.
Current-state value stream (simplified)
Order Entry
Engineering
Machining
Assembly
Shipping
Lead time ~11 days · Value-add time ~1.9 hours
The upper steps of the sawtooth are wait time; the lower steps are processing time. Notice how the days of waiting dwarf the hours of actual work - that gap is what a VSM is built to expose.
"When people first see a value stream map, the number that shocks them is the ratio of value-add time to lead time. It is often under 5 percent. That means 95 percent of the time a job spends in your process, nobody is actually working on it - it is just sitting in a queue. You cannot fix what you cannot see, and the timeline ladder makes that waste impossible to ignore."
The metrics inside a data box
Cycle time (C/T)
How long it takes to complete one unit of work at a step, from start to finish - the actual hands-on processing time.
Lead time
The total elapsed time from when work enters a step (or the whole stream) until it leaves - including all the waiting. Lead time is almost always far larger than cycle time.
Changeover time (C/O)
The time lost switching a step from one type of work to another - retooling a machine, or context-switching a team between task types.
%C&A (percent complete and accurate)
The share of work that arrives at the next step complete and correct, needing no rework. Low %C&A upstream creates hidden loops and delay downstream.
When to use value stream mapping
VSM is the right tool when your problem is flow - when work moves slowly through a system with long queues, delays, and handoffs, even though each individual step is fast. Reach for it when:
- -Lead times are long and you do not know where the time actually goes.
- -You want to reduce delay, inventory, or work-in-progress across a whole flow, not tune one step.
- -Multiple teams or departments touch the work and no one owns the end-to-end picture.
- -You are planning a lean or continuous-improvement initiative and need a baseline everyone agrees on.
If instead you need to capture detailed decision logic, exceptions, and role responsibilities, a process map is the better fit. The two are complementary: VSM for flow and time, process mapping for logic and detail.
Current state vs. future state
Value stream mapping is always done in two passes. You never map the ideal first.
Pass 1
Current-state map
How the value stream works today, with real, measured numbers. Walk the flow yourself, stopwatch in hand. This is your honest baseline - queues, rework, and all.
Pass 2
Future-state map
How the stream should work after you remove waste - fewer queues, combined steps, smoother flow. This becomes the target and the plan for your improvement work.
The distance between the two maps is your improvement backlog. Each difference is a concrete change with a measurable payoff.
Why it works
- -It makes waiting visible. Most process improvement focuses on speeding up steps. VSM shows that the real enemy is usually the time between steps.
- -It aligns teams. One shared diagram with agreed numbers ends the "my part is fine" arguments and points everyone at the whole.
- -It quantifies opportunity. Because every step carries data, you can estimate the payoff of a change before you make it.
- -It targets the right work. It stops teams from optimizing steps that were never the bottleneck.
A quick walkthrough
Read the map above as a story. An order enters and waits two days before anyone starts order entry (5 minutes of actual work). It waits three more days for engineering (45 minutes of work), then five days for machining (30 minutes of work), then a day for assembly, and finally ships.
Add it up: the customer waits roughly eleven days, but the total value-add work is under two hours. The map tells you immediately that chasing faster machining is the wrong move - the eleven days are queues, not processing. The improvement lever is flow: smaller batches, pull signals, and removing the wait between engineering and machining. That is the insight a plain process map would never surface.
From seeing the stream to changing it
Once you can see the whole value stream, you can decide which steps should become AI-assisted or automated - and you have the baseline numbers to measure the before-and-after. A step with a high changeover time or a low %C&A is often a strong candidate: automate the handoff, and the queue behind it shrinks.
In Crismo you can map the value stream and tie the detailed process for each step, with value streams in Crismo.
Keep learning
Frequently asked questions
What is value stream mapping in simple terms?▼
It is a diagram of every step needed to deliver a product or service to a customer, with the timing of each step and the waiting between them. It shows where value is added and, more importantly, where time is wasted.
What is the difference between value stream mapping and process mapping?▼
A process map shows the sequence, decisions, and roles in a workflow. A value stream map overlays timing and flow data - cycle time, lead time, and waiting - to expose delay across the whole stream. VSM is about flow and time; process mapping is about logic and detail.
What are the main symbols in a value stream map?▼
Process boxes for steps, data boxes for their metrics, arrows for material and information flow, inventory triangles for queues, and a sawtooth timeline at the bottom that separates processing time from waiting time.
Is value stream mapping only for manufacturing?▼
No. It started in manufacturing but works anywhere with a flow of work: software delivery, healthcare, insurance claims, procurement, and back-office operations all benefit from mapping their value streams.
What is the difference between current-state and future-state maps?▼
The current-state map captures how the value stream works today, with real measured numbers. The future-state map shows the improved version after waste is removed. The gap between them is your improvement plan.
Model your value stream in Crismo
Crismo lets you map value streams and tie a detailed BPMN process diagram to each step, connecting strategy to execution. It links processes to the flow rather than using the classic Lean VSM symbols.
See value streams in Crismo