You know you have to give feedback. The employee makes the same mistake for the third time. A colleague keeps interrupting in meetings. The project is heading in the wrong direction. So you address it—constructive, factual, with good intentions.
Two weeks later: nothing has changed. Or worse: the relationship is damaged, but the behavior is the same.
Feedback rarely fails because of intent. It fails because of how it is delivered—timing, framing, packaging—and what the other person actually receives rather than what you mean.
The problem is not that managers do not give feedback. The problem is that the feedback does not work. The message you send is not the message that lands. And if feedback does not land, it is wasted time—or worse.
A division head had avoided addressing an issue with one of her best team leads for months: he prepared meetings poorly, and the team was losing time and patience. She waited for the right moment, but the right moment never came—because there is no perfect moment. When she finally raised it, so much frustration had built up that she could no longer stay factual. The conversation escalated. The team lead did not hear the justified criticism; he felt the pent-up frustration, reacted defensively, and the working relationship was worse afterwards than before.
In that one situation, you will find almost all the reasons why feedback fails. The timing was wrong—not because the day was poorly chosen, but because months of postponing had increased the pressure so much that a calm conversation became impossible. The delivery suffered under the pressure: too harshly worded, and the other person shuts down; too soft after months of waiting, and you no longer sound credible. The team lead’s ego pushed back before his mind could even process the feedback, with justification and counterattack. And by then, the intent was no longer clear: did the division head still want to help, or did she just want to vent at last?
Underneath it all, the relationship is the load-bearing layer. Feedback from someone you trust is heard fundamentally differently than feedback from someone whose goodwill you doubt. Without that foundation, even the most constructive feedback is perceived as an attack. The question is not: Did I give feedback? The question is: Did my feedback land?
This distinction is fundamental, and it is blurred surprisingly often. Criticism judges the person: you are wrong, you failed, you are not good enough. It attacks identity. Feedback, by contrast, describes behavior and impact: this behavior has this impact. It separates the person from the action.
| Criticism | Feedback |
|---|---|
| “You are unreliable.” | “The last three deadlines were missed.” |
| “You cannot present.” | “In yesterday’s presentation, you lost the client.” |
| “You are too dominant.” | “In meetings, you often interrupt others.” |
| “That was bad.” | “The result did not meet expectations because…” |
The difference sounds subtle, but it is enormous. Criticism triggers defensiveness. Feedback, at best, opens a conversation. Feedback describes what someone does. Criticism describes who someone is. One can be changed; the other cannot.
A proven tool for making this distinction is the SBI model: Situation, Behavior, Impact. You describe the specific context (when and where), the observable behavior (what exactly the person did—no interpretation), and the impact (on you, on others, on the outcome). For example: “In yesterday’s project meeting, you interrupted your colleague three times before he could make his point. As a result, important information did not make it onto the table, and afterwards the colleague withdrew.” The model works because it is specific and avoids generalizations like “You always interrupt.” But it is a tool, not a magic bullet. It helps with structure, but it replaces neither the relationship, nor the timing, nor honest intent.
And by the way, forget the feedback sandwich: something positive first, then the criticism, then something positive again. If you wrap criticism in praise, neither tastes right. The praise becomes a warning signal (“Here comes the ‘but’”), and the criticism gets lost in the packaging. Be clear: positive feedback when it is appropriate. Corrective feedback when it is necessary. But not both in the same breath.
There is a common misunderstanding: either I am nice, or I am honest. Either I spare feelings, or I tell the truth. That is a false dichotomy.
In her concept of “Radical Candor,” Kim Scott describes two axes: how much do I care personally? And how directly do I challenge? This yields four quadrants every manager should know. High care and high directness produce the goal: honest and respectful at the same time. High care with low directness leads to what Scott calls “Ruinous Empathy”—you do not want to hurt anyone, so you say nothing that helps anyone. Low care with high directness is brutal honesty without respect; it destroys relationships. And low care with low directness is neither honest nor caring—it is politics instead of leadership.
The insight behind it: you can be warmly human and uncompromising on the issue at the same time. That is not cruelty; it is clarity. And that clarity is a sign of respect, because you take the other person seriously enough to tell them the truth. Anyone who avoids difficult conversations because they want to be “nice” confuses kindness with leadership.
A member of management described a feedback conversation he had held on Friday evening at 6 PM, after a long week in which frustration had built up. The conversation escalated, the employee went home feeling like a failure, and the weekend was ruined for both. On Monday, the member of management had to hold a second conversation to repair the first.
Feedback needs the right moment—and the right moment is not when you are ready to give it, but when the other person is ready to hear it. If you are still emotionally charged, wait. Your anger will show through, and the feedback will become an attack. Corrective feedback belongs in a one-on-one conversation; public criticism humiliates and does not lead to change, but to resentment. At the same time, you must not wait too long: feedback loses its power when the situation is weeks or months in the past. Rule of thumb: within 48 hours, but not in the first 48 minutes.
A simple but effective technique: ask the recipient. “I have feedback on yesterday’s presentation. Is now a good time, or would you prefer we discuss it tomorrow?” This question shows respect and significantly increases willingness to listen.
Positive feedback is often neglected—and that is paradoxical: many managers find it easier to address mistakes than to recognize performance. Critical feedback has a clear trigger: a specific mistake, a measurable deficit. Positive feedback requires you to pause, observe, and name what is going well. That takes attention that is rarely left over in day-to-day business. And it requires a willingness to be vulnerable, because genuine recognition is a sign of closeness, not just of management.
Positive feedback serves two crucial functions: it reinforces desired behavior, because people repeat what is recognized. And it builds the relationship that corrective feedback must be carried by. Anyone who only criticizes will eventually no longer be heard. But “well done” is nice, not useful. It is unspecific; the recipient does not know what exactly was good and cannot repeat it deliberately. Instead of “Good presentation,” better: “The way you responded to the client’s critical question—calmly, factually, with concrete data—turned the situation around.”
The real danger, however, lies at the other end: if you praise everything, you praise nothing. Inflated praise not only devalues the individual compliment; it undermines your credibility overall. If every small achievement is met with big praise, the team stops trusting your judgment—including your critical judgment. Positive feedback is most effective when it is rare enough to stand out and specific enough to mean something.
Giving feedback is hard. Accepting feedback is sometimes even harder. As a manager, you should be able to do both—and model both.
The first impulse with critical feedback is to justify yourself. Resist it. Listen all the way through before you respond. “Thank you for raising that. Let me think about it.” That is not weakness; it is composure. Ask for concrete examples to truly understand the feedback: “What would you have preferred I do differently?” Then check honestly whether the other person has a point. You do not have to consider every piece of feedback correct, but you should take it seriously.
If you only receive feedback when something goes wrong, you get a distorted picture. Ask proactively: “What could I have done better? What should I keep doing, what should I change?” Anyone who takes a culture of learning from mistakes seriously has to start with their own feedback. One without the other is not credible.
Sometimes you do everything right and the feedback still does not work. Then it is worth taking a systematic look. First, check the relationship: Does the other person trust you? If not, work on that first. Then check frequency: once is rarely enough. People do not change behavior after one conversation. Repetition is necessary—but consistent, not changing the message every time.
Also check whether consequences are tied to the feedback. Feedback without consequences becomes background music. That does not mean threats, but it does mean that action and inaction must have different outcomes. And check whether feedback is even the right tool. Sometimes the problem is not willingness but capability—then you need development, not feedback. And sometimes the problem is the system, not the person—then feedback directed at an individual is unfair.
Marshall Goldsmith coined the term “feedforward”: instead of endlessly analyzing what went wrong, ask: “How do we do it better next time?” That removes the pressure to justify. The other person does not have to defend what was; they can focus on what is coming. Feedforward is often more effective than the third conversation about the same past mistake.
And know when you need to stop. If feedback does not work over a longer period, even though you have tried everything, you must draw other consequences. Endlessly repeating the same feedback is not leadership; it is helplessness.
First: think about your last corrective feedback. Did anything change afterwards? If not, is it the timing, the relationship, or missing consequences?
Second: when was the last time you actively asked for feedback on your own leadership—and did you act on it, or merely take note of it?
Third: is there someone on your team whom you owe feedback to for weeks now? Schedule the conversation this week.
Many managers avoid feedback because it is uncomfortable, because it could strain the relationship, because it could go wrong. So they say nothing and hope the problem will disappear on its own. It rarely does.
Feedback not given is not neutral. It is a message: the behavior is acceptable. Keep it up. Anyone who avoids feedback accepts the status quo and has no right to complain later about a lack of change.
Which feedback are you currently putting off? You know which. And you also know: every day you wait makes the conversation harder, not easier.
Having difficult conversations – Feedback is often the entry point into a difficult conversation. How to maintain the balance between clarity and respect.
Repairing trust – If feedback has damaged the relationship, you need a plan to repair it.
All Insights can be found in the overview.
Proven tools and models for self-application are available under Solutions.
If you want to take these thoughts further for your company, a no-obligation initial conversation is worthwhile.
