Situation
Create shared direction when sponsors and delivery teams diverge.
Use this when cross-functional groups interpret goals differently or ownership is fragmented. It works best before major investment, roadmap shifts, or operating model changes.
Start with Stakeholder Mapping for this situation unless you only need task-level delivery tracking.
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: A shared problem statement is accepted by all parties.
You are choosing the clearest path over broader comparison work in 90-120 min.
Stakeholder influence 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.
Experience principles
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.
Problem statement
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: If senior stakeholders leave early, the problem statement agreement happens without their input — and the "aligned" output gets overridden in the first review meeting back. Alignment built without the people who hold the authority to commit is fragile.
What changes: If senior availability is severely limited, front-load the problem statement agreement to the first 30 minutes while they are present. If executives can attend fully, the deeper Problem Framing route earns more robust alignment that holds after the session.
Why it matters: When teams use different success metrics, they can appear to agree on a problem statement while each team is still optimising for a different outcome. The alignment is semantic rather than real. This won't surface during the session — it surfaces in the first cross-team planning cycle after it.
What changes: If metrics divergence is known, build a shared success definition step into the session before any problem statement is written. If the divergence is strategic rather than definitional, the real conversation is about competing organisational priorities — name that before running a framing 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.
Use these only if the recommended route is blocked by room shape, confidence, or stakeholder availability.
Fallback 1
A translation workshop that maps experience principles to behavioral measures and leading indicators so teams can track whether principles are actually delivered.
Principle-to-metric map
Avoid this when no agreed principles are in place.
Compare this methodWatch for these signals in the room and use the paired fix before the session drifts.
What it looks like: The senior sponsor leaves early, the remaining group builds a problem statement without their input, and the "agreed" framing gets overridden in the first review meeting back.
Fix: Pause solutioning until one shared problem statement is accepted.
What it looks like: Teams nod at the shared problem statement but describe success differently when asked — one says conversion rate, another says satisfaction score, another says delivery velocity — revealing that each team is still optimising toward their own metric.
Fix: Get each critical stakeholder role to confirm commitments in-session.
What it looks like: The session produces an output that feels agreed in the room but the same misalignment resurfaces in the first cross-team status meeting, because the root cause was a political or structural conflict rather than an information gap.
Fix: Close with a communication owner and message summary for each audience.
Related playbooks
Use these when the room keeps reaching for a famous company method and you need the practical translation: what to borrow, what not to imitate, and which Waypoint move should take over next.
Atlassian Team Playbook
Known here for practical team plays with visible facilitation structure.
Use this when you need to surface where trust, ownership, or momentum is breaking before the room drifts into vague morale talk.
Best when
Teams that can feel friction but cannot yet name where the damage really sits.
Atlassian Team Playbook
A short play for turning vague collaboration complaints into explicit team agreements that can be tested later.
It gives teams a way to stop re-litigating the same collaboration friction in ad hoc conversations.
Best when
Open it when recurring collaboration issues keep slowing delivery, handoffs, or workshop quality.
Apple directly responsible individual practice
Known here as a famous ownership idea with much weaker public documentation than people assume.
Use this when the ownership question matters but you want to avoid founder-folklore certainty.
Best when
Teams that need sharper ownership language without overclaiming a famous company’s method.