Availability bias (also known as the availability heuristic) is a cognitive shortcut that leads people to judge how common, important or likely something is based on how easily they can recall examples of it.

In the context of business decision-making, availability bias causes leaders to overweight information that is recent, vivid, emotionally charged, or highly visible — while underweighting slower-moving, less visible but statistically more important data.

Our brains are naturally wired to prioritise:

• recent events
• emotionally intense stories
• dramatic or high-profile incidents
• highly memorable experiences

As a result, quieter but more statistically meaningful information often fades into the background.

This is why a single viral layoff story can suddenly make an entire industry feel unstable, or one high-profile cyberattack can trigger sweeping security decisions, even if overall risk levels have not meaningfully changed.

What feels most “available” in memory is often mistaken for what is most important in reality.

Availability bias does not distort facts — it distorts attention.

And once attention is distorted, decision-making inevitably follows.

Image 1: Availability heuristic

“If you can think of it, it must be important”

Source: https://statisticsbyjim.com/basics/availability-heuristic/

How availability bias shapes business decision-making

In organisations, availability bias in business decision-making quietly reshapes priorities by shifting focus from structural, long-term signals to recent, highly visible events.

Leaders may overreact to:

• the last complaint they heard
• the most recent headline in the news
• a single vivid anecdote from a key client
• a recent internal incident or failure

As a result, strategic focus moves away from sustainable performance drivers and toward whatever feels most urgent in the moment.

One of the most common expressions of this bias is the tendency to treat the recent past as a reliable guide to the future.

Availability bias leads leaders to overvalue recent, vivid or emotional events, creating false urgency and distorting strategic priorities away from long-term signals.

Recency over trends

When making forecasts, managers often place far more weight on what happened most recently than on long-term patterns.

The latest quarter, last campaign, or most recent crisis feels more “real” than years of historical data — even when the broader dataset is far more representative.

This is a direct expression of availability bias in business decision-making, where cognitive accessibility replaces statistical reasoning.

High-profile events and distorted risk perception

Rare but dramatic events often dominate corporate risk perception far beyond their actual probability.

After a highly public cyberattack or a major competitor failure, executives may behave as if the same event is imminent within their own organisation.

This typically results in:

• sudden budget reallocations
• urgency spikes driven by fear
• overinvestment in visible risks
• underinvestment in less visible but more probable risks

In startups, the same effect appears when one funding success story inflates expectations while hundreds of average outcomes are ignored.

A vivid narrative always feels more convincing than long-term probability data — even when it is statistically irrelevant.

Sharks vs coconuts: a classic availability bias example

A widely cited example of availability bias is the comparison between shark attacks and falling coconuts.

Sharks dominate public perception due to media coverage, films, and cultural storytelling. However, they cause only around 10 deaths per year globally.

Falling coconuts, by contrast, are estimated to cause approximately 150 deaths annually.

Despite this, most people intuitively perceive sharks as the greater threat because dramatic, emotionally charged events are more easily recalled.

This illustrates a core principle of availability bias:

what is easiest to remember is often mistaken for what is most likely.

Countering availability bias in decision-making

Reducing the impact of availability bias in business decision-making requires deliberately changing how information is collected, interpreted, and weighted.

Look beyond recent data

Avoid relying only on recent events when making decisions.

Instead, actively incorporate:

• 5–10 year historical trends
• long-term performance cycles
• multiple economic or market conditions

This helps counter recency-driven distortions created by availability bias.

Broaden information input

One of the strongest ways to reduce availability bias is to expand the diversity of inputs.

This includes:

• cross-functional perspectives
• regional or market differences
• external stakeholders or advisors

A broader information base reduces overreliance on whatever is most mentally accessible.

Question the emotional weight of information

Before reacting to any high-impact or dramatic event, pause and ask:

Is this truly representative, or simply more memorable?

This simple question helps separate emotional salience from statistical significance — a core challenge in managing availability bias.

Replace intuition with structured thinking

Structured decision-making frameworks reduce the influence of cognitive bias in business decision-making, including availability bias.

Examples include:

• structured risk assessments
• multi-source validation
• decisions evaluated across multiple time horizons
• predefined decision criteria

