How do I apply the idea that the system resists change?

The most direct way to practice is through a focused exercise: 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.

Common pitfall: Treating resistance as opposition to be overcome rather than information to be understood. Resistance to system change is usually rational — the resisters are responding to real incentives, real identity threats, or real concerns about the change's viability. The failure mode is labeling all resistance as 'resistance to change' and attempting to power through it, ignoring the legitimate information the resistance carries. Sometimes resistance reveals a genuine flaw in the proposed change. Sometimes it reveals a system element the change agent missed. Effective change leaders treat resistance as diagnostic data: 'What does this resistance tell me about the system that I did not already know?'

This practice connects to Phase 84 (Systemic Change) — building it as a repeatable habit compounds over time.