How to give negative feedback to an employee (with a scored example)
Written by Toby Sinclair
Updated
Key takeaways
Name a pattern with examples, not a mood you have been in.
Do not bury the message under so much balance that they miss it.
Hold the line when they shift the blame.
Leave with actions and a date, or you had a chat, not a review.
No sign-up · about 5 minutes · you’ll need a mic
Open with the performance pattern, not a tour of their strengths. Use two or three behavioural examples from the quarter — what happened, what was expected, what it caused. Balance is allowed. Burial is not. When they blame workload and other teams, acknowledge constraints, then return to what they own. End with actions, owners, and dates. If the message could still mean “you are doing fine,” you have not given the feedback.
1. Negative feedback is a pattern, not a mood
A slipped quarter is not “I have a bad feeling.” It is missed forecasts, late reviews, customers who waited, a standard you named in January that did not show up in June. Bring the examples. Dates and artefacts beat adjectives. “You seem less engaged” invites a debate about your perception. “The Friday pack has missed the noon send three times, and sales walked into the QBR without the numbers” is something you can manage. If you have not collected the examples, you are not ready for the meeting.
2. Balance without burying the message
You can say what still works. You cannot use it as a trapdoor. The sandwich — praise, knife, praise — teaches people to wait for the last sentence and ignore the middle. Try sequence instead: the pattern, the examples, the impact, then what remains true about them, then the plan. They should be able to repeat the problem in one sentence when they leave. If they leave thinking the meeting was a pep talk, you were kind to yourself, not to them.
3. Blame-shifting is a test of whether you hold the line
Workload is real. Other teams are real. Your job is to separate constraint from ownership. “I know delivery was late from engineering. You still own the customer update, and it did not go.” That sentence is the job. If you accept the full transfer of blame, you have just agreed that this person cannot be managed. If you deny every constraint, you look unfair and they stop listening. Practise the split: yes to the context, no to the disappearing act.
4. Collect the quarter before you book the room
If you only have a feeling, you are not ready. Pull the Friday packs, the missed send times, the customer updates that did not go, the standard you named in January. Two or three examples are enough. Ten is a dumping. Book a private meeting with a name that does not lie — “performance this quarter,” not “a quick catch-up.” Have the actions you want already drafted so you do not invent them under emotion. A slipped quarter that waits for the annual review becomes a verdict. This meeting is supposed to be management while there is still time.
5. The recap is part of the feedback
People remember tone and forget examples. Send a short written note the same day: the pattern, the two or three artefacts, the ask, the dates, and when you will look again. That is not a disciplinary letter unless your process says it is. It is how a conversation becomes a standard. If they later say “I thought I was doing fine,” you will both be able to point at the same paragraph. Softening the email after you were clear in the room is how the message dies the second time. If they send a long defence overnight, reply to the actions and the dates, not to every line of the defence. The recap is the record. A debate in email is how the pattern disappears again.
6. If they ask whether this is a formal warning
Answer the question you were asked. If it is not a formal process yet, say so, and say what would make it one — usually the same pattern after the dated review. If it already is, do not hide behind “just a chat.” Ambiguity here is how grievances start. People can take hard news. They cannot take a process they only discover in writing a week later.
Mistakes that waste the only meeting that mattered
Saving it for the annual review. Doing it in passing at the end of a standup. Listing ten issues so none of them is actionable. Setting actions without dates. Softening live because they look upset, then writing a harsher email later. The email is not courage. The room is. Practise staying in the example when they redirect. The quarter already slipped. The only thing left to lose is clarity.
What to say
Pattern, examples, ownership, dated actions. Balance after the message, not instead of it.
You
I need to talk about follow-through this quarter. We missed another release window this morning, and it is the third time the Friday pack has been late.
You
I know the on-call load is real. Updating QA and status is still part of the role, and it is not happening.
You
I need you to own those hand-offs from today. We will review the next three Fridays together. The standard is not changing.
If they say this
They say
“I was up all night on-call. Why is the sign-off the headline?”
You say
“The night is real. The headline is a pattern — this morning and the last few sprints — not one tired day.”
Context can sit in the room. It cannot retire three examples.
They say
“If people looked at what I am juggling, they would understand.”
You say
“I am looking at it. We can talk about scope. We are still talking about the hand-offs you own.”
Scope is management. It is not a reason to skip the examples.
They say
“I cannot promise it will get better next week.”
You say
“Then we need a plan that is honest about capacity, and we still need the next three Fridays owned. “I cannot promise” is not a close.”
A shrug is not an action. Stay until there is a date or a scope change.
Follow-up email
Same-day recap. Examples, ask, dates. No sandwich.
Hi Emily, Following today’s conversation: we missed the release window this morning, and the Friday pack has been late three times this quarter. I need you to own QA updates and status hand-offs from today. We will review the next three Fridays together. The standard is not changing. If the workload needs a scope conversation, we can have that — it does not replace the examples. Toby
Example attempt transcript
A scored example of this conversation — with what worked, and a mistake that is not recommended.
Emily Carter
Hi. You wanted to talk?
Line Manager
I do—Emily, we missed another release window this morning, and I need to talk about the follow-through over the last few sprints too.
What worked
The pattern arrived with today’s example. This morning plus the last few sprints. That is a line you can hold. A vague “I’ve been a bit worried about your performance” is a mood they can talk you out of.
Emily Carter
Honestly, I’d already been up all night on-call. I can’t keep up with all the noise from platform and product. But the sign-off thing—I don’t know why that’s the headline right now.
Line Manager
I get that there’s pressure coming from all sides, but updating QA and status isn’t optional—it’s part of your core role.
Emily Carter
That’s fair, but if people actually looked at what I’m juggling… I just can’t promise it’s going to get better next week.
Line Manager
We’ll work on what’s realistic, but expectations aren’t changing—I need you to own those hand-offs, starting today.
A common mistake
“I know it's been a lot — let's just try to do better and see how next week goes.”
That’s not recommended. Holding the line still needs a date. She heard the standard. She did not hear what “own those hand-offs” looks like by when. Without an action and a follow-up, this is a chat they can file under pressure.
Emily Carter
Okay. I hear you.
This example scored 74 / 100.
No sign-up · about 5 minutes · you’ll need a mic
Frequently asked questions
How soon should I give negative feedback?
What if they cry or get angry?
Should this be documented?
What if the workload really is impossible?
When does this become a formal process?
Related conversations
Explore more conversations
Reading about it is the theory test. Practising it is the driving test.
No sign-up · about 5 minutes · you’ll need a mic
Written by Toby Sinclair, founder of Real Talk Studio. Updated 15 August 2026.