How to manage underperformance

Almost every underperformance conversation happens months late. The manager notices in February, hopes it resolves itself, drops two hints in May that the person does not recognise as hints, and raises it properly in July, by which point they are irritated and the employee is blindsided. A gap that is six weeks old is a coaching conversation. The same gap at six months is a formal process and, often, someone's exit. So the first skill is not eloquence. It is speed.

Write the gap in one sentence before you book anything

If you cannot state the gap in one plain sentence, you are not ready. The meeting becomes twenty minutes of hedging, and the other person leaves vaguely insulted and entirely unclear. A usable gap sentence has an observation, a standard, and no adjectives about the person:

• Not: "Your attitude in client meetings is a problem." Yes: "In the last three client calls you answered questions the client directed at Priya. I need you to let her lead her own account."
• Not: "You're not really stepping up." Yes: "The monthly report has been late four times this quarter, between two and five days each time. It needs to land on the first working day."
• Not: "Quality has slipped." Yes: "Three of your last eight tickets came back reopened. The team average is under one in ten."

Read it out loud once to yourself. If it makes you wince, it is probably about the person rather than the work. The SBI feedback model is a reliable way to rebuild the sentence when your first draft comes out as a character assessment.

Work out which of three problems you actually have

Underperformance looks identical from the outside and comes from three very different places. Treating a clarity problem as a motivation problem is how good people get pushed out.

1. They don't know. Nobody defined the standard, or it changed and nobody said so. Ask: "What do you think good looks like on this?" If their answer describes something reasonable but not what you want, you have your answer, and the fault is partly yours.
2. They can't. Skill, tooling, workload or something outside work. Ask: "What gets in the way when you try to do this well?" Then wait. This route leads to coaching or a change of scope, not a warning. The GROW coaching model is built for exactly this.
3. They won't. They know, they can, and they are choosing otherwise. Rarer than it looks. This is the only one of the three that belongs in a formal process, and even here it is usually disengagement rather than defiance.

You will not always know which it is going in. Take a hypothesis and treat the first ten minutes as a test of it.

The conversation, in sequence

Book thirty minutes, in private, early in the week and never late on a Friday. Do not disguise it as a catch-up: "Let's use tomorrow's one-to-one to talk about the reporting deadline" is fair warning and costs you nothing.

1. First 30 seconds: say why you are there. "I want to talk about the monthly report. It's been late four times this quarter and I haven't raised it properly, which is on me. I want to sort it out with you." No warm-up, no compliment sandwich. People know when a sandwich is coming and hear nothing but the filling.
2. Next 2 minutes: state the gap and the standard. Observation, then standard, then stop. "Late by two to five days, four times. It needs to be in on the first working day." Resist the urge to soften it with three examples of what they do well. That comes later, and it lands better once the hard part is out of the way.
3. Next 10 minutes: shut up. Ask one open question and listen. "What's your read on it?" or "What's been happening?" If they go quiet, count to ten before filling the silence. This is where you find out which of the three problems you have, and it only works if you are listening rather than waiting for a gap to insert your prepared paragraph. See active listening.
4. Next 5 minutes: agree what changes. Ask them first: "What would need to change for this to land on time every month?" A plan they propose is a plan they own. Then add what you will do: cover, training, a decision they have been waiting on, one meeting off their calendar.
5. Last 5 minutes: make it specific and dated. "So: report in by the first working day, starting next month. I'll get you the sales numbers by the 27th so you're not waiting on me. We'll check in on the 5th." Vagueness here is what turns one conversation into six.
6. Within 24 hours: put it in writing. Three or four lines, no formal tone: what we discussed, what changes, what I'm doing, when we review. This is not bureaucracy. It is what prevents "nobody ever told me" in four months' time.

The purpose of the conversation is not to make the person feel bad enough to improve. It is to make the standard so clear that improving becomes possible.

Wrong way, better way

The difference is almost never the content. It is the specificity and the direction of the sentence.

What to do when it goes wrong

Four things go wrong in these conversations. All are survivable if you know the recovery move.

They cry, or go very quiet

Do not apologise for raising it, and do not retreat into reassurance you will have to walk back next month. Say: "Take a minute. There's no rush, and you're not in trouble." Push the tissues over, look at your notes, let the silence sit. If it does not settle: "Shall we stop here and pick this up tomorrow morning?" Then actually pick it up tomorrow morning. Postponing is fine, abandoning is not.

They deny it, or blame someone else

Do not argue about whether it happened. Move to specifics: "Let's take one example. The March report went in on the 6th. Talk me through that week." Specifics either confirm the pattern or reveal a genuine cause you did not know about, which is a good outcome either way. If the blame lands on a colleague, note it and separate it: "I'll look into the handover from finance. Separately, the deadline is still yours."

They agree to everything and change nothing

The most common failure and the easiest to miss, because the meeting felt great. The recovery move is the follow-up you already diarised. "We agreed the 1st. It came in on the 4th. What happened?" Second time, escalate the seriousness rather than the volume: "I want to be direct: this is now the thing that decides how the next few months go for you here." Cheerful agreement without change is usually a will problem wearing a very polite hat.

They turn it back on you

"You've never given me any support." Sometimes true. Take the hit cleanly, because defending yourself here costs you the whole conversation: "You're right that I left you alone with this for too long. That changes from this week. The standard doesn't change with it." Owning your share buys you credibility for the part you are not going to move on.

The formal plan, if you get there

If two or three honest conversations have not moved it, a written improvement plan is not a punishment, it is a fairness mechanism. It should be boring and unambiguous:

• The standard, in numbers or observable behaviour, not adjectives.
• What support you are providing, with dates. A plan with no manager obligations in it is a paper trail, and everyone can tell.
• Review points, weekly or fortnightly, in the calendar before anyone leaves the room.
• An end date, typically four to twelve weeks depending on the role and your local employment rules.
• What happens if it does not improve, said plainly and once. Never imply it and never repeat it.

Check your obligations with HR or a local adviser before you write it down: notice periods, documentation requirements and protections vary enormously between countries, and a well-meant plan written the wrong way creates real legal exposure.

Why this feels so hard

Because you are holding two things at once: care for the person and a standard you are not going to move. Drop the standard and you get a pleasant conversation that changes nothing and tells the team that deadlines are optional. Drop the care and you get compliance, resentment and a resignation in the spring. It is easier in a team where people can already say difficult things without being punished for it, which is what psychological safety buys you.

Now the honest bit. You have read the scripts, and reading them will change almost nothing. The failure mode is never that managers do not know they should be specific. It is that under mild social pressure, with a person they like, at 4pm, the specific sentence comes out as "anyway, no big deal, just keep an eye on it." That gap between knowing and doing only closes through rehearsal: saying the hard sentence out loud, badly, in a room where it is safe to say it badly, getting feedback, and saying it again. That is what experiential learning is for, and why two hours of practice moves behaviour when a two-day slide deck does not.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.