How to Write a Peer Recognition Message That Actually Lands
Someone on your team stayed late to fix a broken handoff, and you want to say something. You type “Great job, thanks for all your hard work!” and hesitate, because you have read that exact sentence on a hundred cards and felt nothing.
The hesitation is correct. Generic praise is easy to write and easy to ignore. The version that lands takes about two extra minutes and needs only one thing: proof that you noticed what the person actually did.
Name The Specific Thing They Did
“Hard work” is not an event. A recognition message needs an action the reader can picture: what they did, on which day, for which problem. Gallup’s writing on recognition makes the same point from the manager’s side: the most effective recognition is honest, authentic and individualized. Specificity is how a reader tells that you meant it.
Before:
Great job on the migration, thanks for all your hard work!
After:
Thanks for catching the duplicate customer records before the migration ran on Friday. Cleaning them up by hand took you most of Thursday, and it meant nobody had to apologize to a client on Monday.
The second version costs two sentences. It also tells the person which behavior to repeat, which the first cannot do.
Say What It Changed
After the action, add the effect: what would have happened otherwise, or what is now possible. This is the part that makes thanks feel earned rather than polite.
Keep the effect factual. “The report went out on time” is believable. “You single-handedly saved the quarter” is not, and the recipient will wince at it. If you do not know the real impact, say what you saw and leave the rest out.
Match The Channel To The Person
A public message in a team channel works for someone who likes visibility and can be a small ordeal for someone who does not. Ask yourself which the person would choose.
A reasonable default: private and specific for anything personal or effortful, public and brief when the credit should be visible to people who decide on promotions. If you post publicly, tag their manager. Credit that never reaches the people who evaluate the work is warm but does little else.
Do not attach a request to the thanks. “Thanks so much, and could you also look at…” turns recognition into a lead-in.
Keep It Short And Send It Soon
Three to five sentences is plenty. Recognition loses force with age: a message the same week reads as noticing, and one a month later reads as a task you finally cleared.
Write it plainly, in your own voice. If you tend to overdo the enthusiasm, an AI rewriter can trim it, but it should not add praise you did not write. A Wrivio Context for this situation could say:
Rewrite this as a short, sincere thank-you to a coworker. Keep it to 3 to 5 sentences. Lead with the specific action, then the effect. Keep every name, date, figure, and commitment exactly as written. Do not add superlatives, exclamation marks, or claims about impact that are not in the original.
Press Ctrl+Shift+Space, paste the draft, and check the diff. Look for any adjective the rewrite added that you cannot back up; delete it. If you want a related pattern for asking rather than giving, see how to ask for feedback on your work in writing, and for a longer-form endorsement, how to write a LinkedIn recommendation.
Common Questions
How long should a peer recognition message be?
Three to five sentences is enough: the specific action, what it changed, and a plain thank-you. Longer messages tend to fill up with adjectives, which makes them read as less sincere.
Should I thank someone publicly or privately?
Choose based on the person, not on what looks best. Private suits effortful or personal help; public suits work whose credit should be visible to their manager. When in doubt, send it privately and copy their manager.
What if I do not know the exact impact of what they did?
Describe what you observed and stop there. A factual “you caught the duplicate records before the migration” is stronger than a guess at how much it saved.
Can I use AI to write recognition messages?
You can use it to tighten your own draft, but the specifics have to come from you, because only you know what happened. Keep the facts fixed and review any praise the tool adds. How to review AI rewritten text covers the checks.
Download Wrivio for Windows to polish a thank-you in seconds without losing the details that make it yours.
Read Next
How to Ask a Coworker to Redo Work Without Friction
The work came back wrong and you need it done again. How to ask for a redo that fixes the work without bruising the person or slowing them down next time.
How to Ask for Help at Work in Writing (Without Feeling Like a Burden)
Asking for help is hard, and vague requests get ignored. How to write a clear, specific request that colleagues can say yes to quickly, with examples.
How to Write a Condolence Message to a Coworker
What to send a colleague who has lost someone: a short message that comforts without creating work, plus how to handle the work question.
How to Write a Welcome Email for a New Hire
A new hire's first email sets the tone for their first month. What to include so they arrive oriented and calm instead of guessing, with a reusable template.
This article is filed underWorkplace Writing, which has 177 articles.