How Feedback Actually Lands

What happens after you speak, and what turns a conversation into change.

This is the fourth and final part of a four-part series on feedback. Part one covered the conditions. Part two covered the leader's inner work. Part three covered the conversation itself. This piece is about what happens after.

You have done the work. The conditions are ready. You have looked at yourself honestly. You delivered the feedback well: you were specific, you paired care with challenge, you made it a dialogue, you named the purpose out loud.

And then you stopped talking.

Most leadership content treats this as the end of the work. The feedback has been delivered. The conversation is closed. Whatever happens next is up to the receiver. The leader's job is done.

That is not what the research says. And it is not what experienced leaders eventually learn.

Feedback does not exist until it is absorbed and turned into behavior. Everything before that is just talking. The conversation that produces change and the conversation that produces nothing look identical from the outside in the moment they end. The difference shows up in the days and weeks after.

Three things decide whether feedback lands and turns into change. They are about the receiver's experience and the system that surrounds it, not about the giver's words.

What Happens Inside the Receiver

Douglas Stone and Sheila Heen, after twenty years of teaching feedback at the Harvard Negotiation Project, argued that the entire feedback industry has been pointed in the wrong direction (Stone & Heen, 2014). We have invested heavily in training people to give feedback better. The actual leverage, they argue, is in receiving. When the receiver knows how to metabolize hard input, the conversation works even when the delivery is imperfect. When the receiver cannot, the most carefully delivered feedback in the world bounces off.

Their research identifies three distinct triggers that block the receiver's ability to hear feedback. Each one fires in a different way and requires a different response.

The truth trigger fires when the feedback feels wrong. The receiver disagrees with the content. They think the giver has the facts wrong, or has drawn the wrong conclusion from the facts. The defense is to argue. To explain. To prove the feedback inaccurate. This trigger fires most often when the feedback is, in fact, partly wrong, which is more common than feedback givers admit.

The relationship trigger fires when the feedback feels wrong coming from this specific person at this specific time. The content might be accurate, but the receiver cannot separate the message from the messenger. The defense is to attack the credibility of the giver. To list reasons why this person has no right to say this. This trigger fires most often when there is unresolved history between the two people that the giver has not addressed.

The identity trigger fires when the feedback threatens the receiver's sense of self. The content might be accurate and the giver might be credible, but the implication of the feedback is that the receiver is not who they thought they were. The defense is to spiral. To overcorrect. To assume that one piece of feedback means everything is wrong. This is the trigger that does the most long-term damage when it is not understood.

The skilled receiver learns to notice which trigger is firing, and to set it aside long enough to consider the content. The unskilled receiver mistakes the trigger for the truth, and defends accordingly.

This matters for the giver too, because the giver can shape which trigger is likely to fire. Specificity reduces the truth trigger by making the feedback harder to dispute. Care paired with challenge reduces the relationship trigger by signaling that the conversation is in service of the receiver, not against them. Naming the purpose reduces the identity trigger by making clear that the feedback is about a behavior, not about the receiver's character.

What it looks like when it's missing

The receiver defends, explains, or counter-attacks instead of engaging with the content. Feedback conversations end with the giver feeling heard and the receiver feeling sentenced. The same piece of feedback gets delivered repeatedly to the same person with no observable change in behavior. The receiver agrees in the moment and reverts within a week.

What to do about it

After the conversation, ask yourself what likely triggered in the receiver. You will not know for sure, but the guess is useful. If you noticed defensiveness, the identity trigger probably fired. If you noticed pushback or argument, the truth trigger probably fired. If you noticed sudden distance, the relationship trigger probably fired.

That guess tells you what the follow-up conversation needs to address. If the identity trigger fired, the follow-up is reassurance that the feedback is about a specific behavior, not about who they are. If the truth trigger fired, the follow-up is to revisit the evidence together and look for what each of you might have missed. If the relationship trigger fired, the follow-up is to address the relationship itself before returning to the content.

Whether the Conversation Looks Forward or Backward

Marcus Buckingham and Ashley Goodall, in a Harvard Business Review piece that has shaped how serious organizations think about feedback, argued that the most effective developmental conversations spend less time on what happened and more time on what to do next (Buckingham & Goodall, 2019). They called this the difference between feedback (which is backward-looking, about past behavior) and "feedforward" (which is forward-looking, about future behavior).

The distinction matters because backward-looking conversations produce explanation, not change. The receiver spends their energy reconstructing what happened, justifying it, contextualizing it, or arguing about it. Even when the conversation goes well, it ends with shared understanding of the past. The future is left implicit.

Forward-looking conversations produce different outputs. The receiver spends their energy imagining a different version of themselves in a future situation. They commit to a specific behavior. They name what success will look like next time. The past is the starting point, not the destination.

This does not mean the past is irrelevant. The past is where the feedback comes from. But the past is fuel, not the engine. The engine is the question, "what do you want to do differently next time?"

A practical rule: spend roughly one-third of the conversation on what happened, and two-thirds on what to do next. Most leaders do the opposite. They marinate in the past, deliver the verdict, and then end the conversation just as it was getting useful.

What it looks like when it's missing

Conversations that end with the receiver understanding the past but not knowing what to do about it. Performance reviews that document history but produce no behavior change. Coaching sessions that turn into archaeology. The phrase "I hear you, but..." which is the receiver's way of saying the past is not where the conversation needed to land.

