Red Team Analysis¶

Why It Matters¶

Confirmation bias is relentless. We naturally seek evidence supporting our beliefs and dismiss contradicting evidence. We're invested in our plans and can't see their flaws. Red teaming creates institutional skepticism - designating someone to attack the plan is more reliable than asking everyone to "think critically" (they won't). It surfaces blind spots and prevents groupthink by making criticism someone's explicit job.

The Key Move¶

For important plans or beliefs, assign a person or take dedicated time to inhabit the role: "How would an adversary attack this? Where are the weakest points? What am I not seeing because I want this to be true?" Separate critique from generation - don't red team while building. After red team analysis, decide: do we abort, revise, or proceed with risks known?

Classic Application¶

Military planning. Before operations, military red teams simulate enemy decision-making: "If I were the enemy, how would I respond to our plan? Where would I attack? What would I expect us to do?" Reveals vulnerabilities in plans that looked good from friendly perspective.

Surprising Application¶

Academic research. Before submitting a paper, assume you're a hostile reviewer who wants to reject it. "What's the weakest claim? What alternative explanations haven't been ruled out? Where are the statistical problems? What would the strongest counterargument be?" Makes the paper stronger and reduces brutal surprises during peer review.

Failure Modes¶

Superficial red teaming (generating token objections). Status games - red team becomes about looking smart by criticizing rather than improving decisions. Unequal red teaming - attacking opponent's positions while giving your own a pass. Continuous red teaming without ever committing (analysis paralysis). Ignoring red team findings when they're inconvenient.

Go Deeper¶

Zenko, "Red Team: How to Succeed by Thinking Like the Enemy"; Hoffman, "Rethinking Red Teaming" (military applications)