Conjunction Errors: 10 Evidence-Based Coaching Practices

Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Conjunction Errors, these are the strongest matches in the current practice library.

About 2 minutes

Try it here: list the parts that must all happen

List the parts of a plan that all have to happen for it to work. Judging each part on its own shows where the risk sits.

Which parts of your plan all have to happen?

Or do it with Io instead.

Practices that may help

  1. 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."
    The Conjunction Fallacy — When "More Details" Feels More Likely
  2. Test each component probability separately
    Before judging a joint claim, estimate each element on its own, then check whether the conjunction is lower.
    The Conjunction Fallacy — When "More Details" Feels More Likely
  3. The Conjunction Fallacy — When "More Details" Feels More Likely
    The conjunction fallacy is the well-replicated tendency to judge a specific combination of events as more probable than one of its components alone — made famous by Kahneman and Tversky’s Linda problem. It happens because vivid, representative details hijack probability judgment, and the fix is to reason about base rates rather than narrative fit.
  4. Audit plans for scenario inflation
    Before committing to a plan that depends on multiple things going right, count the dependencies.
    The Conjunction Fallacy — When "More Details" Feels More Likely
  5. Explicitly distinguish coherence from probability
    A story can be internally consistent and still be rare — learn to separate "makes sense" from "likely."
    The Conjunction Fallacy — When "More Details" Feels More Likely
  6. Consult an outside observer to counteract narrative pull
    Describe the scenario to someone who doesn’t share your narrative context and listen to their probability estimate.
    The Conjunction Fallacy — When "More Details" Feels More Likely
  7. Treat errors as adjacent-possible expansion events
    When something goes wrong, ask what new territory the failure has made visible that success would have hidden.
    The Adjacent Possible, Made Practical
  8. Rule out mind-reading and fortune-telling
    Catch the two most common interpretation errors — assuming you know what someone is thinking, or what is about to happen.
    Check the Facts, Made Practical
  9. Anchor on base rates before adding details
    Start with how common the outcome is in the relevant population, then update — don’t start with the story.
    The Conjunction Fallacy — When "More Details" Feels More Likely
  10. Build branches that are MECE at every level
    Ensure each set of branches is mutually exclusive (no overlap) and collectively exhaustive (nothing important missing).
    Issue Tree Analysis

Does this sound like the set of challenges you might be facing?

Related concerns

Describe your situation in your own words to search the complete practice library.

Practice this with IX Coach

Try this practice