What to do about it

Before the conversation, write down what you want the receiver to leave with. Not what you want to say. What you want them to walk away knowing or planning. If your answer is mostly about the past, the conversation is going to be backward-looking. Reshape it before you have it.

During the conversation, when the past has been adequately covered, name the shift out loud. "Okay, that is the past. Let's spend the rest of this on what's next." That single sentence pivots the conversation and signals to both of you that the purpose has changed.

End the conversation with a forward-looking question and a forward-looking commitment. "What will you try in the next two weeks? What will I see that is different?"

Whether Anyone Follows Up

This is the part that decides whether the feedback was a conversation or a change.

Most feedback dies in the silence after the conversation. The giver delivered the message and assumes the work is done. The receiver, even if they took the feedback well, drifts back into the old pattern within a week because nothing in the system made the new pattern stick.

The research on behavior change is uncomfortable on this point. Decades of work in clinical psychology, organizational behavior, and adult learning all converge on the same conclusion: insight does not produce behavior change. Structure does. The leader who delivers excellent feedback but builds no structure around it has done less than the leader who delivers mediocre feedback and follows up consistently.

What does structure look like? It is not complicated. It is putting the next conversation on the calendar before the current one ends. It is asking, in the next one-on-one, what they tried and what happened. It is noticing, out loud, when the new behavior shows up, so the receiver knows you are paying attention. It is small. It is repeated. It is what almost no one does.

The reason almost no one does it is that follow-up is unglamorous. The dramatic moment is the original conversation. That is where the giver feels brave. That is the story they tell themselves about their leadership. The follow-up is the unglamorous, repetitive, quiet work of actually seeing change through.

Kluger and DeNisi's foundational meta-analysis, the one that runs underneath this entire series, makes a related point (Kluger & DeNisi, 1996). Feedback effectiveness is not determined by the feedback event alone. It is determined by the system of attention around the feedback. Isolated feedback events, even excellent ones, often fail to produce change. Sustained attention, even imperfectly delivered, often does.

What it looks like when it's missing

The receiver agrees in the moment and reverts within a week. The giver gives the same feedback again two months later and wonders why nothing changed. Performance reviews that recycle the same developmental themes year after year. The phrase "we've had this conversation before" which is almost always a sign that the conversation was never followed up.

What to do about it

Before the feedback conversation ends, put the next conversation on the calendar. Not "let's check in soon." A specific date and time. "Let's revisit this in three weeks. Same time, same place."

In the next one-on-one, lead with what you talked about. "How is the thing we discussed three weeks ago going? What have you tried? What's harder than you expected?"

Notice, out loud, when the new behavior appears. "I saw you do that thing differently in the meeting yesterday. That landed well." The receiver needs to know you are watching, not as surveillance, but as care. The watching is part of what makes the change stick.

This is the work most leaders skip. The ones who do it are the ones whose direct reports actually develop.

Why This Closes the Series

Across four weeks, we have taken feedback apart properly.

Week one named the conditions. Feedback fails when the relationship is not safe, the expectations are not visible, or the cadence is too rare. None of those failures are about the words.

Week two named the leader's inner work. Feedback fails when the leader has not examined their own contribution, their own blind spots, or their own capacity to receive. None of those failures are about the receiver.

Week three named the mechanics of the conversation itself. Feedback fails when it lacks specificity, when care is missing or challenge is missing, when the dialogue is one-way, or when the purpose is not named.

This week named what happens after. Feedback fails when the receiver cannot metabolize it, when the conversation looks only backward, or when no one follows up.

Underneath every piece of this is the same finding: feedback effectiveness collapses as the receiver's attention shifts from the task to the self. The conditions, the inner work, the conversation, and the follow-up are all versions of the same discipline: keep the receiver's attention on the work, not on themselves, so that what you say has a chance to become what they do.

The leaders who do this well are not better people than the leaders who do not. They are people who have built the habit of treating feedback as a system, not a moment. They invest in the conditions. They do the inner work. They have the conversation deliberately. They follow up consistently. None of it is dramatic. All of it compounds.

That is the work. It is harder than it looks. It is also the thing that separates the leaders people stay for from the leaders people leave.

A short reflection before you go

Think about a piece of feedback you received in the last year that did not stick.

Which of the four layers broke?

Were the conditions wrong? Was the giver not doing their inner work? Was the conversation poorly mechanic'd? Or did no one follow up?

Whichever layer broke is the one to repair next time. Not just on the receiving side. On the giving side too. Because the leaders who turn feedback into change are the ones who keep all four layers honest, in every direction the feedback flows.

This is the final piece of the series. Thank you for reading. The series hub holds all four pieces together if you want to come back to them, or pass them to someone else.

See our resources section for the free tools that accompany this series.

Subscribe to The Grow Point to keep receiving new work.

References

Buckingham, M., & Goodall, A. (2019, March-April). The feedback fallacy. Harvard Business Review. https://hbr.org/2019/03/the-feedback-fallacy

Kluger, A. N., & DeNisi, A. (1996). The effects of feedback interventions on performance: A historical review, a meta-analysis, and a preliminary feedback intervention theory. Psychological Bulletin, 119(2), 254-284. https://psycnet.apa.org/record/1996-02773-003

Stone, D., & Heen, S. (2014). Thanks for the feedback: The science and art of receiving feedback well. Viking.