How to Tell an Employee They're Underperforming — Without Destroying Them

You have rescheduled this conversation twice. You have rehearsed openings in the car. You know roughly what needs to be said, and you keep not saying it.

That puts you with the majority. In a Harris Poll for Interact, 69% of managers said they are often uncomfortable communicating with employees. The discomfort is human. But look at what avoiding it actually does: the person keeps underperforming, unaware of how serious it is. Their eventual exit arrives as an ambush. And the months in between are paid, in full, by you.

The conversation you are avoiding is also the kindest thing you can do for this person. They cannot fix what nobody has clearly told them.

Why hints don't work — especially here

Most Indian workplaces run on hint culture. The forwarded email with "pls relook". The task quietly moved to someone else. The slightly cooler tone in the Monday meeting. Managers believe these send a message. They send an atmosphere.

Hierarchy makes it worse. In owner-led companies, employees are trained not to read too much into the boss's moods — the boss is stressed, the boss is busy, the boss snapped at everyone this week. Your hints disappear into that noise. Then one day the hints become a termination conversation, and the employee says, truthfully: nobody ever told me.

If a labour dispute ever follows, "nobody ever told me" is not just an emotional claim. Courts expect performance terminations to sit on documented, communicated chances to improve. The conversation you are avoiding is also page one of that file.

The Straight Line

Four parts, in order, twenty minutes. The structure does the emotional work so you don't have to improvise while nervous.

1. Name it — one sentence, no cushions

Sit down privately, no audience, phone away, and open with the point:

"I want to talk about your work over the last three months, because it's fallen below what I need from this role, and I don't want that to keep drifting without us talking about it."

Notice what that sentence does not do. It doesn't start with fifteen minutes of small talk that makes the turn feel like a trap. It doesn't open with "how do you think you're doing?" — a question that forces them to guess the verdict, and reads as a game. One sentence, said kindly and plainly, beats every clever opening.

2. Evidence it — two or three specifics, not a charge sheet

• "The Kotak proposal went out four days late, and I rewrote the pricing section myself."
• "Three client calls in May had no follow-up note until someone chased."

Two or three concrete examples, recent, factual. Not a recital of every miss since January — a charge sheet triggers defence, and defence ends listening. And never "everyone has noticed" or "people are saying". Anonymous crowds cannot be answered; they can only be feared. Speak for yourself.

3. Ask — and actually want the answer

"That's what I'm seeing. What's going on?"

Then stop talking. The silence will be uncomfortable. Let it be.

This question is not a formality — it is where the conversation earns its twenty minutes. Sometimes what comes back changes everything: a health situation at home, a workload that doubled when a colleague left, instructions from a second boss you didn't know about, a skill gap they were ashamed to admit. You are diagnosing at this moment, not sentencing. The pillar's Fix-or-Part Ladder depends entirely on what you learn right here.

Sometimes what comes back is nothing — a shrug, a deflection, a counter-attack. That is also information.

4. Agree — what changes, by when, checked how

End with something written on one line, not a mood. "Proposals go out within two days of the brief, and we'll look at it together every Friday for four weeks." Specific, short-dated, checkable.

Then the habit that separates managers who handle this well from managers who end up in disputes: send a two-line email the same day. "Thanks for the honest conversation today. As discussed: [the one line]. We'll review on [date]." Not cold. Not legalistic. Just written. If things improve, it is the note you'll happily never need. If they don't, it is the first page of the file that makes a fair formal process possible.

What not to do

• Don't sandwich it. Praise-criticism-praise leaves the person remembering the bread and forgetting the filling. Deliver the concern on its own; give real praise its own moment on another day, where it stays credible.
• Don't do it in anger, or in public. The version of this conversation that happens in front of the team, in the heat of a missed deadline, costs you more than it costs them. Everyone watching learns you punish with humiliation.
• Don't promise outcomes you haven't decided. "Fix this and you'll be fine" may not be yours to guarantee. Promise the honest version: a fair chance, real support, and a straight answer at the review.
• Don't outsource it to HR. In a small company the message lands with the weight of whoever delivers it. Sent through HR, the message received is "the boss has already moved on."

If you keep not having it

Put a date in your calendar this week and treat it like a client meeting. If you find yourself rescheduling a third time, the problem may no longer be this employee — a pattern of postponed hard conversations is a management-system problem, and it compounds. That pattern, and how it silently sets your company's real standards, is Why Your Managers Won't Fire Anyone.

And if you've had this conversation with three different people in the same seat over two years, stop. The seat is the problem. The Business Pulse shows you which parts of the organisation keep producing the same conversation — before you spend another one on the wrong person.

Questions managers ask before this conversation

What if the employee cries, or gets angry? Pause, don't retreat. "Take a minute — this is worth doing properly" respects the emotion without cancelling the message. The conversation can survive tears and heat; what it cannot survive is you softening the content mid-way to end the discomfort, because then nothing was actually said.

Should I put anything in writing before the first conversation? No — a letter before a conversation reads as an ambush. Writing comes immediately after: the same-day two-line email confirming what was discussed and agreed. That order — speak first, confirm second — is what keeps the process human and the file honest.

What if they bring up problems on my side — pay, workload, unclear instructions? Listen, and separate the ledgers out loud: "Some of that is fair and I'll act on it. It sits alongside the performance gap — it doesn't replace it." Both things can be true, and the conversation only fails if either side uses one truth to cancel the other.

How is this different from a warning letter? A warning letter is a legal instrument that assumes the informal road is over. This conversation is the informal road. Skip it and go straight to paper, and you lose the one version of events where the person fixes the problem and nothing ever needed to escalate.