Map and stress-test your key assumptions

Before executing, list the assumptions the plan depends on — then ask which ones would kill it if wrong.

Why it works

Every plan rests on assumptions: about customer behavior, competitor response, resource availability, your own capabilities. These assumptions are often invisible because they feel obvious, and they are exactly the things a genuine red team attacks. Making them explicit forces an honest look at which assumptions are load-bearing and which can be verified before betting the plan on them.

How to do it

1. Write the plan’s five to ten most important assumptions explicitly.
2. For each, answer: if this assumption were false, what would happen to the plan?
3. Rank by criticality: which assumptions would cause the plan to fail outright if wrong?
4. For the top two or three, identify whether you can test or verify them before full commitment.

Evidence

The importance of surfacing assumptions is supported by research on planning fallacy and overconfidence: plans fail most often because of assumptions that were never questioned rather than errors in the execution of the plan. Making assumptions explicit is the standard practice in analytical tradecraft. (mechanistic)

The value of assumption mapping is principled and widely used in intelligence and strategy consulting; direct outcome evidence comparing mapped-assumption plans to unmapped ones in real organizations is not available.

Common mistake

Listing only the assumptions you feel confident about, rather than the ones that would be most devastating if wrong. The critical assumptions are often the ones that feel most certain — which is exactly why they don’t get questioned.