How to Run an Assumption Mapping Workshop
Every product plan is built on assumptions. Assumption mapping makes these assumptions explicit, ranks them by risk, and identifies which ones to test first. It is the foundation of evidence-based product development.
This guide covers how to run a 90-minute assumption mapping workshop that produces a prioritized list of assumptions to validate.
Step-by-step guide
Step 1: Prepare the assumption categories
Before the workshop, prepare four categories: Desirability (do users want this?), Viability (will this make money?), Feasibility (can we build this?), and Usability (can users figure it out?). Each category prompts different types of assumptions.
Step 2: Generate assumptions (20 min)
Each participant writes assumptions on sticky notes (physical or digital). One assumption per note. Use prompts: We assume users will... We assume the market will... We assume we can build... We assume users will be able to... Aim for 30-50 assumptions across the team.
Step 3: Map on a 2x2 (20 min)
Map assumptions on a 2x2 matrix: X-axis = how much evidence we have (low to high), Y-axis = how critical this assumption is (low to high). The top-left quadrant (high criticality, low evidence) contains your riskiest assumptions. These are your testing priorities.
Step 4: Identify the leap-of-faith assumptions
From the top-left quadrant, identify the 3-5 most dangerous assumptions: the ones that, if wrong, would fundamentally change or kill the initiative. These are your leap-of-faith assumptions that must be tested before committing engineering resources.
Step 5: Design experiments for each (30 min)
For each leap-of-faith assumption, design the cheapest valid experiment: interview, prototype test, fake door test, or data analysis. Define the success criteria and timeline. This is your testing roadmap for the next 2-4 weeks.
Common mistakes
Not including engineering and design
PMs, engineers, and designers see different assumptions. Engineers flag feasibility assumptions PMs miss. Designers flag usability assumptions. Include all three perspectives.
Testing low-risk assumptions first
It feels safer to validate easy assumptions. But the point of assumption mapping is to test the dangerous ones first. If a leap-of-faith assumption is wrong, you need to know before investing engineering time.
Tips
- Run assumption mapping at the start of every major initiative, before writing the PRD
- Use Miro or FigJam for remote workshops
- Revisit the assumption map monthly: some assumptions get validated by shipping, others need explicit testing
How Vantage helps
Vantage supports assumption-driven product development by connecting research and analytics to PRD generation. After validating assumptions through experiments, import the results as context sources so the generated spec reflects validated learning.