State your estimate before encountering vivid case information
Lock in a prior probability estimate before reading a compelling story or meeting a specific candidate.
Why it works
Vivid case information is the primary trigger for attribute substitution: a compelling story or memorable prototype provides a ready-made easy attribute that replaces deliberate probability reasoning. Pre-committing to a probability estimate before encountering the vivid information anchors the deliberate calculation and makes the subsequent vividness effect visible as a deviation from the prior, rather than as a self-evident update.
How to do it
- Before reading an application, pitch, or case study, write your base-rate probability estimate.
- After reading, write your updated estimate.
- If the update is large, ask explicitly: "What specifically changed my probability — new facts, or affect and representativeness?"
Evidence
Pre-commitment to a prior probability is a standard debiasing technique recommended in decision-quality frameworks. It is consistent with anchoring research showing that established anchors resist vivid informational updates. (mechanistic)
A pre-committed estimate can itself become an anchor that under-weights genuinely informative case evidence. The goal is balanced updating, not complete resistance to new information.
Common mistake
Pre-committing to a number and then treating all deviation from it as bias — vivid information sometimes is genuinely diagnostic. The tool is to make the deviation visible, not to prevent updating.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Attribute Substitution: When Your Brain Answers a Different Question
- Name the question your brain is actually answering
When you reach a quick judgment, ask: "What question did I actually just answer?"
- Check whether your judgment is tracking affect, not the target attribute
When a decision "just feels right," ask whether the feeling is about the actual question or about your current emotional state.
- Interrogate whether similarity is doing the work
When assessing probability or quality, ask whether you’re really judging similarity to a prototype.
- Treat judgment difficulty as a signal to slow down
When a question feels easy to answer, that ease may mean your brain swapped it for a simpler one.
- Decompose the target attribute into components before judging
Break a hard question into its component parts and answer each one directly, rather than letting a heuristic answer the whole.
- Label the easier attribute you’re being tempted to use
Name the shortcut attribute explicitly ("I’m using attractiveness as a proxy for competence") to reduce its pull.
Related concepts
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Base-Rate Neglect: Why We Ignore the Odds
How to let prior probabilities do their real work in your decisions
- Anchoring Bias in Negotiation and Judgment
Why the first number wins — the mechanism, and how to set and resist anchors