Red-team joint scenarios before betting on them

Before acting on a conjunction ("X will happen AND Y will follow"), assign a skeptic to attack the "and."

Why it works

The "and" in a conjunction is typically the weakest point in compound reasoning, yet it’s the element most obscured by narrative coherence — the story feels inevitable once all the pieces are assembled. A designated red-team role removes the collaborative bias toward agreeing on the scenario and specifically targets the dependency: "What breaks the link between X and Y?" This is a structured adversarial decomposition that mirrors how the conjunction fallacy is produced — by isolating the components — and inverts the bias.

How to do it

1. Identify the key "and" in your scenario or plan ("we launch AND adoption follows").
2. Assign someone (or yourself in a different mental mode) to attack specifically the link between the components, not the components themselves.
3. Ask: "In what realistic conditions would X happen but Y not follow?"
4. If convincing scenarios exist, revise the joint probability downward before committing.

Evidence

Red-teaming in decision analysis is an established organizational practice for surfacing overlooked failure modes; its application to conjunction errors is a principled extension of the adversarial collaboration literature. (clinical)

Red-teaming effectiveness depends on the red team having genuine adversarial latitude; teams that are expected to endorse the plan anyway provide little correction.

Common mistake

Red-teaming the individual components ("could X fail?") rather than the conjunction link — this misses the specific error the practice is designed to correct.