Your Brain Can't Stand a Blank Space, So It Fills It With the Worst

It's Friday evening, 6:30 p.m. An email from your manager lands in your inbox: "We need to talk." No subject, no explanation, no meeting time.

You already know what happens next. You spend the weekend mentally getting fired, calculating your savings, inventing three possible explanations and rehearsing a conversation that never happens. On Monday it turns out they wanted to discuss the vacation schedule.

The email contained exactly three words. Everything else you produced yourself.

Uncertainty is worse than bad news

In 2016 Archy de Berker at University College London tested this on people, and the result is worth knowing.

Forty-five volunteers played a simple game: stones on a screen, a snake hiding under some of them. Find a snake, get an electric shock, a real one. The probability of a snake changed as the game went on, and participants gradually learned to estimate it. Throughout, the researchers measured skin conductance and pupil dilation, physiological stress rather than what people said they felt.

Here's where it gets interesting. Not knowing whether a shock was coming turned out to be considerably harder than knowing for certain that it was. The relationship formed an inverted U: a zero per cent chance of a shock was calm, a hundred per cent chance was also relatively calm. The worst point was right in the middle, at fifty-fifty.

Guaranteed pain is easier to bear than possible pain.

Co-author Robb Rutledge offers an everyday example: applying for a job, you stay fairly calm when your chances are close to nothing, and fairly calm when the position is practically yours. What wears you out is genuinely not knowing.

Which leads to something worth keeping in mind. Uncertainty isn't the absence of a problem, something you simply tolerate until information arrives. To the body it's a load in its own right, often heavier than the bad news itself. A weekend spent after "we need to talk" costs more than Monday, whatever Monday turns out to contain.

Why the blank space never stays blank

Which raises the second question: why can't you just not think about it until Monday.

Because the brain isn't built as an observer. It's built as a prediction machine. That's how neuroscientist Karl Friston and philosopher Andy Clark describe it: the brain continuously builds a model of what should happen next and compares it against what arrives from the senses. What reaches awareness isn't a picture of the world, it's the mismatch between expectation and signal.

For a system like that, an unfilled slot in the model is an emergency. Not a neutral blank, but a gap that has to close immediately, because without a prediction there's no way to decide what to do. Clark called life in such a system surfing uncertainty: you stay upright only by continuing to move.

What happens to the gap is known: it fills, and where evidence is missing it fills with the worst plausible version. Why that happens is covered in the article on the spec. Missing a real threat costs your brain more than a false alarm, so the empty space fills with a threat rather than a neutral option.

Which is how three words in a message and a gap the size of a weekend end in a cancelled holiday and a box of sedatives.

So the formula for this whole cluster: wherever information is missing, the brain builds in what isn't there, and builds in the worst plausible version. The five traps below are the same mechanism running on different material.

Five traps in this cluster

1. Catastrophizing. A gap in the future

What it feels like. One unknown turns into a chain rather than a single bad outcome. Each link sounds reasonable on its own, and together they carry you from "she hasn't replied" to "I'll end up alone with no job" in four steps and ninety seconds.

Example. My husband is a diving instructor. He wears a Garmin dive watch with an emergency function: one button, and the watch sends an SOS to every contact you've saved in it. I'm one of those contacts.

One day I get a message from that watch: SOS sent. A minute later, from my husband: "Everything's okay, don't worry." Then silence, phone unreachable.

My brain assembled a version within seconds, and the version was coherent. The alert went out, so something happened during the dive. He wrote to me himself, so he surfaced somehow, but there's chaos around him. He wrote briefly and immediately, so he doesn't want me calling and getting in the way while the rescue is under way. Meaning "everything's okay" isn't everything's okay, it's him holding me off while something terrible unfolds.

Notice what happened to the fact: the single piece of good news in the whole story was reprocessed into evidence for the catastrophe.

An hour later, when he got signal back, I was already working out which service to call and how to explain the location. He had been going through the watch settings, triggered the alert by accident, texted me so I wouldn't panic, and gone off to dive with his students. Which is why he was unreachable.

When it isn't a trap. When you're genuinely assessing risk and doing something with the result: gathering documents, setting money aside, getting a second opinion. Planning for the worst case is ordinary engineering work. It becomes a trap when the scenario runs in your head and not a single action follows from it.

What helps. Stop the chain at its first link and ask not "what if" but "what's the actual probability". The second question matters more: what's the most likely explanation? In my story, the most likely explanation was the one that turned out to be true, someone pressed the wrong button. But I'd fallen fully into catastrophizing and never even considered it.

2. Fortune telling. A gap in the outcome

What it feels like. You're not guessing, you know. I'll fail, they won't take me, it won't work out. It registers not as a forecast but as a fact that simply hasn't arrived yet.

Example. You don't apply for the job because "they'll reject me anyway". There was no rejection. There was you, deciding on their behalf.

When it isn't a trap. When the forecast has grounds: you applied three times and got three rejections, the requirements sit two levels above yours. Experience is data, and data should be counted.

