Directory · A
Not sure this is the right entry? Run the check · New here? Start with the premise
Avoidance
2 min read · 445 words
Avoidance is your system routing around something it has flagged as dangerous. It works instantly, which is the problem — the relief is immediate and the bill arrives later, larger.
Is this you?
Check whatever lands. Nothing is sent anywhere.
The machinery has a protocol for threats it cannot fight: route around them.
This was a functional solution. The organism that couldn’t outrun the predator survived by not encountering the predator. The wiring that produces avoidance is the flight response applied to everything the system has classified as dangerous — not just physical threats but emotional ones, social ones, informational ones. Conversations that might produce conflict. Tasks that might reveal inadequacy. Feelings that might overwhelm. The system routes around them all using the same mechanism: don’t go there.
The efficiency of avoidance is its danger. It works immediately. The threat is not encountered. The discomfort doesn’t arrive. The short-term signal says: safe. The long-term cost — that the avoided thing still exists and often grows — doesn’t register on the same timeline the machinery operates on.
The avoidance circuit runs below conscious choice. The one at the controls often doesn’t notice the rerouting — it presents as a reasonable decision. I’ll handle that later. This isn’t the right time. I don’t want to make things worse. Each explanation is plausible. Each is also the avoidance protocol producing a narrative that justifies the rerouting. The system is sophisticated enough to make avoidance look like wisdom.
To identify avoidance running: look for the pattern, not the individual instance. A single deferred conversation is scheduling. The same conversation deferred six times is avoidance. A single skipped task is prioritization. The same task migrating from list to list without execution is the system routing around something the hardware has classified as threat.
The diagnostic question: what would happen if this were done right now? Not later. Now. If the answer produces a physical response — chest tightening, stomach dropping, the urge to look away — the avoidance system is reporting. The thing being avoided carries a signal the hardware doesn’t want to receive.
The signal is not reduced by avoidance. It accumulates. The conversation not had becomes harder to have. The task not done grows in the system’s threat assessment. The feeling not processed builds pressure. Avoidance trades present discomfort for compound interest on future discomfort. The exchange rate is never favorable.
What the one in the chair can do is notice the rerouting as it happens — catch the plausible narrative, check the physical response, and make a conscious decision about whether to follow the avoidance protocol or override it. Not every override is necessary. Some things genuinely aren’t urgent. But knowing the difference between this can wait and the system is routing around something it’s afraid of is the operating distinction.
Why it disguises itself as good judgement
The circuit runs below conscious choice, which means you rarely experience it as avoiding. You experience it as deciding. I'll handle that later. This isn't the right moment. I don't want to make things worse. Each of those is plausible, and each is the protocol generating a narrative to justify the reroute. The system is sophisticated enough to make avoidance look like wisdom, and it is very good at it.
So the individual instance tells you nothing — you can't catch this by examining a single decision, because each decision is defensible. The pattern is the evidence. One deferred conversation is scheduling. The same conversation deferred six times is a reroute. One skipped task is prioritising. The same task moving between lists without ever executing is something else.
There's a fast physical test. Ask what would happen if you did it right now — not later, now. If the answer produces something in the body — chest tightening, stomach dropping, the urge to look away — that's the system reporting. The thing you're routing around carries a signal it doesn't want to receive.
And the signal doesn't decay while you're away from it. It accumulates. The conversation not had gets harder to have. The task not done rises in threat rating. The feeling not processed builds pressure. Avoidance trades present discomfort for compound interest on future discomfort, and the exchange rate is never favourable.
The right-now test
Two minutes. It distinguishes genuine prioritising from rerouting, which is the only distinction that matters here.
Real questions
How do I know if I'm avoiding something or just prioritising?
Look at the pattern and the body, not at the reasoning — the reasoning will be sound either way, because the system produces a plausible justification each time. A single deferral is scheduling; the same thing deferred six times is a reroute. And ask what happens if you do it in the next ten minutes: genuine prioritising produces a thought about sequencing, avoidance produces something physical. The tightening chest is the reliable instrument here. The explanation isn't.
Why does avoiding something make it harder, not easier?
Because the relief teaches the wrong lesson. Each time you route around it and feel better, your system logs that the thing was dangerous and that avoiding it worked — so the threat rating goes up rather than down. Nothing about the task or conversation itself has changed; your assessment of it has inflated. That's why a conversation postponed for two months is genuinely harder to have than it was in week one, and why the only thing that revises the rating down is approaching it.
Why am I avoiding something that isn't even difficult?
Because the rating isn't based on difficulty, it's based on what the thing might produce. An email that takes ninety seconds can carry the possibility of being told no, or of discovering you got something wrong, and the system is routing around the signal rather than the labour. This is why trivial tasks can sit for months while hard ones get done: the hard ones didn't carry anything your system didn't want to receive, and the trivial one does.
Is avoidance the same as procrastination?
Procrastination is one of the forms it takes, but avoidance is broader — it covers conversations, feelings, information, situations, not only tasks. The overlap is the mechanism: something gets flagged, the system reroutes, and the explanation arrives afterwards. The useful difference in practice is where you look for the cause. With a task you can often fix it by making the first step clearer. With an avoided feeling or conversation, clarity isn't the obstacle and the same approach does nothing.
How do I stop avoiding a difficult conversation?
Make the next step smaller than the conversation and harder to reverse. Don't try to have it — send the message asking for a time. That single move transfers it out of your control, which is what defeats the reroute, because the protocol works by leaving the decision with you indefinitely. Also worth naming the specific thing you don't want to receive, in advance. Most avoided conversations are protecting against one identifiable outcome, and it's almost always smaller once written down than while it was unnamed.
Is avoiding things sometimes the right call?
Yes, and treating every reroute as cowardice is its own error. Some things genuinely aren't urgent, some conversations are genuinely better had later, and some situations are correctly avoided altogether. The operating distinction isn't between avoiding and not avoiding — it's between this can wait and my system is routing around something it's afraid of, decided consciously rather than by default. Deciding to defer is legitimate. Discovering you've deferred six times is not a decision.