One Employee, Three Different Stories

A good employee starts slipping.

They used to respond quickly. Now messages sit unanswered.

They used to volunteer for difficult work. Now they do exactly what is assigned.

They used to bring energy into meetings. Now they barely speak.

Everyone can see the change.

But ask three people what is happening, and you may get three completely different stories.

The manager’s story

The manager sees a performance problem.

“He’s checked out.”

From their perspective, the evidence is obvious.

Deadlines have started slipping. Follow-through is weaker. The employee needs more reminders than before. In meetings, he contributes less and rarely takes initiative.

The manager may have already tried addressing it.

They gave clearer expectations. Asked for more ownership. Became more explicit about deadlines.

Nothing changed.

So the explanation starts hardening:

He has lost motivation.

Maybe he has become complacent.

Maybe this is simply who he is now.

That story makes sense from where the manager is standing.

But it is still a story.

The teammate’s story

The teammate sees something different.

“He’s frustrated with the way things are being run.”

They remember when the employee used to challenge decisions, suggest alternatives, and jump in when something needed fixing.

Then something shifted.

Maybe a new manager arrived.

Maybe responsibilities changed.

Maybe decisions that once belonged to the employee started moving elsewhere.

The teammate does not see laziness.

They see withdrawal.

From their perspective, the employee stopped contributing because contributing stopped feeling worthwhile.

That story also makes sense.

And it may also be incomplete.

The employee’s story

Ask the employee and you might hear a third explanation.

“I’m doing what they asked me to do.”

They may not think they have disengaged at all.

Perhaps six months ago they were told to focus on execution instead of getting involved in everything.

Perhaps repeated suggestions went nowhere.

Perhaps their role expanded without the authority, support, or clarity needed to handle it.

Perhaps they tried to adapt.

So they stopped pushing.

Stopped volunteering.

Stopped challenging.

From the employee’s perspective, what the manager calls “low ownership” might feel like respecting the boundaries of the role.

Same employee.

Same behavior.

Three different explanations.

This is where people decisions get dangerous

The problem is not that one person is lying and another is telling the truth.

The problem is that people interpret behavior from their own position.

A manager experiences missed follow-through.

A teammate experiences someone’s withdrawal.

An employee experiences the events that happened before the withdrawal.

Each person has access to different evidence.

And once an explanation takes hold, new behavior tends to get interpreted through it.

If the manager believes the employee has become complacent, another quiet meeting confirms it.

If the teammate believes the manager caused the problem, another tense interaction confirms that too.

If the employee believes nobody listens, another decision made without them becomes further proof.

Everyone becomes more certain.

The actual cause can become harder to see.

Start with the change, not the character judgment

When a previously solid employee starts behaving differently, one of the most useful questions is surprisingly simple:

What changed before they changed?

Not:

“Why are they unmotivated?”

That question already assumes motivation is the problem.

Instead, reconstruct the sequence.

• When did the change first become noticeable?
• What changed in the employee’s role around that time?
• Did their manager change?
• Did their scope or responsibilities change?
• Did the team structure change?
• Was there a specific conflict, disappointment, or period of sustained pressure?
• Which behavior changed first?

The sequence matters.

Imagine the employee became quieter in March.

In February, a reorganization moved two important responsibilities away from them.

In January, they were still receiving strong feedback and taking on extra work.

That does not prove the reorganization caused the problem.

But it gives you a much stronger hypothesis than:

“He doesn’t care anymore.”

Different explanations lead to different actions

This is why diagnosis matters.

If the real problem is declining motivation, clearer accountability may help.

If the employee has lost confidence in what they own, more pressure may make the withdrawal worse.

If the role no longer fits the person, another motivational conversation misses the point.

If the relationship with the manager changed, putting the employee on a performance plan may formalize a problem the company helped create.

The visible symptom can be identical.

The appropriate response can be completely different.

That is the risk in acting on the first plausible story.

You don’t need everyone to agree

The goal is not to get the manager, teammate, and employee into a room until they produce one perfectly shared version of reality.

They may never see the situation exactly the same way.

The goal is to separate what has been observed from what has been inferred.

“She stopped volunteering for projects” is an observation.

“She stopped caring” is an interpretation.

“He challenges my decisions more often” is an observation.

“He doesn’t respect my authority” is an interpretation.

“She started missing deadlines after her responsibilities doubled” gives you both an observation and a useful point in the timeline.

That distinction creates room for diagnosis.

Before you decide what to do, decide what you actually know

When an employee used to be solid and now something feels off, the first explanation is rarely the only possible one.

The manager has a story.

The team has a story.

The employee has a story.

Before you act on any of them, look for the pattern underneath all three.

What changed?

What happened immediately before the change?

What is observable?

What is interpretation?

And which explanation best accounts for the full sequence of events?

That is the difference between reacting to underperformance and diagnosing what actually changed.

TeamClarity is built for that moment: when you can see the employee has changed, but you are not yet confident you understand why.

Diagnose before you act.