Stress test plans against outcomes beyond the historical range
Ask how your plan holds up if the worst outcome is twice as bad as any historically observed case.
Why it works
Ludic fallacy risk models use historical distributions to set worst-case scenarios — but in real-world domains, the historical maximum is not the maximum. Because models are fitted to observed data, they will always underestimate the tail if the tail is determined by processes that were not active during the observation period. Stress testing beyond the historical range forces the plan to confront outcomes that a model cannot generate by construction.
How to do it
- Take your worst-case scenario from your risk model.
- Double it or triple it: "What if the losses are 2–3x our worst observed case?"
- Check whether the plan survives at that scale, and build the plan toward surviving it if possible.
Evidence
Post-crisis analysis consistently finds that pre-crisis risk models underestimated tail outcomes, often because the models were built from data that did not include the crisis regime. The 2008 financial crisis is Taleb’s canonical example. (observational)
Stress testing beyond historical range is now standard in financial regulation (regulatory stress tests) but adoption in everyday planning is limited. The practice is principled but the specific multiplier (2x, 3x) is a heuristic.
Common mistake
Choosing a stress test level that is slightly worse than the historical worst case rather than genuinely outside it — this exercises the model’s known territory, not the territory beyond it.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Ludic Fallacy: When You Mistake Real Life for a Game
- Check whether the rules of your domain are actually stable
Before applying any probability model, ask whether the rules governing outcomes could change mid-game.
- Build plans with slack for outcomes outside your model
Reserve capacity for events that are not in your risk model — because the most damaging events usually aren’t.
- Prefer positions with optionality over positions with precision
In uncertain environments, prioritize options to pivot over optimized fixed positions.
- Beware false precision in forecasts and models
Treat any precise probability or quantitative forecast with explicit suspicion about whether the model fits the domain.
- Question whether the category you’re reasoning from actually fits
Before applying a model or framework, verify that the category it was built on genuinely matches your situation.
Related concepts
- The Narrative Fallacy: Why We Can’t Stop Making Stories
How causal stories distort hindsight, forecast, and learning — and how to reduce their pull
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Base-Rate Neglect: Why We Ignore the Odds
How to let prior probabilities do their real work in your decisions