Current State vs Future State: The Two Maps Every Lean Project Needs

The current state map shows what is. The future state map shows what is possible. The gap between them is where the improvement work lives.

Why you need both

A current state map without a future state is a diagnostic without a plan. You know what is wrong but not what you are building toward. A future state without a current state is a fantasy. You know what you want but have no grounded understanding of the gap you need to close.

The power of VSM is in holding both maps in the same room. The current state shows the waste clearly. The future state shows the same process with the waste removed. The team can see the gap. The gap becomes the project plan.

Building the current state

The current state maps what is actually happening today. Not the procedure. Not the ideal. What actually happens when you observe the process. Every step, every delay, every piece of WIP, every information flow. The facilitator's job is to keep asking: is that what actually happens? until the map is honest.

Data fields — cycle time, wait time, WIP, defect rate, uptime — come from direct observation during Phase 2. The current state is not complete until every major step has measured data, not estimates.

Building the future state

The future state is designed, not observed. The team asks: given what we now know about waste and constraint, what would this process look like if we eliminated the highest-impact problems?

Future state design rules: set takt time as the ceiling. Eliminate NVA steps where possible. Reduce WIP to the minimum needed for stable flow. Establish pull systems where push creates batching problems. Introduce pacemaker scheduling at or near the constraint.

The gap is the project backlog

Every difference between the current state and the future state is a project or an action. Eliminate step 4 entirely — that is a project. Reduce WIP at step 7 from 40 to 5 — that is a project. Introduce kanban between steps 9 and 10 — that is a project.

Prioritise by impact on the constraint. Every action that does not address the current constraint is background improvement. Start with the actions that move the needle on lead time or throughput, because those are the metrics the customer feels.

Version history is the improvement story

Every time a future state is implemented, it becomes the new current state and a new future state is designed. The progression of current state maps over time is the measurement of how the organisation is improving. VeSiMy stores every version permanently so the improvement story is always visible.