Psychologists Amos Tversky and Daniel Kahneman named the availability heuristic in the 1970s: people judge how likely or important something is by how easily an example comes to mind, not by how often it actually happens (Wikipedia). Vivid, recent, and emotional examples come to mind fastest, so they get weighted as if they were common, even when they're rare.
Marketers live inside this bias constantly, because our job is to consume a stream of vivid, recent signals: competitor launches, viral posts, one furious customer email. The mental shortcut that helps you survive a jungle is the same shortcut that wrecks a roadmap.
Why the vivid thing feels like the important thing
Your brain doesn't distinguish "this is common" from "this is memorable." A single sharp, emotional data point can outweigh a hundred boring ones sitting quietly in your dashboard.
Cybersecurity vendors know this instinctively: they lead marketing campaigns with the most recent, highest-profile breach in the news, because a fresh vivid disaster sells more urgency than an accurate base rate ever could (Renascence). That's the heuristic working exactly as designed, on your customers. It works on you too.
Inside a marketing team, this shows up in three familiar rooms:
- The roadmap gets reshuffled because one competitor's post went viral last week, not because of any actual shift in market share.
- A single scathing customer review dominates a strategy meeting more than the aggregate NPS trendline that hasn't moved in months.
- The channel that got the most recent big win keeps getting more budget, even when its actual average return is mediocre.
None of these reactions are irrational, exactly. They're just miscalibrated: vivid isn't the same as representative.
A SaaS team saw one detailed churn-complaint thread go viral on X and rebuilt Q3's roadmap around it, even though the underlying churn rate hadn't moved and the complaint was a single edge case. Three months later, the actual churn drivers, still ignored in the data, hadn't budged.
Where it quietly distorts prioritization
Big, billboard-style brand campaigns from Nike, BMW, and Apple work partly because they exploit this same bias deliberately, flooding a city with repeated, vivid imagery so the brand is simply the first thing that comes to mind at the moment of decision (Growth Method). That's availability heuristic used on purpose, aimed outward. The dangerous version is when it operates on you, unnoticed, aimed at your own decisions.
Ask yourself, honestly, the next time a data point demands urgent action:
- Did I just see or hear this, or did I check whether it's actually trending?
- Is this one loud voice, or a pattern across many quiet ones?
- Would I still prioritize this if I'd read it as a boring number in a spreadsheet instead of a screenshot in Slack?
That third question does most of the work. Strip the vividness and see what's left.
Availability heuristic vs. recency bias
These two get used interchangeably, but they're not quite the same thing, and mixing them up leads to the wrong fix. Recency bias is specifically about time: something that happened yesterday feels more important than something that happened last quarter, purely because it happened recently (Growth Method).
The availability heuristic is broader: it's about how easily an example comes to mind, and vividness matters as much as timing. A single dramatic customer complaint from six months ago can still dominate your thinking today if it was memorable enough, even though nothing about it is recent. Recency bias is really just one flavor of the availability heuristic, the flavor where "recent" happens to be what makes something easy to recall.
The practical difference matters because the fix is different. Recency bias is corrected by looking further back, pulling last year's data alongside this week's. The availability heuristic also needs you to correct for vividness, asking whether something felt important because it was common, or just because it was dramatic, regardless of when it happened.
Common mistakes teams make with this bias
Knowing the concept doesn't stop it from operating on you; it just gives you a name for what already happened.
- Confusing "I can think of examples" with "this is common." Being able to name three churned customers in a segment feels like data, but three named examples out of two thousand accounts is not a trend.
- Letting the most recent competitor move set the whole strategy. A rival's one loud launch gets treated as a market signal, when it might be an isolated bet that fails quietly next quarter.
- Overweighting internal anecdotes over customer research. A stakeholder's personal experience with the product ("my mom couldn't figure out the signup flow") gets prioritized over usability data from actual users, because it's vivid and personal.
- Skipping the base rate because it's boring. Dashboards with months of steady numbers don't generate urgency the way a single Slack screenshot does, so they get checked last, if at all.
Naming the bias doesn't cure it. Building the check into your process before the next vivid data point lands is what actually works.
Building a base-rate check into the workflow
You can't switch off the heuristic, but you can force a base rate into the room before it decides anything.
- Log the vivid event, then check the trendline before acting; one angry tweet gets logged alongside 90 days of aggregate sentiment, not instead of it.
- Require a "how common is this really" question in any meeting where someone proposes reprioritizing based on a single example.
- Separate "urgent because vivid" from "urgent because measured" explicitly in your triage process, so the two don't get conflated by default.
The goal isn't to ignore the loud signal. It's to make sure it earns its seat at the table instead of walking in for free.
Next time a screenshot lands in your Slack demanding a pivot, pause before the roadmap does. Ask what the quiet data has been saying all along, it's usually been saying it for weeks.