Resources/Glossary/
Current State Map
Process Improvement Tools

Current State Map

The honest picture of how the value stream runs today. Warts and all.

Updated
·
5
min read
Definition

What is Current State Map?

A current state map is the value-stream-map snapshot of how a product family flows through the shop today, from raw material to customer shipment. It shows every process step, cycle time, work-in-process between steps, information flow from the schedule, and the lead-time timeline at the bottom. It is the "before" picture, paired with a future state map as the "after."

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."

How a current state map works

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:

  • Cycle time: how long the work actually takes per piece.
  • Changeover time: how long it takes to set up the equipment for this part.
  • Batch or run size: typical lot size.
  • Uptime or reliability: how often the machine is actually available.
  • WIP count: the number of pieces sitting before this step, expressed in days of demand for clarity.

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.

Where a current state map fits on the shop floor of a small manufacturer

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.

Common mistakes with current state maps

  • Drawing from the conference room. Cycle times from MRP reports are not the cycle times the customer waits for. Walk the floor.
  • Too much detail. A current state map is a flow diagram, not a process map of every operator motion. Keep it readable.
  • Stopping after current state. Without a future state and an implementation plan, the map is wallpaper.
  • Missing information flow. Half the waste in most shops lives in how the schedule moves. The lightning bolts have to be on the map.
  • Picking too broad a scope. A current state for "all our products" is unreadable. Pick one product family.

Current state map and related Lean tools

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.

Common questions

The questions we hear most about this term.

How does a current state map work?
A small team picks one product family and walks the floor, following a real order from raw material delivery to shipment. At each process step, they record cycle time, changeover time, batch size, uptime, and the count of work-in-process sitting before the step. Material flow is drawn as arrows between process boxes. Information flow, usually the schedule signal and the production push, is drawn as lightning bolts from the customer through scheduling down to the floor. A timeline at the bottom alternates between value-add and wait segments. The total at the bottom is the lead time.
How is a current state map different from value stream mapping?
Value stream mapping is the full practice and produces two artifacts: a current state map and a future state map. The current state map is the "before" snapshot. The future state map is the "after" design. Doing value stream mapping always means producing both. A current state map alone is half the exercise, useful as a diagnosis but incomplete as an improvement plan. Most teams that say "we did value stream mapping" mean they produced a current state. The next step, designing the future state, is where the work actually pays off.
Is a current state map the same as a future state map?
No. They are paired artifacts that together make up a value stream map. The current state shows how things work today; the future state designs how they should work after improvement. The two are drawn in the same notation with the same metrics, so the team can compare them side by side. The current state is built by walking the floor with a stopwatch. The future state is built in a conference room with the team that walked the floor, asking how the flow could be redesigned.
What are common mistakes with current state maps?
The biggest is drawing it from the conference room instead of from the floor. Cycle times that come from MRP reports are not the cycle times the customer actually waits for. The second is mapping too much detail, the goal is to see the flow, not record every operator motion. The third is doing it without a future state to follow, the current state alone diagnoses but does not change anything. The fourth is leaving the information flow off the map. Half the waste in most shops lives in how the schedule moves, and a current state without information flow is missing the most important half.
What does a current state map look like on the shop floor of a small manufacturer?
Imagine a 30-person CNC and assembly shop running medical device subassemblies. The team picks the highest-volume part family and walks it from purchase order to shipment over two days. They sketch six process boxes: cut, mill, deburr, kit, assemble, ship. They mark cycle times, days of WIP between steps, and the schedule flow from customer email down to the production board. The finished current state shows 18 days of lead time, 92 minutes of value-add work, and 17 days of waiting in queues, mostly between machining and assembly. The map points at the redesign.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.