A practical workplace conversation
Communication skills: how to respond to a coworker's criticism
“Your work is disorganised” can sting, yet it does not identify what needs to change. Agreeing at once or defending yourself may leave the task unclear. This guide works through one invented coworker conversation and turns a broad label into an observable example and an agreed next step. It is a teaching scenario, not a universal script or a real MekStep employee story.
Do not rush to accept a broad label or argue about it. Ask which incident the coworker means, what they observed, what effect it had and what change they suggest. Summarise what you heard, agree one feasible next step and note how the next version will be checked. If the evidence does not support the judgment, clarify the disagreement respectfully.
Separate a judgment from a work observation
‘Disorganised’, ‘unprofessional’ and ‘always late’ are broad judgments. They may point toward a real problem, but alone they do not identify a file, meeting or action. When you receive criticism, first set the label aside and locate the event that can be examined.
A Program on Negotiation article from Harvard Law School suggests asking what past behaviour was observed and what the other person recommends doing differently in the future. These are conversation questions, not a guarantee that a single question will resolve a disagreement. The situation below is our fictional teaching case.
Pause and keep the task in view
If the wording feels sharp, you can say: ‘I hear that there is a problem with my work. I would like to understand the specific example first.’ A brief pause helps separate your reaction from the information to be checked. It does not mean agreeing with a personal label or hiding disagreement.
Do not infer a coworker's motives from posture or tone. An open question, followed by a check of your understanding, is more useful for this task. If the exchange begins in front of others and details are hard to discuss, suggest continuing it in a calmer setting, following your team's actual practice.
Move from the label to three clarifying questions
The point is not to interrogate a coworker. The questions establish the boundary of a work problem so your next step is not a guess. Start with one event, then ask about a useful alternative. If the other person can describe only an impression, keep it as an impression and request an example rather than treating it as a verified fact.
CIPD's 2022 evidence review says specific information about a task is generally more useful than an overall performance label. Its research scope is feedback from managers or supervisors; it did not directly study criticism between coworkers. We use that limited principle to shape questions here, not as proof of an outcome for this conversation.
- Which file, meeting or moment do you mean, and what did you see or hear?
- What information or action was missing in that instance, and what was the effect?
- What one change would help next time, and who will check it?
Fictional conversation: from criticism to an agreement
Imagine two coworkers in a Yerevan team preparing a one-page project status update. One says: ‘Your work is disorganised.’ The other does not accept this description as a fact and asks: ‘Which update are you referring to?’ The response is: ‘Yesterday's version did not name the owner of the next step.’ This is an invented teaching scenario, not an actual organisation's incident or a measured result.
The receiver checks the meaning: ‘Do I understand correctly that the missing owner is the issue, rather than the entire document?’ They then ask how the owner should be shown and whether they can verify the name themselves. If both agree, they decide to add ‘owner’ and ‘next step’ fields in the next update and compare that version with the team's accepted format. The people involved decide the actual timing; this article sets no real deadline or mandatory procedure.
The general label has now become a missing field in a checkable document and a proposed action. That does not excuse the initial harsh wording. Separately, the receiver can request comments about observable work rather than personal character.
- Initial label: ‘disorganised work’.
- Observable event: the owner field was missing from a fictional previous update.
- Clarification: is the issue the whole document or one field?
- Next step: add the agreed fields and check the next version.
- Open question: who confirms the owner and the team's format?
When you disagree or the example remains unclear
Listening does not oblige you to accept an inaccurate account. You might say: ‘I can see an owner name in that file, but perhaps we are looking at different versions. Could we open the same one?’ Compare the material together and keep both explanations open until the difference is understood. If the coworker cannot identify an event, record the issue as unresolved rather than a proven mistake.
If the conversation turns into personal insults or repeated pressure, set a respectful boundary and use the relevant person or procedure in your organisation. This article states no Armenian legal duty and assumes no particular employer policy. Clarify authority and responsibility in your actual team.
Keep a short action card and return to it
After the conversation, write a short note both people can read in the same way. Do not repeat a harsh personal label as established fact. Record the event, any uncertainty, the chosen change, the responsible person and the point at which the next version will be reviewed. If the owner or format is not yet confirmed, leave it explicitly open on the card.
For example: ‘We discussed the fictional version of yesterday's update. The owner field needs to be checked against the team format. In the next version we will add the confirmed owner and next-step fields, then compare it with the example.’ This is a sample work note, not a real promise or proof of improvement.
- Event: the material or action being discussed.
- Observation: what is visible, and what remains disputed.
- Change: one concrete action instead of ‘work better’.
- Confirmation: who resolves the open questions and when the next version is reviewed.
How this differs from general active listening
General active listening helps you understand what someone said. Here the deliverable is narrower: a checkable work example and an agreement about the next action arising from corrective criticism. ‘I heard and understood’ is not enough if the change, the person confirming it and the way to check the result are still unknown.
The existing guides on listening and body language can support this conversation. Avoid guessing someone's intentions from gestures or tone. The decisive pieces here are the clarified content and the agreed action.
What to remember
- A broad label is not yet an established fact about the work.
- Ask for one observable incident, its effect and one future change.
- Check your understanding and record the agreed action and open questions.
- Clarify disagreement using the same material; separate insults from work observations.
Frequently asked questions
Do I have to accept criticism immediately?
No. Clarify the event and the proposed change first. Then decide what is supported, what remains disputed and what action is possible.
What can I ask after ‘your work is disorganised’?
Ask: ‘Which part of which task made you say that, and what would you like to see in the next version?’ Replace the label with an observable example.
What if my coworker cannot give an example?
Do not record the broad judgment as a proven error. Offer to review the relevant work together or return when a concrete incident is available.
What if the wording is insulting?
Set a boundary for respectful discussion. If it continues, use your organisation's relevant person or procedure. This guide is not legal advice.
Sources
Checked 2026-10-29: