Feedback Examples for Managers
What to Say, and Why the Same Line Lands Differently

The key insight:

The sentence is not the problem. The gap between what you meant and what landed is governed by two dimensions you can actually measure.

Most people searching for feedback examples want one thing: wording they can actually use in the next ten minutes, not a theory of feedback. That is a reasonable thing to want, and this gives it to you directly. It also does the thing the wording lists never do, which is explain why the same sentence, delivered by two different managers, produces two different rooms.

Feedback that names the behaviour, not the person

The single most reliable improvement available to any manager is swapping a character judgement for a specific, checkable observation. It sounds like a small change in phrasing. In practice it is the difference between a conversation the other person can actually act on and one they can only defend against.

CCL's own research on feedback types identifies four common approaches: directive ("I suggest you make priorities clearer"), contingency ("if this continues, the team will stop trusting the estimate"), attribution ("you're disorganised"), and impact ("the deck went out late, and I didn't have time to flag the numbers"). Their finding is specific and useful: impact feedback, describing the effect of the behaviour rather than labelling the person or threatening a consequence, is the version to lead with, because it "informs a person about the results of their behaviour without dissecting the details, assuming motivation, or placing blame." Every example on the table above is built on that principle.

Why the identical sentence lands differently depending on who says it

This is the part the wording lists skip, and it is the more useful half of the question. Two managers can say almost the same sentence and produce completely different reactions in the room, and the reason is rarely the words themselves.

The free Leadership Psychometric on AssessYou scores five dimensions: Vision Thinking, Execution Drive, Influencing Power, People Intelligence and Composure. Two of them explain most of the gap between intended feedback and received feedback.

Execution Drive governs how directly you get to the point. A manager high on Execution Drive tends to compress feedback into the shortest accurate sentence available, which is efficient and, without a counterweight, can read as curt or cold even when the content is fair. A manager low on Execution Drive tends to cushion the message with context and qualifiers until the actual correction is buried three sentences deep, which is kinder to deliver and considerably less useful to receive.

People Intelligence governs how accurately you are reading what the sentence is doing to the other person while you say it. A manager high on Execution Drive and low on People Intelligence delivers a technically correct, genuinely useful piece of feedback that lands as an attack, because they were not tracking the listener's reaction closely enough to adjust the delivery in the room. A manager low on Execution Drive and high on People Intelligence reads the discomfort accurately and, rather than push through it, softens the message until the actual point disappears, which is the vague, evasive failure mode of exactly the same underlying instinct to protect the other person.

Neither failure mode is a character flaw, and neither is fixed. A manager who knows they run high on Execution Drive and lower on People Intelligence can deliberately build in a pause: say the impact sentence, then stop, then watch the reaction before adding anything else. A manager who knows the reverse can set a rule for themselves, the correction goes in the first two sentences or it does not go in at all, before the impulse to soften takes over.

Documenting it, and the language that keeps it useful

Feedback that only ever happens verbally and is never written down creates two problems. The person receiving it can genuinely forget the specifics were raised, and if the pattern continues to a point where it needs to be escalated formally, there is no record that it was ever addressed. SHRM's guidance on delivering constructive feedback makes the blunt version of this point directly: "many judges and arbitrators will tell you that if nothing was written down, it probably never happened." A short note to yourself after the conversation, what was raised, what was agreed, is not bureaucracy. It is the difference between a pattern you can demonstrate and one you are simply asserting.

The same guidance flags a wording habit worth dropping on sight: absolute language. "You always leave this to the last minute" and "you never flag risk early enough" are both, almost certainly, factually wrong, and they hand the other person an easy and legitimate objection, arguing about whether "always" is fair, that has nothing to do with the actual behaviour you wanted to address. Replacing "always" and "never" with "on the last two releases" or "in yesterday's meeting" keeps the conversation anchored to something specific and true.

What this is not

This is a bank of sentences, not a bank of questions. If you are looking for what to ask when gathering structured input from a wider group, 360 feedback questions covers the question design for that separate exercise, and if you are checking a candidate's history rather than coaching your own team, reference check questions covers that different conversation entirely. This page is specifically about the sentence you say in the room, one to one, in the moment the behaviour needs addressing.

It is also feedback flowing downward and sideways rather than upward. If the harder version of this for you is calibrating what you raise with your own manager rather than with your own team, how to manage up covers that asymmetric relationship directly, including where Influencing Power, a different dimension from the two above, does most of the work. For the rest of what senior assessors and structured tools actually look at, see the full Leadership collection.

If you want a structured read on where you actually sit on Execution Drive and People Intelligence, rather than inferring it from how your last few difficult conversations went, take the free Leadership Psychometric on AssessYou. It takes ten to fifteen minutes and scores all five dimensions from your own answers. If you would rather see what the report covers first, the Leadership Psychometric overview sets out how it is built before you create an account.

The same calibration problem exists one level up, where the stakes are considerably higher. JOH Partners' own analysis of the chief audit executive seat covers a function built entirely on delivering unwelcome, specific findings to a board in a way that still lands as useful rather than adversarial, the same distinction between impact and attribution this guide draws for a one-to-one conversation, played out where the relationship cannot simply be repaired with an apology afterwards. Where the underlying issue is not wording at all but scope, corrected work being fed back to people who have already outgrown the level of detail being corrected, a skills gap analysis is the more useful next step than another wording tweak.

Key takeaways

JOH Partners Intelligence

Get the fortnightly brief on GCC careers, salaries, and market moves.

No spam. Unsubscribe any time.