Employee Feedback

The process of giving and receiving performance-related input at work — the most important driver of growth, and consistently one of the most avoided conversations in most organizations.

Employee feedback is the exchange of performance-related information between people at work — from manager to employee, employee to manager (upward feedback), and peer to peer. It's the primary mechanism by which people learn what they're doing well, what they need to change, and how they're perceived by the people they work with. Despite being universally recognized as important, feedback is consistently avoided, delayed, softened to the point of uselessness, or delivered so infrequently (annual performance reviews) that it loses developmental value. Research by Kim Scott, Marcus Buckingham, and others identifies the failure of honest feedback as one of the most pervasive and costly dysfunctions in organizations.

The most common failure mode in feedback is what Kim Scott calls 'ruinous empathy': withholding critical information because delivering it feels uncomfortable, with the result that the recipient never gets the chance to improve and eventually faces consequences (a PIP, being passed over for promotion, termination) that feel like surprises. The antidote — radical candor, direct challenge with genuine care for the person — is simple in concept but requires both skill and a relationship foundation of trust. Feedback delivered without care feels like an attack; care without directness fails to actually help.

Receiving feedback effectively is a skill as important as giving it. The default response to critical feedback is defensiveness — explaining, justifying, or minimizing — which shuts down the conversation and signals that you're not safe to give feedback to. The behaviors that make someone genuinely good at receiving feedback: listening fully before responding, asking clarifying questions to understand the specific behavior being referenced, thanking the person for the input (even if you disagree), and following up to report what you did with it. People who are known for receiving feedback well get more of it — which is a competitive advantage.

How to Give Useful Feedback

  • Be specific: 'In yesterday's client call, when you interrupted the client twice during their explanation, the energy shifted noticeably' is actionable. 'You can be dismissive in meetings' is not.
  • Be timely: feedback closest to the event is most useful. Don't save it for the annual review.
  • Focus on behavior, not character: 'You interrupted the client' describes an action; 'you're dismissive' describes a person. One is changeable; one triggers defensiveness.
  • State the impact: why does this matter? 'It made the client seem less heard, and I noticed them become quieter for the rest of the call.'
  • Ask, don't lecture: 'What was going through your mind when you jumped in? I want to understand before I share my observation.' Often reveals context that changes the feedback.
  • Make it a two-way conversation, not a verdict.

Asking For and Receiving Feedback

The most reliable way to get honest feedback is to ask for it specifically and make it easy to give. 'Do you have any feedback for me?' typically produces 'you're doing great' — the question is too open and the default is encouragement. More effective: 'What's one thing I could do differently in how I run these client calls that would make them more effective?' or 'What's something I should stop doing that I might not be aware of?' Specific, one-thing-at-a-time asks lower the stakes and make it easier for people to be honest. When you receive critical feedback, the most important thing you can do is listen fully without defending, say 'thank you — that's helpful, I'll think about it,' and then actually follow up with what you did with the input. This behavior marks you as someone safe to give feedback to, which means you'll get more of it going forward.

Example

A product manager receives vague feedback at his annual review that he 'needs to work on communication.' Frustrated by the lack of specificity, he asks his manager in a 1:1: 'Can you help me understand specifically — is it the written docs, the presentations, the way I communicate in meetings? And can you give me an example of a moment where it didn't land well?' The manager identifies that his design reviews feel like information dumps rather than collaborative discussions. He changes the format and checks in two months later — the issue is resolved and never appears in a review again.