When Resistance Isn’t the Problem
What Resistance Reveals About the System You Built
There is a particular kind of resistance that almost no one names.
It does not look rebellious. It does not show up as open disagreement. No one refuses outright. No one makes speeches in the hallway.
It looks like compliance.
The new standard is announced. The team nods. The process is technically followed. The boxes are checked. And yet the outcome does not improve.
At that point, the diagnosis usually lands on effort. People are cutting corners. People are not taking it seriously. People need to be reminded why this matters.
But often what you are seeing is not defiance. It is a signal that the system is misaligned with reality.
Behavioral science has long demonstrated that behavior is a function of environmental conditions, not simply intention. Kurt Lewin’s early formulation argued that behavior emerges from the interaction between the person and their environment.
In organizational settings, this means that repeated patterns of behavior usually point to structural conditions, not isolated attitude problems.
Imagine a team shipping risky code into production. The root cause appears obvious. Pull requests are being approved too quickly. Reviewers are not catching defects. It is tempting to conclude that the engineers are careless or disengaged.
Then you look closer.
Some pull requests contain twenty thousand lines of code. The expectation is that a peer will read from top to bottom and root out all the context before approving. In theory, this is a safeguard. In practice, no one can meaningfully analyze that volume of change inside the time constraints of a normal workday. So reviewers scan briefly and approve. They comply with the rule while adapting to the pressure.
That adaptation is a form of resistance.
Not loud resistance. Not ideological resistance. Structural resistance.
Herbert Simon described this dynamic decades ago when he introduced the concept of bounded rationality. People make decisions that are rational within the limits of the information, time, and cognitive capacity available to them.
Under those constraints, a cursory review is not irrational. It is the best available option in a poorly designed process.
When you interpret that behavior as laziness, you add pressure. You remind people of standards. You reiterate expectations.
When you interpret it as information, you ask a different question.
What in the process is making this the sensible choice?
This is consistent with decades of quality and systems thinking. Deming argued that most performance problems are attributable to the system, not the individual. Variation, error, and drift are usually downstream of process design.
In the example above, the friction is not motivation. It is visibility and scale. Reviewers cannot quickly distinguish high risk changes from low risk ones. Everything arrives as an undifferentiated block of code. The cognitive load is unreasonable. Cognitive Load Theory reinforces this point. When task demands exceed processing capacity, performance degrades predictably.
Once that friction is named, the solution shifts. Pull requests are redesigned to include structured commit notations that highlight risk areas. Large changes are broken into smaller, reviewable units. The system begins to support the behavior it claims to value.
Without lectures about diligence, review quality improves. Not because people suddenly care more, but because the process now makes care possible.
This is the move most organizations skip.
They see a gap between desired behavior and observed behavior and treat the gap as a people problem. In reality, the gap is often a systems problem in disguise.
Resistance, especially the quiet kind, is an early warning signal that the current structure is producing tradeoffs you did not intend. People are making rational adjustments inside constraints. They are optimizing locally in order to keep the work moving.
If you want different choices, you have to change the shape of those constraints.
That requires humility. It requires assuming that competent people are doing the best they can with the resources, clarity, and time available to them. It requires looking at the environment before you look at character.
When resistance shows up, it is rarely the root problem.
It is the problem report.
In the Green Path, we use resistance as data. We are opening seats for a Spring Masterclass, and would love to have you join us to see how we understand the reality of the system and create nudges to shift behaviors.
