Hacker News new | ask | show | jobs
by zjs 2164 days ago
Constructive feedback can be positive.

"Hey GEBBL, you did a really good job on that project. It was great that you focused on the end-to-end problem, and not just the main part that PM asked for. This is something you're better at than some other members on your team -- do you think you could help me keep an eye out during design reviews for gaps along these lines?"

It can also be useful to use a related positive to explain a negative.

"Hey GEBBL, you're usually a good speaker, so I thought you'd want to know that I found your presentation this week a little hard to follow. I think it would have been easier to follow with a high-level overview like the one you included at the beginning of last week's."

You can, of course, look at people's weaknesses to find opportunities for improvement, but you can also look at people's strengths. I think think the best feedback is not only constructive, but also motivating and actionable.

For more difficult feedback to navigate, you should be able to funnel it through a manager. "Hey GEBBL's manager, I noticed that GEBBL checked in a change yesterday without testing it properly. It's not a major thing, but I know you're looking for opportunities to give GEBBL constructive feedback." (If you're going to do this, I suggest trying to do it in a balanced way; share positive feedback too so that it's clear you're not complaining all the time.)