Drift Is a Greater Threat Than Resistance

Most change programmes prepare for resistance. They anticipate pushback. They build engagement plans. They appoint change champions and invest in communication. They treat opposition as the primary threat to successful adoption. This preparation is not wrong. But it addresses the wrong risk. In most organisations, drift is a more significant threat than resistance.¹ And unlike resistance, drift rarely triggers a response.²

What drift actually is

Drift is not opposition. It is not visible conflict or deliberate non-compliance. Drift is the gradual divergence between what the change intended and what the organisation is actually doing³ — a divergence that unfolds quietly, without announcement, and often without anyone deciding that it should happen.

It shows up as small accommodations that become habits. Workarounds that solve immediate problems and then become standard practice. Informal interpretations of new processes that vary by team, by manager, by site. Behaviours that looked like adoption six months ago and now look like something else. Drift does not require bad intentions. It requires only that people adapt to the pressures in front of them, rather than to the design intent behind them.

Why drift is harder to manage than resistance

Resistance has the advantage of visibility. When people resist change, the problem is legible. Leaders can identify it, engage with it, and respond to it. The organisation knows where the tension is.

Drift is different. Because it happens gradually and without overt conflict, it does not produce clear signals. Each small adaptation is individually defensible. The workaround makes sense in context. The local interpretation is reasonable given the constraints. The deviation from design intent is minor enough to absorb.

By the time drift becomes visible as a pattern, it has typically been underway for months. The behaviours are settled. The informal rules are established. The organisation has adapted around the intended design — and often cannot remember doing so.

How drift compounds

Drift is not self-correcting. It tends to compound.

As informal accommodations spread, they create social proof. If one team is working around the new process, adjacent teams adopt the same approach. If managers are tolerating deviation in one area, that tolerance is interpreted as signal that deviation is acceptable more broadly.

What begins as isolated adaptation becomes organisational norm. The gap between design intent and operational reality widens — not through any single decision, but through accumulated drift that no one authorised and no one is responsible for addressing. By the time governance registers the gap, closing it requires far more than the adjustment that would have been sufficient three months earlier.

Why governance structures miss drift

Governance structures are designed to detect deviation. They track milestones, measure adoption rates, and report on implementation progress. They compare actuals to plan.

Drift evades these mechanisms precisely because it happens within the boundaries of apparent compliance. Teams complete the required activities. Adoption numbers look adequate. Milestones are met. The deviation is not in whether things are being done, but in how they are being done — and whether how they are being done bears any resemblance to what was intended.

Dashboards rarely surface this distinction. Activity is measurable. Fidelity is not.

What leaders mistake drift for

When drift surfaces in governance reporting, it is frequently misidentified. Leaders see inconsistency across teams and describe it as a training gap. They see workarounds proliferating and call it a communication problem. They see performance falling short of projections and attribute it to market conditions or implementation quality. Each of these explanations may contain partial truth. None of them names drift as the mechanism. The result is that interventions address symptoms while the structural divergence continues to widen underneath.

The relationship between drift and resistance

Drift and resistance are often confused, but they are different problems that require different responses.

Resistance is active. It is people pushing back against change because they disagree with it, distrust it, or find it threatening. The response is engagement, dialogue, and often redesign.

Drift is passive. It is people adapting to change in ways that diverge from intent — not because they oppose it, but because the conditions in which they are working make the intended behaviour difficult to sustain. The response is structural: examining what is producing the divergence and adjusting the design, incentives, or support conditions that are allowing it to compound.

Treating drift as resistance produces the wrong intervention. More communication, more engagement, and more advocacy do not close a structural gap. They address a different problem.

Catching drift early

Drift is detectable before it becomes structural — but only if leaders are looking for the right signals.

The indicators are behavioural rather than metric. They include teams describing their processes in ways that no longer match the intended design. Managers informally sanctioning deviations they were not authorised to allow. Frontline staff explaining why the official process does not quite fit their context. Workarounds being shared across teams as helpful tips. These signals do not appear in dashboards. They appear in conversations, observations, and the gap between what formal reporting describes and what operational reality looks like. Leaders who catch drift early are not better resourced. They are paying attention to different things.

What drift tells you

Drift is diagnostic information. When an organisation drifts from a change design, it is usually because something in the design does not fit operational conditions as well as it was intended to. Incentives are misaligned. Processes are more complex than they appeared. Capacity is lower than the plan assumed.

Drift is the organisation’s way of solving problems that the design did not anticipate. The workarounds are not obstacles. They are evidence. Reading drift as diagnostic information rather than as compliance failure leads to better interventions: adjusting design, realigning incentives, and addressing structural conditions rather than escalating enforcement.

A different question for leaders

Instead of asking “Where is adoption below target?” leaders would be better served asking:

Where is the organisation adapting in ways we did not design for?

That question leads somewhere more useful. It treats divergence as signal rather than failure. It opens the door to structural diagnosis rather than communications campaigns.

Resistance is the risk organisations prepare for. Drift is the risk that actually compounds. The organisations that manage change well are those that learn to see both. This is one way of thinking about why change succeeds or fails. Other pieces go deeper into how organisations can detect drift earlier and distinguish it from the resistance they were expecting.