To give constructive feedback to a coworker, describe a specific work event, explain its actual effect, ask for their perspective, and agree on a practical adjustment. Choose an appropriate time and channel. As a peer, keep the conversation within shared work rather than rating their personality or issuing a performance warning.
For example: “In yesterday’s handover, the file link pointed to the earlier version. I used it to start the review, which meant checking the same section again. Can we compare where the version changed and agree on one final link?”
The example gives the colleague something concrete to examine. It also leaves room for a missing fact: perhaps the folder link changed after they sent the message.
First Decide Whether Feedback Is the Right Conversation
Not every difference needs corrective feedback. A preference, unclear requirement, immediate operational problem, and repeated behavior are different situations.
| What you have noticed | Better starting point |
|---|---|
| You prefer a different writing style | Ask about the audience and agreed standard |
| A handover requirement was never agreed | Clarify the requirement together |
| An error is causing an immediate problem | Correct or flag the work issue through the normal channel |
| A specific recurring action affects shared work | Discuss the action, effect, and adjustment privately |
| Serious misconduct or a formal performance issue | Use the appropriate manager or reporting process |
Do not present an unspoken personal preference as a rule your coworker broke. Check whether the expectation was shared before asking someone to meet it.
If you are reacting mainly to a personality clash, first review working with someone you dislike. A useful work request should remain understandable without the personality judgment.
Prepare One Specific Example
Write down the event, the action you observed, and the effect you can actually describe. Replace general labels with details that the other person can check.
“You are unreliable” becomes: “The last two handovers arrived after our agreed review window.”
“You never listen” becomes: “In this morning’s planning discussion, we moved to the next item before I had finished explaining the test constraint.”
The Center for Creative Leadership’s Situation–Behavior–Impact model similarly organizes feedback around a specific setting, observed behavior, and its effect. CCL also recommends asking about intent rather than assuming it. That model informs the preparation here; the peer scenarios and action checklist below are TaoNique’s applications.
Avoid claiming an impact you have not measured. If you know the mistake required another review, say that. Do not turn it into a claim about lost revenue, customer trust, or everyone’s morale without evidence.
Open the Conversation Without Setting a Trap
Ask for a short conversation at a time when the colleague can engage:
“Could we take ten minutes after the stand-up to discuss yesterday’s handover? I want to make the next review easier for both of us.”
For routine developmental feedback, asking whether now is a suitable time gives the other person a genuine opportunity to suggest another time. Avoid “Can I give you some feedback?” followed immediately by a long criticism before they answer.
Urgent corrections should not wait for a perfect private setting. If the team is about to use an incorrect file, identify the correct file in the work channel. Discuss the broader pattern separately rather than turning the operational correction into public blame.
Move From Observation to a Shared Adjustment
Use this checklist for the conversation:
- Locate the event: name the meeting, handover, or deliverable.
- Describe the action: explain what you observed without a character label.
- Explain the effect: state how it affected your work or the agreed process.
- Invite correction: ask what context you may be missing.
- Agree on one adjustment: confirm what each person will do next.
The final two steps matter for peers. You are not announcing a verdict; you are trying to resolve a shared work problem. If your understanding is wrong, revise it openly.
Constructive Feedback Examples for Coworkers
An incomplete handover
“The handover note didn’t include the approval link, so I couldn’t confirm which version to use. Was the approval stored somewhere else? Could we include that link in the next handover?”
This asks for a discoverable record. It does not imply the colleague deliberately withheld information. For recurring handover gaps, use a knowledge transfer checklist instead of repeating the same reminder indefinitely.
Interruptions in meetings
“During today’s review, the discussion moved on while I was explaining the remaining test risk. I wasn’t able to finish the point. Could we let the person presenting finish before questions, or agree on a clearer turn-taking approach?”
Make room for a different perspective: perhaps they thought the explanation had ended or were responding to a time limit. You can still ask for a workable adjustment.
Late information affects your own task
“The updated figures arrived after the review window we agreed on. That left me using the earlier data for the draft. What timing would work for both teams next week?”
If the colleague cannot control the input date, identify the real dependency. Telling them to “be more proactive” will not create access or authority they lack.
A repeated issue after an earlier discussion
“We agreed to use the approved folder link for handovers. Yesterday’s note used another attachment. Is the agreed process difficult to follow, or do we need to change it?”
Discuss the process before assuming defiance. If the unresolved issue continues to affect delivery, involve the appropriate owner with the facts and decision needed.
If the Conversation Becomes Defensive
Pause and check whether the disagreement concerns the event, the impact, or your proposed change.
“It sounds like we remember the sequence differently. Let’s check the handover record before deciding what to change.”
If they agree with the facts but dislike the delivery, acknowledge that without abandoning the work issue: “I could have raised this more clearly. The review gap still needs a solution.”
Do not recruit other colleagues to validate your criticism, repeat the point louder, or demand an immediate admission. If the conversation becomes hostile, stop and use appropriate support. You do not need to manage every difficult interaction alone.
Follow Up Without Creating a Disciplinary File
For a simple adjustment, a brief recap may be enough: “Agreed: I’ll use the shared index, and you’ll add the approval link before the next handover.”
Record the work agreement in the normal shared place. Avoid secret dossiers of irrelevant behavior, speculative motives, or personal information. Escalation should concern the unresolved work impact and the action needed, not a diagnosis of the coworker.
If you are on the receiving side of the conversation, use the separate guide to handling criticism at work.
Frequently Asked Questions
Should I use a compliment sandwich?
Do not invent praise to disguise a correction. You can acknowledge useful work sincerely, while making the specific improvement request clear. Keep the recipient from having to guess which part is the real message.
Can I give feedback by email?
Yes, particularly for concrete work details that benefit from a record. When tone or context is disputed, a conversation followed by a short recap may be more useful than a long email exchange.
What if I am not their manager?
Speak about shared work, your experience of the impact, and an adjustment you can agree together. Formal evaluation, consequences, or changes to another person’s priorities belong with the appropriate authority.
What if they do not agree to change?
Clarify what remains unresolved and who owns the process. If it materially affects delivery, involve that owner. Feedback is a request for a useful conversation, not a guarantee of agreement.
Reading Perspective
This original guide extends the distinction between being direct and being needlessly blunt in Laoshiren Qimeng (1999). It avoids the book’s broad personality categories and focuses on observable work. The scenarios are illustrative; CCL’s feedback model is credited where used.