Most calendar time in any process is spent waiting, not working. Value stream mapping makes that visible.
A VSM diagram shows every step in a process — value-adding and non-value-adding — along with the time each step takes and the wait time between steps. The ratio of actual work time to total elapsed time is called process efficiency. In most unoptimized software delivery processes, it's below 20%.
The process:
- Map the current state — every step, every handoff, every wait
- Mark which steps add value and which don't
- Design the future state — eliminating the largest sources of waste
- The gap between current and future state is your improvement roadmap
In software and BA contexts, VSM is most useful for analyzing delivery pipelines (idea → production), approval workflows, and requirements hand-off processes. The most common finding: it takes two weeks for a story to go from "written" to "in development" — and most of that time is spent in queues.
I've used a lighter version of this thinking when onboarding to projects — mapping out how work actually flows before suggesting process changes. At LPT, the value stream revealed that developers were waiting on client feedback at multiple points in the sprint, adding days of idle time. The fix wasn't "work faster" — it was restructuring when and how client reviews happened.
Exam tip: VSM distinguishes between process time (active work) and lead time (total elapsed time including waits). The distinction is critical for process improvement analysis — and it appears in CBAP questions about current state analysis.