Underperforming Employee: How to Have the Conversation You Keep Postponing
How to name a pattern after months of silence: the three instances to write down first, the words to open with, and the plan that makes the next step honest.
· 9 min read · Valor team
Most managers do not open this conversation. They open a softer one sitting next to it.
"So, how do you feel things are going?" It sounds generous. What it does is ask the other person to raise the problem for you, and they will not, because from where they sit there is no problem. You have said nothing for months. They say "good, busy, the Hendricks thing got messy but it is handled," and you are twelve minutes into a meeting about nothing. An underperforming employee conversation that opens like this has already been postponed by one more week.
By the time you are searching for how to deal with an underperforming employee, you have usually waited three months too long, and the delay is now part of the problem. Every week you stayed quiet, the person read that silence as approval, because at work that is what silence means.
So this is not the conversation you would have had in June. It has to carry the months you skipped. Here is how to run it anyway.
One missed deadline is an incident. Three is a pattern.
These conversations dissolve because managers bring the most recent thing, and the most recent thing is arguable. The person has had days to rehearse their explanation for Tuesday. So you raise Tuesday, they explain Tuesday, the explanation is half reasonable, and you both leave agreeing that Tuesday was unfortunate.
Nothing changes, because Tuesday was never the subject. The subject is that Tuesday was the third one this quarter.
You have to say that part out loud. Not implied, not carried by your tone. Name the pattern, or the person files this as feedback about a bad week, and files it accurately, because a bad week is all you described.
Vague
I need you to be more on top of your accounts. It has been a rough stretch and I think you know that.
Specific
Three deliverables have gone out late since June. Hendricks on the 12th, Volt on the 3rd, Marsh last Tuesday. That is the pattern I want to fix.
The shape of any hard conversation with a report is laid out in how to have a difficult conversation with an employee. This one has a complication the others do not: you already let it run.
Write down three instances before you say a word
Not a summary of your frustration. Three rows, three things in each.
What happened, with no adjectives. "The Marsh renewal went out eleven days after the date we agreed." Not "the Marsh thing was a mess." Adjectives are opinions and opinions can be argued with. Dates cannot.
When. A date is checkable and "you are always late" is not. Say "always" and they win the argument with one counterexample.
What it cost. Who absorbed it: the client who called you, the two people who worked Saturday. Without it, this is a complaint about process. With it, a business problem they are standing inside.
Then one line for yourself: what you did about each instance at the time. If the answer is "nothing" three times, know that before you walk in. It is the first thing you have to say.
If you cannot get to three real instances, stop. You may not have an underperforming employee. You may have someone who irritates you, which is a different problem and not one they can fix.
The opening, when you have been quiet for months
Own the delay once. One sentence, early, no ceremony, then move on and do not touch it again.
Say it because it is true and they already know it, so it costs nothing and buys you a hearing. Say it only once because two apologies in, they are comforting you and the pattern you came to name has left the room.
You will want to fill that silence with a softener. Do not. The pause after a pattern is where the other person stops defending and starts thinking, and it takes longer than it feels like it should.
Half the time it is not a capacity problem
Ask before you prescribe. Not "is everything okay," which invites the word fine. Ask: "What is your read on why this keeps happening?" Then stay quiet long enough to be uncomfortable.
Roughly half the time, what comes back is not that the person cannot do the work.
- A health thing. The giveaway is a clean before and after: reliable for two years, not reliable since April. This is not a performance plan. It is time, a lighter load, and whatever your company provides. Route it through HR and diagnose nothing yourself.
- A home thing. A separation, an ill parent, a new baby, money. The fix is a named reduction in scope with an end date on it. Temporary and explicit beats indefinite and unspoken.
- A manager thing. Which is to say, you. Priorities that move weekly, decisions that sit in your inbox for six days, a promotion that went elsewhere in March and was never discussed. Ask it straight: "Is there something I am doing, or not doing, that makes this harder?" You get one honest answer, and only if you take it well.
- A clarity thing. They believe the standard they are hitting is the standard. More common than it sounds with someone who joined remotely, or who inherited the work from a person who did it differently. Show them what good looks like as an artifact, not as adjectives.
Capacity is real too: sometimes the job grew past the person and no support closes the gap. You cannot know that in the first fifteen minutes of a conversation you spent a quarter avoiding.
The plan: what changes, what better looks like, and a date
A plan that lives only in a conversation is not a plan. It needs three parts: what changes, described as behavior. What better looks like, in terms someone else could check. And a date, in the calendar, before either of you leaves the room.
"Be more proactive" fails the first test: it cannot be done on a Tuesday morning.
Send four lines the same day: what you raised, what you agreed, the standard, the date. Not to build a file, but so that in five weeks you are both remembering the same meeting.
When they agree to everything and nothing changes
That last question tells you which conversation you just had. Someone who intends to change asks about the details, because the details are about to become their week. Someone who is managing you agrees with everything and asks nothing.
The second is where managers lose the second month too. The plan is agreed on Friday. Thursday's status line does not appear. You tell yourself you will pick it up at the review, because raising it now feels like nagging.
Raise it that day. Small is the point. The subject has changed: it is no longer the client work, it is whether an agreement between the two of you means anything.
The formal step, said without pretending it is a surprise
If the date arrives and nothing has moved, do not perform regret you did not show in June, and do not reach for "unfortunately, it has come to this." That sounds like weather, not a decision.
Say what happened. "On September 29 we agreed on two changes and a review today. Here is where each one stands. So I am moving this to a written plan, with HR in the room." A formal plan is a real record with real consequences, and it is not automatically an ending. Some turn it around inside one. Some use it to conclude, correctly, that the job is wrong for them.
Accuracy is the kind thing here. Softening the language is what leaves someone genuinely shocked three weeks later, and that shock is what you were trying to avoid all along.
This does not work if the person has never been told there is a problem. Six months of good-enough reviews followed by a plain conversation is not honesty, it is a surprise, and it will be read as a decision that was already made. Say that part out loud: that you should have raised it earlier, and that this is the first clear warning, not the last one.
Knowing the words is not the same as saying them
This conversation rarely fails on content. It fails on delivery, and delivery is where three months of avoidance leaks out. You rush the dates because saying them slowly feels cruel. You add "but honestly it is not a big deal" to the end of the pattern. You laugh once, in the pause, and undo the opening. Or you overcorrect, coming in twice as hard as you meant to, compensating for a quarter of saying nothing.
Then there is the thing no script survives: the first sentence back. "If this is about Hendricks, I already spoke to them, it is handled." Your prepared paragraph no longer fits, and the next four seconds decide the rest of it.
The only way to know how you sound is to have said it out loud, to something that answers back, before you say it to the person whose job depends on it. That is what the scenarios are for.
Questions people ask
How do you tell an employee they are underperforming?+
Say it in the first sentence, name the pattern rather than the latest incident, and bring three specific examples with dates and consequences. Something like: 'I want to talk about your work on the client accounts. Three deliverables have gone out late since June, and on Hendricks the client escalated to me directly.' Then stop talking and let them answer before you move on to solutions.
What do you say to an employee who is not performing?+
Cover four things in order: the pattern with dates, where you stand, what you need to understand from them, and what changes from Monday. Do not open with praise, which in this conversation gets heard as the headline. Close with a standard someone else could check and a date to review it, then confirm both in writing the same day so there is a shared record.
What are the signs of an underperforming employee?+
The reliable signals are behavioral and repeated: deadlines that slip without a warning first, work that needs rework from you or a peer, commitments made in meetings that do not show up afterwards, and updates that arrive only when you ask for them. One instance of any of these is a bad week. The same one three times in a quarter is a pattern, and the pattern is what you address.
How long should you give an underperforming employee to improve?+
Four to eight weeks for most role problems, with a short check-in every week rather than one review at the end. Under four weeks does not give a working habit time to change. Over eight and the deadline stops feeling real to either of you. Set the review date in the first conversation, put it in the calendar that day, and keep it even when the week is busy.
What if the employee says this is the first time they are hearing it?+
Assume they are telling the truth, and say so once: 'You are right, I should have raised this in June.' Then keep going. Owning the delay costs you nothing and buys you their attention. What you must not do is apologize a second time, because the meeting then becomes about your discomfort instead of the work, and you will leave without having agreed to anything.
Practice it before you have it
Run this conversation with Sam tonight.
Three months of missed follow-ups and excuses. The talk you keep postponing. In Valor you say it out loud to Sam, account manager, who pushes back like the real thing. Ten minutes, then a score that tells you what actually landed.
The Underperformer
Sam, Account Manager · 3 levels
Read next
How to Have a Difficult Conversation With an Employee: The Four Parts
The four parts that work in any hard conversation with someone who reports to you, the words for each, and what to say when they get defensive or cry.
Performance Review Examples: Phrases That Say Something Real
Performance review phrases band by band, each with the hollow version and the real one, plus how to run the meeting and hold a rating the person disputes.