01 · Definition and why it matters
Definition and why it matters
A future-state process map describes how a process is intended to operate after improvement. It connects changes into a coherent flow rather than presenting isolated actions. In a warehouse, it should show both carton movement and the information that authorizes movement. The purpose is to make the proposed operating logic visible, including who decides, where work waits, and what happens when the normal route fails.
Use it when the change affects several handoffs, queues, or decision points. Prerequisites include an observed current-state map, a defined customer requirement, and enough knowledge of demand and capacity to assess the proposed design. A future-state map is a hypothesis about a better system, not a prediction established by drawing boxes. It should be specific enough to guide a pilot while flexible enough to change when real operation exposes mistaken assumptions.
02 · Start from demand and constraints
Start from demand and constraints
Fictional Northbank Dispatch handles 1,200 cartons during a 450-minute available dispatch day. The simple average demand interval is 450 × 60 / 1,200 = 22.5 seconds per carton. This interval provides context; it does not mean every workstation can or should finish a carton in exactly 22.5 seconds. Carton mix, arrival bursts, staff allocation, and carrier cutoff windows all affect workable capacity.
The current map shows label printing, staging, carrier identification, reassignment, and loading. Carrier identity often arrives after a carton is staged, creating searching and repeat movement. The future-state team includes the order-release owner and transport coordinator, because a warehouse-only map could simply move the delay upstream or load a carrier at the wrong time. They preserve required traceability and approved walking clearances as design constraints. The map boundary begins at dispatch release and ends at verified loading.
03 · Design material and information flows together
Design material and information flows together
Northbank proposes assigning a carrier and lane before label printing, printing carton identity and destination together, staging in the assigned lane, and confirming carton-to-lane agreement before loading. If the assignment changes, the system marks the carton as requiring review rather than quietly updating a screen while an old label remains attached. A named dispatcher owns the exception queue. This ownership prevents the exception route from becoming an unattended pile.
The team shows queue locations, maximum intended queue sizes, and review signals. A target of forty cartons in a carrier lane is a local design limit based on the approved layout and collection pattern, not a statistical control limit. The map also shows the information source and the decision rule for release. Without those elements, arrows can imply continuous flow while the real process still depends on an unanswered message or an informal permission.
04 · Worked capacity and queue interpretation
Worked capacity and queue interpretation
Observed label-and-assignment work averages eighteen seconds per carton under the proposed configuration. One continuously available station would have a nominal average capacity of 450 × 60 / 18 = 1,500 cartons per day, above the 1,200-carton average demand. That calculation does not prove adequacy at carrier peaks. At a peak of 180 cartons in thirty minutes, demand is six cartons per minute, while one eighteen-second station averages 3.33 cartons per minute. The gap requires buffering, a second station, or earlier release.
Northbank chooses earlier release for predictable carrier waves and a shared second station during the peak, subject to test. If a stable interval has average throughput of 160 cartons per hour and average in-process inventory of 80 cartons, Little’s Law gives an average flow time of 80/160 = 0.5 hours. The team uses that relationship only where the boundary, time period, and units match. It does not apply the average to a transient collection rush.
05 · Walk the map before changing the floor
Walk the map before changing the floor
The team traces routine, reassigned, unreadable-label, and network-outage cartons through the proposed map. Each trace identifies the information needed, the person authorized to act, and how the carton returns to normal flow. For an unreadable label, a controlled reprint is linked to the carton record and the damaged label is removed. For an outage, an approved manifest supports loading only within the defined fallback rules, with reconciliation afterward.
Operators then walk the proposed paths physically. A map may shorten logical steps while increasing walking or obstructing replenishment. The safety representative reviews lane space and interactions with forklifts. The transport coordinator checks collection timing. The systems owner checks whether assignments and exception statuses are actually available at the right moment. These reviews turn the map from a drawing into a testable operating design and expose dependencies for the implementation plan.
06 · Limitations, strong practice, and advanced use
Limitations, strong practice, and advanced use
Weak maps draw only the happy path, omit queues, label every task “automated,” or assume average capacity handles peaks. Strong maps show information and material movement, explicit decisions, exceptions, and operating boundaries. They distinguish target values from measured results and list unresolved design assumptions. A map should make disagreement easier to discuss, not conceal it under a polished future-state picture.
Advanced teams map different operating modes separately: routine dispatch, carrier peak, and degraded service. They may use event data to test queue assumptions while continuing to observe the floor. They also compare whole-order flow with carton-level flow, because faster cartons can coexist with delayed complete orders. Northbank’s map is reviewed after the pilot and after the first expansion wave. The intended future state remains a working design that must be reconciled with actual performance, operator feedback, and customer consequences.
07 · Operating conditions and evidence
Operating conditions and evidence
The map should make the release authority visible. Northbank’s proposed software assignment is not sufficient if operators still wait for an informal supervisor message before moving cartons. The team therefore distinguishes information availability from permission to act. Each decision point names the rule, the owner, and the record retained. This reduces ambiguity during both routine operation and exceptions.
The future state also needs a realistic transition. Installing lane markings before the assignment signal works can create a period where physical destinations imply certainty the information does not support. Northbank sequences configuration, verification, markings, and training so the floor and system tell the same story at go-live. The process map informs these implementation dependencies without pretending to be the schedule itself. After launch, observed queues and handoffs are compared with the intended flow. Differences are investigated before the diagram is revised to normalize an ineffective workaround.
08 · Decision record and next step
Decision record and next step
The map’s performance annotations should carry a measurement date or an assumption label. Northbank’s eighteen-second proposed station time is not confused with its current observed time, and the forty-carton lane limit is shown as a design constraint rather than actual inventory. This prevents the future-state drawing from appearing to describe achieved performance before implementation. When the pilot provides observations, the map can show the measured values with their operating scope.
A map also reveals decisions about work that is not ready. An order without a valid carrier assignment remains in an owned release exception rather than entering staging and becoming somebody else’s problem. The exception route needs visibility, review timing, and a release rule. Moving a queue upstream is useful only if it reduces unnecessary handling without hiding customer delay. Northbank therefore measures total dispatch-release-to-loading time as well as lane-level searching. The whole process boundary protects the customer outcome.
| Mapped element | Northbank design | Verification need |
|---|---|---|
| Release decision | Carrier and lane assigned before printing | Assignment exists before carton movement begins |
| Exception route | Named dispatcher owns unresolved assignments | No unattended queue or invisible stalled work |
| Peak capacity | Shared second station during collection burst | Observe queue and loading performance at the peak |
Connections
Related methods and phase use
Placed under Improve because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.