Availability heuristic

What is the availability heuristic?

The availability heuristic is the mental shortcut of judging how likely or common something is by how easily examples spring to mind. Vivid, recent or often-repeated things feel more frequent than they are, so what you remember seeing - not what actually happened - drives your sense of the odds.

Also known as: availability heuristic, availability bias

Prefer to watch? Watch the recap 0:51

The demo

Watch the feed go by, then guess how common the red alerts really are. Your memory and the actual jar won't agree - and that gap is the whole idea.

What this demo shows (text version)

A feed plays items one at a time. A dramatic "red alert" category is shown far more often than its real share, so by the end it feels common. You then guess how many of the hundred items in the underlying jar are red alerts - and the reveal shows there are only a handful. Your estimate is pulled upward by how easily the vivid, repeated alerts came to mind, not by their true frequency.

That's the availability heuristic: we judge how common something is by how easily examples are recalled, so anything recent, vivid or repeated feels more frequent than it is. The practical lesson is to trust counted data over the gut sense of "I keep seeing this", and to remember that whatever you surface repeatedly is what people will come to believe is normal.

People estimate frequency by ease of recall, not by counting. So whatever is recent, dramatic or repeated feels common, even when it's rare - and whatever's quietly typical feels rare. In an interface this cuts both ways: a single loud complaint can feel like "everyone hates this", and repeating one message makes its subject feel widespread. Judge by data, not by what's top of mind, and remember that what you surface repeatedly is what people will believe is normal.

The shortcut exists because recall is fast and counting is slow: your brain treats "I can think of lots of examples" as "this must happen a lot". That works when memorable equals frequent, but breaks whenever something is memorable for other reasons - because it was shocking, recent, emotive or simply shown to you many times. Then ease of recall and true frequency come apart, and judgement follows recall.

In products it shapes perception constantly. A handful of dramatic support tickets can convince a team a problem is widespread; a single viral complaint can outweigh thousands of quiet happy users; and repeating a feature or message makes people believe it's more common or important than it is. The same lever drives "as seen on" social proof and recency-weighted feeds - what's surfaced often becomes what feels normal.

Design with it honestly. When you want something to feel common and trusted, surface real, frequent examples rather than manufacturing a vivid few. And when you make decisions, distrust your gut sense of "everyone is saying" - go to the actual numbers, because the loudest and most recent inputs are exactly the ones your memory over-weights.