Method
A side-by-side map of current-state reality and target future-state outcomes.
Choose this if
This method works when aligning on where you are now and what better looks like.
Pack = one session you can run now. Workspace = a saved thread for method choice, planning, and shareable outputs.
What Workspace helps you carry forward
Artifact preview
Current/future state map
Align · Moderate
Decide fit before you spend session time.
Room fit check
Best when the room needs one concrete change narrative that makes the current state and desired future state comparable enough to guide decisions. This room has enough of the right conditions for the method to hold without extra ceremony.
Primary risk: The future state becomes aspiration theatre instead of a practical shift in outcomes or behavior.
The core facilitation flow, with enough structure to run the method confidently in the room.
Standard setup for Mixed in remote delivery.
Total planned time: 120 min
What happens
Describe current behavior, metrics, and pain points.
Facilitator does
Build current state from evidence: data, artefacts, direct observation, or recent interviews. Stop the room if baseline description becomes aspirational or critical without evidence. A current state that is partly fictional produces a delta map that describes aspiration, not change.
Participants do
Contribute evidence you have directly seen or measured — operational data, customer feedback, direct observations. Aspirational or critical descriptions of current state that aren't grounded in evidence belong in a separate "perception" column, not in the current-state map.
Output / signal of success
The group is aligned on the exact challenge, actor, or scope the rest of the method will serve.
Watch for
Baseline incorporates wishful interpretations of how things currently work.
Recovery tip
If the current-state map is diverging into debate about causes or fixes, park those contributions in a "parking lot" column and return to them after target state is established. The baseline must be agreed before the delta can be measured.
What happens
Agree future outcomes and success signals.
Facilitator does
Write target state in behavioral terms — what people will be doing differently, not what the product will do. Ask 'What changes in the room, in the field, or for the customer?' for each element. Reject any target state item that is a feature description without a human outcome behind it.
Participants do
Write each target state item as a statement about what a specific person or team will be doing differently. For anything that sounds like a product capability, ask yourself: who is doing what differently as a result? That answer is the target state.
Output / signal of success
Gap analysis
Watch for
Target state is written as product features rather than human behavior changes.
Recovery tip
For any target state item that describes a product feature or a delivery milestone, ask: "Who is doing something differently, and what are they doing?" Write the behavior change as the target state. The product is the means — the human outcome is the target.
What happens
Map capability, process, and behavior gaps.
Facilitator does
Place current and future state side by side and compare systematically. Name each gap, its size, and who is responsible for closing it. Unstated dependencies between deltas — where closing one gap creates or requires another — need to be explicit before sequencing.
Participants do
For each delta, name the specific team or role responsible for closing it, and flag any gaps that can't close until another gap closes first. Dependencies made visible now will save sequencing failures later.
Output / signal of success
Transition priorities
Watch for
Deltas are described at too high a level to drive specific actions.
Recovery tip
For any delta described too broadly to drive a specific action, ask: "What specifically would have to change in this team's daily work for this delta to close?" Write the specific operational or behavioral change, not the summary.
What happens
Prioritize near-term moves and ownership.
Facilitator does
Order deltas by dependency (what must be true before each step can start) and by confidence (what can the team actually control?). Check whether the sequence survives if the first step takes twice as long as expected. Name blockers explicitly rather than burying them as risks.
Participants do
Assign a named owner role to every transition step before the session closes. If a step has no owner candidate in the room, flag it as a dependency to be resolved — not a step to be sequenced.
Output / signal of success
Current/future state map
Watch for
Sequence is aspirational rather than based on actual dependencies and constraints.
Recovery tip
For each aspirational sequence, ask: "What would need to be true for step 1 to start?" If the answer involves budget, decisions, or access that aren't confirmed, that's a blocker — name it as a dependency rather than embedding it silently in the sequence.
Prepare the room, the evidence, and the working surface so the session can stay focused on synthesis.
Data, metrics, or direct observations that describe the current state with enough specificity to make the gap measurable. Without evidence-backed current state, the map describes a fictional baseline and the delta analysis produces aspirational rather than actionable transition steps.
Current-state metrics
Optional
Target outcomes
Optional
Mapping canvas
Optional
Capability gap checklist
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.
Remote facilitation choreography
Required
Pre-plan handoffs, breakout usage, and how people rejoin the main board.
Shared digital board with timer and voting
Required
Keep instructions and voting visible at all times.
Current-future map
Keep the output usable, then use the recovery guidance when the room starts drifting.
What this does not produce
Current vs Future State Mapping produces a shared picture of the gap between where the organisation is and where it needs to be. It does not produce a delivery plan or a validated path — the transition steps it generates need resourcing, prioritisation, and dependency resolution before they can become commitments.
Failure mode
Why it happens
Transformation programs use aspirational language — "a seamless customer experience," "a data-driven culture" — because it's easier to get agreement on a vision than on the specific behaviors that would constitute evidence of it. When the future state map reflects that aspirational language, the gap analysis produces transition steps like "improve collaboration" and "build data literacy" — statements that are directionally true but too abstract to implement.
Recover now
If this happens, for each future state item, ask: "What would we see a specific person doing differently if this were true?" Rewrite the item as a behavioral description. "A data-driven culture" becomes "product managers can access and interpret usage data independently without requesting reports from the analytics team."
Prevent next time
Next time, before Step 2 opens, write the behavioral evidence test on the board: "What would a specific person be doing differently?" Apply it to every future state item as it's added.
Failure mode
Why it happens
Participants describe the current state they aspire to or the state they believe it should be, rather than the state as evidenced by data and observation. This produces a current state map that's partly fictional — and a delta map that describes a smaller gap than actually exists. The transition plan is scoped for the fictional gap, not the real one.
Recover now
If this happens, for each current state item, ask: "What evidence do you have for this?" If the answer is "that's how it should work" or "I think most people do it that way," mark the item as an assumption and flag it for verification. An evidence-free current state is a hypothesis, not a baseline.
Prevent next time
Next time, open Step 1 by separating "observed reality" from "how it's supposed to work" as two explicit lanes. Build the map from the observed reality lane first. The second lane is useful context, but it's not the baseline.
Failure mode
Why it happens
The mapping session produces a clear picture of the path from current to future state and participants feel the work is done. The ownership step feels like administration rather than substance and gets compressed or skipped at the end of a long session. The transition map is shared in a presentation but never converted into committed work.
Recover now
If this happens, hold the room at Step 4 until every near-term transition step has a named owner and a first action. If an owner can't be named, that step needs an escalation before the session closes — it's not a task, it's a decision.
Prevent next time
Next time, put the ownership column on the transition map before the sequencing step begins. It's easier to assign owners while the sequence is being built than to retrofit them at the end of a tired room.
Change the shape of the session only after the fit and runbook are clear.
Standard variant for Mixed in remote delivery. Waypoint is adapting timing, facilitation emphasis, prep, and recovery guidance here, but the room still needs final tailoring to the exact stakes and participants.
Use this after you have checked the fit and know you want to carry the method forward.
The pack is the fastest way to run this now. Use the links below when you need prep, sharing, or a saved reference point.
Guides
The book explains why teams need a legible current-to-future delta in displacement work: customers rarely move until the present path looks less defensible than the disruption of changing.
Open this when you want stronger rationale before choosing the method or taking it into the workspace.
A planner-led brief on how to make incumbent replacement feel safer than standing still by building a stronger case for change, mapping the stakeholder coalition, and sequencing the path to decision.
Sources and references used in this method page.
Prosci change management planning references.
Facilitation approaches for alignment and shared framing.
Reviewed 2026-02-27 by Discovery Waypoint Editorial Team
Related playbooks
These pages translate recognizable external methods into Waypoint-native guidance so the team can borrow the useful part without importing the whole mythology.
A facilitator-grade health check that is useful only if the red signals turn into named repairs immediately.
Open when Teams that can feel friction but cannot yet name where the damage really sits.
A practical team-norm setting play that only works if the agreements stay behavioral, specific, and reviewable.
Open when Recurring collaboration issues keep slowing delivery, handoffs, or workshop quality.
Use the Design Kit as a broad field guide for choosing a move category, then switch back into Waypoint once the team knows the sharper method it actually needs.
Open when A team needs method breadth, especially early in a project or while building HCD literacy.
