Users mistake coincidental temporal sequence for causation

What it is

When a system's inner workings are invisible, users treat the order in which two things happened as evidence of causation — if A preceded B, A must have caused B, even when the two are unrelated. This is a causal illusion, sometimes called the post hoc fallacy. It isn't a sign that users are irrational: in the absence of verifiable evidence, temporal association is the cheapest — and usually reliable — cue for judging causality. Interface opacity simply widens the window in which this shortcut fails.

Why it happens

People have no direct sensory channel onto "causation" itself; causal judgment relies on proxy cues — covariation between events and their contiguity in time or space. In everyday environments this shortcut works well, because most tightly adjacent events really are related. Interfaces raise the failure rate: users see only two external events, the action and the outcome, with the system's internal state hidden, and feedback timing is often inconsistent — sometimes fast, sometimes slow, sometimes coinciding by chance with an unrelated event. Once one such coincidence gets encoded as "this works," confirmation bias then makes users more likely to notice future instances that fit the belief and overlook the ones that don't — so the false belief gets reinforced by selective memory rather than corrected by new evidence.

Studying it

• Paradigm: the contingency-judgment task — participants perform an action tied to an outcome under an experimenter-controlled true causal strength, and their subjective causal-strength rating is compared against that true value. This is the standard lab paradigm, extending operant-conditioning research to human causal judgment.
• Variables: common independent variables are the outcome's base rate and the delay between action and outcome; the dependent variable is the reported causal-strength rating, or the rate at which the action is repeated afterward.
• Use in interface research: diagnosing whether a system's feedback timing is likely to induce mistaken attributions — useful for explaining an otherwise puzzling user habit.
• Methodological caveat: lab paradigms tell participants outright, "here's an action, judge whether it works," putting them in an explicit attribution mindset. Causal illusions in interfaces often arise as a side effect of some other task the user isn't consciously evaluating at all (checking for a refresh while doing something else). This implicit attribution rarely surfaces in self-report and needs behavioral logs instead.

Where it stops holding

• The heuristic isn't a flaw: most of the time temporal association does reflect real causation — an action really did trigger the corresponding system behavior. When a system is highly deterministic and feedback is immediate, this inference chain rarely goes wrong; the error only gets amplified when the response itself is opaque, delayed, or probabilistic.
• When a system offers verifiable causal cues — explicit progress feedback, clear state indicators — users don't need to guess from timing, and the bias doesn't arise. It's a consequence of a specific information gap, not a general user shortcoming.
• Under high cognitive load or heavy multitasking, users lean more on this low-effort timing cue, and the rate of mistaken attribution rises noticeably.

Applying it

• Audit the interface for spots where two unrelated system events tend to land close together in time near a user action (a background load finishing right as an unrelated notification appears); stagger what can be staggered, and label the source clearly for what can't.
• For functions with known unstable response latency, provide a perceptible intermediate state so users aren't forced to infer success or failure from timing alone.
• How to check: run a time-window analysis over action logs to find unrelated system events that frequently co-occur shortly after a given user action — these are the candidate points of misleading coincidence to fix first.

Related

• Same group: A7.12.2 Repeating an ineffective action that once "happened to work" is superstitious behavior in an interface · A7.12.3 Higher response uncertainty makes users more prone to forming false causal beliefs · A7.12.4 Superstitious behavior resists correction by documentation and needs consistent, predictable feedback to break the association
• Nearby: A7.11 Expectation violation and the explanation gap · A7.01 Definition and function of mental models
• Search terms: causal illusion · post hoc fallacy · contingency judgment · illusory correlation