What does it mean that the system resists change?

Homeostatic forces in any system push back against change — expect and plan for resistance. Systems develop self-preserving mechanisms that maintain the current state regardless of whether that state serves the organization well. These mechanisms are not conspiracies — they are structural properties of complex systems. Balancing feedback loops, sunk cost commitments, identity attachments, and network effects all create inertia that opposes change. The change agent who does not anticipate and plan for systemic resistance will be defeated by it — not because the change was wrong but because the system was not prepared to receive it.

Example: A government agency, the Bureau of Digital Services, attempted to replace its paper-based permit process with an online system. The technology was ready. The user interface was tested and validated. The funding was secured. The project failed — twice — before succeeding on the third attempt. The first attempt failed because the clerks who processed paper permits had built their professional identity around expertise in the paper system — they experienced the digital system as a threat to their value, not a tool to enhance it. They found legitimate reasons to maintain parallel paper processes 'just in case,' which doubled the workload and made the digital system appear to cause more problems than it solved. The second attempt failed because the supervisors' performance metrics were based on paper permit throughput — the digital system changed the workflow in ways that made their existing metrics meaningless, so they advocated for reverting to the known system where their performance was measurable. The third attempt succeeded because it addressed the systemic resistance directly: clerks were retrained as digital process specialists (preserving their identity as experts), supervisors' metrics were redesigned for digital workflows (aligning incentives), and the paper process was scheduled for retirement on a fixed date (eliminating the parallel-process escape valve). The technology did not change between the three attempts. The system readiness did.

Try this: For a change you are planning or currently implementing, map the resistance forces using a force field analysis. Draw a vertical line representing the current state. On the left, list the driving forces — the pressures pushing toward the desired change (market demands, leadership commitment, cost pressures, competitive threats). On the right, list the restraining forces — the pressures pushing against the change (identity threats, incentive misalignment, skill gaps, process dependencies, political interests). Rate each force from 1 (weak) to 5 (strong). The change will succeed only if the driving forces exceed the restraining forces. The most effective strategy is usually to reduce restraining forces rather than increase driving forces — because increasing driving forces often triggers proportional increases in restraining forces.