360 Feedback Comment Examples: Teamwork and Collaboration

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

Peers see collaboration best, so these comments are written from a colleague's point of view. The best ones mention a shared project and what changed because of the person's behaviour.

Positive comment examples

  • When I was stuck on the reporting script, you spent an hour walking me through it without being asked. It saved me days.
  • You share credit generously. In the all-hands you named three people who helped on your project.
  • You handle disagreements well: in the design review you challenged the approach but focused on the problem, not the person.
  • You keep shared documents up to date, so the rest of us always work from the latest version.
  • You onboard new colleagues brilliantly. Our last two hires both said you were the reason they got up to speed quickly.
  • You volunteer for the unglamorous tasks, like the release checklist, that keep the team running.
  • You bring people from other teams in early, which has prevented several late surprises.
  • You are reliable in hand-offs: when you pass work on, it comes with context and open questions listed.

Constructive comment examples

  • You often solve problems alone and present the finished result. Involving teammates earlier would spread knowledge and catch issues sooner.
  • In disagreements you sometimes hold your position after the decision is made. Committing once the team decides would help us move faster.
  • Information from client calls does not always reach the rest of the team. A short note in the channel afterwards would keep everyone aligned.
  • You are quick to help people you know well but less available to newer colleagues. They would benefit a lot from your experience.
  • Hand-offs from you sometimes arrive the day before a deadline. Earlier warning would let us plan our work.
  • In retrospectives you rarely share what did not work. Your perspective would make those sessions more useful.
  • You occasionally change shared files without telling the owner. A quick heads-up would avoid confusion.
  • Your messages in group chats can read as blunt to people who do not know you well. A little more context would help.

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 write feedback about teamwork?

Name a shared project or moment, describe what the person did, and explain how it affected the team: "you onboarded our two new hires, and both were productive in a week".

Who should comment on someone's teamwork?

Peers who work with them regularly, ideally three to six, plus anyone they hand work to or receive work from.

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.