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 multiple problem narratives?
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 ambiguous success definitions 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 pressure to start building immediately 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
Multiple problem narratives
Ambiguous success definitions
Pressure to start building immediately
How those risks usually show up
Don’t write How Might We prompts before confirming the core problem statement.
Don’t define success as output volume instead of outcomes.
Don’t let scope creep hide unresolved assumptions.
Don’t write How Might We prompts before confirming the core problem statement.
Fix: Write and approve one core problem statement before creating prompts.
Don’t define success as output volume instead of outcomes.
Fix: Translate success into measurable outcomes with a timeframe.
Don’t let scope creep hide unresolved assumptions.
Fix: List top assumptions with owners and validation dates before close.
More options
Use these when the recommended route is blocked by room shape, confidence, or stakeholder availability.
#1
Value Proposition Canvas Workshop
A structured workshop using the Value Proposition Canvas to connect target customer jobs, pains, and gains with product/service pain relievers and gain creators.
Output artifact: Value proposition canvas
Avoid when: Avoid this when the target segment is undefined.