What is a good employee appreciation message?

One that could only have been written about that person. The test is simple: swap in a colleague’s name. If it still reads fine, it was never really about anyone. Specific observation beats warm adjectives every time.

How often should you send appreciation messages?

When you notice something, which for most people is more often than they act on. Scheduling it is what produces the flat annual version. If it helps, look back at the past week and ask what would have been harder without a particular person.

Does employee appreciation actually affect retention?

The research consistently links regular recognition to lower turnover and higher engagement, and the mechanism is not mysterious: people who believe their work is unseen start looking. What matters more than frequency is whether it is specific, because generic praise is read as a process.

Should appreciation come from managers or peers?

Both, though peer recognition tends to carry more weight. Saying well done is part of a manager’s job, so it carries that discount. From a colleague there is no such explanation, and it reaches work managers never see.

What is wrong with Employee Appreciation Day messages?

Nothing, except the timing tells the recipient why they were written. A message on a scheduled day competes with everyone else’s and reads as an obligation met. The same words in an ordinary week land completely differently.

Recognition messages

Employee Appreciation Messages: 13 Examples That Say Something

Appreciation with nothing specific in it reads as a task somebody completed. These read as something somebody noticed.

The swap test

Take any appreciation message and put a different colleague’s name in it. If it still makes sense, it was never about the first person.

That is most of what separates recognition people remember from recognition they acknowledge and forget. Specificity does more of that work than warmth or length.

Notice the things that didn’t happen

The hardest work to appreciate is preventive. A pipeline that stopped waking people up, or six weeks of data cleanup whose entire purpose is that nobody thinks about it again.

None of it generates an event to react to, so it goes unmentioned by default. Saying it out loud is the only way that work gets recognised at all, and the people doing it usually assume nobody knows.

13 messages you can send

Thank you for being the person who writes down what we decided. Half our meetings would need repeating without you.
Peer, meeting habits
Thanks a small habit with a large effect.
You’ve handled every one of those support escalations without ever making the customer feel like a nuisance. I’ve read the transcripts. It’s a skill.
Manager, support
Cites evidence, which makes the praise checkable.
Appreciating you for the thing nobody sees: our deploy pipeline has not woken anyone up in four months.
Manager, infrastructure
Recognition for an absence, which is nearly always overlooked.
Thank you for saying “I don’t know” in front of the client last week. It made the rest of what we said believable.
Peer, honesty
Praises something most people would apologise for.
You’ve onboarded four people this year on top of your own work, and every one of them has told me you made the first week bearable.
Manager, mentoring
Counts the work and quotes the beneficiaries.
Thanks for reading the whole document before commenting. It sounds small. It isn’t.
Peer, small habit
Short, dry, and immediately recognisable.
Appreciating Marta, who found the pricing error before it reached the invoices. That was a very expensive Tuesday that never happened.
Manager, catch
Puts a value on something that did not occur.
Thank you for pushing back on my design last month. I was wrong and I’d have shipped it. 🙏
Peer, disagreement
The sender takes the loss, which makes the thanks credible.
You are the only person who consistently asks what the support team thinks before we ship. It changes what we ship.
Peer, cross-team
Names a specific and repeated behaviour.
Thank you for keeping your camera off and your notes on. You’ve made the meetings you run the only ones I don’t dread.
Peer, remote work
Specific enough to be a little funny, which helps it stick.
Appreciating Sara for six weeks of unglamorous data cleanup that nobody will notice, which is the point.
Manager, invisible work
Names the invisibility directly rather than working around it.
You reply to junior engineers with the same care you use for the CTO. I’ve noticed. So have they.
Manager, character
Praises consistency, which is rarely singled out.
Thanks for taking the customer call on your day off and then not mentioning it. Marek told me.
Manager, discretion
The last three words do the work.

What makes one land

Point at one thing. Appreciation that lists three qualities usually names none of them.
Recognise the absence of problems. Work that prevents incidents is invisible by design, so it needs saying out loud.
Say it when you notice, not when the calendar says to. Employee Appreciation Day produces a spike of messages people discount precisely because they arrived together.
Let peers do it. Managers are expected to say nice things, which quietly devalues it. A colleague has nothing to gain.
Keep it separate from feedback. Appreciation followed by “one small thing though” is remembered as the small thing.

Questions people ask

What is a good employee appreciation message?: One that could only have been written about that person. The test is simple: swap in a colleague’s name. If it still reads fine, it was never really about anyone. Specific observation beats warm adjectives every time.
How often should you send appreciation messages?: When you notice something, which for most people is more often than they act on. Scheduling it is what produces the flat annual version. If it helps, look back at the past week and ask what would have been harder without a particular person.
Does employee appreciation actually affect retention?: The research consistently links regular recognition to lower turnover and higher engagement, and the mechanism is not mysterious: people who believe their work is unseen start looking. What matters more than frequency is whether it is specific, because generic praise is read as a process.
Should appreciation come from managers or peers?: Both, though peer recognition tends to carry more weight. Saying well done is part of a manager’s job, so it carries that discount. From a colleague there is no such explanation, and it reaches work managers never see.
What is wrong with Employee Appreciation Day messages?: Nothing, except the timing tells the recipient why they were written. A message on a scheduled day competes with everyone else’s and reads as an obligation met. The same words in an ordinary week land completely differently.