What is Assumption Mapping?
Assumption mapping is a collaborative exercise where a team identifies all the assumptions underlying a product idea and plots them on a matrix. One axis represents how important the assumption is (if wrong, does the initiative fail?). The other represents how certain the team is (do we have evidence or are we guessing?).
The quadrant with high-importance, low-certainty assumptions contains your "leap of faith" assumptions. These are the beliefs that must be true for the product to succeed but that you have the least evidence to support.
Why Assumption Mapping Matters
Every product initiative is built on a stack of assumptions. "Users have this problem." "They will pay to solve it." "We can build it in 3 months." "Our go-to-market channel will work." Most teams never make these assumptions explicit, let alone test them.
Assumption mapping forces intellectual honesty. It moves the team from "we believe" to "we assume, and here is how we will verify." This prevents the expensive surprise of discovering a fatal flaw after months of building.
How to Map Assumptions
Brainstorm assumptions as a team. Use sticky notes. Ask: "What must be true about the user, the market, the technology, and the business for this to succeed?" Aim for 15-20 assumptions.
Plot each assumption on the 2x2 matrix. Y-axis: importance (how critical is this assumption?). X-axis: certainty (how much evidence do we have?).
Prioritize the top-right quadrant (important and uncertain). For each, design a quick test. User interviews test desirability assumptions. Fake door tests test demand. Technical spikes test feasibility.
Run the tests and update the map. As assumptions move from uncertain to validated (or invalidated), update the map. Invalidated important assumptions require a pivot or kill decision.
Assumption Mapping in Practice
IDEO uses assumption mapping at the start of every design thinking engagement. Before generating solutions, the team maps assumptions about the user's problem. This ensures discovery focuses on the right questions.
At Spotify, squad leads run assumption mapping when evaluating new bets. The exercise takes 90 minutes and produces a prioritized list of experiments. It has prevented several initiatives from proceeding with untested critical assumptions.
Common Pitfalls
- Only mapping obvious assumptions. Push the team to surface implicit assumptions. "Users will find our product" is an assumption many teams overlook.
- Not testing. The map is useless if you do not run experiments. Each risky assumption needs a test.
- Testing safe assumptions. Teams naturally gravitate toward testing assumptions they are already confident about. Resist this comfort zone.
- Solo mapping. Assumptions surface better in groups. Engineers see feasibility risks. Designers see usability risks. PMs see market risks.
Related Concepts
Assumption mapping is a key tool in product discovery and lean startup methodology. It feeds into experiment design and hypothesis-driven development. The opportunity solution tree provides the broader framework for structuring discovery work.