A recent Harvard Business Review piece makes a sharp observation: feedback only produces improvement when a leader manages the emotions it creates. The article offers six practices for keeping an employee’s attention on the work itself rather than on self-protection, blame, or fear.
Focus on actions instead of character. Invite the employee’s perspective. Turn frustration into a concrete next step. Show that improvement is achievable. Watch what happens afterward. Check where the person’s attention actually goes once the conversation ends.
It’s good advice. Any manager who internalizes it will have better conversations, but there’s a question sitting just underneath the article that deserves more attention than it gets: who is checking?
The six practices focus on one manager, one employee, and one conversation. That’s exactly the right lens for coaching a leader. It’s the wrong lens for understanding whether an organization learns.
Here’s the gap. HBR’s final practice, watching what happens afterward, is arguably the most important one on the list. Withdrawal after feedback can look identical to acceptance. An employee who goes quiet, stops raising issues, or stops volunteering ideas may have absorbed the lesson, or may have simply concluded that the safest move is to stay invisible. The article is right that this distinction matters enormously.
What it doesn’t ask is where that observation goes.
In most organizations, the answer is nowhere. The manager who delivered the feedback is also the person best positioned, and least incentivized, to notice that the employee has gone quiet. There is rarely a mechanism that surfaces a pattern of post-feedback withdrawal to anyone above that manager. No one is aggregating the signal across teams. No one is asking whether a particular manager’s feedback style is producing a disproportionate share of quiet, disengaged employees six months later.
That’s not a coaching failure. It’s an infrastructure failure.
By infrastructure, I don’t mean technology. I mean an organizational process that ensures observations become information, information becomes patterns, and patterns become decisions. Most companies have feedback conversations. Very few have feedback intelligence.
Organizations spend thousands of dollars teaching managers how to give feedback. Almost none spend anything building a way to know whether the feedback actually worked. The emotional data described in the HBR piece, defensiveness, fear, withdrawal, disengagement, is exactly the kind of information that exists inside the organization but routinely fails to travel anywhere useful. It sits with the individual manager, gets attributed to the employee’s personality or resilience, and never becomes something the organization can act on.
This is a familiar pattern to anyone who studies why organizations keep repeating mistakes they should already know how to avoid. The information required to catch a problem early usually exists somewhere in the building. What’s missing is a structure that moves it from where it’s observed to where a decision could be made with it.
The size of the organization changes the shape of the gap, but it doesn’t close it.
At a large company, the gap is structural. The data exists somewhere, engagement surveys, HRIS records, skip-level notes, but no one has built the connective tissue between a manager’s feedback pattern and what happens to that manager’s team six months later. The information is scattered across systems that were never designed to talk to each other.
At a small or mid-sized company, the gap looks different but produces the same blind spot. There’s no HRIS layer to build connective tissue between, and often no HR function at all. The owner or a handful of leaders carry the entire feedback relationship personally. That closeness is usually an advantage. It becomes a liability the moment that same person is also the one who needs to notice their own pattern, or a peer manager’s, without any outside check on it. Proximity substitutes for infrastructure until the day it doesn’t.
For a smaller organization, building that check doesn’t require a system in the enterprise sense. It requires one deliberate habit, done consistently, that someone other than the manager in question owns:
When a good employee goes quiet or leaves, someone, a co-owner, a trusted operations lead, an outside advisor, actually looks back at what feedback that person received in the prior two or three months, not just why they say they’re leaving. A five-minute conversation that asks “what did we tell them, and how did they take it” surfaces more than most exit interviews do.
Any leader who delivers regular feedback has someone who occasionally sits in, or hears about it secondhand, and has permission to say “that landed differently than you think it did.” Without a second set of eyes, even a well-intentioned leader has no way to know their read of the room is off.
At review time, the question isn’t just “did we give feedback,” it’s “did the person leave more engaged or more guarded than when they walked in.” That’s a judgment call, not a metric, but naming it out loud at least once a quarter is enough to catch the pattern before it becomes an exit.
None of that requires software, headcount, or a governance committee. It requires deciding that watching what happens after feedback is someone’s job, not an incidental byproduct of a good manager’s instincts.
The HBR article is a genuinely useful guide for the moment inside the room. But the moment inside the room is not where organizations, of any size, fail. They fail at the layer above it, where nobody, formally or informally, is watching for the pattern the article correctly identifies as the whole point: whether feedback produced learning or just produced silence.
Six good practices in every conversation will not fix that. Someone deciding to watch for what happens after will.
This is the difference between a management technique and an organizational system. Techniques improve individual conversations. Systems improve organizational capability. One manager can get better at giving feedback. A company gets better only when it captures what those conversations reveal and turns them into better decisions.
The Inside Advantage 
Leave a comment