The reaction itself is often not the part that goes wrong when an employee cries, argues or goes quiet in a performance review. What goes wrong is what the manager does with the feedback in the next ten minutes. Some managers drop it, because carrying on feels cruel. Some soften it until it no longer says what it was meant to say. Others push straight through as if nothing had happened. That gets the words said, but it leaves the person in no state to hear them.
This post goes through those three reactions one at a time: tears, arguing and silence. You’ll find what to say for each one, what to avoid saying and what to do if your first response doesn’t work. After that comes a way to decide whether to pause, carry on or reschedule. Last is the short email to send the same day, so the employee has the conversation in writing once the emotion has passed.
It’s written for a scheduled review, where you planned what to say and the reaction is the surprise. If a colleague gets heated in an ordinary conversation you didn’t plan, that’s a different situation. The moves for it are in our guide to de-escalation techniques at work.
What has to be said today, and what can wait
It helps to settle one thing before you get to any of the three reactions, because it decides most of what follows. The reaction and the message are two different things, and you handle them separately.
The message is what the review exists to deliver, and some of it has to be said in this meeting. That part is the outcome. It means the rating and any pay decision that follows from it. It also means saying whether there’s a formal improvement plan (or just as importantly, that there isn’t one). Those are the things the employee will go home and think about. The worst version of their evening is the one where they suspect a bad outcome but nobody has actually told them. The rest can be finished later in the day or the next morning without anyone losing anything. That includes the detail behind the rating, the examples and the conversation about what to work on next year.
Why not drop the hard part when someone is upset? Because a softened review doesn’t stay soft. The rating still goes into the system, so the employee finds out later from a form what you couldn’t say to their face. Jana Tulloch is quoted in a SHRM article on emotional performance reviews by Kathy Gurchiek, and she described the balance like this: “The one thing I’ve learned is that it is important to be supportive and empathetic but firm.” Firm here means the content stays the same, though your tone and your pace can change as much as the person needs. That’s the hardest part of constructive feedback to do under pressure. You have to keep what you say intact while the person in front of you is struggling with it.
There’s also a reason to keep that content pointed at the work rather than at the person. In a large review of feedback research published in Psychological Bulletin in 1996, Avraham Kluger and Angelo DeNisi pooled 607 effect sizes from studies covering 23,663 observations. They were looking at what they call feedback interventions, which simply means any time people are given information about how they performed. Feedback helped on average, but they found that “over 1/3 of the FIs decreased performance.” (FIs is their abbreviation for feedback interventions.) Their explanation for when it backfires was that “FI effectiveness decreases as attention moves up the hierarchy closer to the self and away from the task.” That means feedback about what someone did is more likely to help, while feedback that turns into a judgment about who they are is more likely to hurt. The study wasn’t about crying or about reviews, so it doesn’t tell you what tears do to performance. It’s still a good reason to keep every line you say in an emotional review about the work, and every line you write afterwards too.
The reaction can’t be ignored either. Deborah Grayson Riegel is direct about this in Harvard Business Review: “Regardless of the reason, as a manager, you shouldn’t ignore or diminish the tears, even if they make you feel uncomfortable.” The same goes for anger and for silence. Laura Putnam is quoted in a SHRM article by Natalie Kroc saying that emotions which aren’t dealt with “don’t go away. They just go underground, to the detriment of everybody.”
So you keep the message and you respond to the person. What that looks like is different for each reaction. Once you’ve seen all three, there’s a simple rule for when to stop.
When an employee cries during a performance review
You’ll probably feel a strong urge to make it stop when someone starts crying partway through a review. You might rush to comfort them, or you might carry on as if you hadn’t noticed. Neither helps. The first move is to acknowledge what’s happening, in a few plain words, without guessing why.
Riegel’s advice is specific about what to avoid at this point: “Don’t try to interpret your employee’s emotions, tell them what to do, or judge them.” So you don’t say “I can tell you’re really hurt by this,” because you don’t know what the feeling is. It could be hurt or frustration, or it could be exhaustion or something else entirely. You name what you can see and nothing more: “I can see this is hard to hear. Take your time.” That line works because it’s true and it doesn’t assume a cause. It also tells them they aren’t being rushed. After that, stop talking for a moment and let them have it.
Next, give them a choice. You might say: “We can take ten minutes and come back to this, or we can keep going. Whichever is better for you.” The choice matters because crying in front of your manager can feel like losing control of the situation, and being asked what they want hands some of that control back. It also follows the last part of Riegel’s advice: “Whatever you choose to say, the key is to be clear, understanding, and ultimately allow the person to tell you what they need.” Some people want to get it over with, while others need to step out and come back. You can’t tell which by looking at them, so ask.
A few things are worth not saying, even though they come out easily. The first is reassurance that undoes the message, something like “Honestly, it’s not as bad as it sounds.” If the rating stands, that line is either untrue or confusing, and the employee may hold you to it later. The second is a guess at the cause, such as “Is everything okay at home?” asked in the middle of a rating discussion. It’s kindly meant, but it turns their tears into a topic and pulls the conversation somewhere they didn’t choose to take it. (If they bring up something outside work themselves, that’s a different situation and it’s covered further down.) The third is anything that tells them to stop, like “There’s no need to get upset.” It tells them their reaction is the problem, and asking someone to stop crying rarely makes them stop.
When you pick back up, whether that’s after two minutes or after a break, go back to one specific point rather than the whole review. Matt Franks is also quoted in the Gurchiek piece, and he put it simply: “Be empathetic, but do stick to the facts and keep it professional.” A good way back in is to name where you were and ask: “We were talking about the June launch. Is it all right if I finish that point?” Asking sounds like a small thing, but it shows you noticed what happened and that you’re still going to be straight with them.
Sometimes the tears don’t settle, and carrying on starts to feel like pushing someone through something they can’t take in. The Kroc article suggests a practical option: “If the outburst continues for an extended time, suggest a change of scenery. Encourage the employee to go for a walk or take a break and offer to come along.” The offer to come along is the important part, because it tells them they aren’t being sent out of the room. Talking while walking can also be easier than talking across a desk.
When they argue with the review
Arguing is the reaction that’s easiest to handle badly, because it can feel like a challenge to your authority. The instinct is to defend the rating line by line. The way through is slower than that, and it’s easiest to show with an example. The one below is illustrative: Bridget and Declan are composites, not real people.
Bridget manages a customer onboarding team, and Declan has led client launches for her for two years. This year she’s rating him below expectations on delivery. That’s mainly because two launches went live late: the March one by three weeks and the June one by two. His client feedback has been strong, and the review says so. Bridget gives him the rating in the first five minutes, as she planned to, and Declan’s answer comes straight back: “That’s not fair. March wasn’t on me, and this is the first I’ve heard that delivery was a problem.”
That reply packs three different complaints into two sentences. How Bridget answers depends on which one she’s dealing with, so it helps to slow down.
Her first job is to show she’s heard him without giving the rating away. The obvious line is “I hear you, but…” That’s the one to avoid, because most people hear the “but” as cancelling whatever came before it. Instead she acknowledges his view and holds her own in the same breath: “I can see why you’d see it that way, and I don’t see it the same way yet. Let’s go through it, because you’ve raised a few different things.” The word “yet” is doing honest work there. She hasn’t decided he’s wrong about March, and she isn’t pretending she has. The de-escalation guide calls this move acknowledging without conceding and goes into it in more detail.
Work out what they’re actually arguing about
An employee who argues with a review is usually arguing about one of three things, and each one needs a different kind of answer.
The first is the facts. Declan says March wasn’t his fault. That’s a factual claim, and he might be right. Managers miss things, especially across a whole year, and a review built on a wrong fact should be corrected. So a factual challenge gets a factual answer: what you saw, where it came from and an honest admission if you aren’t sure.
The second is the judgment. Even if every fact is agreed, Declan might think two late launches out of nine don’t add up to “below expectations.” That’s a disagreement about the rating, and he’s allowed to have it. But a review isn’t a negotiation unless your company’s process says it is. So the answer here is to explain how you got to the rating rather than argue the number up and down. Bridget might say: “Two late launches in a year where the target was none is why I’ve rated delivery the way I have. I know you’d weigh it differently, and you can say so on the review.” That last sentence matters because it gives his disagreement somewhere to go other than the next twenty minutes of the meeting.
The third is fairness: “this is the first I’ve heard of it.” This one deserves a straight look, because sometimes it’s true. If Bridget never raised the late launches with him during the year, Declan has a point. The honest response then is to own it: “You’re right that I should have raised it after March instead of saving it for today. That’s on me.” Saying so doesn’t change the rating because the launches were still late. But it often changes how the rest of the conversation goes, because it’s easier to hear the parts you disagree with once a fair point has been admitted. If you did raise it during the year, say when. Say it calmly and without any “I told you so”: “We talked about the March date in our April one-on-one. I don’t think I was clear enough about how much it mattered.”
When they bring something you hadn’t seen
Declan then says something Bridget didn’t know. He says he emailed the data migration team in February and copied the program manager. He warned them that their delay would push the March launch back, and nobody replied.
This is the branch where it’s easy to go wrong, because the manager feels put on the spot and wants to settle it there and then, one way or the other. Don’t. You can’t check an email thread in the middle of a review, and anything you decide in the room will be a guess. The better move is to take it seriously, then say what you’ll do and give a day: “I didn’t know about that, and it matters. Can you forward me the thread? I’ll read it and come back to you by Thursday. If it changes the picture for March, I’ll take it back through our review process.”
Each part of that line has a job. “It matters” tells him the point has landed. Asking him to forward the thread puts the evidence in writing. The day stops “I’ll look into it” from quietly turning into nothing, which is what an employee may fear that phrase means. The phrase “through our review process” promises a route rather than a result, so Bridget can keep it whatever the email says. If your company doesn’t have a formal way to revisit a rating, say what you can actually do instead. That might be raising it with your own manager or with HR.
When the argument goes round in circles
Sometimes you’ve acknowledged the point, answered it and offered a route. Even so, the same argument comes round again a little louder each time. At that stage answering it again rarely helps. The employee probably isn’t asking for information any more. What they want is for you to change your mind, so hearing your reasons a third time sounds to them like you aren’t listening.
The way out is to name the loop without turning it into an accusation. Bridget might say: “I think we’ve each said where we stand on the rating, and going over it again isn’t going to change either of our minds today. Your disagreement matters, so I’d like it on the record properly.” After that she points to where it can go: “You can add your own comments to the review, and they’ll be kept with it. If you want to take it further, HR can tell you what the options are.” Those words describe a route that exists at Bridget’s company, so if yours doesn’t have one, don’t invent it. Say instead that you’ll write his disagreement into your notes from the meeting, which you should do anyway.
Bridget is also careful about what she leaves out. She doesn’t threaten (“if you keep pushing this, it won’t look good”), and she doesn’t hint that the rating might move if he goes to HR. Both of those turn a disagreement about a rating into a contest about power, and he’ll remember that long after he’s forgotten the rating.
If voices are rising and it’s turning into a shouting match, stop the review. You’re no longer in a disagreement you can work through, and the pause rule further down covers what to do next.
What not to promise in the room
When someone is arguing hard and you aren’t sure of every fact, the most tempting thing to say is “Let me see if I can bump that up.” Don’t say it. Don’t change a rating on the spot either, even if you suspect they’re partly right.
There are two reasons. The first is that it teaches the employee that the way to change a rating is to argue loudly enough in the meeting, and anyone they tell learns the same thing. The second is that it’s unfair to everyone else you reviewed this cycle, especially the people who took a hard rating quietly and didn’t push. If a rating really is wrong, it should change because you checked, and it should go through the same process as everyone else’s.
So Bridget ends the meeting without promising anything about the rating, but with a clear promise about the thread: she’ll read it by Thursday. As it turns out, Declan is partly right. The February email is real, and the migration delay accounts for about two of March’s three late weeks. But the June launch was late for reasons that were his. Whether that’s enough to move the rating is a question for the review process, not for the meeting where he raised it.
If arguing with feedback is a pattern with someone rather than a one-off, that’s worth handling as its own subject. Our guide to handling defensive behavior in the workplace covers the longer-running version.
How does your feedback land? A lot of what happens in a review depends on how clearly the message was put in the first place. The free constructive feedback assessment takes about five minutes and shows where your feedback is clear and where it tends to blur.
When they go quiet
Silence is the hardest reaction to read and the easiest to misread. Say you deliver a difficult rating and the employee says “okay” or nothing at all. The meeting ends early, and it can feel as if the review went well. But often you simply don’t know.
People go quiet in a review for different reasons. Some are taking it in and need a minute before they can say anything useful. Others have withdrawn and are waiting for the meeting to end, so they can think or be upset somewhere else. A third group goes along with it on the surface while disagreeing underneath, because arguing with their manager doesn’t feel safe or doesn’t feel worth it. From your side of the desk these can look exactly the same, and Riegel’s warning against interpreting applies here as much as it does with tears. So don’t guess which one you’re looking at. Ask in a way that can’t be answered with a yes or a no. “Does that make sense?” will get you a nod. But “What’s your reaction to the rating?” or “If you were going to push back on any of that, which part would it be?” gives them an opening that a nod doesn’t fill. The second question is especially useful because it gives open permission to disagree. That’s exactly what the quietly disagreeing employee is holding back.
Once you’ve asked, wait. This is where active listening is harder than it sounds, because the urge to fill a silence is strong. Usually it gets filled with one of two things. One is reassurance, such as “This doesn’t mean we don’t value you,” which blurs the message for the same reason it does with tears. The other is more feedback. You add detail to a point that’s already been made, which piles more weight on someone who was already struggling to say anything. A rule of thumb is to wait longer than feels comfortable before you speak again, and when you do speak, keep it short.
Some people genuinely can’t put their reaction into words in the room, and that’s fine. Offer them another way to answer: “You don’t have to respond now. If it’s easier, reply to my email this afternoon with anything you want to say and we’ll pick it up from there.” That gives the quiet employee the same chance to respond that an arguing employee takes in the meeting, just in writing and on their own time.
What you shouldn’t do is treat silence as agreement. Before the meeting ends, check what they heard and what they’re going to do: “Before we finish, can you tell me in your own words what you’re taking away from this, and what you’ll do first?” If what comes back is different from what you meant, you’ve found out now. Otherwise you may find out at the next review, when they tell you quite sincerely that nobody ever told them.
Should you pause, carry on or reschedule?
Any of the three reactions can raise the same question: should you stop? No research gives you criteria for this, so what follows is a rule of thumb. It’s built on the test from the start of this post, which is what has to be said today and what can wait.
| What’s happening | What to do | When to pick it back up |
|---|---|---|
| They can’t continue: they’re crying too hard to talk, or they ask to stop | Stop. If the outcome hasn’t been said yet, say it in a sentence first | The same afternoon or the next morning |
| They’ve stopped talking but can still listen | Offer a short break and let them choose | After a few minutes, starting from one specific point |
| The outcome has already been said | Pause freely. The detail and the development conversation can wait | The same afternoon or the next morning |
| The outcome hasn’t been said yet | Say it once, plainly, then offer the break | After the break, or the next morning |
| Voices are raised and it’s turning into a shouting match | End the review for now and suggest a walk or a break | The next morning, once you’ve both calmed down |
| Any sign they might harm themselves or someone else | Stop the review. Stay with them and get HR or emergency help | Not until they’re safe and HR is involved |
The timing comes from Tulloch’s suggestions in the Gurchiek piece, which put it this way: “Offer to reschedule the meeting to the afternoon or the next morning if the review becomes too overwhelming for the employee.” She doesn’t say next week, and there’s a good reason for that. The longer a half-finished review hangs over someone, the more room they have to fill the gap with guesses. Those guesses are likely to be worse than what you were going to say.
The row that needs explaining is the one about an outcome that hasn’t been said yet. This is a judgment call, not something from research. If a final decision such as a rating or a pay outcome hasn’t been said, say it once and plainly before any long pause: “Before we stop, I want you to have the outcome. Your rating this year is below expectations on delivery, and we’ll go through the reasons when we come back.” The reason is that a break with the outcome unspoken is a break spent guessing. The employee knows something hard is coming and has an hour, or a whole night, to imagine how bad it is. Saying it first means the break is spent taking it in rather than dreading it. If your HR team has a policy on how ratings are communicated, follow theirs.
The email to send the same day
Whatever happened in the room, send a short written follow-up the same day. It does three jobs. First, it gives the employee the content back after the emotion has passed. That matters because someone who was crying, arguing or shut down for part of a meeting often doesn’t remember much of what was said. It also records what you said and what they said back, including their disagreement, so there’s one version of the conversation you can both point to. Last, it keeps a clear record in case the rating is revisited or a future review needs to refer back to it. If you already keep written notes on someone’s performance, this sits alongside them, and our guide to performance documentation covers that side.
Here’s what Bridget sent Declan that afternoon. It’s illustrative, like the conversation above.
Subject: Notes from today’s review
Hi Declan,
Thanks for today. Here’s what we covered, so you have it in writing.
Your rating this year is below expectations on delivery, mainly because the March and June launches went live later than planned, by three weeks and two weeks. Your client feedback has been strong all year, and the review says so.
You disagreed with the rating. You said the March delay came from the data migration, which you flagged in February, and that you hadn’t heard concerns about delivery from me before today. That second point is fair, and I should have raised it sooner.
We took a short break partway through and then finished the conversation.
The rating stands for now. I’ll read the February thread you’re forwarding and reply by Thursday. If it changes the picture for March, I’ll take it back through the review process. You can add your own written comments to the review at any time, and they’ll be kept with it. Let’s meet on Friday to go through what I find.
Bridget
Each part of that email is there for a reason. The paragraph after the greeting sets out the facts of what was decided. It also includes what went well, because a record that only lists problems isn’t an accurate record of the review. The next paragraph gives Declan’s response in something close to his own words, and it includes the point Bridget conceded. Writing down someone’s disagreement can feel like handing them ammunition, but a record that leaves it out is one he can fairly call one-sided.
The line about the break is deliberately flat. It says a break happened and nothing about why or how he seemed, because describing someone’s emotional state in writing turns a record about the work into a comment about the person. That’s the same shift from the task to the self that Kluger and DeNisi found makes feedback backfire. The last paragraph says what isn’t decided yet (the rating stands for now). It also gives the next step with a day attached and says where he can put his own response.
Keep the tone the same as the review itself should have been. That means plain and about the work, with no adjectives about the person. If you find yourself writing “I know this was upsetting” or “you seemed defensive,” delete the line.
One caution. How performance conversations should be recorded varies by country and by company policy, and nothing here is legal advice. Check with HR what format they want and where it should be kept before you rely on an email as the record.
Where this breaks
Everything above assumes that the review is what the person is reacting to, and that the review is fair. Sometimes neither is true. There are three cases where the advice so far doesn’t hold.
The first is when the tears or the anger point to something outside the review. The employee might mention a bereavement, an illness or something happening at home, or they might say something that sounds like harassment or discrimination at work. At that point the review should stop, and it shouldn’t be finished that day. Ask whether they’re safe and what they need right now, and bring in HR. A manager isn’t a counselor, and trying to be one in the middle of a rating discussion doesn’t help the person or the review. If someone is upset about something you can’t fix, our guide to emotional boundaries at work covers how to stay supportive without taking the problem on yourself.
The second is when the employee’s argument is right. They might point to a fact you missed. They might show that you rated the whole year on the last six weeks, or that you weighed one bad quarter more heavily than you would for anyone else on the team. When that happens, the review should change. Use your company’s review process if it allows a rating to be revised, and tell them plainly: “I’ve looked at it again and you’re right about March. I’m changing that section.” You may feel that going back on a review makes you look weak. But an employee who sees a rating corrected on the evidence has more reason to trust the next one. Our guide to addressing bias in performance reviews covers the common ways a review goes wrong before anyone has said a word.
The third is harder, because it’s about you. If someone cried in a review last year and you softened the rating to make it stop, you both learned something from that. The next time tears start, you’ll feel the pull to soften again. Some managers react by deciding the tears were tactical and hardening up instead. The trouble is that you can’t tell. Distress and strategy can look exactly alike from across a table, and Riegel’s advice not to interpret is the honest answer here too: don’t try to decide which it is. People also show distress very differently across cultures and from one person to the next. So a calm face doesn’t mean someone has accepted the review, and tears don’t mean weakness or manipulation. What you can control is that the content of the review stays the same either way. You’ll only find out across a few review cycles whether that’s enough to break the pattern or whether it just makes you colder over time.
The conversation two days later
It’s natural to judge a review by how the meeting went. They cried, so it went badly. They argued, so it went badly. They were quiet and polite, so it went fine. But the reaction in the room is a weak guide to how the feedback actually landed. The quiet employee may have taken in almost nothing, while the one who cried may have heard every word and already be working out what to change. You learn more from what happens afterwards: whether they reply to the email, what they say in it and how the next conversation goes.
Declan replied to Bridget’s email that evening with two paragraphs on the June launch. He still thought the rating was wrong, and after she’d read the February thread, he still thought so. Bridget can’t make him agree, and the follow-up meeting shouldn’t try to.
So plan a short follow-up a couple of days after the review, and give it three jobs. Start by answering whatever they wrote back point by point, so their reply doesn’t disappear into a folder. If they said the record was wrong, correct it or explain plainly why you’re leaving it as it is. Last, agree one concrete next step on the work that they can start this week. That moves the conversation from the year that’s been to the one ahead. The regular steps that come after any review are in our guide on how to prepare for a performance review. Open the meeting with their reply, not with your notes.
The branches in the arguing section are the ones most worth practicing out loud, because they’re the ones you’ll be tempted to improvise when the moment comes. You can rehearse the review conversation with Merlin as a roleplay beforehand in Slack, Microsoft Teams or the web app. Try your answer to “this is the first I’ve heard of it” until it sounds like you.