Solutions
All Resources
Discover "Me" · Work Personality
THE AI COACH THAT ACTUALLY GETS YOU.
Voice or text coaching built on psychology. For you, your team, or the candidates you place.
Hey Compono!
A coach that actually gets you.
Get 10 minutes free, then $15 a month. Cancel anytime.
Get Started ≫Collaboration
performance review phrases
26 teamwork and collaboration phrases across four rating bands, for managers, coaching conversations and self-evaluations. Filter, copy, print. Free, no sign-up.
Start with the rating band that matches the person, then pick the voice you are writing in. Copy a phrase, then change the specifics so it names the real project, the real quarter, the real thing that happened. A comment that could describe anyone is the thing you were trying to avoid.
How these were written, and the five steps to a review that holds up ↓Pulled the right three people into a room in week one and turned a stalled handover into a working process.
Manager to employeeShares credit accurately and specifically, which is why people volunteer to work with them again.
Manager to employeeWorks across team boundaries without needing an org chart, and brings the other team's constraints back with them.
Manager to employeeOthers already route work through them informally. Worth making that visible in the structure rather than leaving it as goodwill.
CoachingReady to chair the cross-team forum rather than contribute to it.
CoachingI set up a fortnightly sync with the two teams we kept colliding with, and rework from crossed wires has dropped noticeably since.
Self-evaluationI made a point of naming who did what in our updates, because the work was being attributed to the loudest person rather than the one who did it.
Self-evaluationContributes reliably in group work and does not leave the unglamorous parts to somebody else.
Manager to employeeDisagrees in the meeting rather than afterwards, which is what keeps decisions stable.
Manager to employeeResponds to colleagues' requests within a reasonable window, and says so when they cannot.
Manager to employeeCollaborates well when asked. The step up is initiating it: spotting the overlap before it becomes rework.
CoachingWorks well with the people they know. Worth deliberately pairing them with a team they have not worked with this quarter.
CoachingI made a habit of checking with the downstream team before finalising, which caught two decisions that would have created rework for them.
Self-evaluationI have started raising disagreements in the room rather than in the corridor afterwards.
Self-evaluationTends to work around blockers alone rather than bringing in the person who could remove them.
Manager to employeeContributions in group settings arrive late in the process, once the approach is already hard to change.
Manager to employeeProtects their own workload in a way that pushes the coordination cost onto others.
Manager to employeeWhen you hit a blocker, name it to the group the same day rather than absorbing it. Absorbing it looks like resilience and costs the team a week.
CoachingWorth agreeing one piece of work this quarter that cannot be finished alone, so the habit gets practice rather than discussion.
CoachingI default to solving things myself, which is slower than asking and occasionally duplicates what somebody else has already done.
Self-evaluationI want to get better at flagging a conflict early instead of hoping the two workstreams resolve themselves.
Self-evaluationColleagues have raised difficulty getting responses or input, and this has been discussed before without a sustained change.
Manager to employeeRepeatedly reopens decisions that were made collectively, which has stalled [project] twice this year.
Manager to employeeThe pattern is affecting other people's ability to do their work, so this needs a written plan with specific commitments and a six-week review.
CoachingWorth separating two things: whether the process is wrong, which I want to hear about, and whether it is being followed, which is not optional while it stands.
CoachingI have not worked well with [team] this year. I want to understand what went wrong from their side before I decide what to change.
Self-evaluationPoint at what happened to the work. Who got unblocked, what rework was avoided, which decision stayed made. "Is a great team player" is a compliment, not a review comment.
How these were written
Written, not calculated. Every phrase names the situation, the behaviour and the effect on the work or the people around it. The four bands sort by rating and the three voices switch between a manager writing about someone, a manager coaching, and a self-evaluation. Teamwork and collaboration are treated as one competency because in review writing they describe the same set of behaviours.
- Phrases are starting points. Name the actual team, the actual handover, the actual rework avoided.
- Teamwork and collaboration are one competency here. In review writing they describe the same behaviours, and splitting them produces two thinner lists that compete with each other.
- Structure is assessed before the person. If somebody has no working route to the people they need, that is an organisational finding wearing an individual's name.
- Written for Australian workplaces and Australian English.
- Unsatisfactory-band comments assume a dated record and a prior conversation.
- Fair Work Ombudsman, Managing underperformance (what a defensible performance record looks like before a difficult comment is written down), accessed August 2026
What to do about it
Collaboration is the easiest competency to rate badly, because the person everybody enjoys working with scores well and the person who asks awkward questions early scores badly, regardless of what happened to the work.
Ask what moved, not who was pleasant
Which blocker got cleared, which rework was avoided, which decision held. That is the evidence.
Check the structure before you rate the person
If the route to the other team does not exist, no amount of individual effort creates one, and the finding belongs to you rather than to them.
Separate disagreement from obstruction
Somebody who argues in the meeting and commits afterwards is collaborating. Somebody who agrees in the meeting and relitigates later is not, and those two often get the same rating.
Give the gap a piece of work, not an adjective
One deliverable this quarter that cannot be completed alone will do more than any phrasing in a review document.
Look at the set
Collaboration gaps clustered in one team usually mean the team was built without the coverage it needs, which is a design problem rather than twelve development plans.
The gap may not be
the person.
Compono Engage reads how a team actually works, not just how people feel about it. That is what separates somebody who will not collaborate from a team assembled so that collaboration has nowhere to happen.
Step 5 asks whether the gap is one person or the shape of the team. Review documents cannot answer that. Team data can.
Common questions
What are examples of collaboration feedback for a review?
Naming a blocker the same day rather than absorbing it, bringing another team's constraints back into your own planning, disagreeing in the meeting rather than after it.
How do you give feedback to someone who does not collaborate well?
Separate unwillingness from structure. If the person has no route to the people they need, that is your problem to fix. If they have the route and do not use it, that is theirs, and it needs a specific commitment with a date.
Should collaboration be rated separately from communication?
Usually yes. Someone can communicate clearly and still not work well across boundaries, and the fixes are different.
Can I use these phrases word for word?
Yes. Swap in the real team, the real project and the real result, or the comment will read as filler to the person receiving it.
Next step
Competency framework
The bands above are competency ratings. This is what a competency framework is, and how the levels are meant to work.
Read the definition →Related tooleNPS calculator (employee net promoter score)
Reviews name the gap one person at a time. This one sizes it across the team.
Run it next →BuyingRequirements builder
Score the platforms you are looking at against the two risks, must-haves first.
Build the scorecard →Talk to usBring us your review cycle
A conversation about what your reviews are telling you as a set, not a demo script.
Talk to us →.webp?width=559&height=292&name=2026.07.21%20Fireside%20KV%20-%201200x627%20(event%20featured).webp)
.png?width=383&height=200&name=team%20(1).png)