This note records why I pruned the Red Team section of the knowledge base and what I kept.
The short version: Red Teaming still matters to me as an identity and stance, but the tool layer had become bloated. A lot of the standalone tools were useful in the setting they were designed for: groups, planning staffs, workshops, and think-tank-style analysis. That is not the main operating context of this knowledge base.
For my current system, Decision Making, Kolbs, and The Shortcut Problem are more useful than maintaining a large Red Team tool catalog.
The important clarification: the things I pruned from my personal wiki are also the things I would cut, compress, or demote from the Red Team Handbook itself.
This is not only a housekeeping note. It is a model for the version of Red Team I would keep if I were rebuilding the program.
What I Kept
I kept Red Teaming as a high-level identity page.
Why:
- It captures a real part of my background.
- It preserves the Army Red Team way of seeing: challenge assumptions, slow down the first frame, protect dissent, and look for blind spots.
- It connects naturally to Metacognition: The Control Layer and Self-Regulation.
- It gives me a philosophical stance without forcing me to maintain every tool as a separate note.
I kept the four UFMCS principles inside the page:
- Self-Awareness and Reflection: know the lens before trusting the picture.
- Groupthink Mitigation and Decision Support: protect useful dissent from hierarchy and premature consensus.
- Fostering Cultural Empathy: understand another actor’s frame without surrendering judgment.
- Applied Critical Thinking: examine assumptions, alternatives, evidence, and failure paths before optimizing inside the first frame.
I also kept links from Red Teaming into the current working system:
What I Pruned From The Wiki And Would Cut From The Handbook
I removed the standalone Red Team tool pages. These are also the handbook areas I would cut or heavily compress.
Examples:
- Analysis of Competing Hypotheses
- Assumption Tools
- Communication Tools
- Failure Analysis Tools
- Five Whys
- Four Ways of Seeing
- Group Process Tools
- Key Assumptions Check
- Premortem Analysis
- SEE-I
- Stakeholder Mapping
- String of Pearls
- Team A / Team B Analysis
- Devils Advocacy
I did not remove them because they are all worthless. I removed them because they are no longer high-leverage as separate pages, and I would not want them to remain central in a modern Red Team curriculum.
Some of these tools can survive as examples inside a smaller decision-making lesson. They do not need to survive as named pillars.
Why The Tools Were Pruned
1. The Section Had Tool Bloat
The Red Team section started to look like a catalog of tools rather than a living decision system.
That is dangerous because a tool catalog can create the illusion of capability. Having a page for a method does not mean the method is useful, practiced, or worth the overhead.
The value is not in knowing many tools. The value is in asking the right question at the right time.
2. Many Tools Assume A Group Or Staff Process
A lot of Red Team tools make sense when people are working together like a planning staff or think tank. They need time, facilitation, roles, and collective attention.
That environment is not my default.
My default is usually:
- studying,
- writing,
- making personal decisions,
- building with AI agents,
- managing attention,
- or trying to decide the next useful action.
For that environment, the ICS decision-making pages are more practical.
3. The Time Cost Can Exceed The Value
Some Red Team methods are expensive. They create matrices, alternative hypotheses, stakeholder maps, premortems, and formal dissent structures.
That can be useful for high-stakes institutional decisions. But for many personal or study decisions, the cost is too high. The method slows the decision more than it improves it.
The danger is becoming afraid to decide because some black swan might exist. At a certain point, the decision problem is not “what did everyone miss?” It is “am I avoiding a decision by pretending more analysis is required?“
4. AI Has Subverted The Tool Layer
AI can now generate many Red Team artifacts quickly:
- competing hypotheses,
- stakeholder lists,
- strongest counterarguments,
- premortem failure modes,
- assumption lists,
- explanation formats,
- Team A / Team B arguments.
That does not mean AI replaces judgment. It means the scarce skill has moved.
The bottleneck is no longer producing the tool output. The bottleneck is deciding whether the output matters.
5. ICS Decision Making Is More Useful For My System
The ICS decision-making model fits my actual problems better.
It asks:
- What decision is actually being made?
- Is this decision worth the time I am spending on it?
- What choice reduces decisional delay?
- What option improves position or expected value?
- Am I judging the process or only the outcome?
- When should I change my decision?
That is closer to my daily life than maintaining twenty Red Team tools.
The Shortcut Problem
The deeper issue is The Shortcut Problem.
Old Red Team language often emphasizes seeing what everyone missed. That still matters. But for my current system, the more common failure is different:
I take a shortcut that lets me avoid the uncomfortable thinking.
This shows up in learning, decision-making, and AI use.
Examples:
- I ask the LLM for the structure before trying to think.
- I use a formal tool because it feels responsible, not because it is needed.
- I keep analyzing because deciding feels risky.
- I protect myself from being wrong by delaying the choice.
- I mistake the presence of a framework for the presence of judgment.
In that sense, modern Red Teaming for me is less about building bigger toolkits and more about detecting evasions.
Cultural Empathy And Overcorrection
I also pruned the standalone cultural empathy direction.
Cultural empathy was probably more important 20 years ago, especially in military contexts where mirror imaging and cultural ignorance were major operational failures.
But today, in many Western contexts, the danger has shifted. Cultural empathy has often overcorrected into what Gad Saad calls Suicidal Empathy: empathy that becomes excessive, misactivated, or aimed at the wrong targets.
That does not mean cultural empathy is useless.
It means cultural empathy needs boundaries:
- understand another actor’s frame;
- do not surrender judgment to that frame;
- predict behavior more accurately;
- do not excuse predatory behavior because it comes from an outgroup or victim-coded category;
- do not mistake tolerance for survival.
The new center of gravity is not cultural empathy as a standalone virtue. It is calibrated empathy under decision pressure.
If I Were Leading Red Team
If I were leading Red Team today, I would prune hard.
I would keep the two-week course as the core product. It gives the best return for the time spent: enough exposure to change how people frame problems, challenge assumptions, and protect dissent, without turning Red Teaming into a slow professional-tool bureaucracy.
I would cut or heavily reduce the longer, more specialized, tool-heavy courses unless they could prove clear value for a specific role.
I would keep:
- assumption awareness,
- dissent protection,
- perspective shift,
- failure-path thinking,
- decision clarity,
- and post-action reflection.
I would remove a lot of formal tool overhead.
I would train people to ask smaller, sharper questions:
- What is the frame?
- What assumption matters most?
- What shortcut are we taking?
- What are we refusing to notice?
- What is the decision?
- What would change our mind?
- What is the cost of delay?
That is the version of Red Teaming I want in this knowledge base.
Blog Connection
This note is not the blog post.
The blog post is On Red Team’s Closure.
The relationship is this:
- this note explains what I personally pruned from my Red Team wiki;
- the blog uses that pruning as an analogy for what I would cut from the handbook and course architecture;
- the blog argument is about why the closure was understandable, even though I benefited from the program as a former student;
- the reform argument is not “cut Red Team entirely,” but “keep the lean two-week course and remove the slower, tool-heavy parts.”
Possible thesis:
Red Team was not wrong. It became too heavy for the world it now lives in.
The argument:
- Red Teaming was designed for organizational failure modes.
- Its tools were valuable when perspective generation was expensive and group facilitation was the bottleneck.
- AI made perspective generation cheap.
- The remaining bottleneck is judgment, prioritization, and shortcut detection.
- The federal budget-cut story can be read as a signal: bloated analytical practices are vulnerable when they cannot show clear value per unit time.
- The Red Team stance should survive, but the handbook and course structure should shrink.