How to give difficult feedback: 8 scripts for managers

Most managers know the theory of feedback. The problem is the first sentence. The moment arrives, the words are not there, and the conversation is postponed to a day that never comes, until the problem is big enough to need HR. This guide gives the first sentence for eight situations, plus the structure that stops the conversation going wrong after it.

The structure: four sentences

Every script below follows the same four moves, which you can learn once and reuse.

1. The specific observation. What happened, when, and what you saw. Not a pattern, not a character trait, one concrete instance. "In Tuesday's client call you said the feature would ship Friday" rather than "you keep over-promising".
2. The impact. What it caused, for whom. "The client has now planned their launch around it and engineering says it is two weeks away."
3. The ask. What you want to be different, specifically. "Before you commit a date to a client, check it with the engineering lead."
4. The question. Hand the conversation over. "What is your read on it?" or "What was going on from your side?"

Then stop talking. The silence after the question is where the useful part of the conversation happens. Most managers fill it, usually by softening what they just said.

The eight scripts

1. Repeated lateness

"I want to raise something small before it becomes a pattern. You have come in after 10:30 on four of the last six days. The 10 o'clock standup is where the day gets planned, and the team is starting without you. I need you at standup on time. Is something going on that I should know about?"

2. A missed deadline

"The report was due to me Monday and I got it Wednesday evening. I had committed to the client for Tuesday, so I had to go back to them. When you see a date slipping, I need to hear about it the day you know, not the day after it passes. What happened on this one?"

3. Work quality

"I went through the three pull requests from last week and two had the same class of bug we discussed in July. Each one cost the reviewer an hour and shipped late. I need you to run through the checklist we agreed before marking a PR ready. Is the checklist the problem, or is something else getting in the way?"

4. Attitude in meetings

"In the planning meeting today, when Priya proposed the new onboarding flow, you said 'that will never work' and moved on. She stopped contributing for the rest of the meeting, and two other people noticed. I need disagreement in that room, and I need it to come with a reason and an alternative. Can you tell me what you were reacting to?"

5. Personal hygiene or dress

This is the one managers avoid most and the one where directness is kindest. "This is awkward to raise and I would rather say it than have you hear it from someone else. There have been a couple of comments about body odour in the shared space. I am telling you privately so you can deal with it. Is there anything I can help with?"

Keep it to that. Do not explain, do not repeat it, and do not mention who commented.

6. Over-promising to clients

"On the call with Acme you committed to a Friday delivery. Engineering estimates two weeks, and the client has now planned around Friday. Before you commit a date externally, I need you to confirm it with the engineering lead, even if it means saying 'I will come back to you tomorrow'. What made Friday feel safe to say?"

7. Taking credit or not sharing it

"In the leadership update you presented the dashboard as your work. Rahul built the data layer, and he was in the room. I need the team's work credited to the team when you present it; it is also how you build the goodwill you will need from them. Did you see it differently?"

8. A strong performer who is coasting

"Your work is still good, and I want to say that first. In the last quarter it has also been safe: the same kind of task, done well, nothing you have not done before. I think you are capable of more and I do not want you to get bored here. What would you want to take on if you could choose?"

Before the conversation

Pick a time within a day or two of the incident, in private, and tell the person what the meeting is about when you book it: "I want to talk about the Acme call." Surprising someone with difficult feedback in a meeting they thought was about something else damages trust more than the feedback itself. Rehearse the first two sentences out loud. Decide what you will do if the person cries, gets angry or goes silent: in all three cases, pause, acknowledge it, and return to the ask.

Check whether the issue belongs to you at all. Anything that touches harassment, discrimination or a medical condition is not a feedback conversation; it is an HR process, and our first-time manager guide sets out when to hand over.

After: the two-line note

Within a day, send a short written recap. It is not a warning letter; it is a record that protects both of you and makes the next conversation start from a shared memory.

Hi [Name], thanks for the conversation today. To recap: we discussed [the issue, one line], and we agreed [the change, one line] from [date]. We will check in on it in our 1:1 on [date]. Let me know if I have captured anything wrongly.

File the note in your running 1:1 document for that person. If the behaviour recurs after two such conversations, the next step is a formal written warning, and our guide to warning letters and show-cause notices covers that process. Most of the time it never gets there. The behaviour changes after the first clear conversation, which is the whole argument for having it early.

What not to do

Do not sandwich the feedback between two compliments; people hear only the compliments. Do not say "some people have mentioned" when you mean "I noticed"; anonymous sourcing makes the person defensive and paranoid about the team. Do not deliver it in chat. Do not give three pieces of difficult feedback at once; the person will remember the harshest one and nothing else. And do not wait for the performance review. Nothing in a review should be heard for the first time there.