What 'letting go' promises — and where resistance to change actually lives
For decades, "letting go" has been the universal answer in spiritual and personal-development circles. You are stuck — let go. You are anxious — let go. You are clinging to an old identity — let go. The phrase is short, soft, and seems to point at something real. Most people who hear it nod.
But here is what I have come to notice. "Letting go" rarely lets go of anything. It performs the gesture. It moves you through a recognizable motion. And then the resistance to change — the actual structural thing that was keeping you stuck — is still there, untouched, often stronger for the gesture aimed at it.
The "letting go" framing places the resistance in your hands, as if it were an object you could drop. The image is wrong. The resistance is not in your hands. It is in the architecture of how you have been organizing your life — and architectures do not drop when you open your palms.
The gesture that releases nothing — and looks like everything
I have watched myself perform "letting go" many times. I have watched many people I respect perform it. The gesture has a particular look — a softening of the voice, a breath out, sometimes a slight downward turning of the head. The body cooperates. The room cooperates. Whoever is watching nods.
Nothing has been released. The structural thing — the trajectory, the achievement engine, the identity that was being maintained — continues running underneath the gesture. The gesture and the structure operate on different layers and do not communicate.
This is not a critique of the people who do this. It is mostly what I do too, when I try to "let go." The gesture is genuine. The release is not. The gap between them is the actual subject of this article.
What I have been slowly learning is that the gesture is often the thing that prevents the release. As long as I am performing "letting go," I am not noticing what is actually holding on.
What actually survives the 'letting go'
When the gesture is done — the breath out, the soft voice — what remains is the same set of structural forces that were present before. Specifically: the resistance.
The resistance survives because the gesture was not aimed at it. The gesture was aimed at the feeling of being stuck, not at the architecture of being stuck. Feelings can be moved temporarily. Architectures cannot. After a few hours, sometimes a few minutes, the original feeling returns. The conclusion most people draw at this point is: I did not let go enough. I need to do it again, harder.
This is the wrong conclusion. The repetition will not work either. The resistance is structural, and structural things do not soften through repeated emotional gestures aimed at feelings rather than at the underlying structure.
What survives the "letting go" is what was actually doing the work of keeping you in place. Naming it is the first thing that changes anything.
The function the resistance has — and how I came to notice it
For a long time I treated my own resistance the way most people treat theirs — as a problem to defeat. I thought of it as the obstacle between me and the next version of my life. The framing was: I am here, I want to be there, and resistance is in the way.
Then I noticed something. The resistance was almost never random. It activated in specific patterns, around specific kinds of moves, with specific kinds of intelligence about what was being asked of me. It was not noise. It was protecting something. It had a function.
What I have noticed in my own resistance, and in the resistance of people I trust, is this: the resistance keeps the asker honest about what they are actually asking. It refuses moves that would cost something not yet acknowledged. It is, in a strange way, on your side — just not on the side you think you are on.
What I notice the resistance is protecting — and what protecting it has cost me
When I started watching the resistance instead of fighting it, I began to see what it was protecting. The list, for me, was uncomfortable to write. The resistance was protecting:
- the version of myself that had figured out how to be liked
- the trajectory my older work was still riding
- the income stream that depended on me staying recognizable
- the relationships built around the person I was, not the person I was becoming
These are not embarrassing things to want to protect. They are the things most people are quietly protecting. The resistance is doing its job by refusing the moves that would compromise them.
What protecting them has cost me is harder to name. Years of small dishonesty, mostly. Pieces of work I did not write because they would have moved me past where I was supposed to be. Conversations I did not start because the relationships could not absorb them. The resistance is not free, even when it is working as designed.
Reading Steven Pressfield's "The War of Art" now — what it named clearly, what I see differently
Steven Pressfield's The War of Art was the first place I read someone treating Resistance — capitalized, deliberate — as a real force rather than a personal failing. He named it as a structural enemy of any creative or spiritual project. The book gave me a vocabulary I am still using.
What he names clearly: the universality of Resistance, its preference for the most important work, the way it disguises itself as practical reasoning. These observations have not been bettered.
Where I have come to see it differently: Pressfield treats Resistance as something to be defeated, every day, by sitting down and doing the work. That works some of the time. But it can also become a war that itself keeps the Resistance in place — a counterforce that confirms the very thing it is fighting.
What I now think Resistance is asking is not for defeat. It is asking for genuine examination of what would be lost if it stopped resisting. Pressfield's frame stops short of this examination — by design, I think, given what his book was for.
What inner resistance looks like for those whose success has stopped working
For people whose success has stopped delivering — the segment I have been describing across recent posts — inner resistance has a specific shape. It is not the obvious resistance of avoidance or procrastination. The person at this stage is, by definition, capable of sustained work. They have proven that capacity many times.
The resistance shows up differently. It shows up as the inability to take seriously the recognition that:
- has arrived
- the trajectory was wrong
- more of what worked will not work now
- the question is the trajectory itself, not the next move along it
The resistance to that recognition is harder to see because it does not look like resistance. It looks like: another launch, another commitment, another reorganization of priorities. The activity continues. The trajectory question does not get faced. The resistance is doing its work, beautifully, under the cover of productive motion.
Why fighting the resistance is what keeps it alive
There is a structural feedback loop with resistance that took me years to see. When you fight it directly — using will, discipline, "doing the work" — you confirm to it that what it is protecting is worth protecting. Resistance is, among other things, a measurement of how much you have invested in keeping a position. The harder you fight it, the more its sensors register that you are still committed to the underlying structure.
The fight becomes the proof.
This is why people can spend decades disciplining themselves against their own resistance and find that the resistance has not weakened — it has, if anything, become more sophisticated, more pre-emptive, more skilled at activating before the conscious mind notices the move that would have triggered it.
The fight does not weaken the resistance because the fight is what tells the resistance the position is still worth defending. The resistance is not a wall to push through. It is more like a thermostat — measuring how much pressure is being applied, and matching it.
What I notice when the resistance softens on its own
What I have noticed, on the days the resistance has softened, is that I was not trying. I had stopped pushing. Sometimes I had given up — quietly, without ceremony, without "letting go." The position the resistance was protecting had become, somewhere underneath, no longer mine. And without my noticing, the resistance had relaxed.
The softening is never a victory. It does not feel like one. It feels more like the slow disappearance of a friction I had stopped being aware of. The resistance does not announce its departure. I notice, much later, that I have been moving through something I used to push against.
What is happening on those days is honest examination of what is being protected, without trying to defeat the protection — though I cannot tell whether the examination causes the softening, or whether both arise from something I haven't named yet. I have written about this position elsewhere — what it means to teach from inside the question rather than from past it.
(And I notice — as I write this — that "naming the softening" can itself become the next thing the resistance protects against being seen. There is no escape from this layer. Only the slow getting-used-to-it.)