Sensitivity Analysis Protocol¶
Vary key assumptions or parameters to see which ones materially change the conclusion.
Essence¶
Sensitivity Analysis Protocol is the archetype for testing whether a conclusion survives plausible changes in the assumptions that support it. It is not merely a chart, a table, or a solver setting. The core move is to make uncertainty operational: choose the assumptions that might matter, vary them across defensible ranges, watch the decision-relevant outcome, and identify which assumptions are harmless, material, critical, or invalidating.
The archetype is especially valuable when a model or plan produces a confident recommendation but the input assumptions are uncertain, contested, or likely to move. The goal is not to eliminate uncertainty. The goal is to learn which uncertainty changes the decision.
Compression statement¶
When a model, plan, or decision appears justified but depends on uncertain inputs, systematically vary plausible assumptions, record outcome response, identify critical parameters, and update confidence or follow-up action.
Canonical formula: Given baseline conclusion C from model or plan M with parameters P, vary selected p_i within plausible ranges R_i, observe outcome response ΔC or decision state D, and classify assumptions as stable, material, critical, or invalidating relative to a materiality threshold T.
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A model, analysis, plan, or decision recommendation looks settled, but its conclusion may depend heavily on uncertain assumptions whose influence has not been made visible.
What this problem means
The structural problem is conditional confidence. A plan, model, forecast, ranking, or recommendation appears settled, but its conclusion may depend on uncertain inputs whose influence is hidden. This creates two bad options: either actors overtrust the baseline answer, or they reject the analysis wholesale because uncertainty is present.
Sensitivity analysis creates a middle path. It keeps the baseline explicit but treats it as conditional. The question becomes: under what plausible assumption changes does the conclusion remain stable, and under what changes does it fail?
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Assumption-sensitive decision · grounded
A decision depends on forecasts, estimates, weights, thresholds, or uncertain causal assumptions.
Use this archetype when a decision depends on forecasts, estimates, weights, thresholds, or assumptions that could plausibly be wrong. The narrower requirement in this condition set is: A decision depends on forecasts, estimates, weights, thresholds, or uncertain causal assumptions.
primeSensitivity Analysis (in Operations Research)— Analyze impact of parameter variation.
Unknown influential changes · open
Small changes in context could plausibly change the outcome, but no one knows which changes matter.
A sensitivity protocol turns that disagreement into testable claims: which assumption, over what range, changes which outcome? The narrower requirement in this condition set is: Small changes in context could plausibly change the outcome, but no one knows which changes matter.
Other requirements and context (3)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Supporting contextStakeholders disagree about which assumptions are plausible or important.
The question becomes: under what plausible assumption changes does the conclusion remain stable, and under what changes does it fail? In this archetype, the relevant contextual consideration is: Stakeholders disagree about which assumptions are plausible or important. It helps interpret the situation or strengthens the practical case for examining the archetype.
Supporting contextThe model output is being used to justify a costly, risky, irreversible, or politically contested commitment.
It is a strong fit when the decision is costly, risky, irreversible, politically contested, safety-relevant, or likely to become locked in. In this archetype, the relevant contextual consideration is: The model output is being used to justify a costly, risky, irreversible, or politically contested commitment. It helps interpret the situation or strengthens the practical case for examining the archetype.
Supporting contextA single best-estimate answer is being presented as more certain than the evidence warrants.
This creates two bad options: either actors overtrust the baseline answer, or they reject the analysis wholesale because uncertainty is present. In this archetype, the relevant contextual consideration is: A single best-estimate answer is being presented as more certain than the evidence warrants. It helps interpret the situation or strengthens the practical case for examining the archetype.
Coverage
1 of 2 conditions grounded · 1 open.
When to Use This Archetype¶
Use this archetype when a decision depends on forecasts, estimates, weights, thresholds, or assumptions that could plausibly be wrong. It is a strong fit when the decision is costly, risky, irreversible, politically contested, safety-relevant, or likely to become locked in.
It is also useful when stakeholders distrust a conclusion but cannot yet say what would change it. A sensitivity protocol turns that disagreement into testable claims: which assumption, over what range, changes which outcome?
Do not start here when the baseline objective or decision rule is still unclear. In that case, objective and constraint formulation should happen first. Do not treat this as robust selection either: sensitivity analysis diagnoses fragility; robust solution selection chooses an option after fragility is understood.
Structural Problem¶
The structural problem is conditional confidence. A plan, model, forecast, ranking, or recommendation appears settled, but its conclusion may depend on uncertain inputs whose influence is hidden. This creates two bad options: either actors overtrust the baseline answer, or they reject the analysis wholesale because uncertainty is present.
Sensitivity analysis creates a middle path. It keeps the baseline explicit but treats it as conditional. The question becomes: under what plausible assumption changes does the conclusion remain stable, and under what changes does it fail?
Intervention Logic¶
The intervention begins by stabilizing a baseline case. The baseline records the current model, assumption set, watched outcome, and decision rule. Next, the analyst or decision group selects key parameters: inputs that are uncertain, influential, contested, or consequential if wrong. Each parameter receives a variation range, scenario bundle, distribution, or threshold that can be defended.
The protocol then runs variation tests. Some tests vary one input at a time; others vary combinations or coherent scenarios. The important output is not simply a recalculated number. The important output is the outcome response: what changes, how much it changes, whether the recommendation flips, and whether the change is decision-relevant.
Finally, the results are translated into action. Stable conclusions may proceed with documented confidence. Fragile conclusions may need validation, monitoring triggers, redesign, contingency planning, or robust solution selection.
Key Components¶
Sensitivity Analysis Protocol works as a diagnostic loop that converts a settled-looking conclusion into one whose conditions of validity are explicit. The Baseline Case pins down the reference point — model, assumptions, conclusion, and decision rule — so that any later movement can be interpreted as movement away from a known starting state. From there, the analyst selects each Key Parameter, filtering all inputs down to the ones whose uncertainty actually intersects with consequence. Each chosen parameter receives a Variation Range drawn from data, expert judgment, scenarios, or stress logic; the range must be wide enough to expose fragility but defensible enough to avoid manufactured alarm. The watched Outcome Measure stays fixed during the test so that any change can be attributed to the assumption being varied rather than to a moving target.
The remaining components turn the test mechanics into a decision-grade verdict. The Outcome Response records how the watched measure actually moved under each variation — the evidentiary core that links assumptions to conclusion confidence. The Materiality Threshold tells the protocol which movements count as meaningful, filtering out numerical noise while flagging small changes that flip a recommendation. A Critical Assumption is then identified as any input whose plausible variation crosses that threshold, reverses the recommendation, or violates a constraint; these become the assumptions deserving validation, monitoring, or redesign. Finally, the Robustness Conclusion translates the full pattern of responses into decision language — stable, conditionally stable, fragile, or invalid — so the protocol ends not in a chart but in updated confidence and a clear next move.
| Component | Description |
|---|---|
| Baseline Case ↗ | The baseline case is the reference point for the analysis. It records the model, plan, input assumptions, conclusion, and decision rule before variation begins. Without a baseline, sensitivity testing becomes unstructured tinkering. |
| Key Parameter ↗ | A key parameter is an assumption, coefficient, forecast, threshold, weight, or condition that could materially influence the outcome. The point is not to vary every possible input. The point is to select inputs where uncertainty and consequence intersect. |
| Variation Range ↗ | The variation range defines how far an assumption will be moved. Ranges can come from historical data, expert judgment, external scenarios, policy limits, or deliberate stress cases. A narrow range can hide fragility; an unrealistic range can create irrelevant alarm. |
| Outcome Measure ↗ | The outcome measure is what the protocol watches. It may be a score, ranking, feasibility status, cost, benefit, risk level, recommendation, or decision state. The measure must remain stable during the test so that outcome movement can be interpreted. |
| Outcome Response ↗ | Outcome response records how the watched outcome changes under variation. This is the evidentiary core of the archetype: it connects assumptions to conclusion confidence. |
| Critical Assumption ↗ | A critical assumption is one whose plausible change materially alters the decision, reverses the recommendation, violates a constraint, or substantially changes confidence. Critical assumptions should trigger validation, monitoring, review, or redesign. |
| Materiality Threshold ↗ | The materiality threshold defines what counts as a meaningful change. This keeps the protocol from overreacting to numerical noise or ignoring small changes that flip a decision. |
| Robustness Conclusion ↗ | The robustness conclusion states whether the original conclusion is stable, fragile, conditionally stable, or invalid under plausible variation. It should be written in decision language, not only technical language. |
Common Mechanisms¶
8 documented mechanisms across 4 implementation forms.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Analysis, Modeling & Optimization · 5 mechanisms
- One-way Sensitivity Analysis — Moves one input at a time across its range while holding everything else fixed, then ranks assumptions by how far each alone swings the outcome.
- Probabilistic Sensitivity Simulation — Draws thousands of joint samples from input distributions and reports the share of draws in which the recommendation holds versus flips.
- Scenario Variation — 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.
- Threshold Analysis — Solves backward for the exact value of an input at which the recommendation flips, turning that break-even point into a monitoring trigger.
- Two-way or Multi-way Sensitivity Analysis — Varies two or more inputs at once across a grid of combinations to expose interaction — the effects that appear only when assumptions move together.
Communication, Facilitation & Learning · 1 mechanism
- Assumption Stress-test Workshop — Convenes the people who own or dispute the assumptions to argue defensible ranges, name the decision-carrying ones, and set the validation agenda.
Interface, Display & Cue · 1 mechanism
- Tornado Chart — Draws each input's outcome swing as a horizontal bar, sorted widest-first, so the dominant drivers are legible at a single glance.
Representation, Specification & Plan · 1 mechanism
- Sensitivity Table — Records one row per assumption — its range, outcome response, materiality verdict, and critical flag — so the whole analysis can be audited line by line.
Parameter / Tuning Dimensions¶
The main tuning dimensions are parameter selection, range width, variation structure, outcome granularity, and materiality threshold. A protocol can be narrow and fast, using one-way tests on a few inputs, or broad and expensive, using multi-way scenarios or probabilistic sampling.
Other tuning decisions include whether ranges should represent ordinary uncertainty or extreme stress, whether parameters should vary independently or as linked bundles, whether results should be interpreted numerically or categorically, and whether the output should trigger validation, monitoring, redesign, deferral, or robust solution selection.
Invariants to Preserve¶
The baseline must remain fixed during the test. The watched outcome must remain stable. Variation ranges must be documented and defensible. Critical assumptions must be visible rather than hidden inside aggregate output. Materiality must be tied to decision relevance.
The most important invariant is diagnostic honesty. The protocol should not be used to protect a preferred conclusion. It should reveal the conditions under which that conclusion holds and the conditions under which it fails.
Target Outcomes¶
A good sensitivity analysis produces conditional confidence. It tells decision-makers what they can trust, what they should monitor, what they should validate, and what could change the decision.
The target outcomes are visible fragility, prioritized validation effort, clearer stakeholder disagreement, better monitoring triggers, and stronger downstream robust selection. The output should reduce false certainty without collapsing into indecision.
Tradeoffs¶
Sensitivity analysis trades speed for confidence, simplicity for coverage, and legibility for interaction realism. One-way tests are easy to explain but may miss joint effects. Scenario bundles are more realistic but can be contested. Probabilistic simulations can be rich but may be opaque.
There is also a social tradeoff. A rigorous sensitivity protocol may expose that a preferred recommendation is fragile. That is uncomfortable, but it is the point of the intervention.
Failure Modes¶
Common failures include range laundering, where analysts choose convenient ranges; parameter theater, where many irrelevant inputs are varied while critical ones are avoided; one-way blindness, where dependent parameters are varied separately; and chart substitution, where a tornado chart is mistaken for the full protocol.
Another failure is analysis paralysis. Sensitivity analysis is not complete until results change confidence, monitoring, validation, or decision posture. Endless variation without decision implication is not the archetype working; it is avoidance.
Neighbor Distinctions¶
Sensitivity Analysis Protocol is distinct from Constrained Resource Allocation. Allocation decides how to distribute resources under assumptions; sensitivity analysis tests whether the allocation conclusion survives plausible changes in those assumptions.
It is distinct from Robust Solution Selection. Robust selection chooses an option that remains acceptable across scenarios. Sensitivity analysis identifies the assumptions, thresholds, and scenarios that should inform such a choice.
It is distinct from Uncertainty Explicitness. Making uncertainty visible is useful, but sensitivity analysis actively tests what uncertainty does to the conclusion.
It is distinct from Perturbation Testing. Perturbation testing disturbs a system or model generally; sensitivity analysis varies assumptions with the specific goal of assessing conclusion fragility.
Cross-Domain Examples¶
In budget planning, a city can vary demand growth, labor cost, inflation, and grant timing to see whether a proposed service remains affordable. In infrastructure planning, engineers can vary load forecasts, outage probabilities, and material costs to see whether a design has adequate margin. In public health, analysts can vary prevalence, uptake, treatment effect, and adherence assumptions to see whether a screening recommendation remains beneficial.
In product strategy, a team can vary adoption, churn, support cost, and pricing assumptions before committing to launch. In procurement, a buyer can vary demand, supplier lead time, exchange rates, and defect rates to see whether a sourcing recommendation still holds.
Non-Examples¶
A spreadsheet that recalculates when someone edits cells is not enough. Without defined ranges, watched outcomes, materiality thresholds, and decision implications, it is not a sensitivity protocol.
A solver output under fixed assumptions is not sensitivity analysis. It may be optimization, but the archetype begins when assumptions are varied.
A team choosing the option that performs best across scenarios is closer to robust solution selection. Sensitivity analysis is the diagnostic step that reveals which assumptions and scenarios matter.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Robustness: Maintain functionality under stress.
- Sensitivity Analysis (in Operations Research): Analyze impact of parameter variation.
- Uncertainty: Incomplete knowledge.
Also references 9 related abstractions
- Cost–Benefit Analysis: Evaluate decisions.
- Counterfactuals: Alternate hypothetical scenarios.
- Hypothesis Testing (Null vs. Alternative): Null vs alternative evaluation.
- Monte Carlo Simulation: Random sampling approximation.
- Multiobjective Optimization: Balance competing objectives.
- Optimization: Finds best solution under constraints.
- Probability: Quantifies uncertainty and likelihoods.
- Stationarity: Stable statistical properties.
- Threshold: Safe vs harmful levels.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
One-way Sensitivity Protocol · parameter isolation variant · recognized
Test conclusion fragility by varying one uncertain parameter at a time while holding the rest of the baseline fixed.
- Distinct from parent: The parent includes any governed assumption-variation protocol; this variant uses a one-factor-at-a-time test.
- Use when: {'condition': 'Decision-makers need a simple first pass at which assumptions matter most.'}; {'condition': 'Parameters can be plausibly isolated without creating impossible or misleading combinations.'}; {'condition': 'The goal is explanation and prioritization rather than full uncertainty propagation.'}.
- Typical domains:
- Common mechanisms: One-way Sensitivity Analysis, Tornado Chart
Threshold Sensitivity Analysis · decision flip variant · recognized
Identify the parameter value or condition at which a decision, ranking, constraint, or recommendation changes.
- Distinct from parent: The parent may characterize broad fragility; this variant locates concrete reversal or breach thresholds.
- Use when: {'condition': 'The main question is not whether the outcome moves, but how far assumptions can move before the conclusion changes.'}; {'condition': 'Decision-makers need monitoring triggers or contingency plans tied to critical values.'}; {'condition': 'A recommendation is acceptable only if it survives movement within a plausible safety or confidence margin.'}.
- Typical domains:
- Common mechanisms: Threshold Analysis, Sensitivity Table
Scenario Sensitivity Protocol · scenario bundle variant · recognized
Test a conclusion against coherent bundles of assumptions rather than varying inputs independently.
- Distinct from parent: The parent includes one-way and numeric tests; this variant emphasizes internally coherent scenario worlds.
- Use when: {'condition': 'Important uncertainties move together or define distinct operating worlds.'}; {'condition': 'Qualitative assumptions, institutional conditions, or external shocks cannot be reduced to a single numeric parameter.'}; {'condition': 'Stakeholders need to understand how the conclusion behaves across plausible futures or contexts.'}.
- Typical domains:
- Common mechanisms: Scenario Variation, Assumption Stress-test Workshop
Probabilistic Sensitivity Protocol · uncertainty distribution variant · recognized
Represent uncertain inputs probabilistically and estimate how often the conclusion changes under sampled combinations.
- Distinct from parent: The parent can be deterministic and range-based; this variant adds probabilistic sampling or weighting.
- Use when: {'condition': 'Input uncertainty can be represented with distributions or weighted cases.'}; {'condition': 'Decision-makers care about the frequency or probability of conclusion failure, not only individual stress cases.'}; {'condition': 'Interactions among uncertain inputs are important enough to sample jointly.'}.
- Typical domains:
- Common mechanisms: Probabilistic Sensitivity Simulation, Sensitivity Table
Near names: Assumption Stress Testing, Robustness Check, Parameter Sweep, Sensitivity Test, Scenario Stress Test, Tornado Chart.
Editorial Notes¶
Problem Classification¶
Classification: Uncertainty, Evidence & Inference Failure → Forecast, Scenario, Assumption & Sensitivity Uncertainty
Problem kernel: conclusions hide sensitivity to uncertain assumptions
Rationale: Earliest causal condition: A model, analysis, plan, or decision recommendation looks settled, but its conclusion may depend heavily on uncertain assumptions whose influence has not been made visible.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A model, analysis, plan, or decision recommendation looks settled, but its conclusion may depend heavily on uncertain assumptions whose influence has not been made visible. That is a forecast scenario assumption and sensitivity uncertainty problem because Plans and forecasts hide assumption dependence, alternative futures, reference-class evidence, revision conditions, and uncertainty ranges.
Review outcome: Independent reviewer agreement; high confidence.