12 Messages for When Someone Went Above and Beyond
The hard part is not deciding to say thank you. It is saying it in a way that shows you were paying attention.
Why general praise doesn’t land
“Thanks for all your hard work” is the recognition equivalent of a nod in a corridor. It costs nothing and nobody has ever reread one.
What people keep is evidence that somebody was watching. A message naming the Friday call, or the rows the export was silently dropping, tells the person their work was visible. That is usually the thing they were quietly unsure about.
Write it in two parts
Say what happened. Then say what it made possible.
That order matters. Leading with praise and never getting to the specifics reads as a formality, because the reader can’t tell whether you know what they did. Leading with the facts proves you do, and the praise becomes the conclusion rather than the whole message.
12 messages you can send
Rachel stayed on the Henderson call until 7pm on Friday because the client was mid-crisis and nobody else could pick it up. They renewed on Monday.
Peer, client workStates what happened and what followed, with no adjectives.
Thank you for rewriting the onboarding doc nobody asked you to touch. Three people started this month and none of them had to ask me anything.
Manager, unprompted workMeasures the result rather than praising the effort.
Ola noticed the export was silently dropping rows, chased it for two days, and found a bug that had been there since March. Nobody had reported it.
Peer, engineeringRecognises catching something nobody was looking for.
You took the customer call I was dreading and turned it into a roadmap conversation. I’ve been thinking about how you did that all week.
Peer, salesAdmits what it cost the sender, which makes the thanks real.
Thank you for covering my on-call while I was out. You handled two incidents and left notes so clear I knew exactly what had happened before I finished my coffee.
Peer, coverNames the second favour hidden inside the first.
Sam sat with the new starter for most of Tuesday getting their environment working. That was Sam’s whole afternoon, and it saved a week.
Manager, mentoringPrices the help honestly in both directions.
You rebuilt the deck at midnight after we changed the story. I know how annoying that was. It’s the version the board actually understood.
Manager, late workAcknowledges the frustration instead of skating past it.
Thanks for pushing back on the deadline last week. You were right, and we shipped something we’re not embarrassed by.
Peer, disagreementRecognises the unpopular kind of extra mile.
Priya answered a support ticket at 11pm on a bank holiday because the customer’s payroll ran the next morning. They wrote in specifically to say so.
Peer, supportIncludes the stake, so the timing means something.
You spent a day on a spreadsheet that nobody will ever see, so that the six of us could stop arguing about numbers. Worth it.
Peer, invisible workNames work whose entire value is that it disappeared.
Thank you for chasing legal every day for a fortnight. I’d have given up on day three and we’d still be waiting.
Manager, persistenceCredits stubbornness, which rarely gets thanked.
Marco drove to the warehouse on a Saturday because the scanner was down and the order had to ship. He didn’t tell anyone until Monday.
Manager, operationsThe last sentence is the compliment.
What makes one land
Say what they did before you say how you feel about it. The facts are the compliment.
Include the stake. “Stayed late” means little. “Stayed late because the customer’s payroll ran the next morning” means a lot.
Send it within a day or two. The value drops sharply once the week has moved on.
Don’t attach it to a request. Thanks followed by “and while you’re at it” stops being thanks.
If it cost them something, say so. Naming the cost is what separates recognition from politeness.
Questions people ask
- How do you thank someone for going above and beyond at work?
Describe what they did in plain terms, then say what it made possible. Plenty of thank-you messages skip the first part and lead with praise, which leaves the reader unsure whether you know what actually happened. Put the facts first and the feeling second.
- Should you recognise extra effort if it happened because of bad planning?
Yes, and separately fix the planning. Withholding thanks does not prevent a repeat, it just means the person who absorbed the problem also absorbs the silence. Thank them for the work, then take the process conversation somewhere else.
- Is a public thank-you better than a private one?
Usually. Public recognition tells the rest of the team what the company notices, and effort that goes unseen tends not to be repeated. Some people find it uncomfortable, so follow their lead if they’ve said as much.
- What if you find out weeks later?
Send it anyway, and say you only just heard. Late recognition with a real detail in it is still worth more than none, and admitting the delay is more honest than pretending you noticed at the time.
- How do you recognise effort without encouraging overwork?
Thank the judgement, not the hours. “You spotted that before it reached the customer” rewards the thing you want more of. “You worked all weekend” rewards the thing you don’t.
The values behind it
Other occasions
Only pay for active users who use Evergreen
Lots of support, with a help center and direct email options
Cancel at any time, so why not give us a try
Start feeling good about work
For only $3.99 per active user a month. In the 14 day free trial we don’t plant real trees, but you can skip the trial if you like.
No credit card needed • No setup costs