Future State Map

A future state map is the design half of value stream mapping. The current state diagnoses. The future state plans. Without both, the value stream mapping exercise produces an interesting wall poster and no improvement. The future state is built deliberately, by the team that walked the current state, in a conference room with the constraints of the actual shop in mind. The trap most teams fall into is making the future state aspirational, a vision of perfect flow with no plausible path from where the shop actually is. A good future state is implementable, often in twelve to twenty weeks, with the people and equipment the shop already has.

"A future state has to fit the shop you have, not the shop in the textbook. If you cannot get there from here, it is a poster, not a plan."

How a future state map works

A future state map is built around a set of standard design questions. The team that walked the current state sits down with the map on the wall and works through them:

• Where can pull replace push? The current state usually has multiple push signals. The future state typically reduces those to a single signal sent to one pacemaker process, with pull loops connecting the rest.
• Where can setup reduction enable smaller batches? Setups that take hours force batches that create days of WIP. Targeted setup reduction at the right places enables the future state batch sizes.
• Where should WIP buffers be capped? Uncapped WIP between operations is where most of the lead-time waste hides. The future state caps buffers explicitly, often with kanban signals.
• Where does the schedule go? A current state with the schedule pushed to every operation creates noise. The future state usually sends the schedule to one pacemaker and lets pull signals propagate from there.
• Where are the constraints? The future state has to respect physical constraints (machines, space, skills). Improvements that require capacity the shop does not have are not future state; they are wishlist.

The map uses the same notation as the current state: rectangular process boxes, arrows for material, lightning bolts for information, a timeline at the bottom. The point of the shared notation is direct comparison. The team should be able to lay the two maps side by side and see exactly where the changes are, what each change targets, and how the total lead time changes.

The future state map is paired with an implementation plan that breaks the redesign into a sequence of two-to-four-week improvements. Each improvement targets a specific change between the two maps. The plan usually runs three to six months for a small shop, and the future state map is revisited every quarter as parts of it get built.

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

Imagine the same 30-person fabrication shop from the current state example. The current state showed 21 days of lead time, 47 minutes of value-add work, eight process boxes, and information flow pushed three different ways. The future state design session takes two afternoons with the lead, the shift supervisor, the welder, and the schedule coordinator.

The team designs the future state by working the design questions. The schedule goes to a single pacemaker, the welding cell, with the upstream processes pulling from the welder's signal. A small two-piece kanban loop connects forming to welding, capping the WIP that had been five days. Setup reduction at the welder, from 45 minutes to under 10, enables mixed runs so the cell can change products multiple times per shift. The information flow on the map collapses from three competing signals to one path.

The implementation plan breaks the future state into seven specific improvements over twelve weeks: schedule consolidation in week 1, setup-reduction project in weeks 2-4, kanban installation in weeks 5-6, pacemaker signal training in week 7, then four weeks of refinement. The team confirms each improvement is buildable with the people and budget available. The future state lead time target is 5 days.

Three months in, the shop is running at 7 days of lead time. The remaining 2 days come from a second pass through the future state in the following quarter. That is a future state at small scale. Designed, not dreamed.

Common mistakes with future state maps

• Aspirational instead of implementable. A future state with no plausible path is wallpaper. Every change has to have an owner and a date.
• Ignoring shop constraints. Designing flow that requires equipment or skills the shop does not have produces a wishlist, not a plan.
• Treating the map as the deliverable. The map is a scaffold for the implementation plan. The plan is what changes the shop.
• One pass and walk away. The future state should be revisited every quarter as improvements land and conditions shift.
• Future state without operators in the room. The people who run the value stream have to be part of the design or the future state will be fiction at the workstation.

Future state map and related Lean tools

A future state map is the design half of value stream mapping; the diagnostic half is the current state map. The journey from current to future state is what most lean teams call a lean transformation. The long-horizon ideal a future state map points toward is captured in the concept of true north, the vision of perfect flow the shop aims at over years.