Collaboration performance review phrases and examples

Exceeds expectations

• Brought sales and dispatch to one short call, so orders stopped falling into the gap between them.
• Shared the branch's stock data with finance early, so the audit closed without last-minute chasing.
• Built a shared tracker across two departments, so each could see the other's pending items.
• Sorted a recurring clash between HR and payroll timing by agreeing one cut-off both teams keep.
• Loops in the affected team before a change, so cross-department work does not break downstream.
• Speaks the other function's language in meetings, so finance and operations actually hear each other.
• Volunteered for a cross-branch project and kept both sides aligned on one plan.
• Credits the partner team's part in a joint win rather than claiming it for own department.

Meets expectations

• Works well with other departments on shared tasks without needing a manager to mediate.
• Shares information other teams need rather than holding it within own function.
• Responds to requests from other departments within a reasonable time.
• Joins cross-team meetings prepared and contributes to the shared plan.
• Coordinates handovers between functions so work does not stall at the boundary.
• Respects the other team's constraints when agreeing a joint deadline.
• Raises a cross-department blocker early rather than at the deadline.
• Keeps a shared tracker current so partner teams are not left guessing.

Needs improvement

• Works well inside the team but treats other departments as someone else's problem.
• Holds information within own function, so partner teams plan on stale facts.
• Responds slowly to other departments' requests, which stalls their work.
• Agrees a joint deadline, then works to a private one, surprising the partner team.
• Blames the other department when a shared handover fails, before checking own part.
• Skips the affected team before a change, so the change breaks downstream.
• Speaks only in own function's terms, so cross-team meetings talk past each other.
• Lets a shared tracker fall out of date, so partner teams chase for status.

Self-review phrases

• I loop in the affected team before a change now, so nothing breaks downstream.
• I shared stock data with finance early, and the audit closed without chasing.
• I want to respond faster to requests from other departments.
• I built a shared tracker so both teams can see each other's pending items.

Tips for writing this feedback

• Distinguish collaboration from teamwork: this is about working across roles and departments, not only within one team.
• Ask partner teams, not just the manager, since they see the responsiveness and information sharing a manager may miss.
• Watch for the strong internal player who treats other departments as an obstacle, which is a collaboration gap.
• Credit information shared and handovers kept, the everyday habits that stop work falling between functions.
• Name the specific cross-team situation in feedback, so the point is concrete rather than a general call to collaborate.

Track goals and review cycles for every employee in ZeniaHR.

Frequently asked questions