360 Feedback Comment Examples: Communication

8 positive and 8 constructive comments you can adapt, plus a simple formula for writing your own.

Communication comments work best when they name the situation and the effect. "Great communicator" tells someone nothing; "your project updates let me plan my week without asking" tells them what to keep doing.

Positive comment examples

  • Your weekly update is the one I actually read: three lines on progress, risks and what you need. It saves me a meeting.
  • In the client call on the pricing change you explained the reason before the number, and the client accepted it without pushback.
  • You listen to the whole question before answering. People in our team feel heard when they bring problems to you.
  • Your written handover for the migration was so clear that I could take over on Monday without calling you once.
  • When the plan changed, you told the team the same day and explained why. That stopped a lot of rumours.
  • You adapt how you explain things: technical detail with engineers, impact and dates with leadership.
  • You ask clarifying questions early in kick-offs, which has saved us from building the wrong thing at least twice this year.
  • Your meeting notes always end with owners and dates, so nothing falls through the cracks.

Constructive comment examples

  • Your emails often bury the request at the end. Putting the ask in the first line would get you faster answers.
  • In team meetings you sometimes answer before others have finished. Pausing a moment would let quieter colleagues contribute.
  • Updates on the vendor issue reached the team late. A short note when something changes, even without a solution, would help us plan.
  • Your presentations have strong content but too many slides. Leading with the conclusion would keep leadership engaged.
  • When you disagree in writing, the tone can come across as sharper than you intend. A quick call for sensitive topics might land better.
  • Decisions from your one-to-ones are not always written down, so we sometimes remember them differently. A two-line summary afterwards would fix that.
  • You tend to use internal jargon with new joiners. Spelling out acronyms the first time would help them follow.
  • In cross-team meetings you rarely share your view until asked. Your input is valuable, and offering it earlier would shape decisions sooner.

How to write your own comment

Use the Situation – Behaviour – Impact formula, then add one suggestion:

  1. Situation: when and where it happened ("In Tuesday's client call…").
  2. Behaviour: what the person actually said or did, not what you think of them.
  3. Impact: what it changed for you, the team or the customer.
  4. Suggestion (for constructive comments): one concrete thing to try next time.

Not sure your wording is fair? Paste it into the free feedback bias checker to catch vague or biased phrasing.

Frequently asked questions

How do you give feedback on communication skills?

Describe a specific situation, what the person said or wrote, and the effect it had. Then suggest one concrete change, for example "put the request in the first line".

What is a good positive comment about communication?

One that names the behaviour and its impact, such as "your weekly update lets me plan without a meeting". It tells the person exactly what to keep doing.

Want comments like these about you?

Run a free 360 in 5 minutes. Colleagues answer anonymously by link, and AI turns their comments into themes and next steps.

Start my free 360°

No credit card. No signup for reviewers.

More comment examples

Looking for questions instead? See 360 feedback questions by role.