A new employee can expose an old organisational problem with one innocent question: “Why do we do it this way?”

The question is unsettling not because the answer is complicated, but because everyone else stopped asking. The newcomer has no hidden information; they simply have not yet adapted to what the organisation now treats as normal.

A dashboard that nobody quite trusts, but everyone knows how to read anyway.

An approval step that adds no value, but has existed for so long nobody thinks to question it.

A customer complaint that arrives often enough to become a category rather than a warning.

A delayed decision that gradually stops feeling delayed because everyone has quietly adjusted their expectations around it.

None of these changes happen all at once.

Each one makes the signal a little quieter.

The unusual becomes familiar.

The familiar becomes expected.

And expected things stop generating questions.

The organisation didn’t ignore the problem.

It adapted to it.

Consider what adaptation actually looks like from the inside.

The analyst who updates the dashboard every Monday and mentally adds ten percent to every number before sharing it. Not because she’s been told to. Because she’s learned to. The adjustment has become so automatic she no longer thinks of it as an adjustment.

The project manager who builds an extra two weeks into every timeline. Not because the work requires it. Because decisions always arrive late, and he stopped waiting for that to change.

The customer service team with a template for the complaint that lands every week. Efficient. Professional. Completely indistinguishable from a team that has decided the complaint is simply part of the service.

The leadership team that schedules a monthly review to discuss a problem they’ve been discussing for eighteen months.

None of these people are failing.

They’re doing exactly what capable people do.

They adapt.

That’s what makes it so difficult to see.

The organisation hasn’t become less competent.

It has become competent at functioning despite something it should have fixed.

This is what makes organisational drift so difficult to diagnose.

It doesn’t arrive as a failure.

It arrives as a series of reasonable decisions.

Each one logical in isolation.

Each one making the organisation slightly better at tolerating something it should be changing.

The signal doesn’t disappear.

It simply stops feeling like one.

Think about what happens to a signal the first time it appears.

It registers.

People notice.

Questions get asked.

Sometimes action follows.

Sometimes it doesn’t.

But either way, the signal has been seen.

The second time, it registers a little less.

The third time, someone mentions it almost as an aside.

By the tenth time, it has a name.

By the fiftieth, it has a process.

The organisation hasn’t solved the problem.

It has built infrastructure around it.

Organisations adapt to signals faster than they solve them.

And every adaptation makes the signal quieter.

Not because the problem has changed.

Because the organisation has.

There is a word for what happens next.

Drift.

Not a decision.

Not a failure.

Not a moment anyone can point to.

Just the slow accumulation of adaptations that move the organisation away from the standards it once held: without anyone noticing the distance travelled.

Drift is difficult to see from the inside precisely because it happens through normal behaviour.

People doing their jobs.

Teams solving today’s problems.

Leaders managing what’s in front of them.

Nobody intending to lower the standard.

Nobody realising the standard has moved.

This is why the new employee’s question is so valuable.

Not because they have better answers.

Because they haven’t adapted yet.

They’re still seeing the organisation as it is rather than as everyone else has learned to experience it.

That gap: between what the newcomer sees and what everyone else has stopped seeing, is one of the most accurate measures of organisational drift available.

Most organisations don’t measure it.

Most don’t even notice it closing.

Within a few months, the new employee stops asking.

Not because the questions have been answered.

Because they’ve adapted too.

The question worth asking isn’t whether your organisation has signals.

Every organisation has signals.

The question is how long they remain signals.

At what point does the unusual become familiar?

At what point does the familiar stop generating questions?

At what point does the workaround become the process?

These aren’t dramatic moments.

They rarely announce themselves.

They accumulate quietly, in the background, until the day someone new walks in and asks a question that stops the room.

The day a warning becomes routine is the day it stops being a warning.