Value Stream Mapping Workshop Template

A value stream mapping workshop makes the entire flow of a product or service visible, from request to delivery, so a team can see where value is created and where it stalls. Value stream mapping is a foundational Lean tool: by mapping the current state, calculating flow, and designing a future state, a team turns a vague sense that work is slow into a precise, shared picture of why.

When to use it

Run a value stream mapping workshop when lead times are too long, handoffs are messy, or a process spans many functions and nobody owns the whole. It is the right starting point before a series of kaizen events, because the future-state map tells you which improvements matter most and in what order.

Who attends

Assemble a cross-functional team of five to ten people who together touch the whole value stream, including the people who do each step. No single function can map an end-to-end flow accurately, and the people closest to the work catch the realities a diagram from a conference room would miss.

How to run it

Scope one value stream so the map stays manageable, then build the current state by walking the actual process, not from memory. Calculate lead time against process time to expose how much of the stream is pure waiting. Mark the waste and constraints, then design a future state that improves flow and removes the biggest delays. Finish by turning the gap between current and future into a sequenced transition plan of kaizen actions with owners. The map is only valuable if it drives change.

Facilitator tips

• Map the real current state by walking it, not the idealized version.
• Capture lead time and process time; the gap is where the waste hides.
• Keep the future state ambitious but achievable within a planning horizon.
• End with a sequenced action plan, not just two pretty maps.

Common mistakes

• Mapping how the process should work instead of how it actually does.
• Scoping the value stream so broadly the map becomes unreadable.
• Producing a future-state map with no plan to reach it.
• Mapping without the people who actually run each step.

See the whole flow and fix it. Run it in OrgTP and turn the current-state and future-state maps into a tracked improvement plan.