Respond When an Employee Disagrees With a Performance Example

When you give an employee a specific example of a problem and they push back with a different account of what happened, you have two jobs at once. You need to protect the accuracy of the record, and you need to keep the person across the table willing to keep talking. Most managers only manage one of those at a time. They either drop the example to avoid tension, or they defend it so hard that the conversation turns into an argument about who is right. Neither move fixes the underlying issue, and neither one gets you back to a plan for what happens next.

Why This Conversation Goes Wrong

Disagreement during feedback feels like a threat to your authority, so your first instinct is often to hold your ground. That instinct backfires. If you repeat the same example louder, the employee hears that you are not actually listening, only waiting for them to stop talking. If you back off the example the moment they object, you teach them that pushback makes a performance concern disappear, which trains the wrong behavior for the next review.

The other common failure is treating the disagreement as a character question. A manager who hears "that is not what happened" can slide into thinking the employee is being defensive, dishonest, or unwilling to take feedback. That reaction shows on your face and in your tone even when you do not say it out loud, and the employee picks up on it immediately. Once someone feels accused of lying, they stop trying to solve the problem with you and start trying to defend themselves. From that point, the conversation is no longer about the work.

The fix is to remember that a disagreement over facts is not the same as a refusal to accept feedback. Your job is to find out what actually happened, correct the record if you got a detail wrong, and land on a clear expectation for next time. You do not need the employee to agree with your framing of events. You need an accurate account and a shared understanding of what changes going forward.

How to Prepare

Walk into the conversation with a source for every claim you plan to make. Before you say an example out loud, write down where it comes from, a work record, a meeting note, a dated handoff, a message thread, or something you saw yourself. If your only source is a vague impression from three weeks ago, either dig up something concrete or leave that example out. Vague examples are exactly the ones that fall apart under a simple question.

Plan for the possibility that you have part of the story wrong. Managers rarely see the full sequence of events, and employees usually have context you do not, like a delay caused by another team or an instruction that changed midway through a project. Decide in advance that you will treat new information as useful rather than as an inconvenience to your point. This is easier to do when you have already separated the fact you are checking from the standard you want to set. The fact might be wrong. The standard usually still stands.

Write one open question you can ask if the employee disagrees. Something like "walk me through what you saw at that point" works better than a question that assumes you are right and just wants them to admit it. If you want more background on building this kind of preparation into a broader routine, the HR and Leadership practice conversations hub covers other performance and feedback scenarios you are likely to run into as a manager.

What to Say

State the example plainly, using the source you prepared, and then stop talking. Let the employee respond before you add anything else. If they correct a detail, acknowledge it directly instead of moving past it. If both of your accounts can be true at once, name the shared evidence you both agree on and use that as the anchor for the rest of the conversation.

Manager Priya said, "On the release call last Tuesday, you marked the ticket closed before the vendor confirmed the fix. That's part of why the customer saw the issue again on Thursday." Deon replied, "I did not close it. I set it to resolved once the vendor told me the fix was on its way." Priya said, "Thanks for clarifying that. The system log shows it moved to resolved at 11 in the morning, and the vendor's confirmation came in at 3 in the afternoon that same day. What status would have shown the fix was still pending on their end?" Deon said, "Pending vendor. I picked the wrong status from the list." Priya answered, "Let's use pending vendor any time we're waiting on another team to confirm something, and I'll check the next few tickets with you so it sticks."

Notice what Priya does not do. She does not accuse Deon of lying about closing the ticket. She does not abandon the example either. She checks the specific claim against the record, accepts the correction on the word he used, and turns the exchange into a concrete rule for next time. That last move matters as much as the correction. A feedback conversation that ends with an agreed action is far more useful than one that ends with an agreed set of facts and nothing else.

Mistakes to Avoid

Do not let the disagreement turn into a debate about intent. Whether Deon meant to mislabel the ticket is not the point, and guessing at his motives will only put him on the defensive. Stick to what happened and what should happen differently.

Do not soften the standard just because a detail was wrong. If the underlying pattern still holds after you correct the fact, say so plainly. Deon still used the wrong status, and the customer still saw the issue again. Priya keeps that standard even after admitting the timeline needed a fix.

Do not treat every disagreement as one you can resolve yourself. If the disagreement touches something formal, like a documented policy violation or a decision that affects pay or promotion, escalate it through the appropriate HR channel instead of trying to settle it alone in the room. And do not skip the paper trail afterward. Send a short factual summary of what you agreed on right after the meeting, and ask the employee whether it matches their understanding of the commitment. That message is often what protects both of you if the same issue comes up again.

How to Practice and Score It

Reading through an exchange like the one above is not the same as running it live, especially when someone actually pushes back and your first reaction is to get defensive. Practicing the moment out loud, with a counterpart that argues back the way a real employee would, is where the skill actually forms. DealSpeak is built for exactly that kind of rehearsal. You state your example, the AI counterpart disputes it, and you have to work through the correction in real time instead of rehearsing a version of the conversation where the other person just agrees with you.

Score yourself on three things afterward. First, did you name a source for your example instead of relying on impression alone. Second, did you acknowledge the part you got wrong without abandoning the part you got right. Third, did the conversation end with a specific action both people can point to later, not just a vague sense that things went fine. If you want to see how the same discipline applies outside performance reviews, the post on how to Build Practice Around a Newly Introduced Customer Process works through a different scenario using the same approach of preparing sources, staying specific, and closing with a clear next step.

A disagreement over a performance example is not a sign that the conversation has gone off track. It is often the moment where you find out what actually happened and set an expectation that will hold up the next time. Prepare your sources, stay curious about the employee's account, and close every one of these conversations with a written summary both of you can point back to.