Dr. Wallace's Favorite Mental Models

The Representativeness Heuristic

Why something that "looks like" the answer feels more likely than it really is — and the five-second check that stops it from costing you a hire, a diagnosis, or a bet.

1. Learn it 2. Apply it 3. Save as Skill

1Fast Overview

The 30-second version, for when that's all the time you have.

In one line: you judge how likely something is by how closely it resembles a mental prototype, not by how often it actually happens.

A candidate who "looks like" your best engineer, a chart pattern that "looks like" the last big winner, a patient who "looks like" a textbook case — in each one, the resemblance is doing the work that evidence should be doing. The judgment can feel airtight in the moment and still be wrong, because similarity and probability are two different things that your mind quietly treats as one.
Origin
Amos Tversky & Daniel Kahneman, early 1970s judgment-under-uncertainty research
Family
Cognitive bias / judgment heuristic
Shows up most when
You have a vivid detail and no time (or no habit) of checking the base rate

2Mental Model Compass

Where this model lives, and where its cousins sit around it.

Mental Model Compass for the Representativeness Heuristic A two-axis chart. The horizontal axis runs from scarce statistical data on the left to abundant statistical data on the right. The vertical axis runs from a snap decision at the top to a deliberate decision at the bottom. The representativeness heuristic sits in the upper left, the zone of scarce data and snap decisions, where pattern-matching does the most unsupervised work. Base rate neglect and the law of small numbers sit nearby in that same zone. Availability heuristic sits upper right. Anchoring sits lower right. HIGH-RISK ZONE Snap decision Deliberate decision Scarce data Abundant data Representativeness Base rate neglect Law of small numbers Availability heuristic Anchoring bias Confirmation bias
Representativeness heuristic is most dangerous in the upper-left quadrant: little hard data, a decision you feel pressure to make fast. That's exactly where hiring screens, early-stage diagnoses, and first impressions of a deal live.
Base rate neglect and the law of small numbers are the two failure modes it most directly produces — treat them as this model's near neighbors, not separate problems.
As you move right (more data) or down (more deliberation), the heuristic loses its grip — which is exactly the lever you'll use in the worked application below.

3Progressive Interactive Learning

Five layers, from the core mechanism to the professional edge case. Mark each as you go.

0 of 5 understood

Tversky and Kahneman defined representativeness as how much something resembles its category "in essential characteristics" and reflects "the salient features of the process that generated it." Your mind keeps a library of prototypes — the typical engineer, the typical fraud case, the typical winning startup — and when a new instance matches one closely, it gets slotted in as likely, fast.

The shortcut is efficient precisely because it skips the step of asking how common that category actually is. Resemblance becomes a stand-in for probability, and the two quietly get treated as the same thing.

In the classic 1983 experiment, subjects read a description of "Linda" written to sound like an active feminist, then ranked the probability of several statements, including "Linda is a bank teller" and "Linda is a bank teller and active in the feminist movement." Most people ranked the second as more probable than the first — even though a conjunction of two things can never be more likely than either thing alone.

The description was representative of a feminist, so the mind reached for the feminist-shaped answer, probability rules notwithstanding. This is the conjunction fallacy, and it is the heuristic's signature error: a good story beats a true number.

Take a disease that affects 1 in 10,000 people and a test that is 99% accurate. Most people who hear "the test came back positive" assume near-certain infection. In fact, because the disease is so rare, false positives from the healthy 9,999 vastly outnumber true positives from the 1 — the realistic chance of actually having the disease is still low.

The test result is representative of infection, so it crowds out the base rate entirely. This is why doctors, underwriters, and recruiters who skip the base rate and go straight to "does this look like the thing" get burned by rare categories that nonetheless produce vivid, convincing-looking cases.

A second, related error: people expect even a small sample to look representative of the whole population — three good quarters "must" mean a skilled manager, five good at-bats "must" mean a hot streak. Kahneman and Tversky called this the "law of small numbers," a tongue-in-cheek nod to the true law of large numbers, which only holds for genuinely large samples.

Small samples are noisy by nature. Treating them as representative is the same underlying error as the Linda problem, applied to a sequence of outcomes instead of a single description.

Representativeness is not a design flaw to be eliminated — it is a fast classifier that is right far more often than it is wrong, which is exactly why evolution and experience kept it around. An emergency physician who has seen ten thousand chest-pain cases can often pattern-match a genuine cardiac event in seconds, and that calibrated intuition outperforms a slow checklist when minutes matter.

