Receiving Feedback Well

Feedback That Lands taught the daily give: how to say the hard thing so it changes behavior instead of triggering defenses. This page is its mirror, and the harder half — the daily take. Because feedback is not something you dispense downward like medicine. It’s a two-way channel, and the direction most managers neglect is the one pointing back at them.

The claim underneath this page is blunt: a manager who cannot receive feedback well will slowly stop receiving any at all. Not because there’s nothing to say — there’s always something — but because people learn, in about two bad experiences, that telling you the truth costs more than staying quiet. This page shows you the specific moves that keep the channel open: how to hear criticism without your ego hijacking the moment, and why receiving well is what earns you the right to give.

Why this is the move that protects every other move

Everything the earlier pages built — the one-on-one container, feedback that lands, the trust deposited conversation by conversation — assumes information flows toward you. You find out the priority was wrong, the process is broken, your own instruction confused everyone, while it’s still small and cheap to fix. That early warning is the single biggest advantage a manager can have. And it is entirely at the mercy of how you react the moment someone hands you a hard truth.

Here’s the mechanism. Giving your boss feedback is risky — they hold your review, your projects, your standing. So people run a quick, mostly unconscious cost-benefit before they speak: is this worth it? Your reaction to the last piece of feedback set the price. React badly once — argue, sulk, go cold — and the price goes up for everyone watching, and someone is always watching. React well and the price drops. You are not just responding to one comment; you are setting the exchange rate for all future honesty.

That’s why receiving is the load-bearing skill. A manager who gives brilliant feedback but takes it terribly ends up in an echo chamber: surrounded by yes, blindsided by problems everyone else saw coming. The willingness the whole part depends on — people telling you the truth early — is built or destroyed right here.

The three defensive defaults

When criticism lands, most of us reach for one of three reflexes. None of them are villainous; they’re just protective. But each one teaches the other person the same lesson: don’t do that again.

JUSTIFY   "Well, the reason I did it that way was —"
          You explain. You give context. It sounds reasonable.
          What they hear: my point bounced off. Not worth repeating.

DISMISS   "I think that's a bit unfair / that's just your read."
          You shrink the feedback, question its accuracy, wave it off.
          What they hear: bringing this up gets me an argument, not a change.

COLLAPSE  "God, you're right, I'm terrible at this, I'm so sorry —"
          You over-apologize and fold. It looks humble. It isn't.
          What they hear: now I have to manage your feelings. Exhausting.

Notice that collapse feels like the opposite of defensiveness but does the same damage. When you crumple, the other person’s next job becomes reassuring you — comforting the manager they just criticized. That’s a tax on honesty just as real as an argument, and people pay it once before deciding it isn’t worth it.

All three share a root: they’re about you — protecting your competence, your record, your feelings — at the exact moment the conversation needs to be about the work. The person took a risk to hand you something useful, and all three defaults, however polite, punish the risk.

The common trap — “I’m very open to feedback”

The managers least able to hear criticism are often the ones most confident they welcome it. They say “my door is always open” and mean it — then justify, dismiss, or collapse the moment real feedback walks through the door, without ever noticing they did. The tell isn’t what you say about feedback; it’s whether you can recall a recent time you changed because of it. If your memory is empty, the likeliest reason isn’t that you’re flawless. It’s that people quietly stopped bringing it to you, and you never felt the silence descend.

The core move: get curious before you get defensive

There is one move that replaces all three defaults, and it’s small enough to actually do under pressure: before you react, ask for the specific example behind the general comment.

Feedback almost always arrives as a generalization — “you seem impatient in meetings,” “you’re a bit of a bottleneck,” “the team feels micromanaged.” Your ego hears a verdict and reaches for the shield. Curiosity does something different: it treats the comment as a lead, not a sentence, and goes looking for the incident underneath.

Them:  "Honestly, it feels like you don't really trust us with the big stuff."

Reflex (justify):  "I do trust you — I just need to stay across the risky bits."
Curious:           "That's important — can you give me a recent example?
                    When did it feel that way?"

