Red Teaming

Description

An independent team deliberately challenges a plan, design or conclusion from an adversarial or alternative perspective to expose weaknesses before reality does.

Red teaming institutionalises challenge. A red team, independent from the planners, adopts the perspective of adversaries, competitors, misusers or sceptical stakeholders, and attacks assumptions, logic and execution using structured techniques: alternative analysis, pre-mortems, adversary emulation, devil's advocacy, and stress-testing. It requires organisational backing, clear scope, and rules that protect challengers. In UX it applies to research conclusions (is the synthesis sound?), to abuse and misuse of features (how could this be weaponised?), and to AI products, where red teaming already exists for model safety but rarely for user experience harms.

Attributes

Loss type
Siloed
Effort
Days

Steps

  1. Secure sponsorship and define scope: the plan, design or conclusion to challenge, and the perspectives to adopt.
  2. Form an independent team with diverse expertise, including domain experts and potential adversary perspectives.
  3. Brief the red team with full materials, then let them work separately with structured techniques.
  4. Generate attack scenarios: misuse cases, competitor responses, failure modes, alternative interpretations.
  5. Present findings to decision-makers in a protected format; prioritise by likelihood and impact.
  6. Track responses to each finding and repeat at key milestones.

Sources

  • UK Ministry of Defence DCDC, Red Teaming Guide (2nd ed., 2013)
  • Zenko, Red Team: How to Succeed by Thinking Like the Enemy (2015)

Also known as

  • Red team analysis
  • Adversarial review
  • Devil's advocacy (structured)

Categories

  • Research Operations
  • Research Design & Rigor