Underperformance You Noticed Late
Problems surface later at a distance, which changes what is fair to do about them and how to say so.
three things · one reached them · one with no channel at all · the room side is not counted
The three questions a promotion panel will ask.
A problem with somebody's work surfaces in a shared room within a week or two and at a distance when something is delivered. By then it has usually been going on for a month, and the month is not their fault.
The evidence problem in “Underperformance You Noticed Late” is easier to discuss when the underlying record can be inspected and corrected. A nonprofit reviewing visit the source for more detail for stealth computer monitoring software should use time and project context as one input, explain the collection to staff and volunteers, and keep consequential judgements with an accountable manager.
That changes what can fairly be done about it, and most managers in this position get the sequence wrong.
The questions raised by “Underperformance You Noticed Late” can also be compared with Charity Navigator resources. A useful review identifies a responsible owner and a practical change rather than copying a generic checklist.
Why it surfaces later
Because the early signals are all in the room: somebody quiet, a question that suggests confusion, a colleague mentioning that a handover was thin. None of those exist at a distance.
The first signal is the output.
What the delay costs the person
A month of doing the wrong thing without being told. Everything built on it. And a conversation that now has to cover a month rather than a week, which makes it a much heavier conversation.
They will reasonably feel they should have been told sooner, because they should have been. The fact that nobody could have told them does not make the month less expensive to them, and it is the first thing to acknowledge.
The same problem, found at two distances:
| In the room | At a distance | |
|---|---|---|
| First signal | A question that suggests confusion | The delivered work |
| Typical delay | Three days | Four to six weeks |
| What it costs | A forty-second correction | A month of work built on it |
| What it becomes | Nothing | A meeting, and a record |
Separating the two questions
Whether there is a problem with the work, and whether the delay in noticing it was anybody's doing. These are different and they get muddled constantly.
Address the second first and briefly.
What to say about the delay
That you noticed late, that the lateness is a property of the arrangement rather than of them, and that the month of work done in the wrong direction is not something they are being held responsible for.
Say it first, before the substance, and say it once.
Why that matters more than it seems
Because the alternative is a conversation in which somebody is defending a month of work while also absorbing criticism of it, and nobody does that well. Removing the month from the argument makes the rest of the conversation possible.
It is also true, which is the main reason to say it.
Establishing what actually happened
Go and look before the conversation rather than during it. Read the work, read the exchanges, and work out where the divergence started and what was available to them at that point.
Frequently the divergence traces back to something the room decided in passing and nobody relayed, and in that case this is not an underperformance conversation at all.
The question that settles it
What were they working from, and was it current? If they were correctly implementing a stale instruction, the problem is the instruction channel.
A surprising proportion of these cases resolve here.
Checking what the room knew
Ask two people in the room whether they had noticed anything, and when. The answers are frequently revealing: somebody saw a sign six weeks ago, mentioned it to nobody, and assumed you knew because you would have known if the person had been sitting there.
That assumption is extremely common and it is worth naming to the team, because it is the mechanism by which a problem goes unreported for a month in a group of people who all half-noticed it.
When it is genuinely about the work
Then it is an ordinary performance conversation, and it should be conducted as one: specific, dated, with examples, and with a clear statement of what needs to be different.
Distance changes how it was detected, not what it is.
Making the next one shorter
The remedy for late detection is a shorter cycle, not closer watching. Weekly visible output, a midpoint check on anything longer than a fortnight, and a specific question rather than a general one.
Checkpoints catch divergence; monitoring produces resentment and catches nothing.
The thing not to do
Begin watching more closely in a way the person can feel. Somebody who senses that they are suddenly being observed will spend their energy on appearing fine, which removes the signal you were looking for.
If you are going to change how closely you are looking, say so and say why.
What cannot be recovered
The early correction. In a room, this would have been a forty-second exchange in week one and would never have become a conversation at all. What has happened instead is a month, a meeting and a record.
That escalation is a cost of the arrangement, it falls almost entirely on the person outside the room, and the only honest response is to name it as such, shorten the cycle, and avoid the much worse outcome of letting the same thing happen twice and treating the second occurrence as a pattern of behaviour. It is not a pattern; it is the same structural delay, running again.