How does "Map and stress-test your key assumptions" work?

Every plan rests on assumptions: about customer behavior, competitor response, resource availability, your own capabilities. These assumptions are often invisible because they feel obvious, and they are exactly the things a genuine red team attacks. Making them explicit forces an honest look at which assumptions are load-bearing and which can be verified before betting the plan on them.

How does "Use reverse brainstorming to find failure modes" work?

Forward brainstorming (how to succeed) tends to reinforce the plan’s existing direction, because the team is already oriented toward the goal. Reversing the question — actively generating ways to make the plan fail — activates different associations and removes the optimism bias that forward planning carries. People who would hesitate to raise a risk directly often surface it enthusiastically when framed as sabotage.

How does "Simulate the adversary’s response to your move" work?

Strategy is often planned against a passive competitor — a static snapshot of what they are doing now. Real competitors adapt: your move changes their optimal response. Simulating their response forces you to model their incentives, capabilities, and information, which reveals whether your strategy holds up against an active, intelligent opponent rather than against the idealized plan in a vacuum.

How does "Combine the pre-mortem with red team pressure" work?

A standard pre-mortem asks team members to imagine failure and work backward. This activates concerns but is constrained by what each person is willing to voice in the group. A red team pre-mortem adds a second layer: after the group pre-mortem, the designated red team pushes specifically on the failure modes the group was reluctant to name or dismissed too quickly. The combination surfaces both the socially acceptable and socially risky concerns.

How does "Require the plan to change, not just the risk register" work?

Red team findings are often captured in a risk register and then set aside, leaving the original plan unchanged. This happens because the red team findings are framed as a list of concerns rather than as inputs that require a response. The mechanism of value in red teaming is plan adaptation: the plan improves because it is exposed to adversarial pressure, not because adversarial concerns are documented and filed.

strategy

What is red teaming and how do you use it to find flaws in your own plans?

How to build in adversarial pressure before a plan meets reality

Short answer

Red teaming is the practice of assigning someone — or a structured thinking process — to actively try to break your plan, identify its assumptions, find adversarial responses, and surface the failure modes that optimism and groupthink suppress. It originated in military and intelligence contexts and is now used in corporate strategy, security, and product development. The evidence for its effectiveness is largely organizational and practitioner-based rather than from controlled trials.

Optimism bias and confirmation bias make plans feel more solid than they are. A red team is a structured counter-pressure: people whose explicit job is to find what’s wrong, not to refine what’s right. It is not brainstorming risks — it is actively trying to make the plan fail, which surfaces different vulnerabilities. The practices below cover how to run a red team, what distinguishes it from ordinary critique, and how to use its outputs.

The practices (6)

Why it works

Groupthink and social pressure suppress dissent even when people have genuine doubts, because raising concerns feels disloyal or obstructive. Formalizing the dissenting role removes the social cost: the devil’s advocate is doing their assigned job, not being difficult. This makes it safe to surface doubts that would otherwise stay private, because the role, not the person, carries the challenge.

How to do it

1At the start of any significant planning or decision session, name one person the devil’s advocate.
2Give them explicit license — and responsibility — to argue the strongest possible case against the plan.
3Rotate the role across team members over time, so dissent is normalized as a function rather than attached to one "critic".
4After the session, thank the devil’s advocate explicitly — the team needs to see the role rewarded, not resented.

Evidence

Observational

Research on dissent in groups shows that even a single member consistently arguing an alternative position significantly improves group decision quality, primarily by increasing cognitive diversity of the exploration — even when the dissenter is wrong.

Honest caveat: Effects on decision quality are demonstrated in lab settings; the transfer to organizational decisions, and whether the formal role is as effective as genuine minority opinion, is less well established.

— Nemeth et al. (2001), the liberating role of conflict in group creativity, European Journal of Social Psychology

Common mistake: Appointing a devil’s advocate but treating their challenges as theater to be politely absorbed rather than taken seriously, which preserves the form but not the function.

Go deeper on this practice →

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Start with IX Coach →