Failure-Mode Brainstorm¶
Generative technique — instantiates Premortem Calibration
Generates a broad inventory of concrete ways the plan could fail, seeded by how comparable efforts actually came apart.
The Failure-Mode Brainstorm is the generative engine of the archetype: given the failure frame, it produces the inventory — a wide, deliberately un-pruned list of concrete ways the plan could break. Its defining commitment is breadth over judgment. It is not the moment to decide which failures matter, how likely they are, or which assumption underlies them; it is the moment to get everything nameable onto the wall, including the awkward, low-status, and easy-to-ignore causes. What keeps it from being a mere free-association session is its second commitment: it seeds imagination with real reference cases — how similar projects, expeditions, launches, or rollouts actually failed — so the list is anchored in the outside view rather than bounded by what this particular team can imagine on a good day. Frame comes from the prompt; priority comes later; breadth and grounding are this mechanism's whole contribution.
Example¶
A four-person team is planning a spring attempt on an 8,000-metre peak, and the group chat is all logistics and optimism. Their lead runs a failure-mode brainstorm. With the failure frame already set — assume we turned back or worse, and the expedition is a write-off — she does two things. First she opens the accident bulletins and expedition reports from the last decade on that mountain and pulls the reference cases: the seasons lost to a warm, unstable snowpack; the fixed-rope bottleneck below the summit that stranded parties past their turnaround time; the descent falls that outnumber the ascent ones. Then, with those on the table, the team floods a shared list with their own concrete failure modes — a summit-fever turnaround overshoot, a stove failure at high camp, a client who won't clip in correctly, a satellite phone that dies before the weather window call. No one argues about which is likeliest; the rule is to keep naming. Forty causes go up in twenty minutes, a third of them prompted directly by "that's how the 2019 party got caught." The un-ranked, reference-anchored list is what the team hands to the ranking step — the brainstorm's job is done when the wall is full.
How it works¶
- Inherit the frame, don't recreate it. The brainstorm starts after the failure is assumed; it spends none of its energy on the reframe and all of it on generation.
- Pull reference cases first. Before or alongside generation, surface how comparable efforts actually failed — accident reports, postmortems, base rates — so the list reaches past the team's imagination.
- Flood, then dedupe — do not rank. Capture every nameable cause, explicitly inviting the awkward ones; merge duplicates but resist the urge to prioritize or assign likelihood.
- Widen the categories. Sweep across technical, human, environmental, coordination, and incentive causes so a single vivid failure type doesn't crowd out the rest.
Tuning parameters¶
- Reference-case depth — a quick recall of "how these usually go" versus a researched dossier of comparable failures. Depth broadens and grounds the list but costs time and can anchor too hard on one salient disaster.
- Divergence discipline — how strictly ranking and debate are deferred. Strong deferral maximizes breadth; loosening it lets the group converge sooner at the cost of missed causes.
- Category scaffolding — free-form versus a checklist of failure domains. Scaffolding guarantees coverage but can suppress the genuinely novel cause that fits no bucket.
- Group size and mode — solo lists merged versus live round-robin. More independent inputs widen coverage; live generation builds shared ownership but risks anchoring.
When it helps, and when it misleads¶
Its strength is coverage: it is the mechanism that turns a vague unease into a concrete, inspectable set of failure modes, and by anchoring on real comparable cases it counters the team's natural tendency to imagine only the failures it has personally seen — the same instinct formalized in disciplined failure enumeration methods like FMEA[n1].
It misleads in two ways. Left un-ranked forever, a long list of failures produces unbounded pessimism — vivid but improbable scenarios drown the decision-relevant ones, which is exactly why the brainstorm must hand off to prioritization rather than substitute for it. And a poorly seeded brainstorm exhibits safe-cause bias: the team names technical and external causes freely but avoids the load-bearing assumptions and leadership decisions. The guarding discipline is to insist the reference cases include human and organizational failures, and to treat the raw list as an input to ranking, never as the finished analysis.
How it implements the components¶
The brainstorm realizes the archetype's generation components:
failure_cause_list— its primary output: the broad, deduped inventory of concrete ways the plan could fail, including awkward and low-status causes.reference_case_anchor— it seeds and grounds that inventory in how comparable efforts actually failed, pulling the list past the team's first-hand imagination.
It does not create the assumed_failure_scenario (that frame is set by Prospective Hindsight Prompt, its nearest twin) and it deliberately does not perform the assumption_exposure_map or vulnerability_ranking — mapping causes to load-bearing assumptions and prioritizing them belongs to Assumption Stress Test.
Related¶
- Instantiates: Premortem Calibration — the brainstorm supplies the raw cause inventory the rest of the arc works on.
- Consumes: Prospective Hindsight Prompt sets the failure frame the brainstorm generates inside.
- Sibling mechanisms: Premortem Workshop · Prospective Hindsight Prompt · Assumption Stress Test · Red-Team Failure Review · Risk Register Update · Contingency Buffer Review · Failure Trigger Dashboard
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Failure-Mode Brainstorm operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it generates a broad inventory of concrete ways the plan could fail, seeded by how comparable efforts actually came apart.
Independent corroboration: The frozen evidence defines Failure-Mode Brainstorm as 'Generates a broad inventory of concrete ways the plan could fail, seeded by how comparable efforts actually came apart', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Systematic generation of ways a design or plan could fail derives from reliability and hazard-analysis practice.
Related originating lineages:
- Organizational & Management Science — Premortem and project-risk workshops materially shape group elicitation from comparable failures. Premortem workshops and lessons-learned practice materially shape facilitated generation from comparable failed efforts.
Review resolution: Both reviewers agree that engineering_design is primary. I retain organizational_management only as formative origin lineages; cross_disciplinary_synthesis is appropriate because the final form materially combines the agreed primary with the retained formative lineages. Reach is universal because the structure is portable across essentially any domain with the stated problem, an applicability judgment kept separate from provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. No unresolved historical ambiguity remains after reconciling the secondary fields.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Failure Mode and Effects Analysis (FMEA) is a structured reliability method for enumerating the ways a system or process can fail before it does. The brainstorm is its generative cousin — it produces the raw failure modes; disciplined FMEA additionally scores and prioritizes them, which here is the separate ranking step. ↩