How to tell an employee they're not meeting expectations (with scripts)

The hardest part of telling someone they're not meeting expectations is usually the timing, not the words. Most of these conversations happen weeks late. By then the frustration has built, the examples have piled up, and what could have been one light sentence has become a meeting nobody wants.

This guide covers how to have the conversation early and clearly, with scripts you can adapt for each step.

Before the conversation: get specific

Vague concerns produce vague conversations. Before you say anything, write down:

• One or two concrete, recent examples. "The Q3 forecast went to the client with last month's numbers," not "your work has been sloppy."
• What you expected instead. If you can't describe what good looks like, they can't hit it. Sometimes this step reveals the expectation was never clearly set, and that's worth knowing before you start.
• Why it matters. The effect on the client, the team or the work, in one sentence.

The conversation, step by step

1. Open with the observation, not the verdict

"I want to talk about the client updates. Tuesday's came in after the call, and the two before that did too. I need them the day before so I can prep. What's making that hard?"

It's specific, it names the expectation, and it ends with a real question.

2. Listen for the context you don't have

Sometimes there's a reason: unclear priorities, a blocker on another team, something going on at home. Sometimes there isn't. Either way, you need to hear it before deciding what the gap means.

3. Agree on one change and a date

"So from next week, the update lands by end of day before the call. Let's check in on the 15th and see how it's going."

One change, one date. Then send a two-line summary so you both remember the same thing.

4. If it keeps happening, get more direct, one step at a time

Don't jump from a friendly mention to a formal warning. Turn it up gradually. This is the Accountability Dial™:

Stage	When	What it sounds like
Mention	The first time	"I noticed the update came late. What happened?"
Invitation	It repeats	"This is the third late update. I'm curious what's going on."
Conversation	It continues	"When updates are late, I go into client calls blind. I want to talk about that."
Boundary	Still not changing	"I need updates by end of day before every call. Can you commit to that?"
Limit	The boundary isn't held	"We've talked about this four times. I'm moving the client updates to someone else."

Most gaps close at the first or second stage, as long as the first conversation happens early.

When they push back

If they disagree, don't argue the record. Acknowledge it, restate the example once, and ask what they see differently:

"I hear that it feels unfair. Here's what I saw on Tuesday. What am I missing?"

You don't need them to agree in the room. You need a clear expectation and a next step.

Common mistakes

• Waiting for the review. By then it's a pattern with months of history, and it lands as a surprise.
• The compliment sandwich. It blurs the message. Be kind and clear instead.
• Talking about character. "You're not committed" can only be defended against. "The last three deadlines slipped" can be fixed.
• No next step. A conversation without an agreed change and a date usually just repeats.

Where Ren helps

Ren works in Slack and Microsoft Teams. It notices when a pattern like this is forming, suggests which stage of the Dial a situation is really at, and helps you find the first sentence in your own words, before it becomes a big conversation. You can try it free.

---

Related: Preparing for a tough 1:1 with an underperformer · How to give feedback to an employee · Accountability Dial feedback templates · Ren vs. Lattice