Red Team / Blue Team for People Decisions
Borrowed from security and intelligence, red-team/blue-team makes important people decisions stress-tested before they ship.
- Assign a small red team to argue against the decision before it is finalised.
- Especially useful for high-stakes, irreversible people decisions.
- Run it as a 60-minute structured session, not an open debate.
- If no red-team objection lands, the decision is stronger than it would have been.
The biggest people decisions are also the ones where dissent is least welcome. A senior hire the CEO loves, a re-org the head of engineering has been planning for months, a promotion the team has been promised — all of them benefit from being explicitly attacked before being shipped. Red-team / blue-team is a small ritual that creates room for the attack without anyone losing face.
What red-team / blue-team means here
The blue team is the group proposing the decision: usually the hiring manager and HR partner for a hire, the CEO and CPO for a re-org, the manager and grand-boss for a promotion. The red team is a small group — 2–3 people — explicitly tasked with finding the strongest reasons not to do this. Not nitpicks. The case against.
When to use it
- VP+ hires, especially first-of-function hires.
- Any re-org affecting more than 30 people.
- Reductions in force.
- Senior comp decisions (executive packages, retention grants).
- Promotion to senior leadership (Director and above).
How to run the session
- 1Pre-read (24h ahead)Blue team writes a one-pager: decision, rationale, risks already considered, evidence. Red team reads it.
- 2Minutes 0–15: blue team presentsDecision, why, what trade-offs they accept.
- 3Minutes 15–35: red team attacksStrongest arguments against, asked to be specific and falsifiable. Blue team listens, does not defend in real time.
- 4Minutes 35–50: blue team respondsWhich red-team points change the decision, which do not, why.
- 5Minutes 50–60: decisionProceed, modify, or pause. Written summary captures both the decision and the dissent.
Pitfalls
- Red team is too junior to push back — pick people senior enough to disagree with the CEO.
- Red team is too aligned with the blue team — rotate membership; do not let it become a club.
- Decision was already made and the session is theatre — kills the practice; do not do it.
- No written record of dissent — the future review of the decision will be one-sided.
Over time, blue teams start anticipating the red-team objections in their pre-read. The decisions improve before they reach the session. That is the program working.
Read next
All playbooksPost-mortems happen after the failure. Pre-mortems happen before — and Gary Klein's research shows they boost problem identification by 30%.
Jeff Bezos's most-cited framework: irreversible decisions deserve deliberation, reversible ones don't. Most organizations confuse the two — and pay for it in…
RACI is over-used and often wrong. DACI is better for decisions. Here's when to use which, and the one-page template that turns 'who decides?' from a…