Illusory Correlation.

01Overview

Illusory correlation is seeing a systematic link between two things when none exists — or when the link is far weaker than perceived. Co-occurrence feels like causation because the brain is a pattern engine with loose quality control.

Designers correlate a banner with a signup spike, a colour change with support drop, or a persona trait with churn. Sometimes they are right. Often the timeline aligned by chance, seasonality, or a hidden third variable. Roadmaps chase correlations that dashboards invented.

02Detailed explanation

Illusory correlation thrives in noisy, low-sample product environments:

• A redesign ships the same week as a PR hit — credit goes to UI, not press.
• Support tickets fall when a tooltip is added — but a major bug was fixed the same release.
• Researchers link a demographic tag to a behaviour observed in two participants.
• Teams see "mobile users hate feature X" when mobile sessions coincided with a slow API region.

Stereotypes partly persist through illusory correlation: rare co-occurrences of group label and memorable behaviour become "always true" when base rates are ignored.

03Why it exists

Confirming co-occurrence is cognitively cheap. Disconfirming instances are less memorable — classic availability and confirmation dynamics.

Dashboards encourage line-up comparisons without experimental design. Visual proximity becomes narrative causality in slide decks.

04Effects on users

Users develop superstitions about products: "It breaks when I do X" when X and breakage are unrelated. Support must untangle illusory user correlations too.

They suffer when teams redesign from illusory links — removing features users loved because they coincided with a metric dip driven elsewhere.

05Effects on designers & teams

Teams enshrine illusory correlation in rituals:

• Release post-mortems without controls. Every adjacent metric movement gets a causal story.
• Persona superstitions. Traits stick after two examples — "finance users never scroll."
• Heatmap mythology. Eye movement correlated with success without task outcome linkage.
• Qual sample overfitting. Two quotes establish "correlation" between segment and need.

6Introspective view

Look inward. Teams perceive relationships between variables that are unrelated or only weakly linked.

From an introspective perspective, ask how Illusory Correlation may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

07Practical takeaways

• Hold a changelog of confounds. List everything that changed in a release window.
• Run controlled tests. Isolate one variable when claiming causality.
• Check base rates. How often does the behaviour happen without the supposed cause?
• Segment by hidden variables. Device, region, cohort, new vs returning.
• Delay attribution. Wait through seasonality before crediting UI.
• Teach correlation language. "Associated with" until proven "caused by."

08Design examples

09Ethical risks

Illusory correlation fuels discriminatory design when spurious links between group labels and behaviours become requirements.

Users lose access to valuable features when teams misattribute outcomes and "fix" the wrong thing confidently.

Self-test: Which product belief on your team is built on co-occurrence alone — and how would you test it?

10Related biases