methodStrategy & discovery

Assumption Mapping

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

Download Markdown (.md)

01What 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.[1][2]

Learning priority Test beliefs that are both critical and weakly evidenced
More criticalLess criticalWeak evidenceStrong evidence
  1. Test firstCritical · weak evidence
  2. MonitorCritical · stronger evidence
  3. DeferLess critical · weak evidence
  4. Known detailLess critical · stronger evidence

Positions should change as relevant evidence accumulates.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. Assumptions Mapping FundamentalsDavid J. Bland · Creator course overviewAssumptions Mapping Fundamentals
  2. Assumptions MappingThe Uncertainty Project · Method guideAssumptions Mapping
View saved topics

Start typing to search titles, definitions, categories, and frameworks.