Support Depletion Premortem¶
Foresight exercise — instantiates Hidden Support Depletion Guarding
A structured foresight session that assumes the shell has already collapsed and works backward to name which hidden support gave way, and how.
Most planning imagines success and asks how to reach it; a premortem imagines failure and asks how it happened. Support Depletion Premortem applies that inversion to this archetype specifically: the group is told to assume that, a year from now, the visible shell has collapsed — and their task is to reconstruct which hidden support was quietly depleted, by what pathway, and at what threshold it gave way. Its defining move is prospective and imaginative — it reasons forward from an assumed future failure to surface depletion pathways before any evidence of them exists. This is what separates it from a near-miss review, which reads real past incidents; the premortem has no incident to read, so it manufactures the collapse in imagination to pull the hidden pathways into view early.
Example¶
An election authority is planning to run the next cycle much as it ran the last — the visible shell, procedural compliance and on-time results, has held for years. A support depletion premortem convenes officials, poll workers, and observers and gives them a single prompt: it is eighteen months from now and public confidence in the count has collapsed; write the story of how. Working backward, the group surfaces supports no dashboard was watching. Trust in the process, they realize, is a load-bearing substrate that had been thinning through a pathway of attrition among experienced precinct veterans, growing reliance on undocumented workarounds by overstretched staff, and a slow erosion of the local relationships that once absorbed disputes quietly. They estimate the unsupported span — how many precincts are now run by first-timers with no institutional memory — and the threshold at which a single contested result would overwhelm the remaining trust. None of this had shown up in compliance metrics. The premortem turns an imagined collapse into a concrete list of thinning supports to instrument and rebuild while there is still time.
How it works¶
- Assume the collapse as given. Start from a vivid stipulated failure of the shell, not from a risk list; the certainty of the framing is what loosens candor.
- Work backward to the support. Ask specifically which hidden support ran out, resisting shell-level explanations, until a depletion pathway is named.
- Estimate span and threshold. For each surfaced pathway, sketch how much of the shell would then be unsupported and how close the current state is to that threshold.
- Rank by plausibility and lead time. Prioritize the pathways that are both credible and slow-to-detect, since those are where the archetype hides.
Tuning parameters¶
- Framing certainty — "assume it failed" vs. "imagine it might." The definite framing produces more and franker pathways but can feel alarmist.
- Participant diversity — narrow expert group vs. wide cross-section including frontline and outside voices. Breadth surfaces supports insiders take for granted but is harder to run.
- Time horizon — how far in the future the imagined collapse sits. Longer horizons surface slow-depletion pathways; shorter ones stay concrete and actionable.
- Pathway depth — stop at the first named support vs. push to root pathway. Deeper pushes find the real substrate but cost session time.
- Anonymity — open discussion vs. written-then-shared. Anonymous capture reduces optimism and hierarchy effects but loses live build-on.
When it helps, and when it misleads¶
Its strength is that it surfaces depletion pathways with no incident required — its whole value is being early, running before the substrate has produced any warning a monitor could catch. The prospective-hindsight framing measurably loosens the optimism and groupthink that keep hidden supports unspoken.[n1] It is the cheapest way to populate a substrate map with candidate pathways to then instrument.
Its failure mode is that it produces imagined pathways, not measured ones: a premortem can generate a vivid, plausible collapse story that is simply wrong, and — because nothing is measured — it can equally miss the real pathway if the group lacks the right voices. Treated as a verdict rather than a hypothesis generator, it can send effort chasing a fear. The guarding discipline is to treat every surfaced pathway as a candidate to instrument and test, not a finding — handing it to monitoring and inspection siblings for confirmation — and to widen the room until the people who actually work the substrate are in it.
How it implements the components¶
substrate_depletion_pathway— its central output is a set of named, ranked pathways by which support could be quietly consumed.unsupported_span_model— for each imagined collapse it sketches how much of the shell would then be bridging unsupported ground.collapse_threshold_band— it estimates how near the current state sits to the threshold at which each surfaced support gives way.
It does not mine real survived incidents — reading actual near misses as substrate evidence via near_miss_substrate_review is Near-Miss Substrate Review, which works from recorded events where the premortem works from an imagined future.
Related¶
- Instantiates: Hidden Support Depletion Guarding — this is the archetype's imagine-the-collapse foresight step that seeds the substrate map with pathways.
- Sibling mechanisms: Near-Miss Substrate Review · Void or Slack Mapping · Ground-Penetrating or Deep Inspection · Substrate Integrity Dashboard
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Support Depletion Premortem is defined in the frozen evidence as: A structured foresight session that assumes the shell has already collapsed and works backward to name which hidden support gave way, and how. Its operative deployed or enacted form is therefore Experiment, Test & Rehearsal.
Nearest alternative: Assessment, Review & Assurance — Assessment, Review & Assurance can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Futurism & Strategic Foresight
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Imagining failure after support is exhausted uses the prospective-hindsight premortem method.
Related originating lineages:
- Organizational & Management Science — Continuity planning identifies operational dependencies.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a structured foresight session that assumes the shell has already collapsed and works backward to name which hidden support gave way, and how.
Review resolution: The blind reviewers agree that futurism_foresight is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The premortem, introduced by Gary Klein, uses prospective hindsight — imagining that a plan has already failed — to loosen the overconfidence and social pressure that suppress candid risk-talk; research on prospective hindsight finds it increases the number and specificity of causes people can generate for an outcome. ↩