The message comes in. Before you’ve even read it twice, you’re three responses deep — one drafted in your head, one you’re about to text a friend for a second opinion, one you’re rehearsing out loud. You haven’t asked what the message actually means yet. You haven’t paused to sit with a problem before reacting to it. You’ve just started fixing it.

That’s the reflex this piece is about. Most advice on problem-solving assumes the hard part is finding the right answer. Often the harder part comes first: tolerating the gap before you have one. Learning to sit with a problem long enough to actually understand it, before you start acting on it.

Why the Fix Reflex Kicks In So Fast

An unresolved problem doesn’t feel like information. It feels like an alarm. That’s not just a figure of speech — the amygdala reads ambiguity as a threat cue and fires off urgency before the slower, reasoning parts of the brain have even weighed in. Threats demand action, not study. So the instinct fires: do something, anything, that makes the uncertainty go away. Texting a friend, googling the symptom, drafting the reply — none of that is really solving the problem yet. It’s ending the discomfort of not knowing.

That’s a useful distinction. The urgency you feel usually isn’t coming from the problem itself. It’s coming from how uncomfortable the not-knowing feels. Confuse the two, and you’ll keep mistaking a fast decision for a good one. And of course, this isn’t a flaw reserved for other people. Everyone has fired off the reply, made the call, or started the fix before they’d actually finished thinking — and felt the small, private regret of it twenty minutes later.

What It Actually Means to Sit With a Problem

Sitting with a problem doesn’t mean doing nothing. It means separating two steps that usually collapse into one: naming what’s actually happening, then deciding what to do about it. Most people skip straight to the second step. That’s why the first one so rarely gets done properly.

Try naming the problem in a single, neutral sentence. Not “I need to respond to this,” but “I don’t yet know what this message means, and I’m uncomfortable not knowing.” That sentence does real work. It puts the discomfort on the page instead of in the driver’s seat, and it turns the next move into a choice instead of a reflex. A problem named accurately is already partway solved, even though nothing has changed yet.

Not Knowing vs. Not Wanting to Feel It

Not every unresolved problem is the same kind of unresolved. Some genuinely need more information before any move makes sense — a symptom nobody has checked yet, a decision that depends on a fact you don’t have. Others don’t need more information at all. They need you to tolerate the discomfort long enough to see what’s actually there, because the fixing impulse targets the feeling, not the facts.

Confusing the two is exactly what turns a five-minute symptom into a two-hour search history — the same reflex behind self-diagnosing every ache online instead of sitting with a little uncertainty until it resolves on its own, or genuinely warrants a call to someone qualified. Before acting, ask plainly: am I missing information, or am I just uncomfortable? The two questions point toward completely different next moves. Only one of them is actually worth solving.

A Concrete Way to Delay the Fix

Naming a problem clearly still leaves the urge to act right now. So build in a small, real delay rather than relying on willpower alone. Write the problem down — the neutral sentence from earlier — and set an actual time before you’re allowed to act on it. Twenty minutes for something minor. A full night’s sleep for something larger. The exact length doesn’t matter much. What matters is that the delay is real and scheduled, not an open-ended “I’ll wait a bit” that collapses the moment the discomfort spikes again.

This is the same instinct behind resisting the urge to call a professional the moment something breaks, instead of first figuring out whether you could understand — or even fix — the problem yourself. And it’s doing real biological work, not just buying time symbolically: the prefrontal cortex, the part actually capable of weighing a decision, is slower to engage than the amygdala’s alarm. A scheduled delay is what gives it the chance to catch up before the alarm gets to decide unopposed. The delay isn’t stalling. It’s the difference between a decision made from information and one made from discomfort wearing information’s clothes. Most people can’t tell those two apart in the moment. That’s what the delay is for.

The Discomfort Was Information

Sit with a problem long enough and something changes. The urgency it created in the first hour rarely survives to the next morning. What’s left over, after the panic burns off, is usually a much smaller and clearer question than the one that felt so unbearable to leave open. That’s not a coincidence. The discomfort was never a separate obstacle standing between you and the answer. It was part of the answer, if you’d let it finish speaking before you spoke over it.