Business Process Expert·9 min read
Before you start
A value stream map is built by walking a real process, not by theorizing at a desk. If you have not yet seen how a finished VSM reads, skim the value stream mapping overview first - it explains process boxes, data boxes, and the timeline ladder you will build here.
You will need a pencil and a large sheet of paper (VSM is traditionally done by hand), a stopwatch or timing data, and access to walk the actual flow. Follow the seven steps below in order.
Pick one product family
Do not try to map everything. A value stream map covers one product family- a group of items or requests that flow through roughly the same steps. In a factory that might be "machined brackets"; in an office it might be "standard supplier invoices" or "new-customer onboarding."
How to choose
Pick the family with the highest volume or the most pain - long lead times, frequent complaints, or a lot of rework. That is where a map pays back fastest.
Walk the flow backward from the customer
Start at the end - the customer receiving the finished product - and walk the process upstream, step by step, to where it begins. Working backward keeps you anchored on what the customer actually pulls, rather than what each department thinks it produces.
Do this on the floor, not in a meeting room. Physically follow one real unit of work through the stream and note every place it stops, waits, or changes hands.
Draw the process boxes
Lay the steps left to right in the order work flows. Each major step gets one process box. Aim for the major stages only - usually five to ten boxes. If you are drawing twenty, you are at process-map level of detail, not value-stream level.
Add a data box under each step
Below each process box, attach a data box with the numbers that matter for that step. Measure them - do not guess. Standard fields:
- -Cycle time (C/T) - hands-on time to process one unit.
- -Changeover time (C/O) - time lost switching between work types.
- -Uptime - how often the step is available when needed.
- -%C&A - share of output that arrives complete and accurate downstream.
Not sure which symbols to use for boxes, arrows, and queues? The VSM symbols guide covers the full notation.
Add inventory and the timeline ladder
Between the process boxes, mark where work piles up and waits - the inventory or queues. Then draw the timeline ladder along the bottom: a sawtooth line whose low steps are processing time and whose high steps are waiting time. This is the single most important part of the map.
Put the processing time under each process box, and the waiting time in each gap between boxes. The ladder makes the ratio of value-add to waiting impossible to ignore.
Calculate lead time vs. value-add time
Add up the two totals separately:
- -Lead time = sum of all processing time + all waiting time (the customer's total wait).
- -Value-add time = sum of processing time only.
Divide value-add by lead time to get your process efficiency. Do not be surprised when it lands under 5 percent - that is normal, and it is exactly the number that motivates change.
Design the future state
Now draw a second map: how the stream should work once you remove waste. Attack the waiting first, since that is where the time lives. Look for:
- -Queues you can shrink with smaller batches or pull signals.
- -Handoffs you can remove or combine.
- -Rework loops caused by low %C&A upstream.
- -Manual, rule-based steps a system could handle.
The differences between your current-state and future-state maps are your improvement plan. Turn each one into an action with an owner and a target date.
"The most common mistake I see is teams building a beautiful current-state map and then stopping. The map is not the deliverable - the future state and the actions between the two are. If you finish step six and admire the chart without doing step seven, you have measured your problem without fixing it."
From future state to automation
When you reach step seven, the manual, rule-based steps you flagged are your automation shortlist. Because your map already carries the numbers, you can measure exactly what automating a step does to lead time. In Crismo you can map the value stream and tie a detailed process to each step with value streams.
Keep learning
Frequently asked questions
What is the first step in creating a value stream map?▼
Pick one product family - a group of items or requests that flow through roughly the same steps. Mapping one family keeps the map focused and readable instead of trying to capture everything at once.
Why do you walk a value stream backward?▼
Starting from the customer and working upstream keeps you anchored on what the customer actually pulls, rather than what each department believes it produces. It surfaces the real demand-driven flow.
How do you calculate lead time and value-add time?▼
Lead time is the sum of all processing time plus all waiting time - the customer's total wait. Value-add time is the sum of processing time only. Dividing value-add by lead time gives process efficiency, often under 5 percent.
Should I draw a value stream map by hand or in software?▼
Draw the first current-state map by hand while walking the process - it keeps you observing rather than formatting. Move to a tool afterward when you want to share it, iterate, or model the future state.
What is the difference between the current-state and future-state map?▼
The current-state map records how the value stream works today with measured numbers. The future-state map shows the improved version after waste is removed. The differences between them form 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