Red Team Your Own Conclusion
A red team challenges your conclusion before events do. Take the view of an adversary or critic, then test your logic, your information, and your projections.
One convenient story
Uncertainty can tempt us to reduce a complex situation to one convenient story. A structured review helps us examine what that story leaves out. Last week’s tool, SWOT, maps the ground you are standing on. The red team tests the story you built on it.
What a red team does
In intelligence work, red-teaming is the practice of deliberately challenging one’s conclusions by simulating the mindset, resources, and objectives of an adversary or critic. It forces the analyst to step outside their own perspective and examine weaknesses in their logic, information, and projections.
Chapter 4 presents it as one tool for testing assumptions and exposing blind spots. You do not need an adversary to use it. A critic’s view is enough.
The Alarm That Wasn’t
Chapter 4 of The Stoic Strategist illustrates the method with a scenario.
Just after midnight, a newly assigned military analyst reviews satellite imagery of what appears to be a mobile missile platform moving through a region known for proxy militia activity. Communications intercepts show a surge of chatter. Political tension with a neighboring state has been rising. The pieces seem to fit.
The analyst drafts an urgent warning. The chain of command responds swiftly. Aircraft are re-tasked, ground assets take a defensive posture, and political advisors are briefed. It feels like clarity.
Within hours, it collapses. The “missile platform” is a weather radar truck rented by a private engineering company. The surge of chatter is civilian contractors discussing a construction bid. No hostile intent. No military threat. Just overlapping signals mistaken for coordination.
What went wrong
The initial report was not reckless. The analyst had fragments that seemed to align. But pattern recognition, mixed with urgency and stress, can become pattern projection. Urgency led the analyst to treat a plausible interpretation as a settled conclusion.
The cost was time, credibility, and operational energy. It could have been worse. The analyst later remembered not the mistake itself but the speed with which clarity gave way to certainty.
A brief red-team review would have asked three questions.
| Question from the book | Adapted for managers |
|---|---|
| What would this situation look like if it were not a threat? | What would this look like if it were not a problem? |
| Who stands to benefit from our overreaction? | Who would benefit if I overreacted? |
| What is missing that should be here if this were truly hostile activity? | What is missing that should be here if this were truly a problem? |
The right-hand column adapts the book’s questions to the workplace.
Doubt the first impression
Intelligence teaches us to doubt first impressions, identify gaps, and pressure-test assumptions. Stoicism teaches us to seek clarity and remain undisturbed by fortune. Combining red-teaming with SWOT trains the mind to move from reactive judgment to composed insight.
What this looks like for a manager
A drop in output. A manager sees a sharp drop in her team’s weekly output and starts drafting an escalation to her director. She asks the questions. What would this look like if it were not a problem? The drop could reflect a change in how the work is counted. What is missing that should be here if it were a real problem? Missed deadlines. Complaints from clients. There are none.
She checks how the figures are compiled before she sends anything.
A curt email. A manager reads a short, curt email from a client and concludes the account is at risk. He asks what the email would look like if the client were simply busy. He asks what is missing that should be there if the account were at risk. He finds nothing else: no canceled meeting, no change in requests.
He replies in his usual tone and keeps the meeting.
The drill
This is Step 3 of the Strategic Pause from Chapter 4. Run it on the SWOT analysis described here.
Which assumptions in my SWOT might be wrong?
If someone wanted to see me fail in this situation, where would they focus?
Am I overvaluing control or undervaluing uncertainty itself?
Then return to Step 4: commit to one next step that tests an assumption or fills an important information gap.
Final Reflection
Which of my assumptions might be wrong, and where would someone who wanted to see me fail focus?
