Value stream mapping has a paradox: it is simultaneously the most commissioned lean workshop and the most commonly wasted one. The difference between the two outcomes is not the mapping - any trained facilitator produces a decent map. It is whether the three days end in decisions.
The three deliverables
A current-state map built from walking, not from the ERP. The team follows a real product family from order to delivery, timing what actually happens: processing times, queues, batch sizes, information flows, rework loops. The number that matters at the end is the ratio of value-adding time to total lead time. In most first-time maps it lands between 0.5% and 5% - a number that reliably changes what leadership believes about where time goes.
A future-state design with explicit trade-offs. Where continuous flow, where pull with supermarkets, where a planned bottleneck, what batch sizes, which pacemaker process. These are decisions with costs, and they belong to the leaders in the room - a facilitator who designs the future state for you has quietly taken ownership the organisation needs to keep.
An implementation plan with owners and dates. The future state decomposes into loops, each with a named owner, a measurable target, and a date. This is the deliverable that separates a workshop from wallpaper.
The format
Two days of preparation (product family selection, data skeleton, participant mix), then 3 to 5 days on site: one to two days current state including the walk, one day future state, one day planning and commitment. The room needs the people who own the stream - production, planning, quality, logistics, and someone who can commit money. In Switzerland a senior-facilitated VSM workshop prices at roughly CHF 12'000 to 25'000 scoped; see the rates guide.
One rule of thumb worth enforcing: map one product family, not the whole plant. A map of everything is a map of nothing.
When VSM is the wrong tool
Skip the workshop when the problem is already precisely located (a changeover, one machine's OEE - go directly at it with SMED or TPM), when the process is genuinely unstable day to day (stabilise first; you cannot map chaos usefully), or when leadership has no intention of changing the planning logic - a future state built on pull is a fiction if scheduling will keep pushing.
For administrative and service streams - claims, case management, order-to-cash - the mechanics differ (the Makigami variant handles invisible work better) but the three-deliverable test is identical.
FAQ
How long does a value stream mapping workshop take?
Three to five days on site, plus about two days of preparation. Current state and the walk take one to two days, future state one day, implementation planning one day.
What does a VSM workshop cost in Switzerland?
Roughly CHF 12'000 to 25'000 with a senior facilitator, scoped to include preparation and a follow-up review. The internal cost - key people in a room for three days - is comparable and should be planned as deliberately.
What is a good value-adding ratio?
First maps typically show 0.5 to 5% value-adding time against total lead time. The absolute number matters less than the improvement loop it starts: future states commonly target cutting lead time by 30 to 70%.
VSM or process mapping - what is the difference?
Process mapping documents steps. Value stream mapping adds time, inventory, and information flow, and exists to redesign the stream, not describe it. If you only need documentation, VSM is overkill.