How to give feedback that actually changes something

You've said the thing three times now. You softened it a little more each time, and the behavior hasn't moved. Or you haven't said it at all, because the last time you tried, the conversation went sideways and you spent the rest of the week managing the fallout.

This article covers why most feedback fails, and the exact language that makes it easier to hear. It also covers when to deliver it, the templates to use, and a diagnostic for when repeated feedback isn't changing anything. Read the first half before your next 1:1, and come back to the diagnostic section when someone on your team has heard the same feedback more than twice.

The advice comes from Kim Scott, who led teams at Google and wrote Radical Candor; Alisa Cohn, an executive coach who has worked with founders and senior leaders for more than 20 years; Mellody Hobson, co-CEO of Ariel Investments; and the Mochary Method curriculum, the coaching material Matt Mochary developed with startup CEOs and now publishes for free.

Why most feedback fails

Most feedback fails for one of four reasons, and all four are fixable.

Kim Scott's frame is worth having in your head before every one of these conversations. She defines the target as caring about the person and telling them the truth at the same time, and most of us miss on one axis or the other.

Scott calls the common failure ruinous empathy: you remember that you care about the person, you worry about hurting them, and you leave out the part they needed to hear. Most managers who think they have a directness problem actually have this problem.

Point at a specific action they took

This one change does more than anything else here. Every piece of feedback should point at something a video camera could have recorded.

The Mochary Method curriculum uses that test explicitly. "Please be more punctual" is not something a camera can capture. "Please text me if you're going to be more than a minute late to our meetings" is. If your feedback can't pass the camera test, you're asking the person to read your mind about what "better" means.

Alisa Cohn works with her clients on exactly this before the conversation happens. She has them find the evidence first, and the preparation makes the conversation easier on both sides.

Cohn also states the standard alongside the gap. She'll say the writing needs to be at a certain level, here are the specific reasons it isn't there, and here's why that standard matters for how the team executes. Now the person knows what to aim at.

One more rule from the Mochary curriculum's note on giving feedback badly: say what you want them to do, not what to stop. "Marty, your zipper is down" is only half the message. The full version says what to do about it and why it matters for the work.

Say it close to when it happened

The most common structural mistake is saving feedback for a scheduled slot. Kim Scott is direct about this.

Scott describes these as two-minute impromptu conversations that happen between meetings. Her own example is a boss who gave her feedback while they walked to the next meeting together, which cost neither of them any extra time. If you're booked back to back all day, those two minutes never appear, and everything gets deferred to a formal slot where it lands ten times harder.

Two practical constraints from the Mochary feedback doc. First, use a medium where you can see the reaction. In person is best, video is fine, audio is worse. Never give critical feedback by email, text, or Slack, because you can't see the person get angry and you can't reassure them. Second, write the feedback down for yourself before you deliver it. In the moment your brain will push you to soften it, and the note keeps you honest.

The Like and Wish That template

For ordinary week-to-week feedback, the Mochary curriculum uses a two-line structure that takes about fifteen seconds:

Both halves have to be concrete. The affirming half does real work here: it tells the person which behavior to keep, and it makes the second half survivable. The Mochary doc is emphatic that you affirm the relationship every single time you give feedback, not occasionally.

Reed Hastings' version, which the Mochary material calls the current best practice, adds one more beat: explain why the change helps the company and helps the person. So the full shape is what you liked, what you want instead, and what it makes possible.

Tell people where they stand

Relative feedback tells someone whether a specific thing went well, which still leaves the bigger question open: am I doing a good job here? Most people carry constant low-grade anxiety about that, and the annual review is far too late to answer it.

The Mochary absolute feedback template is a monthly 1:1 ritual that takes three minutes:

The number feels blunt the first time you say it out loud, and that bluntness is why it works. A 3 with a clear path to a 4 removes more anxiety than a vague "you're doing great," and nobody who hears a 3 every month is shocked when a 2 arrives. As the Mochary material puts it, bad news is less anxiety-inducing than no news.

