EnglishFrançaisEspañol

Illusory Correlation – when you see a connection that isn’t there

Reference entry

Article options

Perception & patterns · Apophenia · Entry 6

Do you think two events are connected when it’s just coincidence? That’s Illusory Correlation – the tendency to see a relationship between unrelated things.

Electric editorial collage illustrating Illusory Correlation

Examples and situations

  • Stereotypes – “People with tattoos commit more crimes,” even though statistics don’t support it.
  • Medicine – “I took a vitamin and my cold went away,” but it might have healed naturally.
  • Finance – “The stock market drops when the moon is in a certain phase,” but correlation doesn’t mean causation.

Questions to check

  • Check the data – correlation ≠ causation.
  • Consider context – two things happening together doesn’t mean one causes the other.
  • Be skeptical of gut instincts – many ‘obvious’ connections fall apart under real analysis.

Long-form guide

Illusory Correlation — When coincidence feels causal

On Monday our trial conversions jumped 18%. By Tuesday the team chat was certain: the new onboarding video did it. By Thursday the lift evaporated, but the story stuck. We had etched a link where none existed and almost rerouted the roadmap around it.

On this page

What the bias does

Illusory correlation is that reflex. Two events happen together and we assume cause-and-effect. The brain loves tidy explanations more than messy variance, so it sneaks a narrative in before the data can object. This page is a practical field guide: what the bias is, where it hides, and the rituals that keep your analysis grounded when coincidence shows up wearing a lab coat. Illusory correlation makes unrelated variables feel connected. It thrives on small samples, selective attention, and emotionally charged observations.

Why it matters: You waste cycles engineering fixes for issues that were random noise; You reinforce stereotypes because vivid anecdotes beat silent statistics; You bet on strategies that never had a causal lever, so they fail quietly; You stop exploring alternative hypotheses once the tidy story lands. In product analytics, medicine, investing, or hiring, the result is the same: we overfit our decisions to moments that were never signal.

Market moves and narrative fallacies

A handful of disappointing interviews with candidates from a single bootcamp can solidify into a myth about the entire program. The sample is tiny, and the interviews likely shared the same rushed interviewer. Yet the perceived link spreads through the org, narrowing the funnel. A spike in tickets lands the same week you shipped an experiment.

You assume causality, roll back the feature, and only later notice that seasonality hits the same week every year. The correlation was temporal, not causal. A stock rallies after a charismatic founder interview. Commentators connect the two because stories travel faster than macro data. In reality, index rebalancing or currency shifts were the driver.

Why our minds buy the story

A cold eases a day after drinking ginger tea. The relief feels like proof. Without a control, you forget that most colds resolve on the same cadence regardless of tea. Availability. Vivid pairings are easier to recall, so we overweight them compared to dull counterexamples; Selective sampling. We often only observe the cases that confirm the link (e.g.

, only published research, only escalated tickets); Emotional load. When events feel important, we search harder for meaning, which nudges us to accept the first plausible association; Time pressure. Teams under deadlines prefer a satisfying explanation to an honest "we do not know yet." Knowing these drivers makes it easier to design counter-moves: slow down, expand the sample, and invite dissenting data.

Run a correlation sanity check

Before you reorganize a roadmap, run this quick gauntlet. It takes under thirty minutes once you practice it, and it protects you from expensive mirages. Write the observed correlation in plain language. "When X happens, Y seems to rise." Log the base rates for X and Y across the last relevant time window; Search for cases where X happened without Y and where Y happened without X;

Check for gating factors: did a filter, migration, or data gap change who shows up in the metric?; List at least three alternative hypotheses and the evidence you would expect if they were true; Decide what minimal extra data or experiment would convert uncertainty into confidence. When you document this sequence, you create reusable artifacts for the next spike. Patterns emerge in the process, not the chart.

Illusory correlation vs. Texas sharpshooter

Clustering illusion says random streaks look meaningful. Illusory correlation says two variables move together so there must be a link. The first is about patterns inside one variable; the second is about relationships between variables. Together they create the deadliest combo: a random clump paired with a quick story. Confirmation bias filters incoming data once you have a belief. Illusory correlation manufactures the belief in the first place. When you train teams to demand mechanisms, you starve both biases.

The Texas sharpshooter paints the target after shooting the barn. Illusory correlation notices nearby bullet holes and assumes the shooter aimed there. Both love tidy targets, but illusory correlation thrives on co-movement while the sharpshooter thrives on selective boundaries. Make every weekly metrics review start with "What else could explain this?"; Track a "null wins" board where teams earn credit for proving a pattern was random; Teach fast experiments: geo holdouts, staged rollouts, instrumented toggles; Share postmortems when correlation misled you. Shame thrives in secrecy; learning thrives in daylight. Your goal is not to eliminate intuition. It is to give intuition a friction-filled runway so only real causality gets to take off.

Decision checklist

  • Capture base rates before you discuss any spike or dip
  • Note sample sizes and selection filters on every chart screenshot
  • Keep a shared doc of recent false alarms and what revealed them
  • Assign a rotating skeptic to propose at least two counter-hypotheses
  • Pause big bets until you can name a plausible mechanism, not just a correlation
  • Schedule a monthly audit of dashboards for hidden filters or cohort biases
More ways to use this idea