Almost every manager has given feedback that went nowhere. The conversation was polite, the person nodded, and six weeks later nothing had changed. That is not usually a sign the person was resistant. It is usually a sign the feedback was not specific enough to act on, arrived too late to connect to anything real, or was wrapped so carefully that the message did not survive the packaging.
Feedback that changes behavior has a particular shape. It names something observable, it arrives close to the event, and it leaves the other person with a clear next action rather than a general sense of disappointment. This guide covers how to get that shape right, including the exact phrasings that work and the ones that quietly undo the conversation.
Quick Answer: How Do You Give Feedback Effectively?
Give feedback close to the event, describe the specific behavior rather than the person, explain the effect it had, and agree one concrete next step. Keep it a conversation rather than a verdict, and check back within two weeks so the person knows it mattered.
Why the Feedback Sandwich Stopped Working
The sandwich, meaning a criticism wrapped in two compliments, is still the most widely taught feedback technique and the most reliably counterproductive one. People learned the pattern. Once someone recognizes the opening compliment as packaging, the praise stops being heard as praise and starts being heard as a warning that bad news is coming.
Worse, it muddies the message. If the criticism is the middle third of a conversation that is two thirds positive, a reasonable person concludes the issue is minor. Then they are surprised when it appears in a performance review.
The alternative is not bluntness. It is separation. Give genuine recognition when it is deserved, as its own conversation, so it reads as true. Give corrective feedback as its own conversation, so it reads as important. Mixing them devalues both.
The Four Parts of Feedback That Lands

Timing: close to the event, not saved up
Feedback has a short shelf life. A missed deadline discussed the same week is a solvable problem. The same deadline raised at a quarterly review is a grievance, because the person has had three months of believing it was fine.
The practical rule is that if something is worth raising at a review, it was worth raising at the time. Reviews should contain no surprises. Anything genuinely new in a review is a failure of the preceding three months, not a revelation.
Specifics: behavior, not character
The difference between useful and useless feedback is almost entirely the difference between describing what someone did and describing what someone is.
"You are disorganized" cannot be acted on. It is an identity claim, and the natural response to an identity claim is defense. "The client deck went out at 9pm the night before the meeting, which left no time for the team to sanity check it" can be acted on, because it names a thing that happened and a consequence that followed.
This is also where strengths-based language earns its keep. A person who is habitually late with documents may be someone who keeps improving the work right up to the deadline. That drive is not a defect to be removed. It is a strength that needs a boundary. A manager who sees it that way gets a different conversation and a better outcome than one who has decided the person is careless. Our piece on strengths-based coaching for managers goes into how that reframe works in practice.
Effect: say what it cost
Most feedback stops at the behavior and never explains why it mattered. The person then has to guess at the stakes, and they usually guess low.
Naming the effect does the persuading for you. You are not asking someone to change because you prefer it. You are showing them a consequence they did not see.
The next step: one thing, agreed out loud
End with a single concrete action, and have the other person say it back in their own words. Two or three actions is a wish list. One action is a commitment. If they articulate it themselves, you also find out immediately whether the message actually landed or whether you have been nodding at each other.
Feedback Examples: What to Say Instead
The table below is the part worth keeping. The left column is phrasing managers use by default. The right column says the same thing in a form the other person can act on.
| Situation | What managers usually say | What works better |
|---|---|---|
| Work is consistently late | "You need to be better with deadlines." | "The last three reports came in on the morning they were due. That removes the review window, so errors reach the client. What would it take to get a draft to me the day before?" |
| Dominating meetings | "Try to let others speak." | "In Tuesday's review you answered the first four questions. Two of them were Priya's area and she did not get to them. Can you hold back on anything outside your scope for the first ten minutes?" |
| Work is technically fine but careless | "Please be more careful." | "The analysis was right but the client's name was misspelled twice. That is the first thing they read. Can we add a two minute read-through before anything external goes out?" |
| Avoiding a difficult task | "You seem to be avoiding this." | "The supplier conversation has moved three times. I am guessing it is not the scheduling. What is making it hard to start?" |
| Good work worth reinforcing | "Great job on that, well done." | "You caught the pricing error before it went out. That saved us a credit note and an awkward call. That instinct to check the numbers twice is worth protecting." |
Notice what the right column has in common. Each one names a specific instance, states a consequence, and ends with either a question or a clear ask. None of them use the word "always" or "never", both of which invite the other person to find the one counterexample and argue about it.
Difficult Conversations at Work
Some feedback is not a tweak. It is a conversation about something that is genuinely going wrong, and those need a slightly different approach.
Prepare the first sentence and nothing else. Managers who script the whole conversation end up delivering a statement rather than having a discussion, and the other person can tell. Know exactly how you will open, then let it be a conversation.
Open with the fact, not the feeling. "I want to talk about the project handover" gives the other person a subject. "I want to talk about your attitude" gives them a threat.
Allow silence. The pause after you have said the difficult thing is where the other person processes it. Filling that silence, usually by softening what you just said, is the single most common way managers undo their own feedback.
Separate the behavior from the explanation. You need to be clear about what has to change. You do not need to win the argument about why it happened. A manager who insists on agreement about the cause often loses the agreement about the fix.
These are learnable skills rather than personality traits, which is the premise of most leadership training for managers worth doing, and the reason we treat interpersonal skills development as a trainable discipline rather than something people either have or lack.
Building a Team That Gives Feedback Back
The real measure of a feedback culture is not whether managers give it. It is whether anyone gives it upward.
That only happens if the first person who tries it has a good experience. If a team member raises something about how you run meetings and you explain why they are wrong, you have taught the whole team that the invitation was decorative. If you thank them, ask a follow-up, and change something visible, you have taught the opposite.
Ask for it specifically rather than generally. "Any feedback for me?" reliably produces nothing. "What is one thing I do in our weekly meeting that makes your job harder?" produces an answer, because it is narrow enough to be safe and specific enough to be answerable. The skills that make managers effective are largely these small structural choices rather than grand gestures, and the same is true across the broader leadership development work we run.
If you want your managers trained on this properly, with practice and real scenarios rather than a slide on the sandwich model, tell us what your managers are struggling with and we will build the session around it. You can see the full range of what we do with teams and leaders on our main site.

