Situation
Surface and mitigate critical failure modes before launch.
Use this before major launches or transformation milestones where failure costs are high. It is useful when teams need a shared risk posture quickly.
Start with Pre-mortem / Risk Storming for this situation unless the initiative is too early to discuss execution risk.
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: Top risks are ranked by impact and likelihood.
You are choosing the clearest path over broader comparison work in 60-120 min.
Risk register
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.
Assumption heatmap
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.
Prioritization matrix
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: Optimism bias in a risk session is often a rational response to political pressure, not just a personality trait. Stakeholders who know that naming a risk can slow or stop a project they want to succeed will systematically underrate likelihood and impact. The method needs to create conditions where naming risks feels safe — not just encouraged.
What changes: If optimism bias is strong, use anonymous individual risk generation before any group scoring. If the room is senior-heavy, have each person submit their top risk privately before revealing to the group. If the bias is systematic across the organisation, name it explicitly before the session opens: "Our job today is to find the risks that are actually there, not the risks that are politically comfortable to name."
Why it matters: Without a risk ownership model, identified risks stay on a list rather than becoming managed commitments. The session produces a risk register that's accurate at the moment of creation and ignored by launch — because nobody was made accountable for any item on it.
What changes: If no ownership model exists, establish one as a session output before discussing specific risks. Define who has authority to own a mitigation before naming the mitigations. If ownership is structurally unclear, that is itself a risk that should be on the register.
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 side-by-side map of current-state reality and target future-state outcomes.
Current/future state map
Avoid this when the change objective is already fixed and funded.
Compare this methodWatch for these signals in the room and use the paired fix before the session drifts.
What it looks like: Everyone places risks as moderate likelihood — the heatmap is flat with no differentiation, the facilitator cannot find enough genuine disagreement to work with, and the session produces a tidy document that nobody takes seriously because it doesn't reflect what people actually believe privately.
Fix: Prioritize risks by impact and likelihood before mitigation design.
What it looks like: High-impact risks are identified and agreed but ownership is deferred to "the team" or "whoever is responsible for this area" — without named individuals, no mitigation action happens before launch and the risk register becomes a historical document rather than a live commitment.
Fix: Assign one owner and trigger signal to every mitigation item.
What it looks like: The session runs out of time before escalation triggers are defined, the follow-up meeting to complete the register never gets scheduled, and the launch proceeds without anyone knowing what signal would cause a pause, a scope change, or a rollback decision.
Fix: Schedule the first risk review checkpoint before closing the workshop.