You're sitting in the meeting, and someone just said the thing you didn't want to hear. Your face is doing something you can't fully control. Your brain is already building a defense. This is the moment that decides whether the feedback actually changes anything, and it's over before most people even realize it's happening.
Four moves for the moment right after, not a general essay on having a growth mindset.
01
Don't respond in the same conversation
Your first reaction to criticism is rarely your best one. "Let me think about that and come back to you" is a complete sentence, and it buys you the gap between the sting and a response you'll actually stand behind.
The instinct is to say something immediately, if only to fill the silence and prove you're not rattled. Resist it. What comes out in that first thirty seconds is almost always some mix of defensiveness and performance, neither of which is the actual you, and neither of which is what you want on record.
Script: "That's worth sitting with. Let me think about it and come back to you tomorrow."
The instinct is to say something immediately, if only to fill the silence and prove you're not rattled. Resist it. What comes out in that first thirty seconds is almost always some mix of defensiveness and performance, neither of which is the actual you, and neither of which is what you want on record.
Script: "That's worth sitting with. Let me think about it and come back to you tomorrow."
02
Separate the delivery from the content
Feedback can be true and also delivered badly, those are two different problems. If you dismiss the message because you didn't like the tone, you lose the useful part along with the part that stung.
It's tempting to focus on how something was said, because the tone is what actually hurt, and the content feels safer to argue with once you've decided the delivery was unfair. But someone being blunt, or catching you off guard, or picking a bad moment doesn't automatically make them wrong. Deal with the delivery separately, if it's worth raising at all, and deal with the content on its own merits.
It's tempting to focus on how something was said, because the tone is what actually hurt, and the content feels safer to argue with once you've decided the delivery was unfair. But someone being blunt, or catching you off guard, or picking a bad moment doesn't automatically make them wrong. Deal with the delivery separately, if it's worth raising at all, and deal with the content on its own merits.
03
Ask one clarifying question, not five defensive ones
"Can you give me a specific example?" gets you information. "Well, what about the time when..." gets you a debate. One is you trying to understand the feedback, the other is you trying to win the conversation.
The difference is easy to miss in the moment because both feel like you're just responding. But a defensive question is really a rebuttal wearing a question mark, it's built to make a point, not to learn something. A real clarifying question is the opposite, it's built to get you enough specifics that you can actually act on what you heard.
Script: "Can you walk me through a specific example of when that showed up? I want to make sure I understand exactly what you're seeing."
The difference is easy to miss in the moment because both feel like you're just responding. But a defensive question is really a rebuttal wearing a question mark, it's built to make a point, not to learn something. A real clarifying question is the opposite, it's built to get you enough specifics that you can actually act on what you heard.
Script: "Can you walk me through a specific example of when that showed up? I want to make sure I understand exactly what you're seeing."
04
Come back with what you're actually going to do differently
Not an apology, a specific change. It's the difference between "you're right, I'll be better" and "I'm going to send the agenda a day ahead of every meeting starting this week." The second one is the only one people actually notice.
An apology costs nothing and changes nothing, and most people who've given hard feedback before have heard plenty of apologies that went nowhere. A specific, observable change is the only thing that actually closes the loop, and it's what turns the feedback from an uncomfortable moment into something that visibly mattered.
An apology costs nothing and changes nothing, and most people who've given hard feedback before have heard plenty of apologies that went nowhere. A specific, observable change is the only thing that actually closes the loop, and it's what turns the feedback from an uncomfortable moment into something that visibly mattered.
After the Feedback: A Quick Worksheet
Fill this out in the gap you bought yourself, before you go back with a response.
| What was actually said, as close to their words as I can get it (not my interpretation of it) | |
| Is there a delivery issue worth raising separately, or is that not actually the point | |
| One clarifying question I still need answered | |
| The specific, observable thing I'm going to do differently, starting when |