The honest picture of how the value stream runs today. Warts and all.
A current state map is the diagnostic backbone of every value stream improvement effort. The whole point is to see how a product family actually flows through the shop today, with all the queues, waits, and rework that nobody experiences from a single station. Most shop owners think they know how their value stream works. Half of them are surprised by what they see when they actually walk it with a stopwatch and a notepad. The honest current state is uncomfortable to look at, which is the point. Until the team has seen the gap between value-add time and lead time on paper, the design conversation has nowhere to start.
"Walk the floor with a stopwatch. Most lead time is waiting. The waiting is usually invisible until you draw it."
A current state map is built by walking. The team picks one product family, follows a real order from raw material receipt through customer shipment, and records data at each step. The drawing notation is standardized across lean implementations: rectangular boxes for process steps, arrows for material flow, lightning bolts for information flow, and a timeline at the bottom for lead time.
At each process step, the team captures the standard set of data:
Information flow is drawn separately. The customer schedule comes into production planning, which then pushes work orders out to each station. Most current state maps reveal that information flow is the messiest part of the picture, with multiple uncontrolled push signals, hot-list overrides, and verbal updates that bypass the documented system.
The timeline at the bottom of the page alternates between value-add segments and wait segments. The total is the lead time. The ratio of value-add to total is the diagnostic punch line. Most current state maps show value-add as 1 to 5 percent of total lead time. That gap is the design space for the future state.
A current state map is not done until the team has both walked every step and confirmed the information flow. A map drawn from MRP reports is a guess.
Imagine a 32-person fabrication and assembly shop running parts for HVAC OEMs. The owner has been told the shop needs more equipment because lead times are creeping up. Before signing a quote on a new mill, the shift lead suggests a value stream mapping exercise.
The team picks the highest-volume part family and walks it over two days. They sketch eight process boxes from incoming stock to ship. They mark cycle times, days of WIP between operations, and the schedule path from the customer email down to the floor. Finished current state: 21 days of total lead time, 47 minutes of value-add work, 20 days of WIP and waits.
The big finding is not at any single process. It is between forming and welding, where five days of WIP sits because the welding cell runs full days of one part number at a time and parts wait until their turn. Another finding: the schedule is pushed in three different ways (MRP, a sales spreadsheet, and a daily verbal update), and the welding cell often follows the wrong one. The fix is not a new mill. It is a small kanban loop between forming and welding, a single source of truth for the schedule, and a setup reduction at the welder.
That is what a current state map at small scale buys. Two days of walking, an honest picture of the flow, and a design space that the team would never have seen from inside any single station.
A current state map is half of a value stream mapping exercise; the other half is the future state map. For lighter, faster process diagnostics that do not require the full VSM notation, a process mapping session is the right entry tool. The metric most often surfaced by a current state map is lead time, and the gap between lead time and value-add time is what defines the design space for the future state.
The questions we hear most about this term.
Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.
Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.