If you're on the receiving end of this and want to prepare for it, the 1:1 playbook covers how to run the conversation from the other side.

When you've given the same feedback three times

This is the situation that sends managers to a coach. You've been clear, or you think you have, and nothing has changed. Celine Teoh, a CEO coach who writes for the Mochary curriculum, uses a three-way diagnostic before you conclude the person is the problem. Ask which of these three is actually broken, because each one has a different fix.

Clarity: are you asking them to read your mind?

Teoh's example is a CEO telling an SVP to "increase visibility in the sales CRM." Visibility means something precise in the CEO's head and nothing at all in the SVP's. The rewrite is "update deal blockers daily in the CRM before our sales meetings, so I can help you unblock them."

Run the camera test again, and then run a second one: if they did exactly what you asked, word for word, would you be satisfied? If the answer is "well, that's not quite what I meant," your feedback was never clear enough to act on. Read the full clarity and capability note for the longer version.

Capability: can they actually do it yet?

Teoh calls this the "why can't my five-year-old drive" problem. The five-year-old isn't being defiant. He lacks the training, the coordination, and the height. If you've asked a two-years-into-the-job manager to run a program a seasoned VP would find hard, no amount of feedback closes that gap.

Teoh recommends the "I intend to" exercise, borrowed from David Marquet's submarine command. Before acting, the person sends you a short "I intend to do X because Y." You review the intention rather than the outcome, which lets you correct the thinking cheaply and lets them keep the decision. Over a few weeks they get better at the thinking, and you stop having to make the call for them.

Caring: do they have a reason to change?

If it isn't clarity and it isn't capability, you're looking at motivation. Teoh's note on motivation gives two causes worth checking.

The first is that you're paying in the wrong currency. Borrowing from Allan Cohen and David Bradford, she points out that people are driven by different things: vision and excellence, learning and new resources, recognition and visibility, inclusion and personal support, gratitude and ownership. You might care about efficiency while the person in front of you is motivated by getting to learn something new. An emerging leader might resist changing course because they need to be seen as steady, not because they disagree with you. Watch what they get excited about and what they say when they push back, then build the request around that.

The second is that your feedback feels like a threat. Teoh uses David Rock's SCARF model: status ("do my colleagues still respect me?"), certainty ("does this mean I'm not right for this company?"), autonomy ("they're trying to control how I work"), relatedness ("I thought we were a team"), and fairness ("this is undeserved"). Guess which one is firing and address it out loud. For autonomy, that sounds like "I value your approach here. This isn't me controlling how you work, it's me wanting to talk through alternatives. How would you want to implement this?"

Teoh's last suggestion is the one most managers skip. For a few days, give no constructive feedback at all and notice every small step in the right direction out loud. She compares it to cheering a toddler learning to walk, where nobody chastises the falling down. It's harder than it sounds, because most of us are wired to spot the gap.

Scripts for the hard ones

When they get defensive

Alisa Cohn has a rehearsed script for this, and her point is that the value comes from having prepared one at all.

Cohn notes that "you're getting emotional" makes some people angrier, so pick your words for the person: "I can see this is upsetting you," or "the temperature between us just changed." The structure underneath stays the same. Name your positive intent, name what you're seeing, and offer to continue now or later while making clear the conversation is happening either way.

When they cry

The Mochary guidance here is short and useful. Crying is how some people release emotion, and it rarely lasts more than a minute or two. Don't talk them out of it, don't put a hand on their shoulder, don't start backpedaling on the feedback. Breathe and let it finish. Then keep going. If you treat crying as unacceptable, the emotion doesn't go anywhere. It turns into a bad mood you'll be managing for a week.

When it's a repeated pattern

Faith Meyer's three strikes process in the Mochary curriculum gives conflict-avoidant managers a structure so the escalation doesn't come out of nowhere.

Alisa Cohn's version of the third conversation is similar and worth saying out loud in advance: "This is going to be a difficult conversation. I've seen this multiple times, we've talked about it multiple times, and it's still not fixed." She points out the upside of doing this properly, which is that you often don't have to fire the person, and if you do, the conversation is straightforward because nothing about it is a surprise.

