Red-Team Failure Review¶
Adversarial review — instantiates Premortem Calibration
Hands the plan to an independent, adversarial reviewer whose job is to find how it fails, free of the insiders' stake in its success.
The Red-Team Failure Review is the archetype's independence mechanism. Its defining property is not the analysis it does but who does it: a person or group deliberately placed outside the plan's ownership, tasked and rewarded for finding failure rather than defending success. That structural separation is the whole point. Insiders — however skilled — share the success story, the sunk effort, and the social cost of dissent; a red team shares none of these, so it can name the leadership assumption, the incentive problem, or the capacity gap that the room cannot say out loud. The red team therefore does two things no insider mechanism can: it generates failure causes independently, unanchored by the team's framing, and it substitutes structural independence for interpersonal courage, relieving anyone of the need to be the one who says the uncomfortable thing. It is the antidote to safe-cause bias.
Example¶
A hospital network is a month from cutting over to a new patient-records system, and its own IT and clinical teams have a polished incident-response plan for the migration weekend. Because the teams that wrote the plan also own its success, leadership commissions a red-team failure review: two security engineers from a different division, plus an external consultant, are given the plan and a single charge — break it; assume you are the outage, and tell us how you win. Freed from the authors' investment, they generate causes the insiders never raised: the rollback procedure assumes a clean database snapshot that the backup window can't actually guarantee; the "war room" bridge depends on the same network segment being migrated; the on-call rota has one person who understands the legacy interface, and he is on the cutover team, not the recovery team. Crucially, because the finding comes from outsiders with no stake, no insider has to be the person who tells their own director that the recovery plan has a single point of failure that is a colleague. The red team's report — a set of independently-generated failure paths, delivered without the political cost of internal dissent — is what it hands back.
How it works¶
- Separate the reviewer from the owner. The essential setup is structural: whoever runs the review must not own the plan, its budget, or its reputation.
- Charge them to break it, not to grade it. The mandate is adversarial — find the path to failure — not a balanced assessment that lets the success story reassert itself.
- Generate independently before reading the insiders' list. The red team produces its own failure causes first, so its output is not just a re-ranking of what the team already thought.
- Report through the independence, not around it. Findings are surfaced in a way that attributes them to the outside review, so no insider carries the social cost of having raised them.
Tuning parameters¶
- Degree of independence — an internal peer from another team versus a fully external adversary. More independence buys more candor and less shared blind-spot, at higher cost and lower context.
- Adversarial intensity — a constructive critical read versus a no-holds-barred "assume you are the attacker." Higher intensity surfaces more and uglier failures but can breed defensiveness and be dismissed as unrealistic.
- Access to insider material — blind review versus full briefing. A briefed team is faster and sharper; a blind team is less anchored but may miss context and re-raise handled risks.
- Timing — a single pre-commitment review versus a standing adversarial function. Standing red teams catch drift over time but risk becoming domesticated and losing their edge.
When it helps, and when it misleads¶
Its strength is that it defeats the failure mode insiders structurally cannot: it names the politically unsafe cause, because the naming is done by people with nothing to lose — the logic that gives organized red teaming its value across military, intelligence, and security practice[n1]. It is the mechanism to reach for precisely when the team is too invested, too aligned, or too hierarchical to critique itself.
It misleads when independence curdles into contrarianism. A red team rewarded only for finding problems will manufacture them, producing a wall of low-probability objections that a review board can use to reject anything — status-quo bias wearing the costume of rigor. It can also be theater: a red team with no real independence, or whose findings are politely filed and ignored, launders the plan rather than testing it. The guarding discipline is to protect the team's independence for real and to route its findings into the ranking and safeguard steps, so adversarial generation becomes calibrated action rather than a veto.
How it implements the components¶
The red team realizes the archetype's independence components:
independent_failure_generation— it produces failure causes from outside the plan's ownership, unanchored by the team's success framing, reaching causes insiders won't raise.psychological_safety_boundary— it supplies that boundary structurally: because the outsiders carry the critique, no insider bears the social cost of dissent, a different route to the same protection the workshop provides through facilitation ground rules.
It does not build the assumption_exposure_map or produce the vulnerability_ranking — the insider analytic work of tracing causes to load-bearing assumptions and prioritizing them belongs to Assumption Stress Test, its nearest twin; the red team supplies the outside challenge the stress test cannot supply about its own blind spots, and then the stress test ranks what both surfaced.
Related¶
- Instantiates: Premortem Calibration — the red team is the archetype's independence and adversarial-generation mechanism.
- Sibling mechanisms: Premortem Workshop · Prospective Hindsight Prompt · Failure-Mode Brainstorm · Assumption Stress Test · Risk Register Update · Contingency Buffer Review · Failure Trigger Dashboard
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Red-Team Failure Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it hands the plan to an independent, adversarial reviewer whose job is to find how it fails, free of the insiders' stake in its success.
Independent corroboration: The frozen evidence defines Red-Team Failure Review as 'Hands the plan to an independent, adversarial reviewer whose job is to find how it fails, free of the insiders' stake in its success', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Independent adversarial challenge descends from military red teaming.
Related originating lineages:
- Engineering & Design — Failure-mode and safety review materially shape systematic search for how a plan breaks.
Review resolution: Both blind reviewers agree that military_strategic_studies is the primary origin. Explicit reconciliation of alternate origin disagreement adopts reviewer_a's classification because independent adversarial challenge descends from military red teaming. The resulting lineage records alternates=engineering_design, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
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¶
The red team and the workshop both protect dissent, but at different layers: the workshop makes the room safe through stated ground rules, while the red team removes the need for in-room courage altogether by putting the critique in outside hands. High-stakes, high-hierarchy decisions often want both — safe facilitation for insiders and an external adversary for the causes insiders still won't voice.
[n1] Red teaming is the practice of a designated independent group adopting an adversarial stance to test a plan, system, or organization's own assumptions, developed in military and intelligence analysis and now common in cybersecurity. Its power comes from the structural separation between the team that owns the plan and the team charged with defeating it. ↩