Every initiative rests on beliefs. Map them all, then plot each by importance and evidence — the high-importance, low-evidence quadrant is what to test first.
▸ Try the interactive toolAssumption Mapping is the practice of systematically surfacing every belief a product initiative depends on, then prioritising those beliefs by two dimensions — how important each is to success, and how much evidence currently supports it — so the team knows which assumptions to test first.
The core insight is that not all assumptions are equal. An idea rests on dozens of beliefs, but only a few are both critical and unproven — and those are the ones that can quietly sink it. Plotting every assumption on an importance-vs-evidence grid makes the dangerous quadrant visible: high importance, low evidence. Those are the leap-of-faith assumptions to test before committing, rather than the comfortable ones you already have evidence for.
Plot every assumption on two axes — importance (how much success depends on it) and evidence (how much support it has today). The high-importance / low-evidence quadrant holds the leap-of-faith assumptions: test these first.
Teams test the assumptions that are easy or comfortable to test, and leave the genuinely risky ones — the ones that can kill the idea — quietly unexamined.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Testing comfortable assumptions | Effort goes to beliefs you already half-confirmed, not the risky ones. | The grid steers testing to high-importance, low-evidence beliefs. |
| Hidden leap-of-faith beliefs | A critical unproven assumption sinks the idea late. | Surfacing every assumption brings the dangerous ones into view. |
| Treating all assumptions equally | Spreading test effort thin across trivial and critical alike. | Two-axis prioritisation focuses on what actually matters. |
| Confusing opinion with evidence | “We're pretty sure” treated as proof. | The evidence axis forces an honest audit of what's really known. |
Brainstorm all the beliefs the initiative depends on — about users, value, feasibility, viability, the market. Cast wide; the dangerous assumption is often one nobody thought to say aloud.
How much does success depend on this being true? A belief that's wrong-but-survivable is low importance; one that's fatal-if-wrong is high. Be honest about which are load-bearing.
How much real evidence supports it today — not opinion, not hope, but data and research? Most teams discover their confidence rests on far less than they assumed.
Map all assumptions on the two axes. The high-importance, low-evidence corner is your test list — the leap-of-faith beliefs that can sink the initiative.
Turn each danger-quadrant assumption into a testable hypothesis (Tool 13) and run the cheapest experiment that could prove it wrong. Retire risk in order of how lethal it is.
A team building a new feature had tested plenty — the interface, the flow, the wording — and felt thoroughly validated. They mapped their assumptions anyway and found something uncomfortable: the single most important belief, that users would change an entrenched habit to adopt the feature, had almost no evidence behind it.
Everything they'd tested was real but low-stakes; the one assumption that could kill the whole initiative sat unexamined in the high-importance, low-evidence corner. A cheap experiment aimed squarely at it — would users actually switch? — mattered more than all the interface testing combined. The map redirected their effort from the comfortable to the critical.
The deliverable is the two-axis grid with every assumption plotted, and the high-importance / low-evidence quadrant marked as the test backlog.
| Importance | Evidence | What to do |
|---|---|---|
| High | Low | Test first — the leap-of-faith risks |
| High | High | Proceed — but monitor |
| Low | Low | Ignore for now |
| Low | High | Settled — don't waste tests here |
The assumptions most likely to kill your idea are the ones you're least likely to test — because they're often the scariest to examine. The map drags them into the open and puts them at the front of the queue.
The discipline is honesty on both axes, but especially evidence. Teams routinely mistake familiarity for proof — a belief repeated often enough starts to feel evidenced when it never was. Forcing each assumption onto the evidence axis exposes how much of an initiative actually rests on hope. And pairing that with importance gives the crucial focus: you don't need to test everything, only the beliefs that are both load-bearing and unproven. That's the difference between discovery that feels thorough and discovery that actually de-risks the build.
The dangerous belief is often the unspoken one. Push to surface every assumption, including the scary ones.
“We're sure” isn't data. Rate the evidence axis on real research, not feeling.
Effort on survivable assumptions is comfortable but wasteful. Focus on the load-bearing ones.
Assumptions shift as you learn and pivot. Revisit the map.
The four risks (Tool 01) are the top-level categories; assumption mapping breaks each into specific, plottable beliefs.
Each danger-quadrant assumption becomes a falsifiable hypothesis (Tool 13).
The prioritised assumptions set the agenda for the lean experiment framework (Tool 15).
Assumptions cluster around the solutions in the OST (Tool 03) — the map decides which to test first.
Pick a product idea and list every belief it depends on — push past the obvious to the unspoken ones. For each, rate importance (fatal if wrong?) and evidence (what really backs it?).
Find the one assumption that's both most important and least evidenced. That's your leap of faith.
If the riskiest assumption is one you'd never have thought to test — because it felt too obvious to question — the map has done its job.