Red-team your plan with a formal adversarial review
Assign someone the explicit role of finding every way your plan could be wrong or fail.
Why it works
A formal red team — originally a military technique — assigns the role of adversary to a person or group whose job is to defeat the plan. Unlike ordinary critique, which is politely bounded, a red team has permission and expectation of aggressive challenge. This changes the social dynamics that confirmation bias typically exploits: the red teamer is expected to find problems, not to be constructive, which unlicenses the confirmation-protective instincts of both reviewer and presenters.
How to do it
- After finalizing a plan, designate one person as the red team — ideally someone outside the project with relevant expertise.
- Give them the explicit mandate to find every flaw, not to balance strengths and weaknesses.
- Do not allow the plan author to defend in real-time; the red team presents findings first.
- Respond to each finding with either a mitigation or an explicit acceptance of risk.
Evidence
Red teaming is an established practice in military intelligence and cybersecurity, with documented ability to surface vulnerabilities that internal teams miss. Formal research is primarily organizational case study rather than controlled experiment. (clinical)
Red team quality depends entirely on the skill and genuine independence of the red team member; an insider who is too aligned with the plan will produce weak challenges.
Common mistake
Assigning the red team role to someone who agrees with the plan and wants it to succeed — producing a nominal red team whose critiques are too gentle to be useful.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Confirmation Bias: Seeing What You Expect to See
- Deliberately consider the opposite hypothesis
For any belief you are testing, explicitly generate the strongest case for the opposing view.
- Run a pre-mortem before committing to a plan
Imagine the plan has already failed and ask what went wrong.
- Deliberately seek out sources that disagree with you
For any important belief, find and read the best-regarded opposing view.
- Invite an adversarial collaborator
Find someone whose genuine prior is the opposite of yours, and work together on the same evidence.
- Maintain a belief-tracking log with timestamps
Record your beliefs and confidence levels before evidence arrives, so you can see whether you actually updated.
- Structure the analysis before searching for evidence
Define what you’re looking for and what would count as evidence before starting your search.
Related concepts
- Bayesian Thinking: How to Update Beliefs Rationally
Holding beliefs as probabilities and updating them when evidence arrives
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Mental Models: Charlie Munger’s Latticework Approach
Building the multi-disciplinary toolkit that lets you see what single-discipline thinkers miss
- The Availability Heuristic: Why Memorable Feels Probable
The mental shortcut that makes vivid and recent feel probable — and the practices that correct for it