Skip to content

Situation

Map the current state end-to-end

Create a shared view of journeys, handoffs, and bottlenecks.

Use this when teams need one shared current-state picture before prioritizing improvements. It is effective when ownership or process understanding is fragmented.

Use this page to choose the method before you start planning the session.

Session risk to manage

Key risk: The map becomes descriptive and never drives action.

Prioritise the facilitation structure that keeps trade-offs explicit and closes with named ownership.

Common constraints

  • Cross-team process knowledge is uneven
  • Too much detail to fit one session
  • Stakeholders disagree on where flow starts/ends
  • Duration2-4 hours
  • Group size6-15 people
  • OutputCurrent-state journey map
  • RemoteRemote-friendly

What good looks like

Use these signals to keep the room aimed at the outcome before it drifts into discussion.

  • Map boundaries and critical moments are agreed.
  • Bottlenecks and ownership gaps are explicit.
  • Priority intervention points are identified.

Recommended techniques

Choose the route that matches the time you have, the room you can assemble, and the level of convergence you need.

  • 60-90 min

    Current vs Future State Mapping

    Best when you need a credible recommendation in one working session without expanding into a half-day format.

    Output artifact: Current/future state map

    Open recipe
  • 2-4 hrs

    Service Blueprinting

    Use when you have enough room to build shared understanding before committing to the shortlist.

    Output artifact: Service blueprint

    Open recipe
  • Exec alignment

    Customer Journey Mapping

    Use when the room needs stronger sponsor clarity, sharper trade-offs, or explicit ownership before moving on.

    Output artifact: Current-state journey map

    Open recipe

Qualifying questions

These questions are here to explain the recommendation logic, not just diagnose the room.

What decision should this session unlock by the end of the working block?

Why it matters: If the decision is vague, the room will drift into discussion instead of converging on a usable output.

What changes: If the answer is specific, Waypoint can recommend tighter decision formats. If it stays broad, Waypoint should push you toward framing or mapping first.

How real is the constraint around cross-team process knowledge is uneven?

Why it matters: Availability determines whether you can run a deeper co-creation format or need a tighter, more executive-friendly move.

What changes: If availability is genuinely tight, Waypoint should favor lighter formats. If the right room can attend, it should open up deeper working sessions.

Will too much detail to fit one session create friction in the room?

Why it matters: The biggest source of friction tells you where facilitation structure needs to do more work.

What changes: If the answer is yes, prefer formats that make trade-offs explicit. If not, Waypoint can recommend a lighter path with less convergence overhead.

What will you do if stakeholders disagree on where flow starts/ends remains unresolved during the session?

Why it matters: Some risks can be parked; others require a method that produces enough evidence or ownership before the group leaves.

What changes: If it cannot stay unresolved, Waypoint should bias toward techniques that leave owners, assumptions, or evidence checks visible before the room closes.

Risks and pitfalls

Start with the risks most likely to show up in the room, then use the fixes to keep the session on track.

Session risks to manage

  • Cross-team process knowledge is uneven
  • Too much detail to fit one session
  • Stakeholders disagree on where flow starts/ends

How those risks usually show up

  • Don’t map every edge case before agreeing primary flow.
  • Don’t treat mapping as documentation only without prioritised actions.
  • Don’t skip ownership mapping for critical handoffs.
  • Don’t map every edge case before agreeing primary flow.

    Fix: Timebox the primary flow and defer edge cases to a backlog lane.

  • Don’t treat mapping as documentation only without prioritised actions.

    Fix: Add one action column to every mapped pain point before ending.

  • Don’t skip ownership mapping for critical handoffs.

    Fix: Mark an owner on each critical handoff directly on the map.

More options

Use these when the recommended route is blocked by room shape, confidence, or stakeholder availability.

  1. #1

    Service Safari Observation

    A field observation method where teams experience or observe the service in context, capturing friction, workarounds, and emotional moments.

    Output artifact: Observation notes

    Avoid when: Avoid this when access or ethics constraints prevent observation.

    Open recipe