Most feedback is received badly. Not because the person delivering it was bad at it — although they often are — but because the receiver's instincts get in the way before the message has had a chance to land.
Defend, justify, argue, dismiss, or accept-but-internally-resent. Five common reactions. None of them produce useful change.
The skill of taking feedback well isn't a personality trait. It's a small set of moves you can practice. The people who get good at it grow faster than the people who don't, by a meaningful margin.
What gets in the way
Three reflexive reactions that block useful feedback:
The defence kicks in before you've heard the whole thing. Someone starts saying something critical and your brain goes immediately to "but actually, X". You stop hearing the rest. You start composing the response. By the time they finish, you haven't fully received the message — you've received the first sentence and then your own internal counter-argument. The feedback can't change anything because it didn't actually arrive.
You take the message as a verdict on the person. Feedback is usually about a behaviour, a moment, a specific decision. The temptation is to hear it as a global judgment — "I'm not good at this", "they don't think I'm capable". That's almost never what was meant. But the moment it's heard that way, the conversation becomes a self-protection exercise instead of a learning one.
You assume the giver got it wrong. Sometimes they did. Often they didn't. The instinct to discount feedback because the giver didn't have full context is a way of avoiding the work of taking it seriously. Even partial feedback usually has something true in it. Filtering for what's true is more useful than dismissing because it's not 100% accurate.
What good reception looks like
A few moves that change how feedback lands:
Listen all the way through. Don't compose a response while they're talking. Don't interrupt to clarify or defend. Wait until they've finished. The cost of pausing is small. The cost of missing the actual content is large.
Reflect it back before responding. "What I'm hearing is that when I did X, it made Y harder for the team. Is that right?" This does two things — it confirms you understood, and it gives the giver a chance to clarify if they didn't quite say what they meant. Most miscommunications about feedback get caught here.
Sit with it before deciding what to do. The instinct is to respond immediately — agree or disagree, commit to change, push back. Resist that. "Let me think about this for a day" is a fine response. The feedback will land differently when you're not still in the moment of receiving it. Some things you'll agree with on reflection that you'd have argued with in the conversation.
Separate the message from the messenger. The person delivering the feedback might have delivered it badly. They might have got some specifics wrong. They might not be your favourite person. None of that automatically makes the feedback wrong. Filter for the parts that are true and useful, regardless of how the rest landed.
What to actually do with it
Reception is half the work. The other half is whether the feedback produces change.
A few practices that close the loop:
Pick the part that's most likely to be true and act on it. Don't try to act on everything. Pick the one element that you think has the highest chance of being a real pattern. Work on that. The compounding return is much higher than spreading across all the feedback at once.
Tell the giver what you're going to do. Not as a performance — as a closing of the loop. "I've been thinking about what you said, and I'm going to try X for the next month." This does two things: it tells them their feedback mattered, and it commits you publicly to the change. Both raise the probability of follow-through.
Check in later. A few weeks after, ask the same person whether they've noticed any difference. Their honest read on whether the change actually happened is more useful than your own self-assessment. If they say "no, I haven't noticed", that's the signal that whatever you thought you were doing didn't translate.
When feedback is genuinely off
Sometimes the feedback is wrong. The giver had bad information, misread the situation, or projected something onto you that wasn't there. Two moves for those cases:
Don't argue in the moment. Listen, reflect it back, and say you'll think about it. Disagreeing immediately is rarely productive — it tells the giver their feedback isn't welcome, even when it's wrong. Better to go away, think, and come back if you still disagree.
Come back with specifics. If you've thought about it and concluded the feedback was off, address it directly. "I've been sitting with what you said, and I want to push back on this part because of X." That's a real conversation. It's not defensive — it's a continued engagement with the substance. Done well, it strengthens the relationship rather than damaging it.
The wrong move is silently rejecting the feedback. The giver thinks you took it on board. You haven't. The next time the same pattern shows up, the giver will conclude you don't take feedback well, when the actual issue is that this particular feedback was wrong and you didn't say so.
The shift
Taking feedback well is a skill. It can be practiced. The people who develop it grow faster than the people who don't.
Listen all the way through. Reflect it back. Sit with it. Pick the part most likely to be true and work on that. Close the loop. Push back when needed, with specifics.
None of this is complicated. All of it requires overriding the instinct to defend, which is the part most people don't put the work in on.
If you're getting feedback that actually changes behaviour, reception is the half that lives with the receiver — and the half most career advice underweights. And active listening is the underlying skill that makes both giving and receiving feedback work.