Glossary
Red teaming in strategy
Red teaming in strategy is the practice of having a separate team argue against a plan as a competitor, a regulator, an investor or a customer would, to find how it could fail before it is adopted.
The AI-native strategy company · Starting in India
Glossary · strategy1 term
Definition
A red-team report sets out the strongest arguments against a strategy and the conditions under which it fails; every strategy1 plan ships with one. Before an option reaches the Strategy Council, critics argue against it from the competitor's, regulator's, investor's and customer's side, and two judges check the result.
Explained in full on Evidence and trust.
Context
Plans written by the people who want them to succeed tend to understate risk. A written red-team report puts the counter-case in front of decision-makers before money is committed, so they can see what would have to be true for the plan to fail.
In practice
The red team is one of the agent types in strategy1's Agent Mesh, and its guardrail is that a “how this fails” section is required. A red-team report is part of every Bootcamp, Engine Sprint and decision memo, and a red-teamed “no” is treated as a valid result.
FAQ
Four. How would a rival respond? What rule or permit could stop the plan? Would the numbers survive investor scrutiny? Would the customers it depends on choose it? Each critic's case is written down with the conditions under which the plan fails.
Yes. If the red team shows the plan fails under likely conditions, the decision memo says so, with the evidence. strategy1 treats a red-teamed “don't do it” as a result, not a failure.
Two judges check the critics' arguments before the options reach the Strategy Council, and the report then goes to the Council with the options it tested.
A 72-Hour Bootcamp takes one problem your team would scope in weeks and works it to a decision memo your leadership signs. Fixed scope, fixed fee.