This ensures that isolated, vivid events do not disproportionately influence outcomes.

Slow down decision-making

Availability bias is driven by fast, intuitive thinking (System 1).

Slowing down decision-making activates more analytical reasoning (System 2), allowing leaders to evaluate evidence rather than react to memory strength.

Even small pauses can significantly reduce bias-driven errors.

In essence: why availability bias matters

Availability bias is not just a psychological concept — it is a structural influence on how organisations prioritise, allocate resources, and assess risk.

It shapes:

• what leaders notice
• what feels urgent
• what gets funded
• what gets ignored

By actively counteracting availability bias through broader input, structured thinking, and slower decision-making, organisations move toward bias-aware leadership.

This leads to decisions grounded in evidence rather than visibility — and ultimately, more resilient long-term strategy,

The post Availability Bias in Business: Why Urgency Is Often an Illusion appeared first on Pontis Technology.

Every business decision starts somewhere. A number on a slide, an example that comes to mind, or a success story circulating at the last industry event. These starting points feel incidental, but they are rarely neutral.

Two cognitive biases, anchoring and survivorship bias, make this problem particularly costly in business environments. Anchoring bias locks teams onto the first figure they encounter, shaping every estimate, negotiation and forecast that follows.

Survivorship bias distorts strategy by drawing lessons only from visible successes, while the far larger body of failures disappears from the data entirely.

This article explains how each works, where they show up most often in business and project settings, and what leaders can do to reduce their grip.

Anchoring bias: When the first number wins

Anchoring bias occurs when people rely too heavily on the first piece of information they encounter when making a decision.¹ That initial figure, estimate or idea becomes a reference point that pulls all subsequent judgments toward it, even when better data arrives later.

The adjustment people make away from the anchor is almost always insufficient. The result is that the final decision ends up closer to that original number than the evidence actually warrants.

Negotiations and pricing

A used-car dealer opens with an intentionally high asking price. The eventual discount feels like a win, even when the final figure is still inflated. The same psychology surfaces in hiring: the first salary figure on the table quietly defines the range of the entire negotiation, regardless of whether it has any real grounding in the role or market.

Budgeting and planning

When a project’s first estimate lands at, say, €500,000, it becomes surprisingly difficult for teams to accept that the real scope may require twice that amount. The early number functions as a mental benchmark that quietly resists revision, even as new information comes in. In agile environments, if one developer casually estimates eight weeks, the group tends to gravitate toward that figure rather than forming independent assessments, often resulting in collective underestimation of actual effort.

Strategy and ideation

In brainstorming sessions, the first idea put on the table casts a long shadow. Teams tend to evaluate subsequent proposals relative to it, giving the opening idea disproportionate weight. Over time, the discussion narrows around that early suggestion, and potentially stronger options never receive a fair hearing.²

Anchoring is particularly stubborn because it doesn’t spare experienced people. Studies show that real-estate agents’ property valuations are pulled toward the listed asking price even when they believe their judgment is fully independent.² Once an anchor is in place, people also tend to seek out information that confirms it, tightening the bias’s grip on the final decision.

How to counter anchoring bias

The most effective approach is to slow down before the first number takes hold. A few practices worth building into decision-making processes:

• Gather independent references before opening a discussion. Look at multiple benchmarks, cost comparisons or past project data before any internal figure is floated. This reduces the gap between the anchor and reality.
• Challenge the number explicitly. Ask: if this figure were twice as high, or half as low, would we make the same decision? Forcing the question surfaces how much hidden work the anchor is doing.
• Collect estimates anonymously. When teams share numbers before group discussion, early guesses can’t quietly shape everyone else’s thinking. Anonymous polling or written estimates before a meeting significantly reduces anchoring effects.
• Treat the first number as a rough draft. Leaders set the tone here. When they frame early estimates as a starting point rather than a target, teams feel permission to keep questioning, adjusting and revising as new data arrives.

From the first cost estimate that becomes a silent benchmark to the success stories that hide a far larger number of failures, anchoring and survivorship bias are two of the most expensive distortions in business decision-making.