When you're worried they'll quit

The Mochary doc names the excuse managers use most: this person isn't performing, nobody else can do their job, and if I tell them the truth they'll leave and I'll be stuck. The response is that withholding feedback guarantees the failure you're afraid of. Give it well and one of two things happens. They improve, or they admit the job isn't right and help you find their replacement. Both are better than another two quarters of you quietly resenting them.

Take feedback so people keep giving it

Your team decides whether to tell you the truth based on what happened the last time someone tried. From their side, it's a bad bet: if you take it well they get a small improvement, and if you take it badly you might become vindictive. Most people won't make that wager until you prove it's safe.

Asking generically doesn't work. Kim Scott is blunt about the default question.

Scott recommends soliciting feedback from every direct report weekly, with five minutes reserved at the end of the 1:1, and varying the wording so it doesn't sound like a script you stopped meaning. Christa Quarles, then CEO of OpenTable, told Scott she could never say those words and asked "tell me why I'm wrong" instead. That works because it demands an answer.

The Mochary curriculum's five A's are what you do with the answer once you get it:

Acknowledging is the step most managers skip, and Mochary argues it matters more than acting on the feedback. People need to hear their own words come back at them. You can check whether you did it by asking "do you feel heard?"

Mellody Hobson, co-CEO of Ariel Investments, learned the receiving side from a coach and from being on the wrong end of it.

Her story about receiving it is the more useful part. Senator Bill Bradley told her she could be a ball hog. She sat there telling herself not to cry, and her reasoning was practical.

Hobson also has a rule for sorting signal from noise: the first time someone calls you a horse's ass you can dismiss it, the second time you think about it, and by the third time you buy a saddle. When several people tell you the same thing, stop debating whether each of them is right. And when you're the one giving it, she quotes Dick Parsons on the difference between honest and brutal: "I'll be honest, but I don't need to be brutal."

If your own manager is the one who won't hear feedback, the respectful disagreement playbook covers how to raise it without the conversation becoming about your tone.

When nothing changes anyway

You've been specific, you've been fast, you've checked clarity, capability, and motivation, and you've run three strikes. At that point the feedback isn't the problem, and the honest move is to change the situation rather than repeat yourself.

Before you deliver news like this, the bad news playbook has a structure for saying the hard thing early and clearly. If the conversation is about a promotion that isn't happening, the promotion denial playbook covers what the person will want to ask you.

Frequently asked questions

Should I use the feedback sandwich?

No. Mellody Hobson calls it a sandwich that never tastes as good as it sounds on the menu, and the reason is that people learn to wait for the middle and discount the praise. Give specific praise on its own schedule, and give critical feedback with its own reason attached. Affirming the relationship before critical feedback is different from burying the point between two compliments.

How much feedback is too much?

Kim Scott recommends soliciting feedback weekly and giving it in the moment, which sounds like a lot until you notice it replaces the long, tense quarterly conversation. If someone is hearing only criticism from you, add praise rather than cutting back on the criticism. Celine Teoh's suggestion of a few days of nothing but noticing the good is a good reset.

What if I manage someone remotely?

Use video, not Slack or email. The whole reason to avoid one-way channels is that you can't see the person get defensive, so you can't reassure them, and unaddressed anger turns into resentment. A five-minute video call the same day beats a carefully worded message.

What if the feedback is about something I can't describe as an action?

Feelings-based feedback is genuinely harder, and Alisa Cohn acknowledges it. Do the work anyway. Ask yourself what your evidence is that this is happening, and you'll usually find you're reacting to two or three specific moments. Name those moments and say what you thought when they happened, rather than diagnosing the person's character.

Can I give feedback to someone more senior than me?

Yes, and Scott's order of operations applies the same way in every direction: solicit first, then give praise, then give criticism. Ask permission before the critical piece and keep it to something specific you observed.

The feedback checklist