Receiving Feedback — The Harder Half of the Skill

A senior leader asked her team for 'honest feedback'. They gave some. She defended every point. Six months later she asked again. Silence. They'd learned that asking and receiving are two different signals — and only one of them was real for her. By the time most leaders notice the silence, the truth-flow has been off for quarters.

Why it matters

Douglas Stone and Sheila Heen's 'Thanks for the Feedback' reframed the skill: receiving is the bottleneck, not giving. A leader who receives well is told more truth — and gets better decisions as a result. The compounding is powerful: each well-received piece of hard feedback teaches your team that the next one is also safe to share, and the truth-flow opens. Each badly-received piece teaches the opposite.

The other reason it matters: above a certain seniority, almost nobody will tell you anymore. Your title becomes a filter on the truth. The only counter-force is your demonstrated capacity to receive — and that capacity is judged from a few specific moments, not from how often you say 'I'm open to feedback'.

Three triggers

Naming the trigger to yourself buys 30 seconds — enough to choose a response instead of react. Most of the work is internal; the visible part is just the absence of the bad reaction.

The 'and stance'

Example

Ray Dalio's Bridgewater famously rates leaders publicly on how well they take feedback. Whatever you think of the system, the principle is sound: model receiving badly and you'll stop hearing anything that matters. Smaller version: the manager who visibly thanks a junior for pushing back, then acts on the input, gets 10x more useful pushback in the following months. The visible moment is what changes the team's calculus.

Apply on Monday

• Before responding to feedback, name the trigger to yourself.
• Reflect first: 'Let me make sure I got it — you're saying X.'
• Ask for one example to anchor the abstract.
• Say thank you. Take 24h before responding to anything that hits identity.
• When you act on feedback, tell the person you did and what changed.

Common mistakes

• Defending in the moment — kills future feedback.
• Dismissing because of the source.
• Treating one piece of feedback as identity-level truth.
• Asking for feedback you actually want validation for.
• Confusing 'I heard you' with 'I acted on it'.
• Punishing the feedback giver in subtle ways later — teams notice immediately.

Reflection prompts

1. Which trigger fires most for me?
2. Whose feedback am I dismissing because of who they are?
3. What feedback do I keep asking for that I never actually act on?
4. Where has my team gone quiet — and what did I do that taught them to?

Takeaways

• Receiving well is the bottleneck, not giving.
• Name the trigger first; address the content second.
• The 'and stance' beats defensiveness.
• One visible bad reaction costs six months of team truth.