The curious version does three things at once. It buys you the two seconds your defensiveness needs to pass. It signals — unmistakably — that you’d rather understand than win, which is the safety that keeps the channel open. And it converts a vague, unactionable jab into something concrete you can actually evaluate: the Tuesday when I reassigned the client account without asking. You can’t fix “you don’t trust us.” You can fix a specific thing you did on Tuesday.

Ask for the example even when — especially when — you think the feedback is wrong. If it’s genuinely off-base, the example is what will reveal that, and it’ll reveal it to both of you, in the open, instead of you privately deciding they’re mistaken and moving on.

In practice — the andon cord and the manager who pulled it

On a Toyota-style production line the andon cord lets any worker stop the entire line to flag a defect. The system only works because pulling the cord is treated as help, not insubordination — the line lead comes over to understand, not to scold. Now picture the equivalent in an office: someone stops your line — “I don’t think this plan holds up.” A manager who responds “explain, walk me through where it breaks” has just made the cord safe to pull again. A manager who responds “it’s fine, trust me” has quietly welded the cord shut. Both taught the whole team, in one moment, what pulling the cord costs.

Separate the two questions

Curiosity gets you the example. Now you have to do something with it — and here most people fuse two questions that must stay apart:

1. Is this accurate? — Is there a real signal here? Did the thing they describe actually happen, and did it land the way they say?
2. What will I do about it? — Given the signal, what, if anything, should change?

Fusing them is what makes feedback feel like an all-or-nothing verdict you must either swallow whole or reject entirely. But you can accept a signal without accepting every conclusion. Someone might be completely right that meetings feel rushed (accurate) and wrong about the cause and the fix (their conclusion). If you treat the whole package as one thing, you’ll reject the accurate part just to escape the bad conclusion — and lose the useful signal with it.

Feedback:  "You're a bottleneck — you should stop reviewing every release."

Q1 — Is it accurate?     Yes. Releases genuinely wait on me. That's real.
Q2 — What will I do?     NOT "stop reviewing everything" (some need my eyes).
                         Instead: delegate low-risk releases, keep the two
                         that actually carry client risk. Signal accepted;
                         their exact fix, adapted.

Saying this out loud is powerful: “You’re right that I’m slowing releases down — that’s real, thank you. I don’t think stopping all reviews is the answer, but let me find what I can hand off.” You’ve validated the person and the signal without pretending they’ve solved your job for you. That’s the difference between a defensive “yes but” and an honest “yes, and here’s my thinking.”

The order matters. Do Q1 first, generously — look hard for the grain of truth before you evaluate the fix. Most feedback that feels unfair still contains a real signal wrapped in a clumsy conclusion. Your job is to unwrap it, not to use the clumsy wrapping as an excuse to discard the whole thing.

The evidence — the higher you go, the less you hear

A consistent finding in organizational research is that upward feedback gets scarcer and softer as authority increases — people filter what they tell those with power over them, a tendency sometimes discussed under labels like the mum effect (the reluctance to pass bad news upward). Treat the specifics loosely, but the direction is reliable and matches what every senior manager eventually notices: the more senior you are, the more likely it is that no one is telling you the unvarnished truth, and the more deliberately you have to work to earn it. Seniority doesn’t reduce your blind spots. It reduces the number of people willing to point at them.

Receiving well is what earns you the right to give

There’s a quieter reason this skill matters, and it closes the loop with the previous page. The team is watching how you take feedback, and they’re calibrating how much to trust your feedback by it.

A manager who dishes out criticism but bristles at receiving it reads as someone who thinks feedback flows one way because they’re above it. That manager’s feedback lands as judgment from on high — something to endure, not use. But a manager who visibly takes a hard truth, thanks the person, and changes something, models the exact behavior they’re asking for. Their feedback lands differently: as this is how we all get better here, me included. You cannot credibly ask a team to be open to feedback you can’t take yourself. Receiving well is the price of admission for giving well.

This is also how safety scales. When people see you take criticism without punishing the messenger — especially in front of others — they learn the room is safe, and problems start surfacing early instead of festering. One manager who receives well in a visible moment does more for a team’s honesty than any “speak up, my door is open” speech ever will. The speech is words; the moment is proof.

The close: thank, then follow up

Two small acts turn a single good reception into a durable open channel.

