Aug 18, 2026

The Employee Isn't the Only Thing That Changed

When a previously strong employee starts slipping, it is easy to assume the person changed. Sometimes the bigger change happened around them.

A good employee starts missing things.

They seem less proactive. Less engaged. Maybe slower to respond.

The obvious conclusion is that the employee changed.

Their motivation dropped. Their attitude shifted. Their standards slipped.

Sometimes that’s true.

But there is another possibility managers often miss:

The employee isn’t the only thing that changed.

The role changed.

The manager changed.

The team changed.

The expectations changed.

The amount of autonomy changed.

The way decisions get made changed.

And what looks like a problem inside the employee may actually be their response to a system that no longer works the way it used to.

Start with the before-and-after

Consider an employee who performed well for two years.

They were reliable. They took ownership. They solved problems without needing much direction.

Then, over a few months, that starts to disappear.

Now they wait for instructions.

They contribute less in meetings.

Projects take longer.

Their manager describes them as “less engaged.”

If you only look at the employee’s current behavior, declining motivation is a reasonable diagnosis.

But add the timeline.

Three months before the decline became noticeable:

  • A new manager took over.
  • Responsibilities were redistributed.
  • Approval became necessary for decisions the employee previously made independently.
  • Their role became more execution-heavy and less problem-solving-heavy.

Now the same behavior tells a different story.

The employee may indeed be less engaged.

But “engagement problem” describes the symptom.

It doesn’t explain what changed.

Performance happens inside a system

We tend to talk about employee performance as though it belongs entirely to the employee.

Someone is a high performer.

Someone is struggling.

Someone has ownership.

Someone lacks initiative.

That language is convenient, but it can hide something important: performance is partly relational and contextual.

The same person can operate very differently under different conditions.

Give someone clear ownership and they may move quickly.

Put the same person into an environment where every decision requires approval and they may start waiting.

Give someone a role built around solving difficult problems and they may be energized.

Gradually turn that role into repetitive coordination and they may look checked out.

Put a strong employee with a manager whose working style fits theirs and things can feel effortless.

Change that relationship and suddenly both sides may wonder what happened.

The person did not necessarily become a different employee.

The conditions under which they were effective may have changed.

This is where managers can misdiagnose the problem

Once the visible behavior changes, managers naturally react to what they can see.

Less initiative becomes:

“They need to take more ownership.”

Lower energy becomes:

“They need to be more engaged.”

More hesitation becomes:

“They need to be more decisive.”

Missed expectations become:

“We need to manage their performance more closely.”

Those responses can make sense if the diagnosis is right.

But imagine the employee stopped taking initiative because their new manager repeatedly overruled decisions they previously owned.

Telling them to “show more ownership” doesn’t address the contradiction.

Or imagine their performance declined after their role expanded into work that depends heavily on skills that were never central to their previous success.

More accountability may not restore the old performance.

It may simply increase pressure inside a role that no longer fits.

This is how a real problem can produce the wrong intervention.

Look for changes around the employee

When someone who used to perform well goes off track, the useful question isn’t only:

What’s wrong with this person?

Ask:

What changed around the time this started?

Look at the period before the first visible shift.

Did their manager change?

Did their scope expand or narrow?

Did responsibilities move between people?

Did the team lose someone important?

Did decision-making become more centralized?

Did priorities start changing more frequently?

Did a promotion quietly turn a strong individual contributor into a struggling manager?

Did the company grow enough that the informal way they used to get things done stopped working?

These aren’t excuses for poor performance.

They’re diagnostic information.

The goal isn’t to remove responsibility from the employee. It’s to understand what you’re actually asking them to respond to.

Sequence matters

The order of events can tell you more than the symptom itself.

Suppose the sequence is:

  • Employee performs strongly.
  • Reporting structure changes.
  • Employee begins asking for more clarification.
  • Initiative declines.
  • Deadlines start slipping.
  • Manager concludes the employee has lost motivation.

That sequence should make you curious.

The motivation explanation may be correct.

But there is another hypothesis worth testing: the reporting change created uncertainty, reduced autonomy, or introduced a working-style mismatch. The later performance problems followed from that.

Change the sequence and the diagnosis might change too.

That’s why “they’re underperforming” isn’t enough.

You need the before-and-after.

Don’t turn systems thinking into excuse-making

There is an opposite mistake here.

Once managers recognize that context matters, they can become reluctant to hold anyone accountable.

That’s not the point.

An employee can be responsible for their behavior and be responding to a changed environment.

A manager can have reasonable expectations and have unintentionally created friction.

A role can be necessary for the business and no longer fit the person who once succeeded in it.

Diagnosis isn’t about deciding who to blame.

It’s about identifying the dynamic accurately enough to choose the right next move.

Sometimes that move will be clearer expectations.

Sometimes it will be changing the role.

Sometimes it will be repairing a manager relationship.

Sometimes it will be acknowledging that the fit has genuinely deteriorated.

And sometimes the conclusion really will be that the employee isn’t meeting reasonable expectations despite a workable environment.

But you want to arrive there after examining what changed—not before.

Before you act on the employee, examine the environment

When a previously solid employee suddenly feels different, don’t freeze the surrounding organization in your mind and treat the person as the only variable.

Reconstruct the situation.

What were they like when things worked?

What conditions existed then?

What changed next?

What behavior changed after that?

That timeline can expose a very different problem from the one visible today.

Because sometimes the employee didn’t simply lose motivation.

Sometimes the organization changed the conditions that allowed them to be good in the first place.

And if you diagnose the person without diagnosing those changes, you may end up trying to fix the wrong thing.

That is exactly the kind of unclear employee situation TeamClarity is built for: helping you understand what changed, what may be getting misread, and what deserves attention before you act.

TeamClarity

Have a real case? Submit it.

If this pattern feels familiar in a real employee situation, the TeamClarity preview now includes an early-access case submission section you can use to share what changed.

Share This Essay