The Story You're Telling Yourself About This Employee

An employee misses a deadline, gives a shorter answer than usual, and skips a meeting they normally attend.

Before the manager checks what happened, an explanation appears:

“They’re pulling away.”

Maybe they are frustrated. Maybe they have lost interest. Maybe they are preparing to leave. Maybe they no longer respect the team.

The explanation may be right. But once it arrives, every later detail can start serving it. A delayed response becomes evidence. A question sounds like resistance. A normal quiet day feels like confirmation.

The manager is no longer simply observing behavior. They are protecting a story.

Stories make uncertainty feel manageable

People decisions are uncomfortable when the facts are incomplete. A manager may know that an employee’s behavior changed without knowing why. That gap creates pressure to find a coherent explanation quickly.

Stories provide one. They turn scattered observations into a pattern with a beginning, a motive, and an implied next step.

The employee is disengaged, so increase oversight. They are resentful, so address their attitude. They are overwhelmed, so lower the workload. They are no longer a fit, so begin planning an exit.

The convenience is real. So is the danger. A story can make a complicated situation feel settled before the underlying pattern has been examined.

The first explanation is not always the strongest one

Consider an employee who has become less responsive over six weeks. Their manager believes the employee is disengaged because a promotion went to someone else.

That is plausible. But other explanations remain open.

The employee’s responsibilities may have expanded without a clear reset of priorities. A new approval process may have slowed work. A conflict with another team may have made every handoff more costly. The employee may be dealing with a personal situation they have not chosen to share.

These possibilities do not carry the same implications. Some call for a direct expectation. Others call for role clarification, conflict repair, or patience while more information becomes available.

The point is not to avoid conclusions forever. It is to avoid treating plausibility as proof.

Notice what the story causes you to ignore

Once a manager believes an employee has stopped caring, information that does not fit the story becomes easy to overlook.

The employee still delivers difficult work. They warn the team about a customer risk. They ask for context before committing to a plan. They are quiet in large meetings but engaged in one-on-one problem solving.

Those details matter because they narrow the diagnosis. A person who has lost all investment may look different from someone who is careful only in environments where priorities are unclear.

Ask yourself:

• What behavior would I expect if my explanation were true?
• What behavior would contradict it?
• Which evidence have I discounted because it is inconvenient?

This is not an academic exercise. It changes what you do next.

Replace labels with a sequence

“They have become unreliable” compresses a situation into a character judgment.

“They began missing internal handoffs after two responsibilities were combined, while their customer work remained strong” gives you a sequence to investigate.

The sequence may reveal that the issue is localized. It may show that the behavior began after a manager change, a conflict, or a shift in authority. It may show no meaningful external change, which keeps other hypotheses alive.

Specific descriptions also make a conversation fairer. An employee can respond to what happened on a date, in a process, or in a type of work. It is much harder to respond constructively to a conclusion about who they have become.

Ask someone who is not carrying the same story

Managers should be cautious about turning colleagues into a jury, but another informed perspective can expose blind spots.

Ask what the employee is doing differently, not whether they seem difficult. Compare observations across contexts. Is the change visible to everyone, or mainly to the manager? Does it appear in the work itself, in the relationship, or only in a particular meeting format?

Different observations do not automatically make one person right. They help separate a broad pattern from a relationship-specific interpretation.

The employee may be responding to the manager’s style. The manager may be noticing a real issue others have not yet encountered. Either way, the difference is useful evidence.

A conversation should test the story, not announce it

Opening with “You seem checked out” invites the employee to debate the label. Opening with a concrete change creates room for information.

You might say:

“You used to flag delivery risks early, and lately I’m hearing about them closer to the deadline. I have a few theories about why, but I don’t want to assume. What changed in the work or the process?”

That approach does not hide the concern. It makes the manager’s uncertainty explicit and asks the employee to help examine the sequence.

The response may confirm the original story. It may replace it. It may reveal that the manager saw only one part of the situation. A useful conversation can produce any of those outcomes.

Do not let a coherent story outrun the evidence

The most dangerous explanations are not the obviously irrational ones. They are the ones that sound reasonable, fit a few facts, and point toward an emotionally satisfying action.

“They are not committed anymore” makes pressure feel justified. “They are protecting themselves” makes withdrawal seem inevitable. “They are simply not capable at this level” makes a role change feel like the only honest option.

Sometimes those conclusions are correct. But they should survive contact with the timeline, the employee’s actual work, and a conversation that does not force a confession.

When a good employee changes, ask what story you started telling yourself and what evidence would make you revise it. That discipline does not make management indecisive. It keeps a plausible explanation from becoming an irreversible decision before the situation is clear.

TeamClarity is built for that moment: when the manager has a strong impression, but needs a better way to distinguish signal from the story forming around it.