Imagine a team sending out a weekly report. A chatty colleague attaches an old version, makes a joke, and gets help replacing it. Later, a quieter colleague makes a similar mistake and hears that they need to be more of a team player. This is an invented example, but it captures a familiar source of frustration: the feedback seems to concern personality more than the work.
That contrast alone cannot establish unfair treatment. The consequences, responsibilities, and response to each mistake may differ. It does, however, give the team a reason to examine its standards.
Small talk has a place
A brief conversation can make it easier to approach someone, ask for help, or notice that they are having a difficult day. Enjoying these exchanges is no sign of laziness. Preferring fewer of them says little about someone's ability or willingness to cooperate.
The useful distinction is between optional social conversation and communication needed for the role. Discussing a film and confirming which report version to send serve different purposes. They may happen in the same conversation, but essential information still needs to reach everyone concerned.
Some roles also involve building rapport through conversation, including customer-facing work. Those expectations should be made clear and assessed through relevant behavior. They need not extend to sharing private matters or socializing after hours. Nobody needs to attach a weekend diary to their timesheet.
Turn vague feedback into something usable
Being told to communicate more offers little direction. A more useful discussion identifies an example: a deadline change was not passed on, a handover lacked instructions, or a question needed an answer before work could continue.
An employee can explain how they currently share progress and agree on who needs updates, through which channel, and when. A short written note may be suitable for routine updates; an urgent problem may require a call or another agreed route. Sending a message is not always enough if the recipient cannot access it or the decision remains unclear.
These habits can help coordination. They do not guarantee good performance or a favorable review, and they should not become a demand that one person solve every communication problem.
Managers need to make the work visible
A useful review connects expectations to the role: whether a report meets the agreed quality standard, whether a delivery date was realistic and met, and whether a handover let the next person proceed. Helping colleagues and improving after an error can also matter, when supported by specific examples.
Counting completed tasks does not automatically make a review fair. Workload, complexity, available support, and changes in requirements affect what those numbers mean. Similar errors should be discussed using consistent criteria, with room to explain relevant differences.
Managers also need to make decisions and changes available in an accessible shared place. Important instructions should not depend on being present for a particular coffee break. Brief written summaries and clear opportunities to ask questions can help people with different communication styles participate.
Keep the discussion grounded
If a review feels unclear, focus on your own work: agreed expectations, completed tasks, relevant dates, and the feedback received. Keep only necessary business facts in an approved location. There is no need to build files on colleagues, collect their private evaluations, or record conversations without permission.
Social-media advice may describe one person's experience, but it cannot explain every workplace. A concern may involve missed information, unclear expectations, or inconsistent evaluation; it does not by itself establish anyone's motives.
In your workplace, what concrete contribution is being assessed when someone is described as a good communicator?
