De-risking Your Bets: A Practical Guide to Assumption Mapping
Every roadmap is a stack of untested assumptions. Assumption mapping surfaces the load-bearing, unproven bets and tells you what to test first, before you waste a quarter.
Every Roadmap Is a Stack of Untested Assumptions
When a feature fails, it is rarely because the team built it badly. It is because a hidden assumption turned out to be false, customers did not actually want it, would not pay for it, or could not figure out how to use it. The roadmap looked like a plan, but it was really a pile of bets, and nobody had sorted the safe ones from the company-ending ones.
Assumption mapping is the discipline of pulling those bets into the open before you spend a quarter building on top of them. It is the cheapest risk management a product team has access to.
Name the Assumptions Behind the Idea
Take any initiative and ask what has to be true for this to succeed. You will usually surface four kinds of assumptions:
- Desirability: do customers actually want this and feel the problem strongly enough to change behavior.
- Viability: does it make business sense, will it drive the metric we care about.
- Feasibility: can we actually build and operate it within our constraints.
- Usability: can people figure out how to use it without hand-holding.
Most teams over-index on feasibility, the engineering question, and under-test desirability, which is where products usually die.
Map by Importance and Evidence
Plot each assumption on two axes: how important it is, and how much evidence you have for it. The assumptions that are both load-bearing and unproven are your real risks. This is the quadrant, borrowed from the work of teams like Strategyzer, where your discovery effort belongs. Everything else is a distraction.
Test the Riskiest Assumption First, Cheaply
Once you know your riskiest assumption, design the smallest experiment that could prove it wrong. The point is not to validate, it is to try to kill the idea while it is still cheap. A landing page, five customer interviews, a fake door, a concierge test. If the assumption survives a genuine attempt to disprove it, your confidence is earned rather than assumed.
Keep reading
The PM Role Is Splitting: Which Product Manager Are You Becoming?
The generalist PM is becoming the hardest role to hire for — because the job is splitting. The specialize-vs-AI-generalist fork, the four flavors of "AI PM," and the one career question that now matters most.
Jobs to Be Done: Why Your Customers "Hire" Your Product (and What That Changes)
Customers don't want your product — they hire it to get a job done, and fire it when something does the job better. Here's how Jobs to Be Done reframes discovery, prioritization, and messaging.
Continuous Discovery: How to Talk to Customers Every Week (Without It Eating Your Roadmap)
Most teams do discovery in bursts, then build on stale assumptions for months. Continuous discovery — small, weekly customer touchpoints — keeps you close to reality. Here's how to make the habit stick without it eating your roadmap.