Scenario Demand Stress Test¶
Scenario analysis — instantiates Demand Curve Calibration and Response Design
Pushes the calibrated demand schedule to extreme, off-baseline conditions to find where it breaks before a real shock does.
A Scenario Demand Stress Test takes an existing demand schedule and deliberately drives it into conditions it was never estimated under — a cost doubled, a substitute suddenly free, a competitor slashing prices, capacity halved — to see whether the resulting decision still holds. It is not an estimator; it is a robustness exercise. Its defining question is not "what is demand?" but "under what shock does our plan built on this demand become wrong?" By constructing a handful of stark, coherent scenarios and running the schedule (and rivals' likely reactions) through each, it converts a single-point forecast into a stress profile and marks the conditions under which the decision must change.
Example¶
An electric utility is planning summer generation capacity around a demand schedule built from ordinary years, and wants to know where that plan snaps. It builds a small set of stark scenarios rather than one forecast: a record heat dome that pushes air-conditioning load far past any observed peak; a time-of-use pricing rollout that shifts load but triggers a rebound as customers over-cool cheap off-peak hours; and a scenario where a large industrial customer installs on-site solar and strategically drops off the grid at peak.
Running the schedule through each exposes different failure points. The heat-dome case pushes demand into a region the curve was never calibrated in — the extrapolation band is wide and the reserve margin thin. The rebound case shows the pricing plan could raise total consumption even as it flattens the peak. The strategic-defection case shows a single actor's response reshaping the residual curve. None of these is a prediction; together they yield a decision rule — "hold this much firm reserve unless the heat-dome and defection cases can both be ruled out" — that a single expected-demand forecast would never have produced.
How it works¶
- Construct coherent extremes. Build a few internally-consistent scenarios that move cost, substitutes, capacity, or rival behavior well past the baseline — not random shocks but plausible stories.
- Run the schedule off-baseline. Push the demand curve into each scenario's conditions, explicitly flagging where you have left the range it was estimated in.
- Screen strategic reactions. Ask how competitors, large customers, or arbitraging agents would respond to the same scenario, and fold their reaction into the residual demand.
- Read out a decision rule. Identify which scenarios break the plan and translate that into a robust rule — a reserve, a hedge, a trigger to re-decide.
Tuning parameters¶
- Scenario severity — mild scenarios are plausible but rarely break anything; extreme ones stress the plan hard but risk being dismissed as fantasy. Calibrate to consequential-but-credible.
- Number of scenarios — few keep the exercise legible; many cover more of the space but dilute attention and invite cherry-picking the comforting one.
- Strategic-response depth — from "hold rivals fixed" to a full reaction game; deeper is more realistic but speculative and heavy.
- Decision-rule stance — how conservatively the readout binds: plan for the worst credible case, the median case, or somewhere between, trading resilience against cost.
When it helps, and when it misleads¶
Its strength is surfacing fragility before reality does: it reveals where a comfortable point forecast would fail, catches second-order effects like rebound and strategic defection, and turns "what is demand" into a decision rule robust to being wrong. For irreversible capacity and pricing commitments, that is worth more than a sharper central estimate.
Its failure mode is the Lucas critique in operational form[1]: a demand relationship estimated under one regime need not survive a large policy or cost change, so pushing an old elasticity into an extreme scenario can produce confident nonsense if the behavior itself would restructure. The exercise is also only as good as its imagination — the scenario that actually happens is often the one nobody drew — and it invites anchoring on whichever scenario is politically convenient. The classic misuse is treating the stress scenarios as forecasts and planning to their midpoint. The guarding discipline is to keep scenarios coherent and few, mark where the schedule has left its valid range, and use the readout to set triggers and reserves, not to predict.
How it implements the components¶
uncertainty_and_extrapolation_band— its core act is running the schedule outside its estimated range and making that extrapolation, and its width, the center of attention.strategic_response_screen— each scenario folds in how competitors and large agents would react, screening for demand reshaped by strategic behavior.decision_integration_rule— the readout is a robust decision rule (reserve, hedge, re-decide trigger) rather than a demand number.
It stresses a schedule it is handed but does not estimate the baseline curve itself (demand_schedule_model) — that is the Demand Curve Estimation Workbook — and it does not compute the substitution coefficients its scenarios assume (cross_elasticity_matrix), which come from the Cross-Elasticity Matrix.
Related¶
- Instantiates: Demand Curve Calibration and Response Design — turns the schedule into a stress profile and a robust decision rule.
- Consumes: Demand Curve Estimation Workbook supplies the baseline schedule the scenarios perturb.
- Sibling mechanisms: Conjoint or Discrete Choice Model · Cross-Elasticity Matrix · Demand Curve Estimation Workbook · Demand Segmentation Dashboard · Equity Access Impact Review · Price Sensitivity Experiment · Revealed Preference Choice Log · Shadow Price Probe · Waitlist and Stockout Analysis
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Scenario Demand Stress Test operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it pushes the calibrated demand schedule to extreme, off-baseline conditions to find where it breaks before a real shock does.
Independent corroboration: The frozen evidence defines Scenario Demand Stress Test as 'Pushes the calibrated demand schedule to extreme, off-baseline conditions to find where it breaks before a real shock does', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Experiment, Test & Rehearsal — Scenario Demand Stress Test includes features of an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation, 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: Operations Research
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Pushing a calibrated demand-and-capacity model through extreme off-baseline loads to locate failure thresholds is operations-research stress analysis. IMF stress-testing doctrine distinguishes sensitivity and coherent scenario analysis under exceptional but plausible shocks; economics supplies demand behavior while OR supplies capacity modeling.
Related originating lineages:
- Disaster Management & Risk Reduction — Surge planning independently tests service failure under shocks.
- Economics & Finance — Scenario Demand Stress Test's terminology and operating form—pushes the calibrated demand schedule to extreme, off-baseline conditions to find where it breaks before a real shock does—are rooted most directly in economics, finance, and mechanism-design practice.
- Futurism & Strategic Foresight — futurism_foresight contributes scenario construction, trigger design, and anticipatory governance to the mechanism's formative or independently convergent form; that contribution does not displace the primary operations_research lineage.
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: pushes the calibrated demand schedule to extreme, off-baseline conditions to find where it breaks before a real shock does.
- Statistics & Experimental Design — statistics_experimental_design contributes sampling, sensitivity, inference, and controlled testing to the mechanism's formative or independently convergent form; that contribution does not displace the primary operations_research lineage.
Review resolution: The blind reviewers disagreed on primary lineage (operations_research versus economics_finance); authoritative or primary research supports operations_research as the best historical origin. Pushing a calibrated demand-and-capacity model through extreme off-baseline loads to locate failure thresholds is operations-research stress analysis. IMF stress-testing doctrine distinguishes sensitivity and coherent scenario analysis under exceptional but plausible shocks; economics supplies demand behavior while OR supplies capacity modeling. The cited IMF, Introduction to Applied Stress Testing; IMF, Stress Testing for Banking Supervisors directly supports the defining operation used in that choice. All independently supported contributing domains are retained without an arbitrary cap, while domain_reach=multi_domain records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Lucas, R. E., Jr. "Econometric Policy Evaluation: A Critique". Carnegie-Rochester Conference Series on Public Policy 1, 19–46 (1976). Warns that policy changes can alter agents' decision rules and the econometric relationships used to evaluate a new regime. registry ↩