Black Friday: 20% off everything 0d 00h 00m 00s Shop the sale →

How to Give Difficult Feedback to an Employee (and Stop Putting Off the Conversation)

Illustration from the Feedback card in The Leader's Toolkit: a manager talking, with a feedback loop in a speech bubble

There's something you need to say to someone on your team. You've known for a few weeks. You've hinted at it once, maybe twice, and it didn't land. Each week you don't say it, it gets harder: the examples pile up, you get more irritated, and the conversation you're imagining gets bigger.

Most difficult feedback isn't difficult because of the words. It's difficult because of the waiting. This guide covers why managers put it off, how to prepare so the conversation is short and clear, what to do when the person gets defensive, and how to follow up so it actually changes something.

If you want the basics of feedback first, with a step-by-step model and worked examples, start with our guide to giving constructive feedback. This article is about the one you've been avoiding.

Why you keep putting it off

Be honest about which of these is stopping you. Each one has a different fix.

What you tell yourself What's usually going on What helps
"It's not a big enough deal yet." You're waiting for a bigger example so it feels justified. Small and early is easier for both of you. Say it now, while it's still small.
"They're a good person. I don't want to upset them." You're treating feedback as a judgement of them, not of the work. Write the behaviour, not a label. Then it's about the work.
"They'll get defensive." You're expecting an argument you haven't prepared for. Prepare for the reaction as well as the message (see below).
"I'm not sure I'm right." You might not have enough facts. Check before you speak. Then say what you saw, not what you heard.
"I've already mentioned it." You hinted, and hints sound optional. Say it once, plainly, and agree what happens next.

The cost of waiting is real, even if nobody mentions it. One first-time manager on r/managers wrote that they'd tried to "protect" a struggling report by softening feedback and ratings. Their advice to other new managers was that it only made things worse later, for the employee and for them.

Before the conversation: prepare with the Feedback card

The Feedback card in The Leader's Toolkit is built for this step, and it's for preparing, not for reading out in the meeting. It asks you three things:

  1. Who needs to hear something you've been softening or putting off? Write the behaviour or result, not a label for the person.
  2. What will you say, when, and how will you check it landed? Practise the opening sentence out loud before you go in.
  3. Afterwards: how did they respond, and what will you follow up on?

In practice, that means writing down four things before you book the time:

  • What you saw. Two or three specific, recent examples with dates. "The last three client updates went out without the figures checked" can be acted on. "You're careless" can only be argued with.
  • Why it matters. The effect on the client, the team or the work, in one sentence.
  • What good looks like. If you can't describe it, they can't hit it.
  • Your opening line. Something like:

"I want to talk about the client updates. The last three went out without the figures checked, and the client noticed on Tuesday. I need that to change, and I'd like to hear what's getting in the way."

Say it out loud once. Most managers soften the message at the opening until it means nothing ("It's probably nothing, but..."). If you've practised the line, you're more likely to say it as written.

Check your facts first. One of the most discussed r/managers threads of the past year came from a manager who'd put someone on a performance plan based on a stakeholder's complaints, then found out the complaints had been made up. In the follow-up post, the writer said the stakeholder had admitted it. If the feedback isn't something you saw yourself, verify it before you deliver it, or deliver only what you can stand behind.

Give it directly. Another widely upvoted post argued that managers should take an issue to the person themselves rather than escalate it, unless they're prepared for a much blunter response from above. Going around someone feels easier. Usually, it isn't.

In the room: say it once, then listen

Book time in private, not the last five minutes of a 1-1. Then keep it simple:

  1. Say your opening line, with the examples. Then stop talking.
  2. Ask for their view. "How do you see it?" or "What's been going on?"
  3. Listen properly. This is where most difficult conversations are won or lost.
  4. Agree what good looks like, and one or two next steps.
  5. Set a date to check in, and put it in both calendars.

