Help Centre / Methodology / Building a current-state map

Building a current-state map

Updated just now · 8 views ·

The current-state map is the diagnostic tool. It must reflect reality, not the process document. The whole VSM discipline collapses if the current-state map is aspirational instead of observed.

Rules for honesty

  • Walk the process yourself. Don't take second-hand accounts.
  • Record real cycle times. Don't use "typical" or "target" numbers.
  • Include every hand-off, even if it feels obvious.
  • Show the exception paths, not just the happy path.
  • Get sign-off from operators, not managers.

What good looks like

A current-state map that surprises the sponsor. If you show it to leadership and they say "yes that's exactly what we thought", you probably didn't dig deep enough. Real processes are always messier than the org chart suggests.

How long

A 1-day process typically takes a team 2-3 days to map honestly. A month-long enterprise process might take 2-3 weeks. Rushing this step is the single biggest failure mode.

Was this article helpful?

0 found this helpful