---
name: Availability Heuristic
status: active
territory: argumentative-artifact-examination
host_mode: propaganda-audit
also_loadable_in: []
msi_wired: true
msi_family: behavioral
sources:
  - title: "Tversky & Kahneman (1973), Availability: A Heuristic for Judging Frequency and Probability, Cognitive Psychology 5(2):207-232"
    url: https://doi.org/10.1016/0010-0285(73)90033-9
  - title: Kahneman (2011), Thinking, Fast and Slow
    url: https://us.macmillan.com/books/9780374533557/thinkingfastandslow/
---

# Availability Heuristic

## Why it matters

What springs to mind easily feels common — so whoever fills your memory with vivid examples controls what you believe is likely.

For example: a segment opens with three wrenching murder stories, back to back. You come away certain crime is surging. You were never shown a crime rate. You were shown three things you can't stop picturing — and your sense of "how often" quietly tracked how easily they came to mind.

- **What it reveals.** A frequency claim — "this is everywhere," "it's an epidemic," "happening more and more" — propped up by vivid cases instead of a rate. The cases are doing the convincing; the number is missing, and you didn't notice it was missing.
- **How it changes the read.** Instead of asking *"how scary is this story?"* you start asking *"how often does this actually happen?"* — and whether the piece ever told you. Most of the time it didn't. It handed you images and let your memory do the counting.
- **When to foreground it.** Any time a text argues *how common* something is using examples you can picture — three murders, a runaway lawsuit, one viral fraud — without a base rate. Especially when the examples are recent, dramatic, or emotionally loaded.
- **What you'd miss without it.** That the dull, common risk was edited out. The footage you remember is selected for memorability, not for how often it happens — and the things that kill quietly never make the reel.
- **Where it misleads.** Sometimes vivid *is* common — a flood of examples can be honest reporting of a real surge. This flags that the count came from recall, not data. Whether the thing is actually rare is a separate question the rate would settle.

## Realtime examples

