THE DRIFT PROBLEM: HOW GOOD TEAMS SLOWLY STOP BEING GOOD

The strangest thing about organizational drift is that it feels like nothing.

There's no event. No decision. No morning where someone announces that standards are being lowered and performance expectations are being revised. Nobody votes on it. Nobody agrees to it. It just happens — incrementally, almost invisibly — until one day someone looks up and the operation that used to run well no longer does, and nobody can quite explain when the change occurred.

I've watched it happen in maintenance organizations, in engineering teams, in entire manufacturing plants. The mechanism is always the same.

A standard slips. The context is understandable — short-staffed, high pressure, genuinely unusual circumstances. The exception gets made. Life goes on. Nobody mentions it. Two months later the same situation arises and the exception gets made again, a little more easily this time, because it already happened once. By the third time, it's not an exception anymore. It's the new normal.

And then somebody tries to correct it, and the team treats it as a change — because from their perspective, it is.

What Drift Actually Is

Drift is the process by which organizations update their behavioral standards without ever making a deliberate decision to do so.

It doesn't happen because people are lazy or uncommitted. It happens because systems are living things. Left unattended, they find equilibrium — and equilibrium is usually at the level of whatever the organization actually enforces, not whatever it says it believes.

In maintenance, this looks like: PMs that get compressed from sixty minutes to forty because the shift is running behind. Which becomes thirty-five minutes. Which becomes "we hit the highlights." Which becomes a PM that generates compliance numbers without generating any real equipment intelligence.

In leadership, this looks like: a feedback conversation that gets postponed because the timing isn't right. Which becomes a pattern of postponing. Which becomes a team that doesn't expect feedback until something has gone visibly wrong. Which becomes a team that stops telling the leader about problems because experience has taught them that the information doesn't change anything.

The endpoint isn't catastrophic failure. It's normalized mediocrity.

Why It's Hard to See

Drift is invisible from the inside for the same reason that gradual change of any kind is invisible: you're inside it.

The people in the organization don't experience a lower standard. They experience the standard. The way things work. The way things have always worked, as far as anyone can remember. And when an outsider — an auditor, a new leader, a benchmarking team — points out the gap, the first reaction is usually defensive. Because from the inside, what looks like a gap from the outside looks like context.

This is why the most accurate view of an organization's standards almost always comes from someone who wasn't there when they formed.

It's also why high-performing organizations build deliberate mechanisms for outside perspective — whether that's formal assessments, peer benchmarking, or a leader who has the discipline to look at what the system is producing rather than explaining what it intended.

The Cost of Delay

Drift compounds. This is the part that makes it genuinely expensive.

A small deviation that goes unaddressed for a week is a minor correction. The same deviation unaddressed for three months is a culture problem. The same deviation unaddressed for a year is an entrenched belief about how the organization operates, defended by the people who've been operating that way and are now being asked to change.

Early correction costs discomfort. The conversation is slightly awkward. The person might push back. The standard has to be restated in a way that makes clear it's actually a standard and not a suggestion.

Delayed correction costs everything else: the lost performance over the period of drift, the significantly harder conversation required to reverse an established pattern, the credibility damage that comes from finally enforcing a standard you tolerated long past the point when it mattered.

The question isn't whether you're willing to have the uncomfortable conversation.

It's whether you're willing to have it now, when it's small — or later, when it's expensive.

Building for Anti-Drift

Organizations that manage drift well share one characteristic: they have mechanisms that surface deviation before it normalizes.

In maintenance, these are predictive and condition-based signals that flag deviation from baseline before the gap becomes a failure. The analogy to leadership is exact: feedback systems that surface deviation from standards before the gap becomes culture.

Practically, this means a few things. Standards that are explicit enough to detect deviation — not "do good work" but "here's what good work looks like and here's how we'll know if we're not doing it." Feedback that's given before problems compound, not after they've become visible to everyone. Consistent follow-through on expectations, not just during the first month of a new initiative.

This isn't complicated. But it requires doing the thing most leaders delay: naming what's slipping while it's still small, calmly, without drama, and without waiting for the context to be perfect.

Drift doesn't announce itself. The only way to manage it is to be paying attention before the gap becomes impossible to miss.