Strategy
Assumption Mapping
A practical UX and product strategy method for surfacing uncertainty and prioritising validation work.
How to run assumption mapping to identify high-risk unknowns, align teams, and focus research or experiments where they matter most.
What it is
Assumption mapping is a UX and glossaryProduct StrategyProduct strategy defines how a product will achieve business goals by solving user problems in a focused and sustainable way. It sets direction, priorities, and trade-offs to guide decision-making.Open glossary term method used to visualise and categorise assumptions underlying a product, glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term, or project.
It involves listing assumptions, then evaluating them by risk (impact if wrong) and certainty (how confident the team is).
The method highlights which assumptions need validation through serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service, testing, or glossaryExperimentAn experiment is a structured test used to evaluate hypotheses and measure outcomes.Open glossary term.
The focus is on uncovering hidden beliefs that could affect product success.
Key takeaway
The goal is to prioritise what to test, reduce risk, and make informed design and business decisions.
When to use it
Use this method when uncertainty exists in a project.
It is most useful when:
It is less useful when:
Assumption mapping is often used alongside JTBD, proto-personas, and experimentation planning.
How to run it
Set up properly
Be clear on the scope of assumptions, who should be in the room, and how you will assess risk and certainty. The exercise depends on people admitting what they do not know.
Include people from outside the core team. Shared assumptions are invisible to those who share them.
Run the method
Assumption mapping surfaces what a team is taking for granted and sorts it by risk. It is most useful at the point where glossaryConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term is high and evidence is thin.
- List assumptions about users, market, technology and glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, phrased as statements that could be false.
- Evaluate each on certainty and impact separately. The two are frequently confused, and the combination is what matters.
- Plot them on a two-by-two of certainty against impact.
- Highlight the high-impact, low-certainty quadrant. That is the entire output of the exercise; everything else is glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term.
- Discuss and prioritise the serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service or glossaryExperimentAn experiment is a structured test used to evaluate hypotheses and measure outcomes.Open glossary term needed, assigning each to somebody.
Focus on the leap-of-faith assumptions, the ones where being wrong invalidates the whole plan. Teams reliably spend their serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service budget on the comfortable ones instead.
Capture and make sense of it
The value comes from knowing what to test first. After the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, document:
- Assumptions ranked by risk, with the reasoning
- Which need validating before anything is committed
- How each will be tested, and by whom
- Assumptions accepted deliberately, so the choice is on the record
Use this to direct serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service where it changes decisions. It is the cheapest way to avoid confidently building the wrong thing.
Key takeaway
Use this to reduce uncertainty and make smarter decisions.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If assumptions aren’t challenged, risks go unnoticed.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps reduce risk and guide evidence-based design and product strategy.
Get in touch
If this sounds like something you need, we can help you map assumptions, prioritise validation, and make evidence-based decisions to reduce risk and improve outcomes.
No guesswork. No assumptions. Just clarity and focus.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is assumption mapping in UX?
It is a method for identifying and prioritising assumptions to guide research and reduce risk.
When should you use assumption mapping?
At the start of a project, before making design or product decisions.
What can you map?
Assumptions about users, market, technology, behaviours, and outcomes.
Why map assumptions before testing them?
It helps teams focus on testing what matters most and avoid costly mistakes.
Does assumption mapping improve UX?
Indirectly. By validating assumptions, you design with confidence and reduce errors.
Quick take
If your team is guessing, you’re at risk. Map assumptions to identify uncertainty and test what matters.
Related Services
Related Guides
