Your Feedback Is Not Failing Because You Are Too Nice
Picture the last difficult feedback conversation you had with someone on your team. Chances are, somewhere in the first ninety seconds, it quietly turned into two separate meetings happening at once. You were talking about the missed deadline. They were deciding whether your version of events was even accurate, and whether you had any business bringing it up in the first place.
TL;DR: Difficult feedback conversations often fail because they turn into a debate about the past, over whether the account is accurate and whether the manager has standing to give it, instead of a conversation about what changes next. Being more forceful doesn’t fix that; clarity does. Describe the behaviour and its impact, ask what needs to be different next time, and say your purpose out loud (development, accountability, risk, or formal concern).
That’s the part nobody warns you about in manager training. The conversation fails before anyone has decided whether to change anything, because it’s stopped being about the future and started being a small trial about the past.
You’re not having the conversation you think you’re having
You walk in ready to talk about the missed deadline or the tense client call. They walk in ready to defend their version of events, and often, without quite realizing it, to defend it against you specifically. Research on feedback dynamics backs this up: recipients of negative or mixed feedback tend to dispute both the accuracy of the message and the credibility of whoever’s delivering it (Gnepp et al.). Once that happens, you’re not coaching anymore. You’re litigating.
There’s a second layer to this. Employees respond very differently depending on why they think the feedback is happening. If you don’t say the reason out loud, they’ll guess, and their guess is rarely charitable (Xing et al.).
Your job isn’t to make the message softer. It’s to make the purpose, the evidence, and the next step impossible to misread.
Saying it more firmly doesn’t fix this
There’s a tempting instinct when feedback isn’t landing: say it with more edge next time. A meta-analytic review of performance feedback across organizational settings points the other way. How feedback is framed and delivered matters far more than how forcefully it’s delivered (Sleiman et al.). Push harder on something someone already hears as a verdict, and you mostly just get a better defended employee, not a better one.
Discomfort was never really the problem. The problem is a conversation that’s stuck arguing about something nobody can change.
Two moves that keep the conversation forward-looking
Name the behaviour and impact, then ask what changes next time. Name the specific behaviour and its impact, then ask directly: “What needs to be different in the next situation like this one?” That question does something useful. It moves their attention off defending what already happened and onto the one part they can actually do something about.
Say why you’re having this conversation. Development, accountability, risk reduction, or a formal performance concern: pick one and say which. Employees can usually tell when a manager is being vague about this, and the vagueness is often what fuels the credibility fight in the first place.
A quick way to test yourself
Before your next hard conversation, run it twice in your head. Once as a judgment about what already happened. Once as a forward-looking conversation about what happens next time. You’ll probably notice the two versions get very different reactions from the person on the other side of the desk. That gap is exactly the shift you’re going for.
Frequently Asked Questions
What if the employee disagrees with your account of what happened? You don’t need full agreement on every detail of the past to move forward. If you’ve named the specific behaviour and its impact, you can still ask the forward-looking question, “what needs to be different next time,” even while some facts are contested. Staying in the argument over the record is what stalls the conversation, not the disagreement itself.
Does this approach only work for negative feedback, or does it apply to positive feedback too? The research behind it (Gnepp et al.) is mainly about negative and mixed feedback, where the credibility fight is most likely to happen. But naming the specific behaviour and stating your purpose works just as well for reinforcing something that’s going right; it’s just lower stakes, so managers rarely bother being as precise.
What if I’m not actually sure why I’m giving this feedback? That’s worth sitting with before the conversation, not during it. If you can’t say whether this is development, accountability, risk reduction, or a formal concern, the conversation is likely to come across as vague to the employee too, and vagueness is exactly what tends to trigger the credibility fight this approach is trying to avoid.
How is this different from the classic feedback sandwich? The sandwich (praise, criticism, praise) is about softening the delivery. This approach isn’t concerned with softening anything, it’s about removing the ambiguity that makes people argue about the past. You can deliver this directly, even bluntly, and it still works, as long as the behaviour, purpose, and next step are clear.
Is this a skill I can practice, or does it just come with experience? It’s practiceable. Try running the same hard conversation two ways in your head beforehand: as a judgment, then as a forward-looking discussion. Notice how differently each version is likely to land.
Sources
Gnepp, J., Klayman, J., Williamson, I. O., & Barlas, S., The Future of Feedback: Motivating Performance Improvement Through Future-Focused Feedback. PLoS ONE. DOI: 10.1371/journal.pone.0234444
Xing, L., et al., Supervisor Negative Feedback and Employee Motivation to Learn. DOI: 10.1177/00187267211038514
Sleiman, A. A., et al., A Quantitative Review of Performance Feedback in Organizational Settings. DOI: 10.1080/01608061.2020.1823300
