Practice knowledge base
Value Stream Mapping
Value Stream Mapping shows the complete path of work from a client request to the outcome and helps find delays, waste, excessive handoffs, and bottlenecks.
Documentation sections
What it is
Value Stream Mapping describes all steps in value creation: who initiates the work, where it flows, where it waits, and how it is transferred. The practice makes the process visible across different functions and separates useful work from waiting, rework, and approval overhead. It addresses the management challenge of slow work, when teams see only their segment and do not understand where time is lost across the entire flow.
When it helps
- Client requests pass through many teams, but no one sees the entire route.
- Result deadlines increase due to waiting, repeated approvals, and manual handoffs between roles.
- Teams dispute the causes of delays, relying on local perceptions rather than the overall factual process.
- Management needs to choose which bottlenecks to eliminate first to accelerate the flow without excessive burden.
How to start
- 1 Select one important stream: a product release, application processing, incident resolution, or another repeatable path from request to outcome.
- 2 Gather people from all key segments of the stream and together describe the current process as it is, including waits, reworks, and manual handoffs.
- 3 For each step, record the owner, input, output, execution time, waiting time, frequent causes of stoppage, and tools used.
- 4 Identify waste: unnecessary approvals, redundant data entry, queues, unclear readiness criteria, dependence on a single person or system.
- 5 Select 1-3 changes with the greatest impact on flow speed and assign owners to verify the effect.
Expected effect
The practice provides a shared understanding of the actual process and reduces disputes between functions about where delays occur. The team sees which changes will speed up the flow and which will only improve a local segment without benefiting the client.
Common pitfalls
- Mapping an ideal process instead of the actual work path with exceptions, waits, and reworks.
- Limiting the scope to a diagram of steps without measuring waiting times, queue volumes, and causes of stoppages.
- Turning the session into a blame game, causing participants to hide real process problems.
- Attempting to improve everything at once instead of selecting a few bottlenecks with a clear owner and impact metric.
Further reading
- Book: Mike Rother, John Shook, Learning to See, Lean Enterprise Institute.
- Book: James P. Womack, Daniel T. Jones, Lean Thinking.
- Book: Karen Martin, Mike Osterling, Value Stream Mapping.
FAQ
How does VSM differ from a regular process flowchart?
A flowchart typically shows the order of actions. VSM additionally captures the value stream: waits, handoffs, queues, execution times, dependencies, and waste that affect the speed of the outcome for the client.
Is it necessary to map the entire company's business process immediately?
No. It is better to start with one significant and repeatable stream where delays are already noticeable. Too broad a scope makes the map abstract and hinders the selection of specific improvements.
Who should be invited to a mapping session?
Representatives from all segments through which the work actually flows are needed: initiators, executors, approving roles, supporting functions, and the owner of the outcome. Without them, the map will quickly become an assumption.
How can you tell if the map has been beneficial?
After mapping, concrete solutions should emerge: which waits to eliminate, which handoffs to simplify, which rules to clarify, and by which metrics to verify the effect on deadlines, quality, or workload.