Situation
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.
Start with Customer Journey Mapping for this situation unless the scope is one internal process only.
Choose the structure that keeps trade-offs visible and forces the room to land somewhere explicit.
Open the method first if you need to judge the format. Start a workspace when this needs method fit, a session plan, and shareable follow-through in one saved thread.
Start with one method now, then compare a lighter or deeper route only if the room shape changes.
Recommended first
Choose this when the session goal is: Map boundaries and critical moments are agreed.
You are choosing the clearest path over broader comparison work in 2-4 hours.
Current-state journey map
Open methodIf time is tight
Use this when you need a credible move quickly and cannot support a heavier room shape.
You gain speed, but you accept a lighter evidence base or less breadth in the room.
Service blueprint
Open methodIf you need more depth
Use this when the room can spend more time building shared understanding before committing.
You gain more context and stronger buy-in, but the session asks for more time and facilitation energy.
Current/future state map
Open methodIf the session is working, these are the signals you should be able to point to by the end.
Use these questions to confirm this is the right room before you commit to the method.
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.
Why it matters: Uneven process knowledge means parts of the map will be accurate and parts will be assumption or approximation. If this isn't managed explicitly, the most vocal participants fill the knowledge gaps with their version of the process — and the map becomes a political document rather than a shared picture.
What changes: If knowledge is highly uneven, run a pre-session evidence gathering step and brief participants to bring their specific section of the process before the session. If one team dominates the knowledge, use silent sticky note generation before any group discussion to surface what others know independently.
Why it matters: When the scope is too large for one session, the facilitator faces a choice between a shallow pass across the full journey or a deep pass across a scoped section. Getting this wrong produces a map that is either too abstract to drive action or too narrow to show the real end-to-end picture.
What changes: If the scope is genuinely large, agree the primary flow boundaries before the session opens — decide start and end points with the session owner before anyone enters the room. If detail pressure is from stakeholders wanting completeness, introduce a "primary flow" and "edge case backlog" as two separate artifacts before the session structure is agreed.
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.
Use these only if the recommended route is blocked by room shape, confidence, or stakeholder availability.
Fallback 1
A field observation method where teams experience or observe the service in context, capturing friction, workarounds, and emotional moments.
Observation notes
Avoid this when access or ethics constraints prevent observation.
Compare this methodWatch for these signals in the room and use the paired fix before the session drifts.
What it looks like: One team fills the map with their version of the process, another team pushes back with a different version, and the session spends 45 minutes debating which description is accurate rather than building a shared picture of what actually happens.
Fix: Timebox the primary flow and defer edge cases to a backlog lane.
What it looks like: The map grows to 8 stages with 12 substeps, participants stop engaging by stage 5 as the level of detail exceeds what the room can process, and the session ends with an exhaustive document nobody will maintain or use to drive decisions.
Fix: Add one action column to every mapped pain point before ending.
What it looks like: Two teams claim the process starts at different points, the map has two competing entry points neither team will concede, and the facilitator can't establish a shared scope boundary before the session runs out of time.
Fix: Mark an owner on each critical handoff directly on the map.