First, thank them genuinely — at the end, regardless. Not the reflexive “thanks for the feedback” that signals the conversation is over, but a real acknowledgment of the risk they took: “That can’t have been easy to say. I’m glad you did.” You’re rewarding the courage, separately from whether you agreed. This matters most when you disagree — thanking someone for feedback you’re going to partly decline is exactly what proves the channel is safe even when you don’t get your way.

Second, and most neglected — follow up later on what you changed. A week or a month on, close the loop: “You told me I was rushing our meetings. I’ve started leaving the last ten minutes open — has that helped?” This is the move almost everyone skips, and it’s the one that makes feedback feel worth giving again. Without it, feedback disappears into a void; the person never learns whether their risk mattered, so they conclude it didn’t. With it, they see cause and effect — I spoke, something changed — and the next honest thing becomes far easier to say.

The full sequence, in one motion:

  1. CURIOUS   →  "Can you give me a specific example?"
  2. SEPARATE  →  Is it accurate?  (then)  What will I do?
  3. THANK     →  "That took courage to say. Thank you."
  4. FOLLOW UP →  (later) "Here's what I changed. Did it help?"

None of these require you to be thick-skinned or preternaturally calm. They require you to notice the defensive reflex, buy two seconds with a question, and treat honesty as the scarce, valuable thing it is.

How it connects

This page completes the feedback loop with Feedback That Lands: the give and the take are one skill practiced in two directions, and neither works alone. It also arms you for Hard Conversations Without Flinching — a manager who can absorb a hard truth without collapsing or attacking is the same manager who can deliver one steadily. And it deposits directly into the trust account from the part overview: every time you receive well, you make the next honest thing cheaper to say, which is exactly how a group of people and a goal becomes reliable outcomes instead of a room full of quiet.

Try this

The next time someone gives you even mild feedback this week, run the sequence deliberately and watch yourself do it. Before responding at all, ask for a specific example (“when did that come up?”). Silently separate the two questions — is there a real signal, and what (if anything) will I change — and resist collapsing them. End by thanking them for the risk, not just the content. Then, and this is the part to actually schedule: put a note in your calendar two weeks out to tell that person what you did with it. If no one gives you feedback this week, that silence is itself the finding — go ask one person, “what’s one thing I could do better?”, and practice receiving the answer.

Reflect

1. When you last received criticism, which default did you reach for — justify, dismiss, or collapse? What did that reaction teach the person about bringing you the next hard truth?
2. Can you recall a specific recent time you changed your behavior because of feedback someone gave you? If the memory is thin, what does that suggest about how safe people feel being honest with you?
3. Think of a piece of feedback that felt unfair. If you separate “is there a signal here?” from “do I accept their fix?”, is there a grain of truth you rejected along with the clumsy conclusion?
4. Who on your team is most likely to tell you when you’re wrong — and who has gone quiet? What did your past reactions have to do with each?
5. When did you last follow up with someone to tell them what you changed after their feedback? If never, whose honesty have you accidentally let vanish into a void?

Show reflections

1. The point is to catch your specific reflex, because you can’t interrupt a pattern you can’t name. Justify and dismiss look defensive; collapse hides as humility but taxes the other person just as much. Whichever it is, the lesson it teaches is the same — the price of honesty just went up — and naming it is the first step to lowering it.
2. An empty memory is rarely evidence that you’re flawless; it’s usually evidence the channel has closed. Be especially suspicious if you feel open to feedback but can’t point to a single behavior it changed. The gap between the two is where your blind spots live.
3. Most “unfair” feedback is a real signal wrapped in a bad conclusion. The skill is unwrapping it — accepting the accurate part while adapting or declining the proposed fix — rather than using the bad wrapping as a reason to bin the whole thing. If you rejected it wholesale, you probably threw out a signal to escape a conclusion.
4. The person who tells you you’re wrong is your early-warning system; protect them fiercely. The one who went quiet often did so after a specific bad reaction of yours — trace it back. Restoring that channel usually means one visibly good reception, not a speech about openness.
5. Following up is the rarest and most powerful move because it proves the loop is real — I spoke, something changed. If you’ve never done it, feedback has been disappearing into a void on your end, and people have quietly concluded their input doesn’t matter. One “here’s what I changed, did it help?” reopens the channel faster than anything else.