Assumption Stress Testing

Test whether a plan still works when its core assumptions are broken, reversed, strained, delayed, or made uncertain.

Solution archetype #

68

Problem family

Uncertainty, Evidence & Inference Failure

Problem subfamily

Forecast, Scenario, Assumption & Sensitivity Uncertainty

The Diagnostic Story

Symptom: A plan is approved and everyone is confident — but that confidence rests on a cluster of premises that were never written down, never challenged, and never tested. Risks are discussed, but nobody asks which assumptions those risks would break. When disruption eventually arrives, the team discovers that several "independent" assumptions fail together in ways that were entirely foreseeable.

Pivot: Convert hidden premises into explicit stress-test objects: name the assumptions the plan needs to hold, describe how the plan fails when each is violated, and use that exposure to produce safeguards, monitoring triggers, and staged commitments rather than reassurance theater. The intervention is not about pessimism — it is about making fragility visible before it becomes sunk cost.

Resolution: Assumptions are now named, owned, and connected to the plan elements they support. High-consequence assumption failures have safeguards, fallbacks, or explicit acceptance decisions rather than surprise. Monitoring systems detect assumption drift early enough to revise course rather than absorb damage.

Reach for this when you hear…

[product strategy] “We built the whole roadmap on 'enterprise customers will want the self-serve tier' — and nobody stress-tested that until six months post-launch.”

[infrastructure planning] “The capacity model assumed stable demand growth, but we never asked what happens if two of those assumptions fail in the same quarter.”

[policy design] “The implementation plan listed twenty risks but never once asked which of our core premises those risks would actually break.”

When This Archetype Applies

No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.

Diagnostic problem

A plan, model, strategy, policy, or roadmap appears robust only because its core assumptions have not been surfaced, challenged, or tested against futures in which they are false, reversed, delayed, strained, or only partly true.

What this problem means

Plans often look coherent because their premises stay in the background. A schedule assumes capacity. A policy assumes compliance. A business case assumes adoption. A resilience plan assumes staff, authority, and communications will be available under stress.

The structural problem is false robustness: the plan appears strong because the conditions required for success are not named, tested, owned, or monitored. When the future violates those premises, the plan fails in ways that seem surprising only because the assumptions were invisible.

Show the applicability expression

Applicability expression6 distinct conditions

Unchallenged load-bearing premiseandany oneQuestionable decision premisesorBest-case plan assumptionsorUnexamined failure assumptionsorPressure suppresses challengeorUnoperationalized uncertainty

Algebraic1∧(A∨B∨C∨D∨E)

groundedpartly groundedopen

Equivalent to the 5 condition sets it replaces, with 4 duplicate condition cards removed.

1Required in every casenumbered 1–1

These hold no matter which pattern applies.

1

Unchallenged load-bearing premise · open

The cited premise or pressure is load-bearing and remains insufficiently challenged, making robustness conditional on it. more

and also

5At least one of theselettered A–E

Any single one of these completes the pattern.

A

Questionable decision premises · open

A decision depends on premises that are uncertain, weakly evidenced, politically convenient, or socially hard to question. more

or — any one satisfies this slot

B

Best-case plan assumptions · open

A plan is being approved on best-case continuity, stable demand, adequate capacity, stakeholder cooperation, regulatory permission, or assumed timing. more

or — any one satisfies this slot

C

Unexamined failure assumptions · open

The team has produced a roadmap, forecast, model, business case, policy, or contingency plan but has not asked what assumptions would make it fail. more

or — any one satisfies this slot

D

Pressure suppresses challenge · open

There is pressure for confidence, consensus, speed, or funding that could suppress uncomfortable assumption challenge. more

or — any one satisfies this slot

E

Unoperationalized uncertainty · open

Known uncertainty exists, but the planning process has not converted it into safeguards, trigger monitoring, or staged commitments. more

Other requirements and context (1)

Why these sit outside the expression

Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.

• Application gateThe cost of discovering a false assumption after commitment would be high, irreversible, unsafe, or reputationally damaging. more

Coverage

0 of 6 conditions grounded · 6 open.

Read the methodology · Download the trigger-logic data

Mechanisms / Implementations

