Scenario Variation¶
Comparative analysis — instantiates Sensitivity Analysis Protocol
Bundles many assumptions into a few internally coherent named worlds and reads the outcome under each to judge whether the plan survives all of them.
Scenario variation abandons the idea of moving inputs independently and instead assembles a small set of internally coherent worlds — each a named bundle in which many assumptions shift together in a way that could actually co-occur — then reads the outcome under each world and concludes how robust the recommendation is across them. Its defining move is coherence: assumptions are grouped by a plausible story rather than swept across a mechanical grid, so a "harsh winter" world simultaneously raises demand, spikes spot prices, and stresses generation, exactly as those would move together in reality. It answers "does the plan survive the few worlds we can actually defend?" — not "how does each knob move the answer?" and not "what fraction of random draws break it?"
Example¶
A regional electric utility is deciding whether its existing generation portfolio is adequate for the coming winter or whether it must contract expensive standby capacity. Rather than wiggle demand, fuel price, and outage rate one at a time, the planners build three coherent worlds. Mild winter: below-normal peak demand, soft gas prices, normal plant availability. Expected winter: normal on all three. Harsh winter: a sustained cold snap that pushes peak demand up, drives gas prices up because everyone is heating at once, and raises the odds of a generator tripping — three moves that historically arrive together. They read the same metric, reserve margin at system peak, under each world. Mild and expected clear comfortably; the harsh world dips below the required margin. Because that harsh world is entirely plausible, not a contrived worst case, the robustness conclusion is clear: the portfolio is adequate in ordinary winters but fragile in a cold snap, so contracting standby capacity is justified.
How it works¶
- Author a few worlds. Build three to five internally consistent scenarios — typically a base case plus stress worlds — each specifying a complete assumption set, not a single perturbed input.
- Enforce coherence. Every assumption in a world must be mutually plausible; the discipline is that the world could really happen, co-movements and all.
- Read one metric per world. Evaluate the same stable outcome under each scenario so the worlds are directly comparable.
- Conclude across worlds. Judge robustness by which worlds break the plan — failure only in an implausibly extreme world is reassuring; failure in a defensible one is fragility.
Tuning parameters¶
- Number of worlds — more scenarios span more of the future but dilute focus and invite cherry-picking; three to five is the usual sweet spot.
- Span — how far the stress worlds reach, from mild variation to near-catastrophe; too timid hides fragility, too extreme invites dismissal.
- Coherence discipline — how strictly assumptions within a world must be mutually consistent; loose worlds smuggle in impossible combinations.
- Weighting stance — whether worlds are left as illustrative cases or informally weighted; keep them categorical, because attaching real probabilities crosses into probabilistic simulation's lane.
When it helps, and when it misleads¶
Its strength is that it respects co-movement and communicates: bundled uncertainty (a recession that hits demand, credit, and costs at once) is represented honestly, and stakeholders reason about a handful of vivid worlds more easily than about a variance table.[1] Its failure mode is scenario-selection bias and false coverage — the worlds are chosen by hand, so a team can quietly omit the world that would break its plan, and the actual future often lands between the scenarios drawn. The classic misuse is presenting three comfortable scenarios as if they bracket the full range of outcomes. The guarding discipline is to include at least one genuinely adversarial world and to state plainly that the scenarios illustrate rather than exhaust the space.
How it implements the components¶
scenario_set— its signature: it constructs and curates the small library of coherent named worlds that are the unit of analysis.outcome_measure— fixes the single stable metric read once per world so the worlds can be compared.robustness_conclusion— states, in decision language, whether the recommendation holds across the worlds or fails in a defensible one.
It does not vary inputs one at a time or across a continuous grid — parameter_prioritization_rule is One-way Sensitivity Analysis's and correlation_or_dependency_note is Two-way or Multi-way Sensitivity Analysis's. Crucially it does not assign probabilities to its worlds or count draws past a boundary (decision_flip_point, Probabilistic Sensitivity Simulation); its worlds are few and categorical, not many and sampled.
Related¶
- Instantiates: Sensitivity Analysis Protocol — this is the protocol's coherent-worlds comparison.
- Consumes: Assumption Stress-test Workshop — the worlds are usually authored and pressure-tested there.
- Sibling mechanisms: One-way Sensitivity Analysis · Two-way or Multi-way Sensitivity Analysis · Threshold Analysis · Tornado Chart · Sensitivity Table · Probabilistic Sensitivity Simulation · Assumption Stress-test Workshop
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Scenario Variation operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it bundles many assumptions into a few internally coherent named worlds and reads the outcome under each to judge whether the plan survives all of them.
Independent corroboration: The frozen evidence defines Scenario Variation as 'Bundles many assumptions into a few internally coherent named worlds and reads the outcome under each to judge whether the plan survives all of them', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Representation, Specification & Plan — Scenario Variation includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Futurism & Strategic Foresight
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: Bundling assumptions into coherent named worlds is canonical scenario planning.
Related originating lineages:
- Operations Research — Robustness evaluation materially reads plan outcomes across worlds.
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: bundles many assumptions into a few internally coherent named worlds and reads the outcome under each to judge whether the plan survives all of them.
Review resolution: Both blind reviewers agree that futurism_foresight is the primary historical origin. Explicit reconciliation of alternate_origin_disagreement, domain_reach_disagreement starts from reviewer_a's mechanism-specific evidence: Bundling assumptions into coherent named worlds is canonical scenario planning. Reviewer A proposed alternates=operations_research, origin_mode=single_lineage, domain_reach=universal, and encyclopedia_synthesis=false; reviewer B proposed alternates=organizational_management, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (operations_research, organizational_management) without an arbitrary cap, selects origin_mode=single_lineage to represent the combined lineage evidence, and records domain_reach=universal and encyclopedia_synthesis=false. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Schoemaker, Paul J. H. "Scenario Planning: A Tool for Strategic Thinking". Sloan Management Review 36(2): 25–40 (1995). Uses scenarios to vary several uncertain factors together as internally consistent worlds. registry ↩