What helps. Separate what happened from what you predicted. "I think they might reject me" instead of "they'll reject me" sounds like a technicality and works anyway: a hypothesis can be tested, a flat statement can't.

3. Mind reading. A gap inside someone else's head

What it feels like. You don't know what the person is thinking, but the gap closed instantly and, naturally, not in your favour. "OK" instead of the usual "okay, thanks" becomes "she's annoyed with me". A colleague doesn't say hello, so you must have offended him.

Example. A friend replies a day later. In that day you worked through five versions, all of them about something you did wrong. The version where her phone died was never on the list.

When it isn't a trap. When you're going on what the person said or did, rather than a tone you painted in yourself. "She told me she's angry" is information. "She ended her message with a full stop instead of a smiley" is not information.

What helps. Split a page in two: what the person DID and what you ADDED. The first column usually has one line, the second has twelve. And the most effective option, uncomfortable as it is: ask them, out loud, in words. One question closes the gap better than any exercise.

4. The spotlight effect. A gap in how others see me

What it feels like. The mirror version. Now you're certain everyone can see straight through you: they noticed you were flustered, they realised you hadn't understood the topic, they clocked that you're not at your best today.

Example. I was presenting at an important meeting, talking about optimization systems, and mixed up the names of two of them. I caught it myself, in the moment. And from then on I was certain the whole room had caught it too: I tried to keep a straight face, finished the talk, and spent the evening thinking about nothing else.

The next day I asked a colleague whether he'd noticed the mistake. He said: "No, was there a mistake?" A second colleague, when I joked that mixing up those two systems takes real skill, asked: "Wait, who mixed them up?"

Nobody noticed. Except me, who spent an entire evening on it.

When it isn't a trap. When it's something genuinely visible: you turned up forty minutes late and in your underwear... that got noticed.

What helps. Remember how attention is distributed: everyone has their own gap to fill, and they fill it with themselves, not with you. Easy to check, too. Try to recall what you noticed about the other people at that same meeting. Probably nothing.

5. Projecting motives. A gap in someone else's intentions

What it feels like. Another person's action gets an explanation, and the explanation is always about intent. Not "it happened" but "he did it on purpose". The gap here isn't in the facts, it's in the reason, and a whole motive drives into it.

Example. Someone doesn't let you into the lane. It was personal. A colleague doesn't invite you to a meeting, so he's squeezing you out. In both cases the most likely explanation is boring: didn't notice, forgot.

When it isn't a trap. When there's a pattern. Once is a coincidence. The fifth time in a row, and only you, is data, and there's no need to ignore data out of politeness.

What helps. Before accepting the version with intent, come up with two boring ones: carelessness and overload. Not to excuse everybody, but so that the bad-intent version has to pass a check rather than arriving first by default.

What they have in common

Five different names, one mechanism.

Catastrophizing closes a gap in the future. Fortune telling closes a gap in the outcome. Mind reading closes a gap inside someone else's head. The spotlight effect closes a gap in how others see you. Projecting motives closes a gap in someone else's intentions.

Different material, identical operation: information is missing, the brain builds it in, and what it built is served as knowledge. And what it built is nearly impossible to tell apart from what was observed. Which is why arguing with the content rarely works: convince yourself your colleague isn't annoyed, and an hour later your brain reassembles the same version out of a fresh detail.

The practical conclusion follows from that. What you need to catch isn't five separate traps but one moment: the moment information ran short. A gap is easier to spot than five different conclusions are to untangle, and without the gap none of them assemble.

What to do about the uncertainty itself

If the load comes from not knowing, that's what to work on, rather than the thoughts it produced.

Call the gap a gap. Write down what you know as fact, and separately what you built in. In my story with the watch there were two facts: an alert was sent, and my husband wrote "everything's okay". The rest, rescue operation included, was my own production.

Shrink the gap instead of enduring it. Ask. Clarify. Message first. The conversation you're dreading is almost always cheaper than a weekend spent waiting for it, and de Berker's data says exactly that: certainty, even unpleasant certainty, costs the body less.

If you can't shrink it, give it a deadline. Sometimes there's nowhere to get the information: the result comes on Thursday, the person answers when they answer. Then a scheduled point does the work: "until Thursday I don't think about this, on Thursday I deal with it". That isn't banning the thought, it's moving it to where something can be done with it.

Remove the source of the false signal. The engineering part. If a "we need to talk" with no subject knocks you sideways once a week, you can ask for the subject line. If silence in a chat does it, agree on a rule: "seen it, replying tonight". A system that fires exactly as designed doesn't get talked out of it. It gets a different input.

The gaps will keep appearing. But between "I know what happened" and "I built this in because the data ran short" there's a difference worth an entire weekend.

All cognitive traps >

Next: Your Brain Cuts the World in Half Because It's Cheaper - the second cluster, about how what's left collapses into two piles. Then double accounting, the illusion of control and reaction as evidence.