How to Take Feedback Without Getting Defensive. It Takes Six Seconds.

A project manager once told me, in front of two other people, that my status reports were impossible to act on. My mouth was open before she'd finished the sentence. I explained the reporting template, the constraints, the fact that nobody had ever complained, and I did it in a reasonable tone of voice while being completely unreasonable. She was right. It took me about four months to admit that, and by then she'd stopped telling me things.

The thing that fires when somebody criticises your work isn't judgement. It arrives before judgement does. You feel the heat in your face, and your brain starts assembling the defence, and none of that is a decision you made.

Six seconds is roughly how long it takes to pass if you don't feed it. That's not science, it's just the number I've found works: count six, slowly, while looking at the person. The counting is the point. It occupies the part of you that was about to speak.

What comes out of your mouth in those six seconds is almost always the worst version of what you think. "Well, the reason I did it that way is..." is the classic, and notice what it does. It converts a conversation about impact into a debate about intent, and the person giving the feedback now has to argue with you about your own motivations, which they can't win and won't try.

So the whole technique is: don't speak first. Let it pass. You genuinely do not need to say anything for six seconds and nobody will find it strange.

Once the six seconds are up, you need something to say, and rehearsing it in advance matters because you won't be composing well in the moment.

"Can you give me a specific example?" This is the workhorse. It isn't a challenge if you say it plainly, and it turns vague feedback into something you can actually use. Half the feedback you get will be a general impression the person has never had to evidence, and the act of finding an example clarifies it for both of you.

"What would you have done instead?" Useful, and slightly risky, because sometimes the answer is worse than what you did. Ask it anyway. If their alternative is worse, you've learned what they thought your options were, which is usually the real misunderstanding.

"Let me think about that, can we pick it up tomorrow?" The escape hatch, and it's a legitimate one. Use it when you can feel that you're going to argue. Saying it out loud takes more nerve than arguing does, and it lands far better than people expect.

What you don't say, ever, is "that's not fair". Even when it isn't. Fairness is a conversation for a different day and saying it now guarantees the feedback stops coming.

This is where the actual work happens, and it's quiet, and nobody sees it.

The morning after, write the feedback down in the other person's words. Not your improved version of it. Theirs. Then split it.

What's straightforwardly true. There's usually some, and the sooner you can look at it without flinching, the better. My status reports really were impossible to act on. Everything I said in my defence about the template was accurate and also entirely beside the point.

What's true about the effect but wrong about the cause. This is the biggest bucket and it's where most of the value sits. Someone tells you that you don't listen in design reviews. Maybe what's actually happening is that you've already read the document and you're three steps ahead, and you're cutting people off because you're impatient rather than because you're not listening. The effect is real. Your reading of the cause is more accurate than theirs. Both things are useful and only one of them was available to them from the outside.

What's just wrong, based on information they don't have. This exists too, and it's smaller than you think it is on the day and bigger than nothing. Deal with it in a separate conversation, calmly, with the information attached. Not in the moment, and not as a rebuttal to the rest.

Then pick one thing from the first two buckets and change it. One. The whole point of the sorting exercise is to end up at a specific behaviour, not a general feeling of having been improved.

Here's what happens to leaders who are hard to give feedback to, and it's worse than the reputational bit.

Information stops arriving. Not dramatically, nobody announces it. People just calculate, roughly accurately, that the cost of telling you something outweighs the benefit, and they route around you. The architect stops mentioning that your design has a scaling problem. The delivery manager stops flagging that the client is unhappy, and starts managing it herself until she can't.

You end up with a version of reality that has been pre-filtered for your comfort, and you make decisions on it, and you cannot understand why things keep surprising you. That's the actual price. It isn't a bruised ego, it's a corrupted instrument panel.

And the tell is horribly subtle. It looks like everything being fine. It looks like a team that agrees with you a lot.

The reason most of us are bad at receiving feedback is that we only ever get it involuntarily, in situations we didn't choose, from people who are slightly annoyed. Of course we're bad at it. We never practise in easy conditions.

So make easy conditions. But not by asking "any feedback for me?", which is a question everybody has learned to answer with "no, all good". It's too broad and too obviously a formality.

Ask something narrow enough that an honest answer is easy to give. "In yesterday's architecture review, was there a point where I shut the discussion down too early?" You've named the meeting, you've named the behaviour, you've made it clear you already suspect the answer. That's a question somebody can answer honestly without having to decide to be brave.

Pick one person who has seen you work closely in the last fortnight, and who is not your manager. Peer, someone on your team, the delivery lead you sit next to.

Ask them one narrow question about one specific meeting. Then count to six before you say anything back, and say "can you give me an example" rather than anything else that occurs to you.

Write down what they said the next morning, in their words, and pick one thing off it to change by the end of the month. Tell them which one you picked. That last part is what makes them tell you the next thing.