This Harvard Business Review piece is helpful because it gives you a better benchmark for what effective feedback actually sounds like. The big idea is that useful feedback is specific, behavior-centered, and oriented toward helping someone improve rather than simply delivering criticism. It draws a clear line between feedback that sounds good to the giver and feedback that is actually useful to the receiver, which is a distinction most managers do not think about carefully enough.
That matters because a lot of weak feedback fails in one of two ways: it is so vague that nothing changes, or it is so evaluative that the other person fixates on judgment instead of action. Vague feedback sounds like "You need to step up" or "Your communication needs work." The person hearing it cannot act on it because they do not know what specific behavior to change. Evaluative feedback sounds like "You are not a team player" or "Your attitude is a problem." The person hearing it gets defensive because they feel labeled rather than coached. They push managers toward a third option: feedback that is precise enough to be actionable and grounded enough to be received without a fight.
The authors also highlight the importance of framing feedback around impact rather than intention. When you tell someone what their behavior caused, you give them a reason to care about changing it. When you tell someone what you think they meant by their behavior, you invite an argument about motives. The difference between "Your comment shut down the discussion" and "You were trying to dominate the meeting" is significant. The first is observable and difficult to dispute. The second is an interpretation that the other person will almost certainly reject.
Another useful idea is that good feedback includes a forward-looking element. It is not enough to describe what went wrong. The person needs to understand what "better" looks like in concrete terms. A manager who says "In the next client presentation, I want you to lead with the data before the recommendation, and pause to check for questions after each section" has given feedback the person can rehearse and execute. A manager who says "Be more polished next time" has given feedback that sounds reasonable but is functionally useless.
This is a good reset if your feedback tends to drift into either pattern, vagueness or judgment, and it offers a practical standard for what clarity actually sounds like in a real conversation.
Key ideas to carry into practice
- Good feedback stays close to observable behavior instead of broad character labels. Describe what you saw, not what you concluded about who they are.
- Constructive criticism has a place, but it works best when it creates clarity about what to change next, not just what went wrong.
- Strong feedback is easier to act on because it connects actions to impact. "Here is what happened, and here is what it caused" is the core structure.
- The more specific and grounded your language is, the less likely the conversation is to become defensive.
- Include a forward-looking element: tell the person what better looks like in concrete, practicable terms.
- Test your feedback before delivering it by asking yourself: could the person act on this tomorrow without asking me to clarify?
Common questions
Q: What does good feedback sound like when someone keeps interrupting in meetings?
A: Try: "In today's planning meeting, you cut off Mia twice while she was answering. It made it harder for the team to hear her recommendation, and it changed the tone of the conversation. I want you to pause and let people finish before you jump in." That is behavior-based, specific, and actionable.
Q: What would a weaker version sound like?
A: Something like "You need to be more professional in meetings" is too broad. It may be true in spirit, but it does not tell the other person what to change or why it mattered.