# Assumption Mapping

A method for exposing beliefs behind a product idea and prioritizing the assumptions that are both critical and weakly supported.

- Type: method
- Domain: Strategy & discovery
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/assumption-mapping/>)

## What it means

Assumption mapping makes the beliefs underlying a strategy or solution explicit, then compares them by importance and available evidence. Teams focus learning on assumptions whose failure would seriously damage the idea and for which confidence is currently weak.

## Why it matters

Most product proposals bundle beliefs about customers, behavior, channels, technology, operations, economics, and regulation. Mapping prevents the loudest opinion from deciding what to test and helps teams spend experimentation effort where new evidence could most change the decision.

## When to use it

Use it before funding a new concept, after generating solutions, during roadmap reviews, or whenever a team claims confidence without showing evidence. It works well as a bridge between an opportunity, a proposed solution, and a test plan.

## How it works

1. Describe the product bet, intended outcome, and boundaries.
2. List assumptions across desirability, usability, feasibility, viability, ethics, and go-to-market concerns.
3. Rewrite each assumption as a specific belief that could be contradicted by evidence.
4. Assess how critical each belief is and how much relevant evidence supports it.
5. Select the most critical weakly evidenced assumptions.
6. Design proportionate tests and update the map with what is learned.

## A practical example

A payroll startup proposes instant contractor payments. Its map reveals that bank integration is understood, but the belief that contractors will pay for speed is critical and unsupported. The team tests willingness and context with real payment choices before investing in full automation.

## Where it breaks

The axes are subjective and can create numerical theater. Teams may overlook assumptions they lack expertise to notice, including legal or societal harms. A map also becomes stale quickly; it must link to evidence and decisions rather than remain a colorful workshop artifact.

## Common mistakes

- Listing tasks or known facts instead of uncertain beliefs.
- Testing what is easiest rather than what could invalidate the bet.
- Treating stakeholder confidence as evidence.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/assumption-mapping/#visualization-assumption-mapping>)

## Sources

1. [Assumptions Mapping Fundamentals](<https://davidjbland.com/courses>) — David J. Bland · Creator course overview
2. [Assumptions Mapping](<https://www.theuncertaintyproject.org/tools/assumptions-mapping>) — The Uncertainty Project · Method guide

## Related topics

- [Hypothesis-Driven Design](<https://wiki.soroush.uk/topic/hypothesis-driven-design/>)
- [Opportunity Solution Tree](<https://wiki.soroush.uk/topic/opportunity-solution-tree/>)
- [A/B Testing](<https://wiki.soroush.uk/topic/a-b-testing/>)
