The same sentence lands completely differently depending on who says it.
This design has a problem, from someone who has spent months paying attention to your work, sounds like help.
The identical words from someone who has never once said anything encouraging to you sound like an attack.
Nothing about the feedback changed. Everything about the reception did.
That is not people being fragile. That is people reading context, correctly.
So if you want your hard feedback to land, do the quiet work first.
Notice their good work out loud before you need to notice the bad. Not flattery, and not constantly. Just specific and real, a few times, in advance of ever needing to criticise anything.
Be a person they have seen be honest about their own mistakes. Nobody takes correction easily from someone who behaves as though they have never needed any.
Show up for the boring parts. Review their pull requests when nothing is on fire. Answer the small question at four on a Friday.
None of that is about the feedback. All of it is what makes the feedback survivable.
Then, when the moment comes, you have a bank account to draw on.
I have watched two engineers give the same note to the same person in the same week. One got a thoughtful rewrite. The other got a defensive reply and a grudge that lasted a year.
The difference was entirely in the six months before the note.
There is a version of this that goes wrong, so let me name it. This is not about being liked first so you can be harsh later. That is a transaction and people can smell it.
It is about being genuinely invested, so that when you say something difficult it is obviously coming from the same place as everything else you have said.
If you have not built that yet, you can still give the feedback. Just give it smaller, softer, and expect it to take longer to land.
Trust is not a prerequisite anybody tells you about.
It is the thing that decides whether your good advice gets heard or filed away as noise.
– Asael Shinder
Top comments (0)