See real, dated analyses where this pattern turned up in the news → **[Availability Heuristic on Main Street Independent](https://mainstreetindependent.com/analyses/lens/behavioral/availability-heuristic)**

## How to invoke it in Ora

You're watching a news segment that opens with three vivid murder stories and tells you crime is exploding. You want to know what those stories are doing to your sense of how common crime is.

Paste the segment and ask:

> "Propaganda audit: a TV segment opens with three vivid murder stories to convince viewers that crime is exploding. What is the manipulation?"

Ora names the frequency claim, shows that it rests on memorable cases instead of a rate, and points out the base rate the segment never gave you.

One thing to know: a plain description like "this segment uses scary examples" doesn't reach the analysis — Ora asks a clarifying question instead. The words *manipulation* or *propaganda audit* are what point it in the right direction.

Paste the whole thing — the actual segment or article, not a summary. The tactic lives in which examples were chosen and what was left out, and a summary smooths exactly that away.

One thing Ora won't do: tell you whether crime is actually rising. It shows you that the case for "rising" was built from things easy to recall rather than from a count. What the real rate is, you check from the data.

## How it works

Here is a small experiment you can run on yourself. Take the letter "k." Are there more English words that *begin* with k — like *king, kitchen, knife* — or more words with k as their *third* letter, like *ask, bake, lake, make, joke*?

Almost everyone says words that begin with k. It feels obvious. You can rattle off a dozen in seconds: *keep, kind, kite…* The third-letter ones come slowly, if at all — your memory isn't filed that way.

But the easy answer is wrong. In ordinary English text there are about three times as many words with k in the third position. The reason you got it backwards is the whole point: you didn't actually count words. You couldn't. So your brain quietly swapped the hard question — *how many are there?* — for an easy one — *how fast can I think of some?* — and reported the answer to the easy question as if it were the answer to the hard one.

That swap is the availability heuristic, named by Amos Tversky and Daniel Kahneman, the psychologists who first put it under a microscope. When you don't know how common something is, you reach for examples, and you read the ease of finding them as the answer. Things that come to mind fast feel frequent. Things that come slowly feel rare.

It is usually a decent shortcut — common things *are* often easier to recall. But it breaks the moment something is memorable for reasons other than how often it happens. A plane crash is vivid; a car crash is ordinary, so cars feel safer than they are, though they kill vastly more people. A shark attack makes the news; the falling coconut and the rip current don't. Lottery winners are paraded on television; the hundred million losers are invisible, so the odds *feel* better than a coin you'd never bet on.

And here is the part anyone trying to move you already knows: the easiest way to make something feel common is to make it easy to recall. Show three vivid cases in a row and the count takes care of itself — no rate required, no lie told. The examples can all be true. What's been arranged is which ones you'll remember.

So when a piece insists something is everywhere, the question isn't whether the examples are real. It's whether anyone ever told you the number — or just made sure you'd picture the cases.

## Framework & implementation

*This section uses Ora's own terms for the parts of an analysis, so that if you open the actual mode and lens files they line up. Each is glossed in plain language on first use.*

### Pipeline execution

The Availability Heuristic is one of the mental models listed under "always loaded" in Propaganda Audit's **`ANALYTICAL PERSPECTIVES`** block — so it is active on every propaganda audit, whether or not the prompt names it. Propaganda Audit runs at **Gear 4**, Ora's most thorough setting: two analysts read the artifact independently, each critiques the other's work, both revise under that critique, and a consolidator merges what survives. The lens threads through those stages like this.

**Detection.** The lens engages on the cases in its **Detection Signals** — an estimate that jumps after a single dramatic event or media cycle, a "this happens all the time" backed by recalled instances rather than data, vivid risks rated common while quiet ones are rated rare. The precondition, from its **Applicability Conditions**, is a judgment about *frequency, probability, or commonness* where recall is the most accessible source — no base rate on hand — and the recalled instances are uneven in vividness, recency, or emotional charge. When the artifact actually supplies a rate, the lens still engages but qualifies rather than asserting a clean availability effect.

**The Depth and Breadth analysts.** Two models read the artifact in parallel. The **Depth analyst** commits to a single reading and defends it: this frequency claim, these vivid cases standing in for a count, this direction of distortion. It then runs the lens's **Application Steps** — most importantly, *locating the actual base rate from a source independent of the recalled instances* (incident logs, comprehensive statistics) and measuring the gap between the artifact's implied frequency and that rate. The **Breadth analyst** works the same artifact at the same time, scanning for every frequency judgment leaning on memorability, not just the loudest one. Neither sees the other's work.

**Cross-adversarial evaluation.** Each analyst's reading is handed to the *other* one to critique against the mode's criteria. The lens's signature failure is caught here, keyed to its third **Critical Question**: has an independent base rate actually been produced, or has the analyst only objected that the examples are vivid? An evaluator who flags vividness without supplying the rate is doing the same thing the artifact did. Over-diagnosis — calling it availability where vivid genuinely tracks common, the lens's fifth Critical Question — is filed as a required fix the same way.

**Revision and claim-check.** The reviser addresses the fixes — and this is where the base rate meets the world. A factual claim like "violent crime has fallen over the past decade" is marked a **flagged claim** and sent to a web-search tool; it has to resolve against outside sources before the revised draft moves forward. The independent rate the lens demands is the rate the pipeline verifies, so the correction can't itself be an anecdote.

**Consolidation and output.** The consolidator merges the two revised readings into one corpus, and the formatter places it into the audit's set sections. The finding lands first under **frame-manipulation techniques active** — flooding attention with vivid, easily recalled instances is itself a recognized technique, beside loaded terms and manufactured doubt. It also lands in the **not-at-issue content inventory**, because the artifact *presupposes* the vivid cases are representative without ever arguing it — the representativeness is assumed, not asserted, doing persuasive work below the line. Its consequence is recorded under **audience predicted uptake**: a reader who overestimates how common the dramatized thing is.

**What the analysis will not assert.** It reports the mechanical pull: these vivid cases are standing in for a count this judgment never made. It does not impute intent — a vivid example can manipulate or merely illustrate, and the lens won't claim the author *meant* to mislead. And naming the tactic is not the same as disproving the artifact's conclusion: the thing really might be common. That is settled by the base rate, not by spotting the heuristic.

### Origin and evidence

The Availability Heuristic was introduced by Tversky and Kahneman in their 1973 *Cognitive Psychology* paper — the k-word demonstration above is theirs. The mechanism is substitution: asked how frequent something is, the mind tries to retrieve instances and reads the *ease* of retrieval as the answer, so vivid, recent, or emotionally tagged cases — recalled faster and in greater number — register as more frequent than equally common but mundane ones. The substitution runs below awareness; the person experiences the inflated estimate as a direct reading of frequency, not as a recall-based proxy. Kahneman's *Thinking, Fast and Slow* treats it as one of the foundations of the field's account of intuitive judgment and connects it to risk perception — why publics fear the dramatic hazard and discount the statistical one.

### Applications and common uses

The Availability Heuristic is among the most-applied findings in behavioral science, used on both sides — to inflate a perceived frequency and to defend against an inflated one.

- **Risk communication and public health.** The lever that makes a rare, dramatic hazard feel common — a single outbreak, a shark attack, a plane crash — while the routine killer fades. Communicators exploit it to mobilize attention and fight it to keep the public calibrated; the discipline is leading with the rate, not the anecdote.
- **News and political messaging.** Three vivid cases in a row manufacture a trend with no statistic told and no lie stated. Auditing this — does the "epidemic" rest on memorable instances or on a measured rate? — is the case the example on this page walks through.
- **Marketing and fundraising.** The testimonial, the one spectacular winner, the harrowing single story stand in for a base rate the audience never sees, so the good outcome feels likely and the bad cause feels urgent.
- **Forecasting and intelligence review.** A standing professional use is checking whether an estimate spiked because of a recent salient event rather than because the underlying rate moved — the lens's test applied to another analyst's judgment, the same debiasing disciplined forecasters run on their own.
- **Litigation and policy.** A single shocking incident drives a damages narrative or a new law out of proportion to how often it actually occurs; the counter is to re-anchor the discussion on incidence data.

The value in every case is the same: the independent base rate. Whether you are defending against a manufactured "epidemic" or trying to mobilize attention honestly, the lever is whether you can say how often the thing actually happens, from a source other than the cases you happen to remember.

### Failure modes and when not to use it

The lens's characteristic ways of going wrong are catalogued in its **Common Failure Modes**, mostly from over-application:

- **Anecdote-as-data** (the artifact's error, and the analyst's risk). Vivid recalled cases get treated as frequency evidence. The fix is not to point out that they are vivid — it is to require an actual rate from an independent source before any frequency claim is accepted, including the analyst's own correction.
- **Media-driven recalibration.** Estimates and resource allocations swing with the news cycle. The tell is that the shift tracks headlines rather than measured impact; the discipline ties the judgment to a moving-average of impact, not to recent prominence.
- **Counter-availability** (*over-correction*). Treating *every* vivid example as misleading throws out genuine signal — some rare events are vivid precisely because they matter. The fix is to separate vividness-as-sign-of-importance (sometimes right) from vividness-as-cause-of-overestimate (the bias), not to dismiss salience wholesale.
- **Selective availability.** Recalling only the instances that confirm a prior and reading the ease of recall as proof. The diagnostic is the asymmetry — disconfirming cases come slower — and the correction is to deliberately go looking for them.

**When not to reach for it.** When the artifact actually supplies a base rate, the frequency claim is grounded in data, not recall, and the lens qualifies rather than diagnoses. When vividness and frequency genuinely line up — a domain where the dramatic case really is the common one — a flood of examples can be honest, and calling it availability is the over-diagnosis the lens's fifth Critical Question guards against. And the diagnosis it most easily blurs into is the **Affect Heuristic**: availability is judgment driven by *ease of recall*; affect is judgment driven by *feeling*. They often travel together, but the test differs — recall-based versus emotion-based — and conflating them muddies both.

## Related

- **Propaganda Audit** — the analysis that hosts this lens; reads persuasion tactics in a piece of writing.
- **Affect Heuristic** — the sibling shortcut: judgment steered by *feeling* rather than by ease of recall.
- **Base Rate Neglect** — the broader pattern of which availability is one cause: the actual rate gets ignored in favor of the vivid instance.
- **Anchoring** — a related decision-making pattern: the first *number* you see sets the range every later number is judged against.

## Sources

- [Tversky & Kahneman (1973), Availability: A Heuristic for Judging Frequency and Probability, Cognitive Psychology 5(2):207-232](https://doi.org/10.1016/0010-0285(73)90033-9)
- [Kahneman (2011), Thinking, Fast and Slow](https://us.macmillan.com/books/9780374533557/thinkingfastandslow/)