Four people who are certain they are working, and one team that disagrees

There is a conversation that happens in almost every team we work with, usually in the second individual interview of the day. Someone explains, with visible sincerity, that they are carrying more than their share. Two hours later a colleague names that same person as the one who does the least.

Both are telling the truth as they experience it. That is what makes the situation hard, and it is why the reflex response — a firmer conversation about effort — usually makes it worse.

Four versions of it recur.

1. The one who is never not busy

Genuinely overloaded, and genuinely the last to leave. The diary is full. The inbox is handled. Nobody, including the person themselves, could describe what this week produced.

Activity and output are different quantities. This profile converts a large amount of the first into a small amount of the second, and the fullness of the diary is precisely what conceals it, from everyone and most of all from them. Their working belief is that they are behind because there is too much. Usually they are behind because nothing has been declined in two years.

They are also the most demoralised profile of the four when confronted, because the effort is real. Effort is not what is being questioned.

What helps: not time management. A conversation about what to stop. The practical version is to name the three outputs that matter this quarter and agree, explicitly and in writing, what is being dropped to protect them. This person will not drop anything without permission, because dropping things is what they believe they are being criticised for.

2. The one whose work is genuinely invisible

Here the team is wrong, and this is the profile most often mishandled.

Some of the most valuable work in a team leaves no trace. The client who was about to escalate and did not. The dependency someone spotted three weeks out. The newcomer who was unblocked in a ten-minute corridor conversation. The specification that was argued into shape before it reached the developers.

None of it appears in a status report. All of it is noticed only when it stops, by which point nobody connects the deterioration to the person who left.

Two forces compound it. Work of this kind is disproportionately carried by people who do not narrate their own contribution — and it is disproportionately carried by the same individuals over time, which is worth a manager’s attention on its own. And where part of the team is remote, proximity bias adds a straightforward visual correction: presence in the room reads as contribution, absence reads as absence.

What helps: the manager making the work visible, not the person. Asking someone to advertise their own coordination work puts them in an impossible position. Naming it yourself, once, specifically, in a setting where the team can hear it, changes the collective account in a single sentence.

3. The one who works on what they find interesting

High output, real competence, and a body of work that only intermittently intersects with what the team needed.

The tooling that was rebuilt because the old one was inelegant. The analysis nobody commissioned. The refactor that was necessary but not this quarter. Each piece is defensible in isolation, which is why this profile survives review after review, and why the team’s frustration never quite finds an argument.

They experience the criticism as philistinism, and they have a point in the narrow sense: the work is often good. It is simply not the work.

What helps: priorities that exist somewhere other than in the manager’s head. This profile self-assigns in the absence of a visible order of importance, and they will keep doing it as long as the order is implicit. Written priorities, reviewed monthly, remove the vacuum. Where this pattern is widespread across a team, the problem is not four individuals, it is that nobody has said what matters most.

4. The one whose currency is presence

Arrives early, leaves late, is on the messaging tool at eleven at night. Sincerely believes that this constitutes commitment, and is sincerely aggrieved when it is not treated as such.

Sometimes this is a workload problem in disguise. Sometimes it is an environment that once rewarded exactly this and has not said that it stopped. Frequently it is a person for whom leaving on time feels like an admission of something, which is a different conversation altogether.

What makes it corrosive is the standard it sets. A team that reads hours as virtue penalises everyone with a constraint on their hours, which is not a random subset of the team, and produces the sharpest resentment of the four profiles.

What helps: the manager naming the measure explicitly and then living by it. If output is the measure, say so, and stop remarking approvingly on late departures. This profile is responding accurately to signals that are still being sent.

The diagnostic

Before responding to any of the four, three questions, in this order.

What was agreed? If nothing was written down, there is no performance question to answer yet, only a manager’s expectation that was never communicated. Start there.

What arrived, and when? Against the agreement, not against an impression. This is the step that separates the profiles: the invisible worker has delivered, the misdirected one has delivered something else, the busy one has delivered late, the present one has delivered a normal amount over abnormal hours.

Who else knows? If the outputs are real and the team does not know about them, the gap is yours to close and it is not a performance issue at all.

The common error is to skip all three and go straight to a conversation about attitude. Attitude conversations are unfalsifiable, they leave the person with nothing actionable, and they are how a visibility problem becomes a conflict — with the roles described in four people, one conflict assembling around it shortly afterwards.

Defining the output rather than policing the effort is the core of the manager and leader toolkit, and it becomes non-optional once part of the team is remote.