• Assumption Audit: Sweeps a whole plan or decision for the assumptions it silently rests on, keeps the load-bearing ones, tests their support, and names what would have to be true instead where support is thin.
• Assumption Register: A shared record of the premises a plan is betting on — each with its evidence basis, an owner, and an expiry or invalidation condition — so the beliefs holding up a decision are named and re-checked rather than silently assumed true forever.
• Failure Mode and Effects Table: Adapts FMEA structure to assumption failure: one row per way a key premise could break, each rated for effect, severity, and detectability into a priority score, with a named mitigation.
• Premortem: A facilitated exercise that assumes the plan has already failed and works backward to infer which premises must have been false, surfacing the hidden assumptions that forward planning glosses over.
• Red-Team Future Challenge: Assigns a protected team the standing job of arguing that the plan's most favored premise is wrong, manufacturing the dissent that hierarchy, optimism, and sunk cost would otherwise suppress.
• Resilience Tabletop Exercise: A facilitated, real-time rehearsal in which a team responds to an unfolding adverse scenario, exposing which response-plan assumptions — staffing, authority, communications — break under live coordination stress, then revising the plan.
• Scenario Stress Test: Constructs a bounded, internally coherent adverse future — a defined shock — and runs the plan's forward premises through it to see which ones break when the whole world moves at once.
• Sensitivity Analysis Workshop: A working session that systematically varies a model's numeric inputs to measure how far the conclusion moves with each — and how assumptions compound — ranking which quantitative premises the answer actually hangs on.
• Stress-Test Scorecard: A one-page verdict sheet that consumes the results of the stress tests and gives each key assumption a confidence grade, a reversibility flag, and a disposition — safeguarded, monitored, or knowingly accepted.
• Trigger Dashboard: A live monitoring surface that watches a named leading indicator for each critical assumption and, when one crosses its threshold, alerts the assumption's owner — keeping premises governed after the plan is committed.

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 (4)

• Black Swan (High-Impact, Low-Probability Events): High-impact unexpected events.
• Scenario Planning: Construct plausible futures.
• Sensitivity Analysis (in Operations Research): Analyze impact of parameter variation.
• Uncertainty: Incomplete knowledge.

Also references 10 related abstractions

• Bounded Rationality: Limited decision capacity.
• Counterfactual Reasoning: Hypothetical alternatives.
• Fail-Safe: Default to safe state on failure.
• Fault Tolerance: Continue operating under failure.
• Feedback: Outputs influence inputs.
• Hypothesis Testing (Null vs. Alternative): Null vs alternative evaluation.
• Invariance: Properties unchanged under transformation.
• Resilience: Absorb shocks and adapt.
• Robustness: Maintain functionality under stress.
• Stress and Rupture: Accumulated tension leads to break.

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Scenario Assumption Stress Test · implementation variant · recognized

Tests key plan assumptions by placing them inside divergent future scenarios or adverse contextual shifts.

Quantitative Sensitivity Stress Test · mechanism family variant · recognized

Varies numerical assumptions or parameters to reveal which variables make a conclusion, forecast, or plan fragile.

Premortem Assumption Extraction · implementation variant · recognized

Uses an imagined future failure to infer which assumptions would have to be wrong for that failure to happen.

Adversarial Assumption Challenge · governance variant · recognized

Assigns challengers to contest assumptions that hierarchy, incentives, or optimism make hard to question.

Assumption Trigger Governance · governance variant · candidate

Emphasizes monitoring signals and decision rules that govern what happens when a critical assumption starts to fail.

Editorial Notes

Problem Classification

Classification: Uncertainty, Evidence & Inference Failure → Forecast, Scenario, Assumption & Sensitivity Uncertainty

Problem kernel: plans appear robust only under hidden assumptions

Rationale: Core assumptions remain unstated and untested against plausible reversal, delay, strain, or partial failure, concealing forecast sensitivity.

Independent corroboration: The earliest necessary condition in the frozen evidence is: A plan, model, strategy, policy, or roadmap appears robust only because its core assumptions have not been surfaced, challenged, or tested against futures in which they are false, reversed, delayed, strained, or only partly true. 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.