Fear as information: how to tell a real warning from noise

By Chadi Nassar · May 7, 2026 · 5 min read

The test is one sentence long: write the fear down concretely. If it names a specific, real, external consequence, it's signal — slow down. If it dissolves into vague what-ifs, it's static — acknowledge it and act anyway. Most of the fear that keeps people stuck is static. But not all of it, and the skill worth building is the honesty to tell which one you're holding.

Fear is information, not instruction

A gazelle freezes when a predator appears at the edge of the grass — correct response, competent wiring. You freeze in front of a blank email to someone you want to pitch — same mechanism, wrong century. Your threat-detection system doesn't distinguish well between physical and social danger; the prospect of humiliation activates many of the same pathways as the prospect of injury. So the alarm fires at anything unfamiliar and exposed, and it fires before conscious evaluation — that speed is the tell. A genuine analysis takes a moment and produces a mixed result. The instant, full-body "I'd rather not" arrives in under a second, which means it's a reflex, not a judgment.

None of this makes fear the enemy. Fear tells you something is at stake — the thing that scares you usually scares you because it matters. Information says: this matters, pay attention. Instruction says: stop. Only one of those is reliably true.

The signal-or-static test

Signal-fear survives being written down. "If I sign this lease, I can't undo it." "If I quit now, I can't make rent in three months." "If I do this, that specific person gets hurt." It points at a real feature of the situation, stays as solid on the page as it felt in your chest, and deserves your attention — run the decision through the Three Filters before moving.

Static-fear evaporates when you ask it for details. "What if it goes wrong?" "What if I look stupid?" "What if I'm not ready?" None of those name anything specific, because there's nothing specific to name — only the discomfort of doing something new, dressed up as analysis. Static doesn't earn a veto. It earns a nod of acknowledgment — yes, I'm nervous; yes, this matters — and then the first small move anyway.

Don't wait for the fear to pass

It won't, not on a timescale that helps you. The calm, ready feeling people wait for is largely a consequence of acting, not a precondition (here's the research on why). What changes with practice isn't the alarm — it's your relationship to it. Each time the alarm fires, you act on something small, and the predicted catastrophe fails to arrive, you bank a data point: the alarm is a reflex, not a verdict. Enough data points and the fear stops setting your agenda. It still visits. It just doesn't get a vote it didn't earn.

✱ From the book

This essay is adapted from F*ck It, Do It by Chadi Nassar, including the chapter on when NOT to act. Read the first chapter free.

FAQ

How do I know if my fear is rational?
Write it in one concrete sentence. Names a real external consequence → signal. Dissolves into what-ifs → static.

Should I wait until I'm not afraid?
No — the calm arrives after the move. Act with the fear present once you've checked it isn't signal.

Why does my brain treat an email like danger?
The threat system doesn't separate social from physical risk; it fires at the unfamiliar. Competent wiring, wrong context.

Chadi Nassar is the author of F*ck It, Do It. Lebanese, educated in Canada, based in Dubai. fidi.today