"Improve your communication skills" on a performance review — what to do next
10 September 2026
A review line about communication is a summary of several moments, written months after them. Before you can act on it you need three things the review does not contain: which situations it refers to, which behaviour was noticed, and what evidence would show it changed. Ask for those in that order.
It is the most common line in performance management and the least useful sentence in the document. It appears under areas for development, sometimes with an example, usually without.
Here is what it actually is. Your manager noticed something several times across a year, could not name the pattern, and compressed it into the phrase everyone uses. The underlying observations were real. The summary threw away everything you needed.
Your job is to get the observations back.
Three questions, in this order
Which situations? Not “when have I communicated badly”, which invites another summary. Ask which kinds of meeting: written updates, live discussion, senior audiences, cross-team work, conflict. The answer narrows the problem enormously, and it is a question managers can usually answer, because they remember contexts better than behaviours.
What did you notice? Once you have the context, ask what they saw. Offer the specific options rather than waiting, because naming behaviours is the hard part. Was I too slow to get to the point? Did I not push back enough? Did I go too deep for the audience? A concrete menu is far easier to answer than an open question.
What would show it changed? This is the question almost nobody asks, and it is the one that matters most. If they cannot say what improvement would look like, the line will reappear next year regardless of what you do, because there is no test it can pass.
When they cannot answer
Plenty of managers cannot, and it is worth not treating that as evasion. Reconstructing which behaviour produced an impression eight months ago is genuinely hard, and the vague phrase is what the memory collapses into.
The move is to change the timing rather than push harder. Ask them to tell you in the moment next time. “If you see it in a meeting, message me after.” That is a small ask, it costs them almost nothing, and it produces the specific observation the review could not.
Then narrow it to one thing
Whatever comes back, resist working on all of it. Pick one behaviour, keep it for a month, and make it small enough to check.
Good candidates, in rough order of how often they turn out to be the real issue:
- Answer the question in the first sentence, context after.
- Make the recommendation explicit, rather than presenting options.
- Stop after the point instead of restating it.
- Match the depth to the audience, and offer detail rather than delivering it.
- Hold a position when challenged, unless given new information.
One rule. Two competing rules produce hesitation in the moment, which reads worse than the original habit.
Build the evidence before the next cycle
This is the part that decides whether the line disappears next year.
A review is written from impressions, and impressions are formed slowly and updated slowly. If you change the habit but nobody registers the change, the same sentence gets written again. That happens more often than it should.
So make it visible. Tell your manager which specific thing you are working on, so they have a category to notice. Ask for a check-in halfway rather than waiting for the next review. And keep some evidence of your own, because “I think I’m getting to the point faster” is not an argument, while a change you can actually point to is.
The uncomfortable part
You will not be able to tell, unaided, whether the habit has changed.
The behaviours in question are invisible from the inside. In the moment, the caveats feel necessary, the context feels required, and the hedging feels like accuracy. Your sense of how long you talked is unreliable. This is precisely why the feedback recurs year after year for people who genuinely tried.
Something external has to close that loop: a colleague briefed to watch for one specific thing, a manager willing to flag it in the moment, or a recording of a meeting you were actually in.
Questions
- Should I push back on the feedback?
- Ask for specifics rather than disputing it. The line is usually a compression of real moments, so arguing about the summary loses information you need. Asking which meetings it came from gets you the underlying observations.
- What if my manager cannot give examples?
- That is common and it is not obstruction. Reconstructing which behaviour caused an impression months later is genuinely hard. Ask them to flag the next instance in the moment instead, which is much easier for them and more useful to you.
- How does this affect promotion?
- Communication lines block promotions more often than technical ones, because a promotion committee reads them as risk about how you will operate at the next level. That is also why a vague line is worth converting into something measurable before the next cycle.
- How long should I expect this to take?
- One habit worked on consistently shifts inside a month or two. What takes longer is building the evidence that it shifted, which is what the next review will actually turn on.
Read next
- "Work on your executive presence" — what your manager actually means
Executive presence is a description of an effect, not a skill. Here are the specific behaviours managers are reacting to when they use the phrase.
- "You need to be more concise" — what they are actually reacting to
Being told to be more concise is rarely about total words. It is about how long the listener waited for the point. Here is what people are reacting to and what to change.
- "You are too in the weeds" — decoded
This feedback is not about knowing too much detail. It is about the order you deliver it in, and who you make do the summarising.