═══════════════════════════════════════════════════════════════
DISCOVERY WAYPOINT — CURRENT VS FUTURE STATE MAPPING
Current/future state map | 90–120 min | 5–12 people | Difficulty: Moderate
discoverywaypoint.com/techniques/current-vs-future-state-mapping
═══════════════════════════════════════════════════════════════

BEFORE YOU START
  Program / transformation: ______________________________
  Date: _______________  Facilitator: _____________________
  Scope (what process or experience are we mapping?): _____
  Decision this map must unlock: _________________________

⚠ Anchor current state with evidence, not memory.
  Bring: current metrics, complaints, and incident data.

───────────────────────────────────────────────────────────────
STEP 1 — SUCCESS DEFINITION  [0–20 min]
───────────────────────────────────────────────────────────────
  Success metric (measurable): __________________________
  Success horizon (when?): ______________________________
  Who decides if we've succeeded? _______________________

───────────────────────────────────────────────────────────────
STEP 2 — CURRENT STATE  [20–55 min]
───────────────────────────────────────────────────────────────
  How it works today:
  __________________________________________________________

  Key metrics today:
  __________________________________________________________

  Friction and pain (with evidence source):
    1. _______________________________________ | Source: ___
    2. _______________________________________ | Source: ___
    3. _______________________________________ | Source: ___
    4. _______________________________________ | Source: ___

  Workarounds people use (signals of unmet needs):
  __________________________________________________________

  Teams and systems involved:
  __________________________________________________________

⚠ "It's always been this way" is not evidence.
  If you can't name a source, mark it as assumption.

───────────────────────────────────────────────────────────────
STEP 3 — FUTURE STATE  [55–90 min]
───────────────────────────────────────────────────────────────
  How it would work:
  __________________________________________________________

  Target metrics (specific and testable):
  __________________________________________________________

  What users would experience differently:
    1. _______________________________________________________
    2. _______________________________________________________
    3. _______________________________________________________

  What internal operations would change:
    1. _______________________________________________________
    2. _______________________________________________________

  What does NOT change (scope boundary):
  __________________________________________________________

⚠ "Better, faster, easier" is not a future state.
  Write a measurable outcome. If you can't measure it, refine it.

───────────────────────────────────────────────────────────────
STEP 4 — GAP ANALYSIS + TRANSITION ACTIONS  [90–120 min]
───────────────────────────────────────────────────────────────
  Gap                           | Type                | Priority
  _____________________________ | Process/Tech/People | H / M / L
  _____________________________ | Process/Tech/People | H / M / L
  _____________________________ | Process/Tech/People | H / M / L
  _____________________________ | Process/Tech/People | H / M / L

  First transition moves:
  Action                          | Owner       | Date
  ______________________________ | ___________ | ______
  ______________________________ | ___________ | ______
  ______________________________ | ___________ | ______

⚠ No owner = won't happen. Assign before you close.

───────────────────────────────────────────────────────────────
QUALITY CHECK
───────────────────────────────────────────────────────────────
  ☐ Current state anchored in evidence, not opinion
  ☐ Future state has at least one measurable success signal
  ☐ Every gap has a type (Process / Tech / People)
  ☐ Every transition action has a named owner and due date
  ☐ Scope boundary is explicit

Full facilitation guide: discoverywaypoint.com/techniques/current-vs-future-state-mapping
Discovery Waypoint — discoverywaypoint.com