Directory · R
Not sure this is the right entry? Run the check · New here? Start with the premise
Resistance
2 min read · 471 words
Resistance isn't evidence the change is wrong. Your system preferred the old pattern before you tried to change it and goes on preferring it during — so expecting the new thing to feel right is backwards.
Is this you?
Check whatever lands. Nothing is sent anywhere.
Resistance is the system’s pushback against change, demand, or input that conflicts with current configuration.
The hardware is biased toward maintaining current state. Energy goes into running the operations that have been working; less energy is required when the system runs default than when it runs new patterns. Resistance is the felt friction when the operator attempts to introduce change against this default. The new behavior, the difficult conversation, the challenging input — each meets resistance from the system that would prefer to continue running what it has been running.
The mechanism is partly protective. Some resistance signals legitimate caution: the change being attempted is too fast, too large, or too unsupported by current resources. The resistance is data the operator should consider. Some changes warrant slower introduction, more support, or different timing than the operator initially planned.
But much resistance is not legitimate caution. It is the system’s preference for the familiar overriding the operator’s deliberate choice to do something different. The familiar pattern that produces dysfunction continues to fire because firing is what it has been doing. The new pattern, even when clearly better, meets resistance because it is new. The Inertia entry’s territory. The operator who interprets all resistance as legitimate caution will rarely produce change, because most attempts at change will meet resistance and most will be abandoned.
From the chair: when resistance arises against attempted change, distinguish the source. Is the resistance reporting legitimate constraint — the change is genuinely too fast, the resources are inadequate, the timing is wrong — or is it the system’s preference for the familiar. The first warrants adjustment of the change attempt. The second warrants moving forward despite the resistance.
The operational discipline: resistance is not evidence the change is wrong. The system preferred the previous pattern; that preference was being expressed before the change was attempted, and continues to be expressed during the attempt. The expectation that the change will feel right or natural is structurally incorrect for changes that genuinely break with previous patterns. The change that is encoded as default did not start that way; it became default through repeated running despite the initial resistance.
The other application: in others. The other operator who is resisting input the operator is providing may be receiving legitimate cause for caution, or may be running their system’s preference for the familiar against information that warrants updating. The same diagnostic applies. Pushing harder against legitimate caution produces breakdown. Backing off from the system-preference resistance leaves the situation as it was. The operator who can read which is current is more effective in providing input that lands.
Resistance is not always wrong. It is also not always right. The work is to read what it is reporting and respond accordingly.
Two sources, and only one is information
Running an established pattern is cheap; building a new one costs. Your system is biased towards maintaining its current state, so when you introduce something different you feel friction — and that friction is present whether the change is excellent or terrible, because it's generated by novelty rather than by quality.
Some of it is legitimate caution. The change may genuinely be too fast, too large, or unsupported by your current resources. That resistance is data and warrants adjusting the attempt — slower, smaller, better supported, different timing.
Most of it isn't. It's a preference for the familiar overriding a deliberate choice, and it fires hardest precisely for the patterns that are doing damage, because those are the most thoroughly grooved. Which creates a trap: someone who treats all resistance as legitimate caution will almost never change anything, since nearly every attempt produces some.
The discipline follows from that. Expecting a genuine break with a previous pattern to feel right or natural is structurally incorrect. Everything that's now your default began as something that met resistance and got run anyway, repeatedly, until it stopped costing. The feeling of wrongness is not a verdict — it's the price.
Sort the resistance before you obey it
Four questions. They separate the caution worth taking from the preference that will cost you the change.
Real questions
Does resistance mean I'm doing the wrong thing?
Usually not, and treating it that way is how most change gets abandoned. The friction is generated by novelty rather than by quality — your system preferred the old pattern before you attempted anything and keeps preferring it throughout. So resistance shows up for excellent changes and bad ones alike, which makes it useless as a verdict and useful only once you've sorted which kind it is.
How do I tell useful resistance from just not wanting to?
Ask whether you can name a concrete missing resource — time, money, skill, support, recovery — and whether the resistance would ease if the change were smaller or slower. Legitimate caution responds to scale and points at something specific. Preference for the familiar doesn't shrink when the change does, and tends to produce reasons rather than requirements. If the reasons keep changing while the conclusion stays the same, that's the second kind.
Why does the right change feel so wrong?
Because familiarity and correctness are different readings, and your system only produces the first one. Anything that genuinely breaks with a previous pattern will feel unnatural, by definition, until it's been run enough times to become the new default. Every default you currently have started this way. Expecting the new thing to feel right from the start is asking for a signal that can only arrive after the work, not before it.
Why do I quit at the same point every time?
Because the early repetitions are the most expensive and there's no visible progress yet to offset them — so the cost is at its highest exactly where the evidence is at its thinnest. That's a structural trap rather than a character pattern. What helps is knowing the shape in advance and recording how the friction changes per repetition, so you have something to weigh against the feeling when it argues for stopping.
Why do I resist things I actually want?
Because wanting the outcome and preferring the current pattern are separate processes, and they can run simultaneously without contradiction. You can genuinely want the result while your system objects to the construction work required to get there. It isn't self-sabotage and it isn't ambivalence about the goal — it's the energy cost of displacement being felt directly, and it shows up most strongly for the things you care about because those involve the biggest changes.
Should I push through resistance or back off?
Sort it first, because the answer differs. If a resource is genuinely missing or the change is too large to sustain, back off and adjust — that resistance is doing its job. If it's a preference for the familiar, proceed at whatever size you can manage today, because waiting for it to lift means waiting indefinitely. The error to avoid is deciding by how strongly it's firing, since the preference version often fires hardest.