Survivorship Bias: What the Data Isn’t Showing You

Survivorship bias happens when we focus only on the visible successes and draw conclusions from them, while overlooking the much larger group of attempts that failed and disappeared from view. The result is a distorted picture of what works, what’s realistic and what the actual odds are.

In business, failure rarely makes it into the case study. Successful companies get interviews, conference keynotes and articles. Companies that followed the same strategy and failed quietly disappear. Over time, this creates the illusion that success is more predictable and more common than it truly is.

Strategy and best practices

Leaders study Apple, Google or the latest unicorn and try to extract transferable lessons. But the thousands of companies that attempted similar strategies and fell short are absent from that analysis. As Farnam Street researchers³ note, companies that fail early are ignored while rare successes are celebrated for years, creating a distorted sense of which approaches reliably work. The winning company’s path appears to be a formula, when in reality, many others followed the same formula and failed.

Product development

A software team that analyses only its active, paying users is studying the survivors. Customers who churned, leads who never converted and features that never gained traction are missing from that dataset. The team ends up investing in what current users love while missing the insights hidden in the products, features and customer relationships that didn’t make it. Without a clear-eyed look at failure, it’s easy to build confidently in the wrong direction.

A famous illustration

During World War II, Allied engineers studied the bullet holes on bombers that returned from missions and proposed reinforcing the areas that had sustained the most damage. The logic seemed sound, until statistician Abraham Wald pointed out the flaw: they were only looking at the planes that made it back. The aircraft shot down in truly critical areas never returned to be counted. The right response was to reinforce the areas with no visible damage, because those were the spots where a hit meant the plane didn’t survive. The most important data was the data that was missing entirely.

How to counter survivorship bias

The core habit is straightforward: flip the question. For every success you’re analysing, actively seek out the equivalent failures.

• Study failures as rigorously as successes. Post-mortems shouldn’t be reserved for projects that shipped. Failed initiatives, churned customers and abandoned ideas are often richer sources of learning than polished success stories.
• Seek out the voices that usually go unheard. Interview customers who didn’t convert. Talk to employees who resigned. Review projects that were quietly shelved. These perspectives reveal blind spots that success stories never surface.
• Put the real base rates on the table. Before committing to a bold strategy, look at the historical success rate of similar attempts in your industry. If one in ten comparable initiatives typically succeeds, that context belongs in the decision. It doesn’t kill ambition, it grounds it.
• Assign someone to ask the uncomfortable question. When a success story is being used as evidence that something works, someone in the room should always ask: what about the ones that didn’t? A formal “critical challenger” role ensures failure data doesn’t get quietly bypassed.

Survivorship bias is, at its core, a blind spot in how we construct reality. When leaders give failure the same analytical weight as success, decisions become grounded in evidence rather than in polished winner stories.

Up next: Part 3 covers availability bias and the framing effect, two forces that show how a single vivid event can quietly redirect strategy, and how the same restructuring plan can appear as a win or a loss depending solely on how it is presented.

Frequently Asked Questions

Now that you’re up to speed with part 2, perhaps you would like to remind yourself of part 1

Sources

¹ J. Perfetti, “The Bias Trap,” Duke Corporate Education, 2025. Available: https://www.dukece.com/insights/the-bias-trap/

² “Mental Model: Anchoring,” Farnam Street Blog, 2008. Available: https://fs.blog/mental-model-anchoring/

³ “Survivorship Bias: The Tale of Forgotten Failures,” Farnam Street Blog, 2019. Available: https://fs.blog/survivorship-bias/

Atlassian, “5 Cognitive Bias Examples and How to Avoid Them in Decision-Making,” Atlassian Blog, 2019. Available: https://www.atlassian.com/blog/productivity/cognitive-bias-examples

F. Gottlob, “How to Avoid Survivorship Bias in Product Management,” Medium, 2025. Available: https://medium.com/@falkgottlob/how-to-avoid-survivorship-bias-in-product-management-lessons-from-the-british-bomber-study-25edb8ab4ab7

The post The First Number in the Room: How Anchoring and Survivorship Bias Distort Business Decisions appeared first on Pontis Technology.