Directory · R
New here? Start with the premise →
Resistance
2 min read · 471 words
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.