Premortem¶
Facilitation technique — instantiates Assumption Stress Testing
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.
A Premortem is a meeting move: before a plan is committed, the facilitator declares that it is now a year later and the plan has failed, badly, then asks everyone to write the story of why. Its one defining trick is the reversal of stance — instead of asking "what could go wrong?" (which invites loyal reassurance), it treats failure as an accomplished fact and asks people to explain it. That prospective-hindsight framing loosens tongues and memory in a way forward risk-hunting does not: reasons that were unsayable become sayable because no one is predicting doom, only accounting for it. The output is not a ranked risk table or a scenario model — it is a harvested list of the load-bearing premises the plan was quietly resting on, with the most-mentioned ones marked as the assumptions that most deserve testing.
Example¶
A museum is committing to a blockbuster traveling exhibition — a marquee collection on loan, a custom gallery build, a marketing push timed to the school year. On paper the plan is airtight. In the premortem the director says: "It's eighteen months from now. The show opened, and it was a quiet disaster. Take five minutes — write down why." The room, freed from having to be optimistic, fills a wall with failure stories. The insurer's conditions forced climate-control upgrades that blew the build budget. The lender delayed a signature loan, gutting the marketing hook. A competing institution ran an overlapping show across town. Rain-soaked opening weeks kept the family audience home. Collected and clustered, the stories expose the premises no one had written down: that the loan agreements would close on schedule, that this collection was uniquely un-competed, that weather-independent advance sales would carry attendance. Those three, named aloud by half the room, become the assumptions the team now takes to a real test — rather than discovering them in the post-mortem.
How it works¶
- Assume the failure as fact. The facilitator states flatly that the plan has already failed; the task is to explain the failure, not to predict or hedge it.
- Write before speaking. Everyone drafts their account privately first, so the loudest or most senior voice does not anchor the room and quiet dissent survives.
- Harvest and cluster. Read out the causes, group the recurring ones, and translate each failure story back into the premise it implies — "the loan closed late" becomes the assumption "the loan closes on schedule."
- Rank by frequency and conviction. The premises named independently by many people, or with the most force, are flagged as the load-bearing ones to hand downstream for real testing.
Tuning parameters¶
- Failure framing — total catastrophe versus disappointing-but-survivable. A stark "it failed" frees more candor; a milder "it underdelivered" surfaces subtler, more realistic premises.
- Anonymity — signed contributions versus anonymous cards. Anonymity protects the politically costly assumption at the price of follow-up conversation.
- Timeboxing — a fifteen-minute round versus a half-day. Longer sessions reach deeper premises but drift toward rumination and repetition.
- Facilitator neutrality — whether the plan's owner runs the room. An outside facilitator prevents the sponsor from steering the harvest toward comfortable causes.
When it helps, and when it misleads¶
Its strength is uniquely psychological: prospective hindsight measurably loosens the imagination and, more importantly, gives people social cover to voice a doubt they were sitting on.[1] It is fast, cheap, and it surfaces the unstated premises that a checklist of known risks never reaches.
Its failure mode is that it stops at surfacing. A premortem generates a vivid list and a feeling of rigor, then the meeting ends and nothing is tested, owned, or revised — "stress theater" in its purest form. It also skews toward dramatic, memorable failure stories over dull-but-likely ones, and it can be captured by a dominant participant if writing-first is skipped. The guarding discipline is to treat the premortem strictly as an intake step: every load-bearing premise it names must be routed onward to a real test, a safeguard, or a monitored trigger, or the exercise was catharsis, not stress testing.
How it implements the components¶
key_assumption— its backward reasoning names the specific premises the plan silently depended on, distinguishing the load-bearing few from incidental worries by how often and how forcefully they recur.assumption_inventory— the harvested, clustered set of implied premises is exactly the structured inventory the rest of the archetype consumes.
It does not map or rank the failures it surfaces (failure_mode_map, criticality_filter) — that is Failure Mode and Effects Table — and it does not stage a protected adversarial attack on a favored premise (red_team_challenge_role) — that is Red-Team Future Challenge. The premortem opens the space; it does not structure or contest what falls out.
Related¶
- Instantiates: Assumption Stress Testing — the premortem is the discovery front-end that surfaces the premises the rest of the archetype tests and governs.
- Sibling mechanisms: Failure Mode and Effects Table · Red-Team Future Challenge · Resilience Tabletop Exercise · Scenario Stress Test · Sensitivity Analysis Workshop · Stress-Test Scorecard · Trigger Dashboard · Assumption Audit
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Premortem operates as an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation because it 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.
Independent corroboration: The frozen evidence defines Premortem as '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', so its operative form is Experiment, Test & Rehearsal.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Premortem is most plausibly rooted in the psychology tradition because its characteristic form depends on individual cognition, motivation, judgment, and behavior. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Related originating lineages:
- Organizational & Management Science — The organizational_management tradition materially shaped Premortem through its own practice of the coordination, governance, learning, and redesign of organized work.
Review resolution: Both blind reviewers agree that psychology is the primary origin. Explicit reconciliation resolves origin mode disagreement. Formative alternate lineages are retained as organizational_management; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The premortem is a one-shot, whole-group generator; it is at its best precisely once, at the moment of commitment, when the plan feels most finished. Re-running it repeatedly dulls the surprise that makes it work. Because it only surfaces, it is nearly always paired with a structuring or testing mechanism downstream — it is the match, not the fire.
References¶
[1] Prospective hindsight — imagining that a future event has already occurred and explaining it — was shown by Deborah Mitchell, J. Edward Russo, and Nancy Pennington (1989) to increase the number and specificity of reasons people generate for an outcome. Gary Klein later packaged it for planning as the "premortem." withdrawn registry ↩