Premortem Calibration¶
Imagine a plan has already failed so hidden risks and overoptimistic assumptions become visible before commitment hardens.
The Diagnostic Story¶
Symptom: A plan is evaluated mostly through its success narrative. Risk discussion is short and generic; estimates assume smooth execution; team members privately worry but hesitate to voice concerns that might sound disloyal. Contingency plans are vague, ownerless, or disconnected from realistic failure paths. Confidence is expressed as enthusiasm, and no one asks how the plan could fail despite good intent.
Pivot: Shift the evaluation frame deliberately: assume the plan has already failed, then ask what caused it. Use the failure causes to revise scope, safeguards, ownership, buffers, and go/no-go criteria before commitment hardens — protecting honest risk disclosure from blame and separating calibrated readiness from performative optimism.
Resolution: Hidden assumptions, weak dependencies, and plausible failure paths surface while revision is still possible. Plans become more robust through targeted safeguards, and probability, budget, and schedule expectations are better calibrated. The decision record shows which vulnerabilities were anticipated and how they were addressed, improving future learning.
Reach for this when you hear…¶
[product launch] “We go live in two weeks and the whole team is bullish, but I want to spend an hour assuming the launch tanked and working backward — because right now our contingency plan is basically 'hope'.”
[infrastructure ops] “Every major incident we've had was something someone privately thought was a risk but didn't want to be the person who slowed the rollout down.”
[public health planning] “The deployment plan assumes healthcare workers will show up for training on the new protocol, but nobody asked what happens if uptake is forty percent instead of ninety.”
When This Archetype Applies¶
Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.
Diagnostic problem
A plan, forecast, commitment, or launch is evaluated mostly through its success narrative, while plausible failure paths, weak assumptions, and downside preparations remain underexplored.
What this problem means
The structural problem is success-story dominance. People often evaluate a favored plan by imagining the path where effort, coordination, demand, capacity, technology, politics, and timing cooperate. This creates confidence, but it can also suppress information about failure paths.
The failure information may be missing for several reasons: optimism bias, sponsor enthusiasm, social pressure, lack of implementation detail, uncertainty avoidance, or fear of seeming negative. As a result, the group underweights plausible breakdowns until the cost of correction is higher.
Show the applicability expression
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Costly hidden vulnerabilities · grounded
Potential failure is costly enough that hidden vulnerabilities should be surfaced before execution.
The source archetype describes the situation as follows: Failure would be costly enough that hidden vulnerabilities should be surfaced before execution. The normalized requirement above isolates the load-bearing portion used in this condition set.
Assumption-dependent plan · grounded · any one of 5
The plan depends on uncertain assumptions about demand, behavior, coordination, funding, capacity, timing, regulation, or external conditions.
People often evaluate a favored plan by imagining the path where effort, coordination, demand, capacity, technology, politics, and timing cooperate. The narrower requirement in this condition set is: The plan depends on uncertain assumptions about demand, behavior, coordination, funding, capacity, timing, regulation, or external conditions.
Other requirements and context (3)
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.
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Application gateThe group is preparing to commit resources, reputation, attention, authority, or irreversible action to a plan.
Supporting contextDecision makers are excited, time-pressured, status-invested, or socially aligned around success.
Solution feasibilityPeople can still revise scope, safeguards, ownership, buffers, monitoring, or go/no-go criteria.
The team should still be able to add safeguards, adjust scope, change sequencing, assign owners, define warning triggers, or change the decision itself. In this archetype, the relevant feasibility condition is: People can still revise scope, safeguards, ownership, buffers, monitoring, or go/no-go criteria. It identifies something that must be possible or available for the intervention to be workable.
Coverage
2 of 2 conditions grounded.
Mechanisms / Implementations¶
- Assumption Stress Test: Isolates the plan's load-bearing assumptions and pushes each to its breaking point to see which ones sink the plan if they turn out wrong.
- Contingency Buffer Review: Converts ranked failure causes into right-sized schedule, budget, and scope buffers, anchored on how much slack comparable efforts actually needed.
- Failure Trigger Dashboard: Turns the scariest failure paths into a small set of watchable early-warning indicators, each wired to a named owner who acts when it trips.
- Failure-Mode Brainstorm: Generates a broad inventory of concrete ways the plan could fail, seeded by how comparable efforts actually came apart.
- Premortem Workshop: A facilitated session that imagines a future failure and works backward to causes and prevention actions.
- Prospective Hindsight Prompt: Asks people to stand in an imagined future where the plan has already failed and explain, in hindsight, why it did.
- Red-Team Failure Review: Hands the plan to an independent, adversarial reviewer whose job is to find how it fails, free of the insiders' stake in its success.
- Risk Register Update: Records the ranked vulnerabilities and the changes they triggered in a living, dated ledger so the premortem's findings outlast the meeting.
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)
- Optimism Bias: Overestimate positive outcomes.
- Probability: Quantifies uncertainty and likelihoods.
- Scenario Planning: Construct plausible futures.
Also references 5 related abstractions
- Counterfactual Reasoning: Hypothetical alternatives.
- Margin of Safety: Buffer capacity.
- Resilience: Absorb shocks and adapt.
- Robustness: Maintain functionality under stress.
- Uncertainty: Incomplete knowledge.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Project Premortem Calibration · domain variant · recognized
Applies premortem calibration to project plans so schedule, scope, dependency, and delivery assumptions are revised before commitment.
Red-Team Failure Calibration · mechanism family variant · recognized
Uses an adversarial or independent review role to construct credible failure paths and recalibrate confidence in a favored plan.
Assumption Stress-Test Calibration · implementation variant · candidate
Focuses the premortem on load-bearing assumptions and asks how the plan fails if those assumptions weaken or break.
Monitoring-Trigger Premortem · temporal variant · recognized
Uses premortem failure paths to define early-warning indicators, monitoring triggers, and response ownership after the plan proceeds.
Editorial Notes¶
Problem Classification¶
Classification: Uncertainty, Evidence & Inference Failure → Forecast, Scenario, Assumption & Sensitivity Uncertainty
Problem kernel: success narrative excludes plausible failure paths
Rationale: Earliest causal condition: A plan, forecast, commitment, or launch is evaluated mostly through its success narrative, while plausible failure paths, weak assumptions, and downside preparations remain underexplored.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A plan, forecast, commitment, or launch is evaluated mostly through its success narrative, while plausible failure paths, weak assumptions, and downside preparations remain underexplored. 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.