A script can help you start a hard performance conversation. It cannot make the conversation safe from discomfort, disagreement, or the possibility that you have misunderstood something.
That is often what managers are hoping a script will do.
You know the work is falling short. You keep drafting the meeting invitation, then deleting it. Maybe you tell yourself you need more data. Sometimes that is true. Expectations may have been unclear, or the workload may be unreasonable. You should understand those things before deciding what the problem means.
But sometimes “I need more data” is a way to postpone the moment when another person might react to what you have to say.
In this scenario, three deliverables have been late over six weeks, and one report did not meet the required standard. Those facts are a reason to talk. They are not, by themselves, a complete explanation of why the work is slipping.
The manager’s first draft might sound like this:
“I wanted to check in and see how things are going. I know there’s been a lot lately. I’ve noticed a few things slipping, and I wanted to get your take.”
There is nothing wrong with asking how someone is doing or inviting their perspective. The trouble is that “a few things slipping” does not tell the employee what you mean. A kind tone cannot make a vague concern clear.
Try beginning with the work you can point to:
“I want to talk about the last six weeks. Three deliverables came in late, and the Mitchell account report did not meet the quality standard we need. I want to understand what is getting in the way and agree on what needs to change.”
That is a starting point, not a verdict. It names what happened, gives the employee a chance to respond, and makes clear that the conversation is about a performance gap. If your examples are incomplete or the expectation was never clear, you need to hear that. If workload, resources, or a personal circumstance is part of the picture, that matters too.
Listening does not require you to pretend the work is fine. And naming the work does not require you to decide, before the conversation, that you already know the whole story.
This is where a script helps: not by controlling the employee’s reaction, but by keeping you from retreating into language so soft that the actual issue disappears. Write down the specific examples and the change you need. Read your opening aloud. Remove the hedging that obscures the point, but keep the invitation to understand context.
You may still feel uneasy. The employee may be upset, or they may disagree with your account. You might learn that you contributed to the problem by giving unclear direction or changing priorities. There is no sentence that prevents those possibilities.
That is the part a script cannot do for you. It cannot remove the risk of being misunderstood, being challenged, or having to revise your own view. It can only help you stay present enough to say what you know and listen for what you do not.
If the work is not meeting expectations, do not make the employee guess what you have noticed. Prepare carefully. Be specific. Then have a conversation, not a performance of certainty.
