Framework · Facilitation techniques · 3 min read
Assumption mapping
Plot assumptions on known↔unknown × important↔unimportant, then test the important unknowns first, so opinions become research questions.
Critical, and you have evidence. Build on it and keep checking.
e.g. "Planners use the tool daily."Critical, but no evidence yet. Turn these into research questions.
e.g. "Planners will trust automatic suggestions."Low risk and already known. No action needed.
e.g. "Users log in with single sign-on."A trap: interesting to research, but it won't change the decision.
e.g. "Users prefer a dark theme."Use it when
- A project kick-off with a product manager and developers, before anyone commits to a solution.
- A stakeholder is sure that "users want X", and you want to turn the opinion into something you can test.
- You must choose which research to do first with limited time.
How to use it
- Write assumptions as testable beliefs. Each person writes beliefs about users, value and delivery, one per sticky, in the form "We believe that…". Check each one: could research show it is wrong? Output: 15–30 assumption stickies. About 10 minutes.
- Plot them together on importance. Place each sticky vertically: how badly does the project fail if this belief is wrong? Discuss only where people disagree. Output: every sticky placed high or low.
- Plot them on evidence. Move each sticky left or right: do we have evidence (data, research, observed behaviour), or is it a guess? Opinions from senior people count as no evidence. Output: a filled 2×2 map. About 15 minutes in total for steps 2–3.
- Turn the top right into research questions. Take the 3–5 most important unknowns and write for each: a research question, a method and what result would change your mind. Output: a short, ranked research plan.
- Assign owners and revisit. Give each test an owner and a date. Move stickies when new evidence comes in, and update the map at each milestone. Output: a living map and test owners. About 5 minutes.
Worked example
In a 90-minute kick-off for a new "suggested plan" feature on an internal operations platform, a UX lead spends 25 minutes on assumption mapping with the product manager, 2 developers and a designer.
| Assumption ("We believe that…") | Importance | Evidence | Next step |
|---|---|---|---|
| Planners will trust automatic suggestions | High | None | Test: 5 planners try a clickable prototype with real data |
| Planners plan the next day at the end of each shift | High | Some (2 interviews) | Check: shadow 3 planners for one shift each |
| Planners use the tool every day | High | Strong (usage data) | No test needed; build on it |
| Planners want to print the plan | Low | None | Park; check later if it comes up |
The first row is the riskiest belief. The team agrees not to start build until the prototype test is done.
Watch out for
- Assumptions written as facts or features. "Add a suggestion button" is a solution. Rewrite it as a belief: "We believe planners want suggestions."
- Senior opinion counted as evidence. "The director said so" is still an unknown. Ask: "What have we seen users do?"
- Mapping and then ignoring it. If nothing from the top right becomes a test with an owner, the session changed nothing.
- Researching the bottom right. Unimportant unknowns can be interesting, but they don't change the decision. Leave them.
Template
Draw the 2×2 on your board and use this list next to it.
ASSUMPTION MAP About 30–45 min
Project / decision: ____________________________________
"We believe that …" (one per sticky; must be testable)
Evidence (known) No evidence (unknown)
Important Build on it TEST FIRST
Less import. No action Park (don't research now)
Top-right assumptions → research questions:
# Assumption Research question Method Owner Date
1.
2.
3.
What result would change our mind?
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.