The session wasn't supposed to be about resistance.
I came in with something else on my mind — a pattern I'd been noticing, a piece of friction I wanted to work through. But somewhere in the first twenty minutes, the conversation shifted. The therapist asked me to talk to the part of myself that digs in. The part that shuts down when asked to do something it doesn't want to do. The part I'd spent years treating as the obstacle.
I didn't expect to find anything there worth listening to.
What came up surprised me.
What You've Been Calling It
If you've typed "AuDHD resistance" into a search engine, you already know the language. Resistance to tasks. Resistance to transitions. Resistance to being told what to do. The gap between what you intended to do and what you can actually make yourself do. The thing that looks like laziness from the outside and feels like something else entirely from the inside.
You've had words for it. Lazy. Avoidant. Stubborn. Unmotivated. Not caring about things you genuinely care about.
If the diagnosis came late, you probably used those words for years. Maybe decades. And even after you had a better framework, the resistance didn't stop. It just meant you had a new layer of confusion on top of it: I understand this now. Why is it still happening?
What the Search Results Say — and What They Miss
The most common explanation online frames AuDHD resistance as a neurological conflict. Autism needs predictability and sameness; ADHD needs novelty and stimulation. The two sets of requirements pull in opposite directions on the same nervous system. Resistance is what happens when neither gets what it needs.
That explanation is real. If you have both conditions, your nervous system genuinely is running competing requirements simultaneously. The routine that helps the autistic side settle can bore the ADHD side into a flat, disengaged state. The novelty that re-engages the ADHD side can put the autistic side on alert. There is no position that satisfies both at once, and that produces a kind of stuck that willpower doesn't resolve.
But this frame — two neurological needs in conflict — describes the mechanism. It doesn't describe the meaning.
It tells you what is happening in the system. It doesn't tell you why a particular part of you learned to dig in at a particular kind of ask. Or what it learned from. Or what it's been doing, all this time, while you've been trying to push through it.
The Guard That Learned
What I found, in that session, wasn't a system in conflict. It was something that had made a decision.
Not a conscious one. Not something I'd chosen. But a decision nonetheless: that moving forward in certain conditions meant exposure. That effort without accommodation just meant effort lost. That asking meant being misread. That trying in the way that made sense to me produced results that didn't land the way I'd intended, over and over, and the feedback loop was rarely kind.
You brought your real pace to something and were told you were slow. You communicated in the way that made sense to you and it landed wrong. You explained what you needed and it was interpreted as making excuses. You put visible effort into something that looked, from the outside, like nothing — and the conclusion drawn was that you hadn't tried.
After enough of that, something learns.
It learns that certain kinds of moving forward mean a particular kind of cost. That asking in certain formats means being misread. That effort without the right conditions isn't neutral — it's deficit-building. And it builds a guard.
That guard is the resistance. It doesn't announce itself as protection. It shows up as stuck. As avoidance. As the thing you can't make yourself do, even when you want to.
What's underneath it isn't malfunction. It's a system that received consistent feedback — not from deficiency, but from experience — that the current format wasn't safe to move in.
The resistance was the correct response to that feedback. The problem is that it generalised. It kept running even when the conditions changed. It applies the same caution to situations that don't warrant it, because it's working from pattern, not from current evidence.
This is different from a neurological conflict between two sets of requirements. It's older. More specific. And it responds differently.
Pushing Through It Doesn't Reach It
Most of the advice about resistance — productivity advice, executive function advice, the well-meaning coaching kind — assumes the problem is either motivation or method. You don't want it enough. Or you haven't broken it down into small enough steps. Or you need an accountability structure, a timer, a different environment.
Some of that helps, sometimes. But it's working at the level of the task, not the level of the guard.
You can push through resistance and get the thing done. People do it all the time. But the resistance doesn't go anywhere when you push through it. It's still there the next time. And the time after that. And what often happens, across years of pushing through, is that the guard gets more entrenched, not less — because the message it keeps receiving is that its concerns aren't worth attending to.
Getting curious about what the resistance is actually protecting is the only thing I've found that moves something underneath the surface.
Not fixing it. Not arguing it down. Getting curious about it.
Different Parts, Different Requirements
What changed in that session was applying inward the same logic I'd been applying outward for years.
We're reasonably good — most of us — at accepting that different people have different requirements. You factor in how someone processes. What their threshold is. What kind of environment they need to function well. If someone shuts down under too many options, you limit the options. If someone needs time before they respond, you build that in. You stop expecting everyone to work the same way.
The harder thing — the thing that took much longer for me — is that different parts of myself have different requirements. And they're not all asking for the same thing.
The part of me that handles crisis well is not the same part that needs to process something slowly before it can respond. The part that engages under pressure is not the same part that shuts down under ambiguity. The part that's good under clear constraints is exhausted by open-ended social situations, and what it needs to recover from that is completely different from what the other parts need.
These aren't contradictions. They're different systems with different requirements, running on the same processor.
The resistant part — when I actually asked it what it needed, directly, in that session — had a very specific answer. Space. Not persuasion. Not a better argument or more information or a clearer plan. Five minutes where nothing was being demanded. Where it wasn't being asked to choose or perform or produce while it was still sorting through what was actually going on.
That was the whole request.
I'd been trying to override it, argue it down, shame it into compliance for years. It had a one-sentence ask that I'd never thought to ask about.
What This Doesn't Resolve
I'm not going to tell you that naming this fixes it. It doesn't.
The guard still shows up. The wall still appears between intention and action. Understanding what the resistance is protecting doesn't make it drop automatically — because it's not a cognitive process. It learned through experience, and it changes through experience, not through being informed that it's no longer necessary.
What changes is the conversation.
Instead of treating resistance as something to defeat, you start asking what it's protecting you from. Whether the format is the problem. Whether what you're trying to do in the way you're trying to do it is something this part of you has experience-based reasons to distrust. Whether the timing is wrong, or the shape of the ask, or the conditions around it.
Sometimes the answer to those questions is practical: yes, the format is wrong. The demand doesn't fit what's available right now. Change the format, and the resistance shifts.
Sometimes the answer is older. A protection that was genuinely necessary at one point and is still running on pattern, in situations where the threat that built it no longer applies. That's slower work. It doesn't resolve in a session.
Most of the time I'm still working out which is which. It's not usually obvious in the moment.
What I've stopped doing is calling it laziness.
That was never the explanation. It was just the word that was available when I didn't have a better one — and it did the work that wrong explanations do: it made the thing harder to look at clearly, and harder to actually address.
The resistance had reasons. It still does. The question is whether those reasons apply to what's in front of you right now — or whether they belong to something older that hasn't been updated yet.
Where to Go From Here
Resistance and masking come from the same place — a system that learned, from experience, what wasn't safe to do openly. If this landed, the fuller picture of that adaptation is here: What Is Masking? A Guide for Late-Diagnosed AuDHD Men
And if you're wondering whether this is part of a wider pattern rather than an isolated thing: Signs of Autism in Men Over 40 That Nobody Named — the specific moments, not a checklist.