Don't bring a script and read from it. You've done the thinking beforehand, so in the meeting your job is to listen. That's what the Active Listening card in The Leader's Toolkit prepares you for: think beforehand about whether you tend to interrupt, fix or half-hear this person (it's often the person you think you already understand), and plan to ask more and fix less. Repeating back what you think they meant ("So the figures come in late from finance, and you've been sending without them to hit the deadline?") shows you've heard them, and often brings out the real cause.

When they get defensive

Defensiveness is the reaction managers dread most, and it's what most of the threads on this topic are about. One manager described a hardworking senior employee who answered every piece of feedback by citing praise from previous managers, even though the feedback was tied to specific examples. Another described a direct report who argued with the wording of every feedback conversation or blamed the client. A third described a young employee who shut down completely whenever feedback came up.

A few things help, whatever form it takes:

  • Don't argue about the label. If they object to "careless", you've given them a label to fight. Go back to the examples: "Let's leave the word aside. These three updates went out unchecked. Can we agree on that?"
  • Let the first reaction pass. People often push back first and think second. Acknowledge it ("I can see this is frustrating to hear") and pause. You don't need to win the moment.
  • Separate the facts from the explanation. You can listen to why it happened without agreeing it was fine. "That makes sense, and the updates still need to be checked before they go out."
  • If they shut down, slow down. Ask one open question and wait. If it's clearly not going anywhere, agree to pick it up tomorrow, and do it.
  • If it escalates, end the meeting calmly. Raised voices or accusations are a reason to stop, write down what happened, and speak to HR about the next step.

One pattern worth noticing: when every conversation turns into a debate about wording or whose fault it was, the issue is no longer the original feedback. It's that they won't accept feedback at all, and that becomes the thing you need to raise.

The feedback that's hardest of all: they're doing the job well

Not all difficult feedback is about poor work. An r/Leadership post described the hardest feedback the writer ever gave: it was to a senior engineer whose work couldn't be faulted, but who took over pairing sessions, rewrote colleagues' work without asking and answered questions meant for others. Nobody wanted to work with him.

When the work is good but the behaviour isn't, the same rules apply, and they matter more:

  • Name the behaviour and its impact on others. "In the last two code reviews you rewrote Sam's changes without asking. He's stopped asking you questions."
  • Say what you value as well, and mean it. The point is to keep their strengths and change one pattern, not to criticise them in general.
  • Agree one specific change, not "be more of a team player".

If this is about someone whose results are strong but who's damaging the team, our post on dealing with toxic team members goes further.

After the conversation: follow up, then coach

The conversation is only the start. What changes things is what you do next:

  • Write a short note the same day. What you discussed, what good looks like and the check-in date. It isn't a warning. It makes sure you both heard the same thing.
  • Keep the check-in date. If you don't, the message is that it didn't really matter.
  • Coach, don't repeat. The Coaching card in The Leader's Toolkit is for the follow-up: help them find the answer rather than handing them yours. Ask what's working, what's still getting in the way and what they'll try next. Notice the urge to solve it for them.
  • Notice improvement out loud, and quickly. If they've changed, say so specifically. That makes it stick.

It's normal to feel bad afterwards, even when it went well. One r/AskManagers thread asked whether other managers feel awful after giving bad feedback, especially to someone who takes it well and tries hard. Feeling bad doesn't mean you did it wrong. It usually means you care how it lands, which is a good sign.

When it's really an underperformance problem

Sometimes one conversation isn't enough. If you've given clear feedback, agreed what good looks like, followed up and nothing has changed, you're no longer dealing with a feedback problem. You're dealing with underperformance, and that needs a plan.

That's what the Dealing with an Underperformer Blueprint in The Leader's Toolkit is for: name exactly what's falling short (work, behaviour, dates), decide what conversation you'll have and what support or consequence you'll make clear, and decide what happens next and by when. Our guide on how to deal with an underperforming employee walks through it, including when a formal plan makes sense.

Situations you'll recognise

These threads inspired this guide. The replies are worth reading in full:

  • The new team lead whose first critical feedback went badly (r/managers). The person got defensive, the conversation went nowhere and things felt awkward afterwards. Next time: a practised opening line, then more listening, and a follow-up date set before you leave the room.
  • The employee who makes repeated mistakes and shifts the blame (r/AskManagers). The writer had tried gentle coaching and process fixes and felt it was time for a formal conversation. That's the point where the Dealing with an Underperformer Blueprint takes over from the Feedback card.
  • The manager whose corrections turn into lectures (r/AskManagers). Written from the employee's side: a quick, direct correction would land better than a long explanation that feels like being parented. Say it once, then ask.

Mistakes that make it worse

  • Hinting. "Maybe have another look at this" sounds optional. If it isn't optional, don't make it sound that way.
  • The feedback sandwich. Burying the message between two compliments teaches people to brace when you praise them. Give praise separately, and often.
  • Saving it up. Ten examples at once feels like an ambush. Two recent ones feel like feedback.
  • Talking too much. The longer you explain, the more it sounds like a lecture. Say it, then ask.
  • No follow-up. Without a check-in date, nothing changes, and both of you know it.

The cards for this conversation

These cards from The Leader's Toolkit are for the work before and after the conversation, not for reading out in the meeting:

  • Feedback: before. Name what you've been softening, write the behaviour (not a label) and practise your opening line.
  • Active Listening: before. Plan how you'll listen instead of fixing or interrupting.
  • Coaching: after. Follow up with questions, not more instructions.
  • Dealing with an Underperformer (Blueprint): when one conversation isn't enough.

The Leader's Toolkit has 52 tools on 54 cards for the conversations managers put off, and over 6,000 copies have been sold.

Frequently asked questions

How do you give difficult feedback to an employee?

Prepare first: write two or three specific, recent examples, the impact and what good looks like, and practise your opening line. In a private meeting, say it once, plainly, then ask for their view and listen. Agree one or two next steps and a check-in date, and send a short written summary the same day.

How do you give negative feedback without hurting someone's feelings?

Describe the behaviour or result, not the person. "The last three updates went out unchecked" is easier to hear than "you're careless". Be direct rather than vague, give it in private and soon after it happens, and make clear you're there to help it improve. Some discomfort is normal. Being clear is kinder than being vague.

What do you do when an employee gets defensive during feedback?

Don't argue about labels or wording. Go back to the specific examples, acknowledge the reaction and let it pass. You can listen to their explanation without agreeing the outcome was fine. If they shut down, slow down or agree to continue the next day. If it escalates, end the meeting calmly and speak to HR.

Should you use the feedback sandwich?

Usually not for difficult feedback. Wrapping criticism in praise tends to hide the message and makes people wary of praise. Give the difficult message plainly, and give genuine praise separately and often.

What if the feedback doesn't change anything?

Check in on the date you agreed. If nothing has changed after clear feedback, agreed expectations and support, treat it as underperformance: set a specific plan with what better looks like, by when, the support you'll give and what happens if it isn't met. Involve HR before any formal step.