Where the practice comes from
Red teaming originates in military and intelligence work: designated units were tasked with playing the adversary in wargames and, later, with attacking the assumptions behind intelligence assessments, a practice formalised across several armed forces and agencies after high-profile analytical failures. The transfer to corporate life keeps the core idea intact. Nobody asks a red team for balance. It is given the plan, the data and explicit licence to build the strongest available case that the plan is wrong.
A red team is not a devil's advocate
Devil's advocacy, as usually practised, is theatre: a rotating token dissenter, appointed in the meeting itself, argues against the proposal for twenty minutes without preparation or data, and consensus resumes with its conscience cleared. A red team differs on every dimension that matters: it is staffed deliberately, works over days or weeks rather than minutes, has access to the same materials as the proposing team, and delivers written findings the decision body is obliged to answer. The devil's advocate makes the room feel rigorous. The red team forces the case to become rigorous, or to fail.
When it earns its cost
Red teaming is expensive attention, and most decisions do not warrant it. Three conditions, usually in combination, do.
- The decision is effectively irreversible: contracts signed, integration begun, the organisation publicly committed.
- The stakes are a material share of budget, resources or reputation: the class of decision where recovery would be a multi-year programme.
- Consensus formed early. When nobody can remember the alternatives being seriously argued, the case has never actually been tested.
The structure of a proper red-team review
| Element |
What good looks like |
| Scope |
The red team chooses its own lines of attack; nothing material is designated off-limits |
| Access |
The same data room, models and interviews as the proposing team, not summaries prepared by the sponsor |
| Independence |
A reporting line to the decision body, never to the plan's sponsor |
| Findings |
A written case, argued to a conclusion, delivered before the decision meeting |
| Response |
The decision body answers each finding point by point, in writing, before approval |
How red teams get neutered
- Staffed with juniors who lack the standing to press a finding when a senior sponsor pushes back. The composition alone signals the exercise was never meant to bite.
- Findings received as a formality: noted in the minutes, answered by nobody, with the approval already drafted.
- Scope limited to the safe questions: implementation risk is examined at length while the strategic premise goes untouched.
- The review scheduled so late that acting on any finding would mean visible embarrassment, which guarantees none will be acted on.
Why external red teams see what internal ones cannot
Every internal red-teamer has a career that continues after the review, inside an organisation where the sponsor has a memory. That exposure shapes findings in ways no charter can fully prevent: conclusions soften, the sharpest lines of attack go unexplored, and the written case stops one step short of the uncomfortable answer. Operators with no reporting line into the organisation carry none of that weight. This is the discipline Digital Advisory runs professionally: a confidential client brief puts the plan in front of selected senior operators who argue with it on the merits, because the merits are the only thing connecting them to it.
