
Positive Feedback for a Coworker: Examples, Emails, and Peer Reviews
Give positive feedback for a coworker by naming a specific work situation, the action you noticed, and how it helped you or the team. For example: “Your handover listed the open requests and their owners, so I could start the next shift knowing what needed attention.” The examples below give you wording for everyday contributions, a thank-you email, and a formal peer review. Choose the situation closest to yours, replace the details with something you observed, and use a level of warmth that fits your relationship. A small, accurate acknowledgment is enough.

What can you say about a helpful handover, explanation, or collaboration?
Recognise the part of the work that made your own task easier. These first four examples cover practical help you can describe without knowing the project's final outcome. Each message can stand alone in a chat or a brief conversation; the sentence after it explains how to adapt it.
1Example 1: A clear handover
“Thanks for listing the unresolved requests and the next person responsible in yesterday's handover. I could pick up the morning work without having to reconstruct the conversation.”
Replace “unresolved requests” with the actual items your colleague documented. If you still needed clarification on one point, you can appreciate the useful information without claiming the whole handover was flawless.
2Example 2: An explanation that made sense
“When you walked me through the reporting steps, you used a completed example and paused for my questions. That helped me understand which details I needed to check before sending my own report.”
Use this when the explanation changed what you understood or did. Naming the teaching action gives more information than saying your colleague is naturally brilliant.
3Example 3: Information brought together
“The meeting summary you shared put the decisions and open questions in one place. I used it to check my next task instead of searching through separate messages. Thank you for organising that.”
Mention the document you actually used. Do not attribute everyone else's progress to it unless you know how they used it too.
4Example 4: Collaboration across responsibilities
“During the draft review, you asked how the proposed change would affect my part of the work before we agreed on it. That gave me space to flag a dependency we needed to resolve together.”
This recognises a specific collaborative choice. It does not require calling the person the best teammate or comparing them with colleagues who were not involved.
How can you recognise reminders, newcomer support, follow-through, and meeting contributions?
Notice contributions that can disappear into the routine: a useful warning, a patient answer, a closed loop, or a question that makes a decision clearer. The next four messages acknowledge those actions directly. Pick the example that matches what happened rather than combining all four into a long compliment.
1Example 5: A timely reminder
“Thanks for reminding me that the attachment needed approval before the client update. I checked it before sending, and the message went out with the approved version.”
The sequence matters here: reminder, check, correct version. You do not need to speculate about the complaint or financial loss that might otherwise have happened.
2Example 6: Support for a new colleague
“I appreciated you showing me where the onboarding instructions live and explaining who handles access questions. I knew where to go when I got stuck later that afternoon.”
If you watched someone help a newcomer, change the ending to an observation you can support, such as “I noticed you stayed until their access question had an owner.”
3Example 7: Following through
“You said you would check the missing detail with the project lead, and you came back with an answer before our next discussion. That meant I could prepare my recommendation with the right information.”
Acknowledge the completed commitment. Avoid turning one helpful follow-up into an expectation that this colleague will always chase every loose end.
4Example 8: A useful meeting contribution
“Your question about who would maintain the checklist helped us notice an ownership gap. We assigned someone before the meeting ended, so I left knowing where updates should go.”
This works well as a short note after a stand-up meeting. Praise the question and the resulting clarification, rather than simply saying the person spoke confidently.
How do you make positive feedback for a coworker specific?
Move from a broad compliment to an event the recipient can recognise. “Great job” can remain as a warm opening, but the next sentence should explain what you appreciated. A small detail often carries more meaning than a stronger adjective.
The Center for Creative Leadership's SBI guidance recommends identifying the situation, describing observable behaviour, and explaining its impact on you. It also advises keeping the behaviour description factual rather than adding judgments. For peer recognition, use those elements to explain one helpful contribution in ordinary language.
| General praise | Specific event | Revised message | Useful setting |
|---|---|---|---|
| You are so organised. | A task list separated decisions from unanswered questions. | Your task list made it clear which decisions were settled, so I could focus my reply on the open questions. | Project chat |
| Amazing communication. | A colleague explained a changed instruction before work began. | You explained what changed before I started, so I used the current instructions. | Direct conversation |
| You are a great teammate. | A colleague reviewed your draft against the agreed brief. | Your comments linked back to the brief, which helped me choose what to revise. | Thank-you email |
| Excellent presentation. | A summary distinguished a recommendation from its supporting details. | You stated the recommendation first, so I could follow how the details supported it. | Private follow-up |
The impact can be personal: “I understood the decision” is useful information. You do not need an organisation-wide result. For more detail on arranging those three parts, see the SBI feedback model. Keep the actual message shorter than the explanation of the method.
How should you write a chat message, email, or formal peer review?
Keep the underlying example consistent while adjusting the amount of context. A chat can rely on a conversation you both remember. An email needs enough information to make sense later. A formal colleague evaluation needs a clear account of what you observed and where your experience is limited.
Example: Short chat message
“Thanks for checking the open questions in the launch brief this morning. Your notes showed me which answers still needed confirmation, so I could prepare the follow-up.”
This version is enough when you both know the brief. Add a friendly closing if it sounds like you, but there is no need to turn a quick acknowledgment into a speech.
Example: Thank-you email
Subject: Thank you for clarifying the launch brief
Hi Maya,
Thank you for reviewing the open questions in the launch brief this morning. You separated the confirmed answers from the points that still needed a decision and identified who could answer each one.
I used those notes to prepare the follow-up without treating the unresolved points as final. I appreciated the care you took with the details.
Thanks,
Alex
Send this privately when the contribution mainly helped you. Copying a manager changes the audience; consider whether the recipient would welcome that visibility and whether the message includes information others should see.
Example: Formal peer review
“I worked with Maya on the launch brief. During our review, she distinguished confirmed answers from unresolved questions and identified the people who could clarify them. Her notes helped me prepare the follow-up using the current information. This is a specific example of the clarity I observed in our work together.”
In a review form, answer the actual prompt. If it asks about collaboration, explain the interaction; if it asks about quality, describe the checks you saw. Do not convert a useful example into a rating on areas you have not worked on together. A formal record should remain understandable to someone who was not present.
Should you praise a colleague publicly or privately?
Choose the audience according to the colleague's preferences, the content of the message, and who needs the context. A direct note is a reasonable starting point when you do not know whether the person enjoys public attention. If wider recognition seems useful, ask whether they would be comfortable with you sharing it at the team meeting.
Public acknowledgment can name a contribution relevant to the group: “Before we close, thanks to Jordan for bringing the outstanding decisions into one list. I used it to prepare today's discussion.” Keep confidential customer details, sensitive project issues, and personal circumstances out of a public message.
When several people contributed, distinguish their work rather than ranking them. For example: “Priya checked the requirements, Luis tested the instructions, and Morgan brought the updates together. Their work gave me a clear version to review.” If you only know one person's contribution, recognise that part without declaring who deserves most of the credit.
Avoid praising constant availability: “You always answer at night” can sound like a request to keep doing it. Recognise the useful action within the event instead: “Your explanation of the exception helped me understand the next step.” Let the recipient accept the thanks without having to promise more work. If they prefer private recognition, respect that preference the next time too.
What if you rarely work with the person you want to thank?
Give a narrow observation rather than a broad endorsement. You can appreciate one interaction without claiming to know the person's overall performance. Name how you encountered their work, describe what you used, and stop at the effect you experienced.
Example: A colleague from another department
“We have only worked together on this request, but I appreciated how you explained the approval sequence. I knew which step belonged to our team and where to send the completed document.”
Example: A resource you used
“I used your checklist when preparing my first supplier update. The distinction between required attachments and supporting notes helped me assemble the message.”
If you heard someone else praise the colleague, do not present their experience as your own. You can pass on the thanks with attribution if it is appropriate to share, but that is different from providing a firsthand evaluation. In a review request, say which work you saw and leave unfamiliar areas unassessed.
For a contribution involving customers, separate the clarity of the message you reviewed from the customer's reaction. “The revised wording explained the next step clearly to me” is narrower than “The customer loved it.” The client communication scenario is a related place to practise explaining such distinctions aloud.
Which compliments should you rewrite before sending?
Rewrite wording that hides the contribution, weakens the thanks, or attaches a new obligation. The goal is to make your appreciation easier to understand, not to make every friendly sentence sound formal. These four edits address different problems.
- Personality label: Change “You're a genius” to “You noticed that the two instructions contradicted each other and checked which one applied. That helped me correct my draft.” The revised version identifies what impressed you.
- Absolute claim: Change “You never miss anything” to “You caught the missing approval in this version before we sent it.” One observed check is enough; you do not need to guarantee future perfection.
- Backhanded praise: Change “That was surprisingly good for someone new” to “Your summary made the decision and its supporting reasons easy to follow.” Remove the comparison with an unstated low expectation.
- Praise followed by a request: Change “You're brilliant at this, so can you take over my report?” to a standalone thank-you for the help already given. If you need more help, make a separate request with room for the person to decline.
Also check whether you are praising a contribution or giving an instruction disguised as praise. “I like it when you agree with my plan” rewards agreement rather than useful work. “Your question helped me explain the trade-off” identifies a contribution even when the colleague challenged you.
Keep a development concern separate from this acknowledgment. You can arrange another conversation about an issue rather than adding “but” and a correction to the end of the thank-you. The constructive criticism examples address that separate task. For this message, finish with the appreciation you intended to communicate.
How can SayNow AI help you practise saying your appreciation?
SayNow AI offers AI conversation practice in professional situations, including interviews, presentations, and negotiations. Its conversation practice approach includes real-time feedback on delivery, structure, clarity, and persuasiveness, alongside communication framework learning. Use that practice to make an acknowledgment sound like something you would say to a colleague.
Choose one event from your own work and prepare three notes: what happened, what the person did, and what it helped you do. Say your appreciation aloud in a practice conversation instead of reading a polished paragraph. Review the feedback on structure and clarity, then choose one adjustment, such as naming the action before explaining the impact.
Say it again with that change. Keep your own vocabulary and a closing that feels comfortable. The aim is a clear, proportionate message you can deliver in person, including when a colleague asks for an example during a review. Practise your next peer acknowledgment in the Performance Review scenario.
What template and final checks can you use today?
Use this template to draft your message, then remove any wording you would not normally say. The situation can be brief: “in yesterday's review” or “when I joined the project” may provide enough context.
Hi [name],
Thank you for [specific action] during [situation].
It helped me [concrete effect you experienced].
I appreciated [detail worth recognising].
Before sending, check that the action is observable, the effect is yours to describe, and the audience suits the recipient. Read the message aloud once. If it sounds inflated, replace an adjective with the detail that led you to choose it. If it contains a new request, move that request into a separate message.
For a longer conversation, the PREP method and 7 Cs of Communication offer related communication structures. You can also explore the SBI feedback guide or use a giving and receiving feedback activity to rehearse exchanging examples with a partner.
Choose one recent contribution and send your positive feedback for a coworker today. Use the smallest accurate example that explains what you valued, and let the thanks stand on its own.
Related Articles
SBI Feedback
Explore how to connect a work situation, an observed action, and its impact.
Constructive Criticism Examples
Prepare wording for a separate conversation about something that needs improvement.
Giving and Receiving Feedback Activity
Explore an activity for practising feedback exchanges with a partner.
Ready to Transform Your Communication Skills?
Start your AI-powered speaking training journey today with SayNow AI.