Assumption Testing & Mapping
Every solution rests on assumptions — and the risky, unchecked ones are where projects quietly die. Here’s how to surface them, map them by impact and evidence (on your own or with your team), and test the riskiest cheaply, before you’ve built the wrong thing.
Why assumptions are where projects die
When a feature ships and nobody uses it, the problem usually isn’t the code — it’s a belief that was never checked. “Users will want this.” “They’ll understand the flow.” “Sales can position it.” Each is an assumption, and any one of them being wrong can sink the work.
Assumption testing flips the order: surface the beliefs first, find the riskiest, and run a small test before committing. Finding and checking that one belief is a riskiest assumption test (RAT) — the engine of continuous discovery, and the bottom layer of every Opportunity Solution Tree.
Four types of assumptions
Naming the type points you at the right kind of test.
Do customers actually want this? Will it solve a problem they care about? The most common reason products fail.
Test with: Interviews, fake-door tests, landing pages
Can people figure out how to use it? Does the flow make sense without someone explaining it?
Test with: Prototype tests, usability sessions
Can we actually build and run it, with our team, tech, and constraints?
Test with: Technical spikes, throwaway prototypes
Should we build it — does it work for the business (cost, pricing, model, legal)?
Test with: Pricing tests, business-model math
Map by impact × evidence
Plot each assumption on two axes — its impact (how much damage if it’s wrong — does the idea collapse?) and how much evidence you already have. One corner matters most:
Your leap-of-faith assumptions. Test these first.
Safe-ish to build on — keep an eye on it.
Don’t waste a test here yet.
Ignore — move on.
Test the riskiest assumption with the smallest experiment that gives a clear signal — and decide the success criterion before you run it, so you can’t rationalize the result afterward.
Map assumptions as a team in 40 minutes
Mapping alone finds the doubts you already have. The belief that sinks a project is usually one nobody in the room thought to question — so map with the people who will build, sell, and support the thing, and keep everyone's first answer private until they have all given one. A run of show that works:
1. Frame
3 minName the solutions on the table and the goal: the few assumptions that could sink them, not every assumption there is.
2. Walk the solutions
6 minGo through each solution so everyone pictures the same thing before they write.
3. Write assumptions alone
7 minIn silence, one per card, under the solution it belongs to. Cover all four types.
4. Share
6 minRead them out, merge duplicates, sharpen the vague ones. No debating yet.
5. Map, blind
8 minEveryone places every assumption on impact × evidence before anyone sees the others. Then reveal, and talk through the biggest disagreements.
6. Plan tests
8 minFor the top two or three only: the smallest test, and the result that would count, written before you run it.
Why blind? The first number said out loud becomes everyone's answer. When each person places every assumption before seeing the others, the spread shows up — and an assumption half the room calls safe and half calls fatal is exactly the one to talk about.
A reusable assumption test template
Copy this card for each assumption you decide to test.
- Assumption
- We believe that busy admins will read a weekly activity digest.
- Type
- Desirability
- Impact if wrong
- High — the whole solution depends on it
- Evidence today
- Weak — one interview mentioned it
- Test
- Fake-door: add a “Weekly digest” toggle, measure opt-ins over 2 weeks
- Success criteria
- ≥ 20% of active admins opt in
- Result
- Validated / Invalidated / Inconclusive
Prefer paper?
Get the printable kit — this card as a fillable one-pager, plus the assumption inventory and the impact × evidence grid. No email required.
Run the workshop on your tree
In Outcomify the workshop runs on your Opportunity Solution Tree. Right-click an opportunity (to map every solution under it) or a single solution and choose Run assumption workshop. A facilitator guide takes the room through the stages with a timer; everyone joins from their own screen, in the room or remote.
- Everyone places each assumption on impact × evidence in private; the reveal shows where the room landed, riskiest first, with the disagreements flagged.
- Plan a test with its success bar for the top two or three. Finishing puts the assumptions and tests on the tree, each assumption with a risk badge.
- Mark each assumption validated or invalidated and attach the evidence from the test, so the result — not the opinion — drives the next decision.
- Canopy can suggest the assumptions hiding under a solution — drafts you review, never silent writes.
Frequently Asked Questions
Common questions about assumption testing and mapping
Keep exploring
A/B test sample size calculator
Free: how many visitors a test needs, and how many days your traffic takes to get there.
Riskiest Assumption Test (RAT)
What a RAT is, how to run one in five steps, and why it comes before the MVP.
Product Experiments
The how: 10 experiments — fake door, concierge, spike — with when to use each and what a clear signal looks like.
Riskiest Assumption Examples
16 real assumptions by type — each with the smallest test and a success criterion.
What is an Opportunity Solution Tree?
Assumptions are the bottom layer — see how the whole tree fits together.
Test the risky beliefs before you build
Map assumptions with your team in a guided workshop, then keep them on your tree — tested, tracked as validated or invalidated, with the evidence attached.