Situation
Test the riskiest assumptions before expensive delivery.
Use this when confidence feels high but evidence quality is low. Especially useful before committing budget or timeline.
Start with Assumption Mapping for this situation unless the initiative is purely operational with a mature evidence base — assumptions are known and well-tested; this method adds process without adding insight.
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: Critical assumptions are prioritized and testable.
You are choosing the clearest path over broader comparison work in 60-120 min.
Assumption heatmap
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.
Usability test plan
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.
Opportunity-solution tree
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: When research time is genuinely compressed, the method must produce testable outputs from a short session rather than a research plan that requires weeks to execute. The choice between methods depends on whether the team needs to map all assumptions first or can jump directly to testing the top known risk.
What changes: If time is extremely tight — days not weeks — the Usability Test Plan Workshop produces a test protocol immediately. If there is enough time for a structured mapping session, Assumption Mapping provides the prioritisation step first. If the critical assumptions are already known, skip the mapping session entirely and go directly to designing the test.
Why it matters: Without an agreed evidence threshold, teams decide assumptions are validated when internal opinion aligns — not when external evidence confirms. This means the validation plan produces a list of tests that get marked "passed" after a single conversation rather than after a systematic evidence-gathering process.
What changes: If no threshold exists, set one before the session ends: name what evidence type and what volume would be sufficient to move forward. If the threshold is disputed, that dispute is the real risk — resolve it explicitly rather than deferring it to the testing phase.
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 team spends the available research time testing assumptions they are already confident about — easy wins — while the genuinely uncertain assumptions that could invalidate the plan remain untested because they feel harder to test quickly.
Fix: Sort assumptions by risk first and test the top tier before anything else.
What it looks like: The team reaches internal consensus that an assumption is correct after a discussion, marks it as validated, and proceeds — without having gathered a single piece of external evidence. The validation plan exists but the word "validated" means "we all agreed" rather than "we tested it."
Fix: Pair internal confidence with one external evidence checkpoint.
What it looks like: Delivery dates are committed before assumption testing is complete, creating pressure to interpret ambiguous or inconclusive test results as confirming — because the date doesn't move if the test fails, so the test has to pass.
Fix: Record explicit go, pivot, and hold thresholds for each critical assumption.
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.
Intuit Design for Delight
A compact innovation system centered on deep customer empathy, going broad to go narrow, and rapid experimentation.
It gives teams a compact innovation language that can stop solution-first momentum from taking over too early.
Best when
Open it when a team wants stronger innovation discipline but does not need a heavy operating model yet.
GV Sprint
Known here for compressing concept selection, prototyping, and testing into one sequence.
Use this when one risky concept needs a fast, shared answer instead of weeks of debate.
Best when
Risky concepts that need one compressed answer and fast user reaction.
Toyota Kata
Known here for turning improvement into a routine rather than an occasional event.
Use this when you need a steadier learning rhythm, not another big improvement initiative.
Best when
Teams that say they iterate but rarely keep a disciplined experiment cadence.