Performance review phrases for communication
Updated · YouDeserveNow editorial
Reviewers rate communication on whether the right people understood the right thing at the right time, and whether decisions moved faster because of it. Specific artifacts and audiences beat adjectives like "clear" or "effective".
What reviewers look for
- ✓Written artifacts others reused (docs, proposals, updates)
- ✓Complex topics explained to non-experts
- ✓Bad news raised early and clearly
- ✓Meetings or threads that ended in decisions
Strong self-assessment phrases (exceeds expectations)
Replace every highlighted [bracket] with a fact you can prove. Reviewers trust specifics, not adjectives.
- I wrote the [proposal] that aligned [teams] on [decision], cutting the planning cycle from [before] to [after].
- I replaced [number] weekly status meetings with a written update read by [audience], saving about [hours] per week.
- I presented [topic] to [leadership group], which led to [decision / funding].
- I flagged the [risk] to [stakeholders] [weeks] before launch, giving us time to [action].
- I documented [system/process]; it is now the onboarding reference for [number] people.
- I translated [technical finding] into a one-page brief that [sales / leadership] used to [outcome].
- I ran the [cross-team] sync that resolved [number] open dependencies within [period].
- I rewrote [customer-facing content], reducing related support tickets by [X%].
Solid phrases (meets expectations)
- I kept [stakeholders] informed with weekly written updates throughout [project].
- I documented decisions and next steps after key meetings so owners were clear.
- I adapted my updates for technical and non-technical audiences.
- I responded to [requests / escalations] within [time] on average.
Growth-area phrases (constructive)
Name a real gap, show what you already did, and commit to a next step.
- I want to raise risks earlier; on [project] I escalated [issue] later than I should have, and I now flag risks in the first weekly update.
- I am working on shorter written updates that lead with the decision needed.
- I am practicing presenting to senior audiences by [specific step].
- I will ask for written feedback on my proposals before they go wide.
Weak to strong: rewrites
Weak
I am a great communicator.
Strong
I wrote the [proposal] that got [teams] to agree on [decision] in [time].
Weak
I kept everyone in the loop.
Strong
I sent a weekly update to [number] stakeholders during [project]; we had zero surprise escalations at launch.
Weak
I presented to leadership.
Strong
I presented the [topic] analysis to [group], which approved [decision / budget].
Phrases to avoid
- ✕"Excellent communication skills" with no example
- ✕Counting meetings attended
- ✕"Kept everyone informed" without audience or outcome
- ✕Jargon reviewers outside your team cannot evaluate
Frequently asked
How do I write about communication in a self-review?
Pick one or two artifacts or moments, name the audience, and state what changed because they understood: a decision, a faster timeline, or a risk avoided.
What is a good communication goal for next year?
Choose something observable, like publishing a monthly written update for [audience] or presenting [topic] to [group] by [date].