The reading room · Digna Legi
Red-Teaming Your Strategy
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Judgment is based on the supplied article text; no external verification of the aviation example was used.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Original article ↗ · about 8 min (text estimate)
Why read this
Confidence can arrive before correctness, so high-stakes decisions need cross-checks designed to survive pressure and momentum.
AI brief · Checked against source text
The main idea
The central claim is that strategy fails less from lack of intelligence than from premature certainty under pressure. The author uses aviation’s wrong-runway landing as a mechanism: once a plausible visual story appears, people stop consulting instruments that could disconfirm it. Red-teaming therefore should be procedural, proportionate, and timed for moments when momentum makes skepticism socially costly.
Go a little deeper
Procedures fail when optional
The author’s sharper point is not that checklists are useful, but that available safeguards can disappear precisely when they are most needed. A procedure that depends on calm discipline is weak against time pressure, social momentum, and apparent clarity. The design problem is making verification difficult to bypass at the brink, when skipping it feels efficient rather than reckless.
Experience can accelerate error
Experience is treated as double-edged. It improves pattern recognition, but it also makes a coherent interpretation arrive faster and feel more authoritative. In strategy and product work, that can turn partial signals into premature commitment: anecdotes sound like evidence, competitor moves look like validation, and early executive support makes reconsideration feel like dissent.
Red-teaming must be a role, not a personality
The author rejects the vague hope that smart people will challenge assumptions when it matters. Under deadlines and rising stakes, organizations usually become more decisive, not more reflective. Red-teaming has to assign responsibility for falsification, separate advocates from validators, and create short rituals that generate disconfirming evidence without turning every decision into a debate.
Friction should be placed where reversal is hardest
The practical advice is not to slow everything down. The author argues for proportional friction: stronger checks belong around decisions with high downside, high ambiguity, and low reversibility. A ten-minute disconfirming evidence check, a one-page differentiation test, or explicit kill criteria can be faster than the later cost of rationalizing a bad commitment.
A case from the article
The wrong runway landing
The Southwest pilots had the correct destination programmed and the correct airport visible on cockpit displays, but after seeing a plausible runway at night they stopped checking the instruments. The plane landed at a smaller nearby airport and stopped with little margin. The case illustrates how ordinary competence, routine conditions, and strong confidence can combine into a repeatable failure mode.
How the case is made
The case is made through a historical aviation incident, a product-leadership analogy, and a practical taxonomy of red-team mechanisms.
Where the idea has limits
The argument is strongest for high-downside, ambiguous, hard-to-reverse decisions; the author explicitly warns against applying heavy checks to every choice.
A question to take away · from Digna Legi
Where has internal coherence become a substitute for evidence in a decision that would be expensive to reverse?
What the original adds
The original gives a fuller toolkit, including disconfirming evidence checks, two-runway tests, pre-mortems, kill criteria, independent verification, assumption ledgers, and launch-time slow-down rules.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.