Feedback No One Receives: Why Your Leaders Avoid Uncomfortable Conversations

Almost every leadership survey turns up the same gap: leaders report that giving feedback is one of the conversations they avoid most, and their teams report that they almost never get a concrete review of what they do. These aren't two separate problems. They're the same conversation, seen from both sides of a silence — one that never happens, or happens so disguised as something else that it lands nowhere.

"I didn't get the chance" is the most common excuse for not delivering a review that's been overdue for weeks. But in the vast majority of cases, it's not a scheduling problem — it's an automatic judgment operating without anyone naming it. "It won't help," "they'll get defensive," "I'd rather avoid the conflict" — these judgments act as though they described a fact, the other person's guaranteed reaction, when they're actually a prediction that was never tested. Ontological coaching starts from that same premise: we don't see the world as it is, we see it as we are, and a leader who "doesn't trust feedback" is almost always acting from a judgment they never examined.

Postponing the conversation doesn't eliminate it, it just moves it into a different domain: what doesn't get said in language starts showing up in the body and the emotions of the team — tension that gets felt in meetings, resentment that piles up, the same mistake repeating because nobody named it the first time. The cost of silence isn't abstract: it gets paid in turnover, in projects delivered badly, in an underlying distrust that no one can pinpoint precisely because it was never put into words.

Avoiding the conversation doesn't avoid the judgment: it just guarantees the other person never finds out what it is.

The problem isn't always the absence of feedback: sometimes it gets given, but as a loose judgment — "you're disorganized," "you lack commitment" — that cites no concrete fact. Faced with a judgment like that, the other person has only two options: accept it wholesale or defend against it wholesale. There's no third option, because there's nothing specific to talk about. The difference with grounded feedback is that it first describes the observable action that triggered it and the impact it had, and only then states the judgment. That turns the review into something debatable, not an attack on the identity of the person receiving it.

Feedback that works has four steps, in order, not all at once: first the concrete observable fact — what was seen or heard, without interpretation; then the impact it had, on the team, the result, or the relationship; only then the judgment or the explicit request going forward, stated as such and not as a complaint; and finally, real room for the other person to respond before closing. Skipping the first step and going straight to the judgment is what triggers defensiveness the most — and it's also the step most leaders skip when they're rushing to get through a conversation that makes them uncomfortable.