CH-07 What if analysis Also serves: Project forward.
Assumes an unexpected event has occurred, explains how it could have come about, and produces scenarios with indicators and consequence assessments.
What it does
Assumes an unexpected event has occurred and explains how it could have come about. Artefact: scenarios with indicators and consequence assessments.
When to use it
Use when the conventional view excludes an event and you want to test how it could arise and what follows.
When it does not fit
The narrative describes only the outcome and not the causal chain.
Result format
The result is a set of scenarios that assume the unexpected event has occurred and explain how it could have come about. Each scenario has its indicators and a consequence assessment.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Content type, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | The conventional line and an assumed event. |
|---|---|
| Additional sources needed | none |
| Not for (rules) | none |
| Not for (text) | The narrative describes only the outcome and not the causal chain. |
Choosing and ordering
| Kind of technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | validate |
| Kind of finding | risk; cause |
| Question answered | why; what next |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to analyse |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | assumption and limitation statement | none | no |
| decision-informing | assumption and limitation statement | none | no |
| decision-informing | independent review | needed; left out below high stakes | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | independent review | needed | no |
| high-stakes | expert review | needed | no |
| high-stakes | second technique with different assumptions | none | conditional |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Describes the assumed event and its consequences without a causal chain from today to the event. |
| Error sources | input data; coder or rater judgement; language model |
| Certainty limits | One label covers two operations in the sources, so the method must be stated; no effectiveness evidence found, and the pathway is hypothetical. |
Related techniques
- pairs with CH-06 High-impact and low-probability analysis Also serves: Project forward.: High-impact analysis adds triggers and watchable indicators for the pathway
- pairs with PJ-18 Backcasting: Backcasting works back from a desired state where this works back from an unexpected one
Evidence and tag basis
Documented. The CIA version works backwards from the assumed event; the UK handbook says its version starts from the beginning and maps pathways to gains and losses, so one label covers two operations. (CIA Tradecraft Primer (2009); UK Red Teaming Handbook)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.