
“You need to work on your communication.”
What exactly is someone supposed to do with that?
Feedback becomes useful when the person receiving it can recognize the behavior, understand it’s impact and leave knowing what could have been done differently.
Suppose a team member publicly criticizes a colleague for missing a deadline. You could say, “You were unprofessional in that meeting.” That communicates your judgment, but not much else.
A more useful conversation might sound like this:
“When you addressed the missed deadline in front of the team, your tone became noticeably sharper, and you said we could lose the account because of the delay. The conversation shifted after that. Next time, I’d like you to address the performance issue directly with the person first and then decide what the broader team needs to know.”
Now there’s something concrete to discuss.
Keep Feedback Grounded
A simple structure helps:
→ What happened?
Describe the behavior you observed without assigning motives.
→ What was the impact?
Explain what changed because of it.
→ What needs to happen next?
Clarify the expectation, then allow the other person to respond.
That last part is easy to overlook. Feedback shouldn’t become a monologue. There may be context you don’t know, a misunderstanding to clear up or another perspective worth hearing.
Timing matters also. Some feedback belongs to the moment. Other conversations are better held privately after everyone has had time to settle.
And while asking “Can I share an observation?” can be courteous, leaders also have a responsibility to give necessary performance feedback. Permission shouldn’t become a way to avoid a conversation the role requires.
Good feedback doesn’t need a long script.
Be specific enough to recognize. Clear enough to use. Open enough to hear something back.
That’s feedback someone can work with.


Leave a Reply