You haven't thought about an old friend in months. Then, on the drive home, they come to mind - and an hour later, they call. You find the experience remarkable. You mention it to people. It feels like more than chance.
Here's the question worth asking: how many times did you think of that person and not get a call? How many calls arrived from people you weren't thinking about? The remarkable event gets registered and remembered. The unremarkable misses don't.
That selective memory - combined with pattern-seeking cognition - is what produces the experience of meaningful coincidence.
What It Is
Coincidence bias is the tendency to perceive meaningful connections between unrelated events, interpreting random occurrences as significant signals rather than as the statistical noise that they are.
It isn't credulity or superstition, exactly. It's a feature of how pattern recognition works in the human mind. The brain is designed to find structure, sequence, and causality - and it finds these things even in genuinely random arrangements. Two events that happen close together in time or space get connected, and the connection generates a feeling of significance that is difficult to dismiss even when you know intellectually that the events are unrelated.
How the Mechanism Works
Several cognitive processes combine to make coincidences feel meaningful.
Pattern completion. The brain actively seeks causal links between proximate events. When two events occur in sequence - thought of a friend, then phone rings - the detection system flags the sequence as a potential contingency. The flag is automatic, not deliberate.
Agency detection. Humans have a tendency to attribute events to intentional forces. A coincidence that involves you specifically - two events that both relate to your life - is particularly likely to feel like it was arranged, as if some process is sending a signal. This was likely adaptive in environments where many events were in fact caused by intentional agents.
Confirmation bias in recording. Coincidences that fit your expectations, beliefs, or ongoing stories about your life are noticed and remembered. The many occurrences that don't produce remarkable coincidences go unregistered. The remembered set is then a skewed sample - full of meaningful-seeming connections, silent on the baseline of non-events.
Neglect of base rates. Most striking coincidences become unremarkable when you account for how many opportunities exist for them to occur. In a large enough population, over a long enough period, almost any coincidence is statistically expected to happen to someone.
The Approved Example
During a software upgrade, the project lead saw that two developers called in sick on the same morning. He felt the timing was too perfect to be chance and began to wonder if the new program carried some hidden flaw that was making people ill. He postponed the rollout and asked for extra testing, delaying the schedule. Later, records showed the developers had unrelated illnesses - a flu and a migraine - confirming the overlap was merely coincidental. The manager learned to check base rates before attributing meaning to simultaneous events.
The decision cost the project time and resources. The coincidence felt compelling precisely because it arrived in a context that had a plausible explanation: a new software rollout. When a coincidence maps onto a story you're already telling, the story provides the apparent explanation, and the coincidence appears to confirm it.
The Mystery and the Reveal
The mystery coincidence bias generates is usually this: How could this have happened by chance?
The reveal, consistently, is this: base rates are higher than intuition suggests, and the registered event is a selected sample from a much larger distribution of unremarkable misses.
Consider the type of coincidence where you think of someone and they contact you shortly after. How many times do you think of people on any given day? How many people might contact you in a week? The overlap is not especially improbable when the denominator is considered. The surprise comes from comparing the event to a reference class of zero rather than the actual reference class of all similar opportunities.
Historical records show cases of remarkable coincidences - multiple people who were separately delayed arriving late for an event, only to find the event location had been destroyed in the interval. These cases are genuinely striking. They're also the ones that get recorded and retold precisely because of their strikingness. The much larger number of cases where the coincidence didn't occur, or where delays led to nothing remarkable, are invisible in the record.
Where It Matters
In personal decision-making, coincidence bias produces superstitious patterns: a particular behavior that happened to precede a good outcome gets repeated on the assumption that it caused the outcome. The sequence is remembered; the cases where the behavior occurred without a good outcome are not.
In professional contexts, as the software example illustrates, coincidences that suggest a causal story can redirect resources toward investigating a connection that doesn't exist. The attention cost and delay cost are real; the causal link being investigated was never there.
In public discourse and conspiracy thinking, coincidence bias is one mechanism through which unrelated events get connected into explanatory narratives. Timing, shared features, or overlapping people trigger the connection, and the connection then gets treated as evidence of coordination.
The Common Misunderstanding
A common response to coincidence bias is: But coincidences do mean something - sometimes they really are signs. Coincidence bias doesn't deny that sometimes correlated events have a genuine causal link. It identifies a systematic tendency to perceive connections in random events, beyond what the evidence supports. The correction isn't to treat all coincidences as meaningless - it's to ask what a statistically fair assessment of the probabilities would show.
A second misunderstanding: only people with magical or superstitious beliefs experience this bias. Coincidence bias operates across all education levels and belief systems. The pattern-detection mechanism that generates it is not optional - it's how the brain works. Belief in the significance of coincidences is one downstream effect; the perception of the coincidence as remarkable is more fundamental.
See Coincidence in everyday decisions
Pick a life context to see how this bias can show up outside the textbook.
Meeting Room Booking Overlap Misinterpretation
A team lead sees two colleagues repeatedly book the same conference room for consecutive slots and assumes the room brings success, then enforces its use for all client calls, creating scheduling friction.
Scenario
During the weekly planning meeting, the lead observed that Priya and Luis each reserved the main conference room for 9 - 10 am and 10 - 11 am on three separate days that week. He recalled that the room had also been used the day before a successful product demo. Thinking the pattern signaled more than chance, he announced that all client calls must be held in that room and removed the other booking options from the shared calendar. Over the next two weeks, several team members complained about double-bookings and missed slots, and the focus shifted from agenda preparation to room logistics. A quick review of the booking log showed that, with 12 team members and four available rooms, random overlaps of this frequency were expected; the streak was simply coincidental.
Where The Bias Enters
The lead's pattern-recognition made the recent room overlaps salient, his agency detection led him to infer an intentional cause, confirmation bias caused him to remember the matching cases while forgetting the many times the room was booked without a notable outcome, and he neglected the base rate of how often any two people might pick the same room by chance given the team size and number of rooms.
Decision Check
Before acting on the perceived link, ask yourself: How likely is it for any two people to choose the same room by chance given our team size and the number of rooms? If the chance is not low, treat the observation as random rather than causal.
This pilot example is illustrative and review-gated. It is designed to explain the pattern, not to claim a documented public case.
Sources
- Dobelli, R. The Art of Thinking Clearly. Sceptre, 2013.

