Current state maps document how the value stream actually operates today including all existing waste, inventory accumulation, and disconnected operations, making visible where flow stops through accurate representation of material movement, performance metrics, and timeline data. Future state maps design how the value stream should operate after implementing specific lean improvements achievable within 6 to 12 months, showing continuous flow, pull systems, and reduced inventory. The two maps work together as diagnostic and prescriptive tools where the current state reveals what needs fixing by exposing flow problems and quantifying waste magnitude, while the future state defines the target condition and improvement roadmap showing which specific changes to implement.
Understanding the fundamental difference between these map types, when to create each, how to design future state systematically using lean principles, and how to bridge the gap through action planning determines whether value stream mapping produces measurable business results or becomes documentation exercise that generates no improvement.
Key Insight: Current state maps diagnose problems by documenting actual waste and flow disruptions through gemba observation. Future state maps prescribe solutions showing achievable improvements within 6-12 months using structured design methodology. Both are essential working together as a diagnostic and prescriptive system.
What Current State and Future State Maps Are
Value stream mapping uses two primary map types serving different but complementary purposes in the transformation process.
Current State Map: Documenting Actual Reality
The current state map captures how the value stream actually operates today with complete honesty about performance including all waste, delays, and disconnects observed during gemba walks. The map shows process boxes for each operation with data boxes containing measured cycle times, changeover durations, uptime percentages, and operator counts. Inventory triangles reveal where material accumulates. Push arrows indicate disconnected operations producing to schedule rather than downstream consumption. The timeline quantifies total lead time and value-added time percentage.
The current state map makes problems visible that aggregate production reports obscure. Reports showing acceptable throughput may hide that products spend 95 percent of lead time waiting rather than being transformed, revealed through a timeline showing days of lead time versus minutes of processing time.
Future State Map: Designing Achievable Target
The future state map shows how the value stream should operate after implementing specific lean improvements within 6 to 12 months. This is not a wish list but a realistic target achievable given current organizational capability and available resources. The map applies lean principles systematically through eight structured questions: connecting operations via pull systems, leveling production to smooth demand variation, implementing quick changeover enabling small batches, creating continuous flow where possible, and positioning single pacemaker process.
The future state serves as a blueprint for transformation showing exactly what the value stream will look like after improvement projects complete. Without a future state providing clear target vision, improvement efforts fragment across unconnected initiatives pursuing different visions.
The Ideal State Concept
Some practitioners create a third map type called ideal state showing the ultimate perfect process if no constraints exist. This represents the absolute best achievable assuming unlimited resources and perfect conditions. The ideal state serves as long-term vision preventing teams from settling for incremental improvements when breakthrough changes are possible.
The recommended sequence is current state documenting reality, ideal state showing perfect vision, then future state defining achievable next step toward ideal. Skipping the ideal state often results in future states that are too conservative merely fixing obvious problems rather than fundamentally redesigning flow.
Key Insight: Current state documents actual reality with complete honesty about waste and performance. Future state designs achievable targets in 6-12 months applying lean principles through structured questions. Ideal state shows ultimate vision preventing conservative future state.
Why Both Maps Are Needed Together
Current and future state maps serve complementary purposes where each addresses critical limitations the other cannot overcome when used independently.
Current State Alone Cannot Drive Improvement
Current state mapping alone identifies problems but provides no guidance about solutions or implementation priorities. Teams creating only current state maps recognize that inventory accumulates, batch sizes exceed daily demand, and changeover times force large production runs. This diagnostic capability is valuable but insufficient because it does not answer which problems to address first, what specific improvements to implement, or what performance improvement is achievable.
Without a future state providing a target and roadmap, improvement efforts pursue scattered initiatives. One manager implements 5S, another pursues TPM, a third installs kanban. These tools may address real problems but lack coordination toward cohesive flow-based operation. Resources spread across disconnected projects producing minimal business impact.
Future State Alone Produces Unrealistic Designs
Future state mapping without accurate current state produces unrealistic designs disconnected from actual constraints. Teams that skip current state base future state on assumptions rather than measured reality. They propose improvements addressing problems that do not actually limit flow or design solutions requiring capabilities the organization has not developed.
The future state becomes a wish list when designers do not understand current performance gaps, equipment limitations, workforce skill levels, or information system constraints. Implementation fails when teams encounter unexpected barriers the current state would have revealed through systematic gemba observation and data collection.
How the Two Maps Work as System
Current and future state maps work as integrated systems where the current state provides a diagnostic foundation enabling realistic future state design, and the future state provides a prescriptive target giving current state business purpose. The current state reveals which wastes dominate the value stream, where flow stops, and what capability gaps exist. This understanding informs future state design ensuring improvements address actual limiting constraints.
The future state defines target conditions making current state problems actionable by showing how they will be resolved and quantifying expected improvement magnitude. The gap between current and future state generates the action plan showing which projects to pursue, in what sequence, with what resources.
Key Insight: Current state alone identifies problems without solution guidance. The future state alone proposes improvements disconnected from reality. Together they form a diagnostic and prescriptive system where current reveals problems, future defines achievable solutions, gap generates action plan.
When to Create Current and Future State Maps
The sequence and timing of map creation follows a structured approach preventing common mistakes that undermine improvement effectiveness and waste team time.
Always Create Current State First
Create the current state map before attempting future state design without exception. This sequence ensures future state proposals address actual problems revealed through observation rather than assumed issues based on incomplete understanding. The current state mapping process builds team knowledge about how the value stream actually operates, what constraints exist, where problems concentrate, and what capability is currently available.
Current state creation timing: Schedule 1-2 day workshop for gemba observation and data collection. Allow 1 week after the workshop for validation with operators and data verification. Present to leadership within 2 weeks of workshop for problem recognition and resource commitment. Complete the entire current state process including validation and leadership review before beginning future state design.
Attempting to create a future state simultaneously with the current state prevents the team from developing a deep understanding of existing problems. The future state design requires knowing not just that problems exist but understanding their magnitude, root causes, interdependencies, and why they persist. This knowledge emerges from systematic current state mapping including multiple gemba walks, performance data collection, and timeline analysis.
Schedule Future State After Reflection Gap
Schedule future state design workshop 1 to 2 weeks after completing current state validation and leadership review. This gap serves multiple purposes: allows teams to reflect on current state problems and begin considering potential solutions, prevents workshop fatigue from attempting both maps in a compressed timeframe, enables leadership input on resource availability and strategic priorities before future state design begins.
Future state design timing: Wait 1-2 weeks after current state completion before future state workshop. Schedule 1-2 day workshop for systematic future state design using eight questions. Use the same core team that created the current state maintaining knowledge continuity. Complete draft future state within the workshop then refine based on leadership review and technical validation.
The team that creates the current state should design the future state because they possess detailed process knowledge and shared understanding of problems revealed through direct gemba observation. Introducing new participants requires re-educating them on current reality the original team already understands, wasting time and reducing future state quality through diluted knowledge.
Update Maps as Implementation Progresses
Treat future state as a rolling 6-12 month target that updates as improvements implement rather than a static endpoint that becomes outdated. As action plan projects complete, update current state map to reflect new reality and adjust future state to maintain 6-12 month projection forward. This rolling approach prevents future state from becoming outdated documents reflecting conditions that no longer exist.
Map update frequency: Update current state every 3-6 months as major improvements complete changing baseline reality. Adjust future state simultaneously to maintain 6-12 month forward projection. Create a new current state after achieving the previous future state becoming a new baseline. Continue this cycle as value stream transformation progresses over years toward ideal state vision.
Key Insight: Always create current state before future state ensuring realistic design based on observed reality not assumptions. Schedule future state 1-2 weeks after current state allowing reflection while maintaining team continuity. Update both maps every 3-6 months as improvements implement keeping projections current.
How to Design Future State Maps Systematically
Future state design follows structured methodology applying lean principles through eight questions answered in sequence rather than unstructured brainstorming.
The Eight Future State Design Questions
The eight questions build on each other where later answers depend on earlier decisions, making the sequence essential.
Question 1: What is takt time? Calculate customer demand rate converted to available time per piece. Divide available production time by customer demand establishing production pace to meet demand without overproducing. Takt time becomes the heartbeat pacing flow throughout the value stream.
Question 2: Will you build a finished goods supermarket or ship directly to orders? Determine whether production creates an inventory buffer for customer pull or produces only when orders arrive. High-mix low-volume typically requires finished goods from the supermarket. Low-mix high-volume may enable direct production to orders.
Question 3: Where can you use continuous flow? Identify which operations can connect for one-piece flow where products move directly between processes without batching. Continuous flow eliminates inventory, reduces lead time, and exposes problems immediately. Connect operations with similar cycle times close to takt time.
Question 4: Where will you use pull systems to control production? Position pull signals using kanban at points where continuous flow is not feasible due to batch operations, geographic separation, or incompatible process speeds. Pull systems authorize upstream production only when downstream consumption occurs.
Question 5: What is the pacemaker process? Select a single point where the production schedule will be set. All upstream processes respond to pacemakers through continuous flow or pull signals. A typical pacemaker is final assembly or the process of feeding finished goods to the supermarket.
Question 6: How will you level the production mix at the pacemaker? Design production leveling smoothing variation in product mix and volume through heijunka. Level loading prevents feast-and-famine cycles batch production creates.
Question 7: What increment of work will you consistently release? Determine pitch increment controlling work release frequency. Pitch equals takt time multiplied by pack quantity. Smaller pitch enables faster response to problems.
Question 8: What improvements will be necessary to enable flow? Identify specific kaizen improvements required. Mark these in future state using kaizen burst symbols. Common improvements include changeover reduction enabling small batches, quality improvement preventing defects, equipment reliability through TPM, and layout changes enabling continuous flow.
Applying Questions to Create Design
Work through the eight questions systematically using current state data and lean principles. The questions are not optional or interchangeable because later answers depend on earlier decisions. Determining pull system locations requires knowing where continuous flow will be implemented. Identifying pacemakers requires understanding pull system structure.
Document answers directly on the developing future state map. Show continuous flow as connected process boxes without inventory. Indicate pull systems with pull arrows and kanban symbols. Mark pacemaker clearly. Add kaizen bursts at operations requiring improvement.
Key Insight: Future state design uses eight structured questions answered in sequence applying lean principles. Questions determine takt time, inventory positioning, continuous flow locations, pull systems, pacemaker, leveling, pitch, and required improvements. Sequence essential because later answers depend on earlier decisions.
Common Future State Design Mistakes
Teams designing first future state maps make predictable errors that reduce improvement impact or create unachievable targets.
Designing Future State Too Conservatively
The most common mistake is a future state that merely fixes obvious problems without fundamentally redesigning flow. Teams identify inventory accumulations and reduce quantities 50 percent, see long changeovers and target 30 percent reduction, observe batch production and propose slightly smaller batches. These incremental improvements fail to transform flow because they accept the existing push system rather than replacing it with pull.
Conservative future states result from skipping ideal states or failing to apply lean principles systematically. Without ideal state vision challenging assumptions, teams propose safe improvements requiring minimal change. Without structured questions forcing decisions about continuous flow and pull, teams default to optimized push rather than redesigned pull.
The correction is revisiting the future state with explicit instruction to design pull-based flow. Ask whether each operation connects to downstream through continuous flow or pull. Challenge any push arrows remaining requiring justification for why pull is not feasible.
Proposing Unrealistic Transformation
The opposite error is a future state requiring unavailable capabilities, resources, or changes impossible given constraints. Teams propose layouts requiring capital not budgeted, automation requiring expertise unavailable, or pull systems requiring IT the organization cannot implement in 6-12 months.
Unrealistic future states result from inadequate current state understanding about constraints and capabilities. Teams know problems exist but not why they persist or what resolving them requires. Future state becomes a wish list when designers do not understand implementation requirements.
The correction is validating future state with operations management, maintenance, engineering, and IT before finalizing. Ask whether proposed improvements are achievable given current capability and available resources within 6-12 months. Adjust future state to realistic targets or extend timeframe.
Failing to Indicate Implementation Sequence
Some future states show disconnected improvements without indicating implementation sequence or dependencies. The map displays kanban, reduced changeovers, cellular layout, and leveling simultaneously without showing which implements first. This creates confusion about where to start.
Future state should indicate implementation phases through annotations showing sequence: reduce variation through leveling, prevent overburden through capacity and standard work, implement pull systems, create continuous flow, then pursue efficiency improvements.
Key Insight: Common mistakes include overly conservative future states optimizing push rather than designing pull, unrealistic transformations disconnected from capability, and showing disconnected improvements without sequence. Correct by applying lean principles aggressively, validating feasibility with operations, and indicating improvement phases.
Within the Lean System
Current and future state value stream mapping sits at the core of lean transformation methodology providing diagnostic and prescriptive tools guiding which lean practices to implement and where to apply them for maximum flow improvement.
Connection to Lean Principles
The future state design process directly applies the five lean principles through the eight questions. Specify value by calculating takt time matching customer demand rate. Identify value stream through current state mapping documenting actual material and information flow. Create flow by determining continuous flow locations and pull system positioning. Establish pull through kanban design connecting operations to downstream consumption. Pursue perfection through kaizen bursts identifying required improvements enabling future state capabilities.
Connection to Lean Tools
Current and future state maps determine which lean tools the value stream needs rather than applying tools generically. The current state reveals problems through symbols and timeline data. The future state prescribes tools resolving those problems. Large inventory triangles between similar-cycle-time operations indicate cellular layout and line balancing needs. Long changeover times indicate SMED need. Batch sizes exceeding daily demand indicate heijunka need. Push arrows throughout the map indicate the pull system and kanban needs. The maps prevent generic tool application by diagnosing specific problems requiring specific countermeasures.
Connection to Continuous Improvement
The mapping cycle provides structure for continuous improvement converting it from scattered activity into systematic transformation. The current state establishes a baseline and identifies improvement opportunities through problem visibility. Future state defines target and improvement roadmap showing desired condition. Action plan structures kaizen activity toward a cohesive goal. Map updates every 3-6 months track progress and adjust targets maintaining improvement momentum over years.
Q&A
Q: Can you create a future state before completing the current state?
No. Future state design requires understanding current performance, constraints, and capability that only comes from thorough current state mapping. Teams attempting future state first base designs on assumptions rather than measured reality producing unrealistic targets disconnected from actual problems. Always complete and validate current state including gemba observation, data collection, and leadership review before beginning future state design ensuring proposals address real constraints.
Q: How long should the future state remain valid before updating?
Future state represents a 6-12 month target remaining valid until major improvements complete or business conditions change significantly. Update future state every 3-6 months as action plan projects finish, adjusting target to maintain 6-12 month forward projection. When the previous future state becomes current reality, create a new current state map establishing an updated baseline then design a new future state maintaining transformation momentum.
Q: Should future state show incremental or breakthrough improvement?
Future state should show breakthrough improvement transforming flow not incremental optimization of existing push production. Create an ideal state map first showing ultimate vision unconstrained by current limitations. This prevents future state from being too conservative merely fixing obvious problems rather than fundamentally redesigning the value stream. Future state bridges current and ideal showing achievable next step toward ideal within 6-12 months.
Q: What if leadership rejects the future state as too aggressive?
Present three options showing trade-offs: aggressive future state with larger resource requirements and longer timeline, moderate future state achievable with current resources in 6-12 months, conservative future state requiring minimal resources but producing limited improvement. Let leadership choose based on strategic priorities and available investment. If a moderate proposal is rejected, ask which constraints prevent improvement and what changes would enable it.
Q: How do you handle multiple product families requiring different future states?
Map each product family separately creating distinct current and future state pairs. Different products with different process sequences cannot share a single map without creating confusion. Start with the highest-volume family or most strategic importance. After implementing improvements for the first family and demonstrating results, map the next family applying lessons learned. Eventually the organization builds a portfolio of value stream maps each showing a transformation roadmap.
LeanSuite: A complete lean manufacturing software
Schedule Demo
