If you’ve ever given a leader honest feedback and watched it get a warm, appreciative nod — followed by absolutely nothing changing — you’ve experienced one of the most common and most frustrating dynamics in workplace communication. It’s tempting to conclude the leader just doesn’t care, or isn’t capable of change. In our experience, that’s rarely the real explanation. Far more often, the feedback itself wasn’t structured in a way that gave the leader anything specific to actually act on.
Why feedback to leaders tends to evaporate
Feedback that disappears without effect usually shares a common shape: it’s general rather than specific (“you don’t communicate enough with the team”), it’s framed around how it made you feel rather than what it actually affected (“it’s frustrating when decisions get made without input”), and it leaves the leader to figure out, entirely on their own, what a fix would even look like. None of that is dishonest or wrong to say — those feelings are usually completely legitimate. But from the leader’s side, vague, pattern-level feedback like this is genuinely hard to act on, because there’s no specific moment to point to and no concrete next step attached. It’s easy to nod along to, and just as easy to quietly file away without any real behavior change following it.
A three-part formula that actually lands
Anchor to one specific, recent, observable moment — not a general pattern. Instead of “you don’t communicate enough with the team,” try something like “in Tuesday’s planning meeting, the timeline changed and the team found out from a calendar update rather than from you directly.” A specific moment is something a leader can actually picture and evaluate, where a general pattern just feels like an accusation they either have to accept wholesale or defend against.
Tie it to a concrete business impact, not just how it made you feel. Following the specific moment, connect it explicitly to something that matters to the leader’s own priorities — “that meant the team spent half a day operating on outdated assumptions before the correction landed.” This reframes the feedback from a personal complaint into a shared business problem, which is a much easier thing for a leader to engage with directly rather than defensively.
Offer a specific, low-cost next step — don’t just leave the problem for them to solve alone. This is the step most feedback skips entirely, and it’s often the difference between feedback that gets acted on and feedback that gets acknowledged and forgotten. “Would it help if timeline changes went out in a short note to the team before the calendar update, even just a two-line heads-up?” gives the leader something concrete and easy to say yes to, rather than an open-ended problem they now have to design a solution for on their own time.
Why this reframing works, structurally
This connects to a broader idea we’ve written about in The Advisory Paradox — that the most valuable feedback, whether from an outside advisor or from someone inside an organization, often does more good by reframing a problem clearly than by simply stating a complaint, however valid that complaint is. A leader who receives “you don’t communicate enough” has to do all the work of translating that into something actionable themselves, under whatever time and attention they have available — and most feedback of that kind loses that race against a busy calendar. A leader who receives the three-part version above has already been handed a clear, specific, low-effort action, which dramatically increases the odds it actually happens.
What to do if the feedback still doesn’t land
Occasionally, even well-structured feedback genuinely doesn’t produce change, and it’s worth knowing what that actually signals versus what it doesn’t. One instance of a well-framed suggestion not being acted on isn’t necessarily a sign the leader doesn’t care — priorities are genuinely competing for their attention, and one specific ask can still get lost. A repeated pattern, though, where the same well-structured feedback keeps landing without any change at all, is different information — it may mean the issue sits deeper than a communication gap, or that raising it again with a different messenger, or through a different channel, is worth considering.
A note on timing and setting
Even well-structured feedback lands differently depending on when and where it’s delivered. Feedback given immediately after the moment it references, in a private setting rather than in front of a group, tends to be received far better than the same feedback delivered days later or in a more public context — not because the content is different, but because immediate, private feedback feels like a genuine attempt to help rather than a public correction or a delayed grievance. If you’re holding onto feedback because the “right moment” hasn’t presented itself, that delay itself often works against you — the specific moment gets fuzzier in memory, and the feedback starts to feel more like an accumulated complaint than a fresh, actionable observation.
What this looks like in practice
We coached a director at a financial services firm who had, for months, been quietly frustrated that her VP consistently made client-facing commitments without looping in the delivery team first — feedback she’d raised generally a few times, always met with agreement and no real change. Restructuring her feedback around one specific recent instance, its concrete downstream cost, and a simple proposed fix (a standing five-minute check before any client commitment involving delivery timelines) got a genuinely different response — because for the first time, the VP had something specific and easy to actually act on, rather than a general impression to feel bad about. You can read more about how we coached that conversation in our financial services feedback coaching case study.
The bottom line
If feedback you’ve given to a leader keeps disappearing without effect, it’s worth revisiting how it was framed before concluding the leader simply isn’t willing to change. Specific, impact-linked, action-oriented feedback succeeds far more often than general, feeling-based feedback — not because leaders are unusually resistant to the latter, but because it genuinely gives them less to work with. Reframe the message, and you’ll often find the same leader responds very differently to what is, underneath, the same underlying concern.