The difference between useful expert intuition and a costly bias, per later work by Kahneman and Gary Klein, comes down to two conditions: a reasonably stable environment, and many repetitions with fast, clear feedback. Where both hold, trust the pattern. Where either is missing — a one-off decision, a noisy or shifting environment, delayed or absent feedback — slow down and check the base rate instead.

4Diverse Examples

The same mechanism, four different professional settings.

The resume that "looks like" your best hire. A hiring manager's top performer went to a particular university, held a particular prior title, and had a particular hobby mentioned in passing. The next resume with those same surface traits gets fast-tracked, while an equally or more qualified candidate without the matching pattern gets screened out.

The surface traits were never shown to predict performance; they were simply present in one memorable case. Representativeness turned a sample size of one into a template.

The textbook-looking patient. A patient's symptoms closely match a well-known, dramatic condition, and the clinician's attention locks onto it. A far more common but less "story-shaped" explanation, with a much higher base rate in that population, gets under-weighted or never considered.

Medical educators teach this explicitly now: "when you hear hoofbeats, think horses, not zebras" is a direct, deliberate counter to representativeness-driven diagnosis.

The stock that "looks like" the last big winner. A young company shares surface features with a past breakout success — similar founder story, similar market language, similar early growth chart shape. Investors extrapolate the earlier company's outcome onto the new one, discounting how many companies with that same profile quietly failed.

This is survivorship bias's close cousin: representativeness supplies the resemblance, survivorship supplies the invisible graveyard of lookalikes that didn't make it.

5Worked Application

Scenario: you're reviewing a shortlist of five job candidates and one resume "feels like" an obvious top pick.

Name the judgment before you make it. Say out loud or in writing: "I am about to rank this candidate highly because they remind me of someone who succeeded here." Naming the mechanism breaks its invisibility.
Write the base rate down first. Before re-reading the standout resume, estimate: of all candidates with a profile this strong on paper, what share actually perform well in this specific role, based on your own hiring history? Commit to a number before the vivid details pull you off it.
List the specific features doing the persuading. Is it the school, the title, the one shared hobby? Separate those surface features from the features your own data actually says predict performance — a structured work sample, a reference check on a named skill, a specific past result.
Run the falsification test. Ask: "If this candidate had every predictive feature but lacked the vivid surface trait, would I still rank them this high?" If the answer changes once you strip the vivid trait, the vivid trait — not the evidence — was driving the ranking.
Blend, don't discard. The goal isn't to ignore the pattern match — it's real signal — but to combine it with the base rate rather than let it override the base rate entirely. A strong surface match plus a strong structured-evidence score is a genuinely strong candidate. A strong surface match with weak structured evidence is a prototype, not a prediction.

6Common Mistakes

Treating "sounds like" as "is probably"

Adding specific, vivid detail to a scenario always makes it feel more plausible and almost always makes it statistically less likely, because you've added a condition that must also be true.

Discounting the base rate once a story appears

A strong anecdote doesn't cancel out a weak base rate; it sits alongside it. The two should be combined, not swapped.

Reading a small sample as the whole picture

Three strong results from a new process, salesperson, or portfolio pick are often just noise, not proof of a durable pattern.

Using it after the fact to explain outcomes

Looking back and declaring an outcome "typical" of the person or cause is representativeness working in reverse — it explains everything and predicts nothing.

7When Not to Use It

Don't demand a full statistical workup for every snap judgment.

In a genuinely stable, high-repetition domain where you or a colleague have deep, fast-feedback experience — an experienced ER triage nurse, a veteran underwriter on a familiar product line, a seasoned machinist spotting a defect — the pattern match has already been calibrated by thousands of corrected guesses. Forcing a full base-rate analysis in that setting slows good judgment down without making it better. Reserve the full five-step check above for decisions that are high-stakes, low-repetition, or made in an unfamiliar or shifting environment — that's where the heuristic is unsupervised and most likely to mislead you.

9Try It Yourself

Build a quick prompt you can paste into any AI assistant — or just use yourself — to stress-test a judgment you're about to make.

Copied
Your prompt will appear here.

10Save as Skill

Preview the portable version of this model below, copy it, download it as a Markdown file, or turn it into a ready-to-use prompt for your own situation.

Skill preview
Copied
Apply to My Problem

Describe your real situation, and this will compose a ready-to-paste prompt that applies the Representativeness Heuristic check to it specifically.

Copied
Your tailored prompt will appear here.