Identify which features are actually diagnostic
Separate features that genuinely differentiate categories from ones that just complete the picture.
Why it works
When a description includes many features consistent with a prototype, people treat the coherence of the picture as evidence of membership — even when most of the features carry no discriminating information. A feature is diagnostic only if it is more common in the target category than in alternatives. Distinguishing decorative features (they fit the story but don’t discriminate) from diagnostic ones activates more careful, Bayesian reasoning.
How to do it
- List the features of the case you’re evaluating.
- For each feature, ask: "Is this more common in the category I’m considering than in others?"
- Mark features as "decorative" if they fit the prototype but don’t discriminate.
- Base your probability judgment only on the diagnostic subset.
Evidence
Research on the dilution effect (Nisbett et al., 1981) shows that adding irrelevant (non-diagnostic) information actually weakens judgment accuracy — people average it in instead of ignoring it. This directly supports separating diagnostic from decorative features. (observational)
The dilution effect itself is context-sensitive; the practical discipline of identifying diagnostic features is a corrective heuristic rather than a guaranteed debiasing procedure.
Sources
- Nisbett, Zukier & Lemley (1981), The dilution effect: Nondiagnostic information weakens the implications of diagnostic information, Cognitive Psychology
Common mistake
Treating a long consistent description as strong evidence — the number of consistent features doesn’t compound into higher probability; only discriminating features do.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Representativeness Heuristic — Judging by Resemblance
- Look up base rates before forming a resemblance judgment
Before deciding "this looks like X," ask how common X actually is in the relevant population.
- Recognize that random sequences don’t "owe" balance
Random processes have no memory — a run of heads doesn’t make tails more likely.
- Treat small samples with explicit skepticism
A short sequence can look representative without being statistically reliable — adjust confidence for sample size.
- Audit person-judgments for prototype substitution
Check whether a judgment about a person is based on their actual behavior or on resemblance to a type.
- Expect extreme results to regress toward average
Unusually good or bad performance predicts more average performance next time — account for this before giving praise or blame.
- Name the prototype you’re comparing against before deciding
Make the prototype you’re using as a reference explicit — hidden templates bias decisions without scrutiny.