Protocol
Stress-test the high-impact scenario without calling it likely
Severity deserves preparation; it does not deserve a fake probability.
Before you use it
- Use when
- A low-probability scenario would be expensive enough that ignoring it could be reckless.
Keep this limit in mind
- Worst-case imagination can inflate fear. Pair this technique with base rates, sensitivity analysis and ordinary expected scenarios.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Describe the scenario, what would have to be true, the earliest indicators, the main consequence and a proportionate hedge or contingency. Keep probability and impact separate. Do not let a vivid worst case hijack the base case.
Steps
- The mitigation is proportionate to uncertainty and impact, and the scenario is not being presented as a forecast.
An example
A critical vendor outage during cutover is not the base case, but a tested rollback and offline contact path may be cheap enough to justify.
Check your result
The mitigation is proportionate to uncertainty and impact, and the scenario is not being presented as a forecast.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingStress-test the high-impact scenario without calling it likely
Evidence and sources
High-impact/low-probability analysis explores consequential scenarios without asserting that they are likely.
Scenario severity should not be confused with probability.
A Tradecraft Primer: Structured Analytic Techniques for Improving Intelligence Analysis · Contrarian Techniques: High-Impact/Low-Probability Analysis
Edition and review
Version 0.1.0
No review details are supplied for this edition.