A manager can spend more time preparing to talk about underperformance than actually talking about it.
You rewrite the message. You soften the opening. You decide you should wait until you have a better example, a clearer plan, or a less stressful week.
Sometimes more preparation is the responsible choice. You should verify the pattern, understand what was expected, and consider whether workload, resources, or unclear direction contributed. But preparation can also become a way to postpone the moment when another person learns what you already know.
The conversation does not have to be perfect. The employee does need a fair chance to understand the gap.
Imagine a manager, Dani, whose report, Marcus, has missed several deadlines. Dani keeps rewriting a message to him. A casual “quick sync” feels misleading. A formal-sounding warning feels too harsh. So she deletes the message and tells herself she will find better words tomorrow.
Meanwhile, a colleague takes on some of the work that did not get done. The delay is no longer contained between Dani and Marcus. It has become part of someone else’s week, too.
Dani may be trying to protect Marcus from feeling criticized. She may also be protecting herself from the discomfort of saying something he might not want to hear.
Those motives can look alike from the outside. The employee still does not know there is a problem.
That is the part managers can miss. We often treat discomfort as a warning that we are being unkind. But a difficult conversation is not automatically cruel. It can be unfair if you enter with a verdict, ignore context, or treat a system problem as a character flaw. It can also be unfair to leave someone guessing about a recurring gap you expect them to correct.
Before you meet, get specific. What happened? What had been agreed? What was the impact? Check that you are describing a pattern you can support, not turning one missed deadline into a judgment about the person.
Then say what you have observed, plainly. For example: “The last two project deadlines slipped, and that delayed the next stage of the work. I want to understand what is getting in the way and agree on what needs to change.”
That is direct. It is not a complete explanation of the problem.
In the imagined conversation, Marcus says he did not realize the missed deadlines had become a pattern. He also explains that he has been struggling with a new system and did not want to appear unable to handle it.
That context matters. It does not erase the missed work; it gives Dani something more useful than a guess about Marcus’s attitude. The next step is to understand what support or clarification would help, and to agree on expectations both of them can name.
You do not need to solve everything in one meeting. You do need to leave with a shared understanding of the gap and a clear next step. The right follow-up depends on the situation. A fixed timeline is not fair or useful in every case, and company processes may apply.
If you are the manager, notice what you are waiting for. A better moment? A script that guarantees no one feels bad? More certainty than the situation can provide?
You may need to prepare more. Or you may be asking preparation to do something it cannot: remove the discomfort from telling another person where things stand.
Make the conversation specific, fair, and open to what you do not yet know. Then have it. Your employee cannot respond to a problem you have not named.
How do you talk to an underperforming employee?
Describe the observable pattern and its impact, then ask what may be contributing to it. Clarify expectations and agree on an appropriate next step.
What if the employee gets defensive?
Stay with specific examples and give them room to respond. Listen for context without abandoning the issue you need to address.
When should you consider a formal performance process?
Follow your organization’s policies and consult the appropriate people. A formal process may be warranted, but it should not substitute for clear expectations or a fair understanding of the situation.
