Purpose
When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Product Discovery Mapping tool
Assumption Mapping
Assumption mapping surfaces critical assumptions and focuses tests on high importance with little evidence.
Assumption Mapping surfaces testable hypotheses behind an idea and prioritizes them by importance and existing evidence. This guide follows the 2×2 variant described by David J. Bland and Strategyzer.
Which assumptions are critical to the idea and have the least supporting evidence?
- Participants
- 2-8
- Time
- About 60–90 minutes
The 2×2 map is qualitative prioritization by importance and existing evidence, not a quantitative risk calculation.
Decision
Frame the decision and idea
The map examines assumptions on which a specific decision or idea depends.
Assumptions
Phrase assumptions as hypotheses
Testable, precise and discrete hypotheses are derived from the idea and its rationale.
Map risk
Map importance and evidence together
Each assumption is placed qualitatively by how important it is and how much evidence supports it.
Plan tests
Turn the riskiest assumption into a test plan
Prioritized assumptions are connected to a test, expected signal and later decision.
Update evidence and positions after experiments. Record disagreement rather than creating false precision.
A good fit when
Use it before larger investments or when a team has many assumptions but cannot see which risks matter most.
Ideal for
- Opportunity validation
- Experiment planning
- MVP scoping
Not good for
- Final forecasting
- Very stable products
Outputs
Testable hypotheses
Precise, discrete assumptions across relevant risk areas.
Assumption map
Assumptions placed by importance and evidence.
Tests and learning
Experiments, decision signals and updated uncertainty.
Assumption Map: importance and evidence
Fictional teaching example
Qualitative 2×2 map: first test assumptions that are important to the idea and have little supporting evidence.
| Importance | Little evidence | Existing evidence |
|---|---|---|
| High importanceWould the idea fail if this assumption were false? | Fictional: Households reserve tools online rather than by phone. Untested. | Fictional: In three invented tests, participants recognized the status indicator. A small qualitative sample, not behavioral proof. |
| Lower importanceHow much would a false assumption affect the current decision? | Fictional: Some people prefer green rather than gray cards. | Fictional: The library opens on Saturdays. An illustrative schedule confirms the time; this is not a critical risk for this test. |
1. Little evidence
- High importance
- Fictional: Households reserve tools online rather than by phone. Untested.
- Lower importance
- Fictional: Some people prefer green rather than gray cards.
2. Existing evidence
- High importance
- Fictional: In three invented tests, participants recognized the status indicator. A small qualitative sample, not behavioral proof.
- Lower importance
- Fictional: The library opens on Saturdays. An illustrative schedule confirms the time; this is not a critical risk for this test.
All entries and test results are fictional. Positions are relative judgments, not probabilities or precise risk scores.
First step
Frame one specific idea or decision and gather existing data, customer learning and delivery risks.
Good to do first
Deep dive
How it works
It places assumptions on a shared map by risk and significance and prioritizes the most critical points from there. This focuses test planning instead of overloading it with equally weighted guesses.
In detail
Assumption Mapping helps because it orders assumptions by uncertainty and relevance, bringing the riskiest thinking errors forward early. Good use breaks large claims down into testable individual assumptions and doesn't just discuss what sounds important. The method works strongly where it turns diffuse gut feeling into a clear test order and thereby focuses discovery.
Facilitation
Ask the team in advance for the silent premises behind the idea, user behavior, and feasibility, so the map gets substance. The work gains weight when a seemingly harmless assumption suddenly carries many other points. Close with a few top risks and an explicit choice of what gets tested or broken down further next.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Sources
How assumptions mapping can focus your teams on running experiments that matter | David J. Bland, Strategyzerstrategyzer.comPrimary source for hypotheses, the importance-versus-evidence map and focus on critical assumptions with little evidence.Assumptions Mapping Fundamentals | David J. Blanddavidjbland.comAuthor source describing assumption extraction, mapping important assumptions with little evidence and focusing tests.
Artifact templates
Assumption Map ChecklistChecklist for critical assumptions by risk and knowledge level.checklist
Assumption Map ChecklistChecklist for critical assumptions by risk and knowledge level.
checklistassumption-map-checklist.md
Checklist for critical assumptions by risk and knowledge level.
- Formulate assumption as a testable statement
- Assess risk
- Assess level of knowledge
- Add data source or test idea
- Mark riskiest assumption
- Define success criterion
- Set owner and date
Assumption Mapping: WorksheetFrame the idea, surface critical hypotheses and choose next tests.markdown
Assumption Mapping: WorksheetFrame the idea, surface critical hypotheses and choose next tests.
markdownassumption-mapping-working-template.md
Frame the idea, surface critical hypotheses and choose next tests.
Assumption Mapping: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Map assumptions behind an idea Time: About 60–90 minutes; tests are additional
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Hypothesis cards, a 2×2 map, existing evidence, cross-functional perspectives and experiment cards.
- Roles: A cross-functional team from product, design/research, engineering and business ownership. Facilitation keeps assumptions discrete and testable.
- Advance information: Gather the decision frame and success signal. Extract assumptions about customer desirability, viability, feasibility and other critical areas.
- Overall time needed: About 60–90 minutes to map assumptions and choose tests; experiments and evidence follow separately.
- Setup: Write each hypothesis separately. Discuss importance, then examine existing evidence. Use the map as qualitative prioritization, not a calculation.
Prepare for the work steps
Decision: Frame the decision and idea
- Decision or offer
- Target user and success criterion
Assumptions: Phrase assumptions as hypotheses
- Idea and intended result
- Customer, business and delivery knowledge
Map risk: Map importance and evidence together
- Hypothesis list
- Available evidence and sources
Plan tests: Turn the riskiest assumption into a test plan
- Important hypotheses with weak evidence
- Access to customers, data or technical evaluation
Assumption Map: importance and evidence
| Importance | Little evidence | Existing evidence |
|---|---|---|
| High importance | ||
| Lower importance |
- High importance: Would the idea fail if this assumption were false?
- Lower importance: How much would a false assumption affect the current decision?
Blank worksheet: phrase each card as a testable hypothesis, note its source or evidence and place it qualitatively by importance and existing evidence.
Source: David J. Bland, Strategyzer
Decision: Frame the decision and idea
Expected artifact: Idea frame and consequences
Decision · success · consequence
Entry:
...
- Can the team name what could cause the idea to fail?
Assumptions: Phrase assumptions as hypotheses
Expected artifact: List of testable hypotheses
Statement · risk area · possible evidence
Entry:
...
- Is each card one distinct and testable statement?
Map risk: Map importance and evidence together
Expected artifact: Assumption map with rationale
Importance · existing evidence · disagreement
Entry:
...
- Are top priorities both important and weakly evidenced?
- Are placements based on sources rather than the loudest opinion?
Plan tests: Turn the riskiest assumption into a test plan
Expected artifact: Prioritized test plan for critical assumptions
Hypothesis · test · signal · decision · owner
Entry:
...
- Does the planned test examine risk rather than generic concept interest?
- Is it clear how the later decision depends on the result?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/assumption-mapping/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Decision Making
Pre-Mortem
Instead of Assumption Mapping, when you want to use Pre-Mortem to play through failure scenarios in advance and name risks early.
Product Discovery
Learning Card
Separates hypothesis, observation, insight, and next action into four fields after a test.
Product Discovery
Test Card
Condenses hypothesis, test, metric, and success threshold onto one card before execution.
Decision Making
Assumption Surfacing
Clarifies options, criteria, and risks by framing the initiative or decision, collecting implicit assumptions, and planning tests or research.
Product Discovery
MVP Test Matrix
Moves customer problem, solution idea, and evidence toward a concrete result through "list assumptions", "map assumptions to dimensions", and "derive the test plan".
Product Discovery
Dual-Track Agile
Separates discovery and delivery so that validated stories only move into implementation after learning loops.
Constraints and origin
MediumWorkshop + async45-60 min
Profile
- Method form
- Mapping tool
- Participants
- 2-8
- Time
- 45-60 min
- Maturity
- Established
- Origin
- Strategyzer
Next up: Riskiest Assumption Test