Most lists of words of appreciation for employees are organized by feeling — "heartfelt," "motivational," "funny." That's a useless way to sort them, because you don't arrive at this page with a feeling. You arrive with a situation. Someone stayed late to unbreak a deploy, or covered a shift, or finally shipped the migration nobody wanted, and you have about ninety seconds to say something that doesn't sound like a form letter.
So this list is sorted by what happened. Sixty phrases across twelve situations, each one written to be pasted and edited in under a minute. First, though, thirty seconds on why "great job" fails — because once you see the mechanism, you can write your own without a list.
Why "Great Job" Doesn't Land
"Great job" fails for a structural reason, not a sincerity one. You probably mean it. The problem is that the sentence contains no evidence you were paying attention. It's interchangeable — it would have worked equally well for anyone, on any day, for any task. The recipient's brain correctly classifies it as a politeness token rather than information.
Specific appreciation works because it carries proof. "Thanks for catching the rounding bug in the invoice job before it hit customers" tells the person three things at once: I noticed, I understood what you did, and I know what it prevented. That's the whole trick, and it's why the phrases below all have a blank in them.
The formula: what they did + what it made possible + what it says about them. You rarely need all three. You almost always need the first two.
One more thing worth knowing before you start pasting. Employees who don't feel adequately recognized are about twice as likely to say they'll quit within the year (Gallup / Workhuman), and organizations with strong recognition cultures report up to 31% lower voluntary turnover (Deloitte). The words are small. The compounding isn't.
When Someone Caught a Problem Before It Got Expensive
The hardest work to recognize, because the outcome is an absence — nothing broke. Name the thing that didn't happen.
- "You caught the ___ before it reached a customer. Nobody's ever going to know how close that was except us, so: thank you."
- "Everyone sees the fires. Almost nobody sees the ones that never started. That was you this week."
- "That was a five-minute fix that saved us a two-week cleanup. Genuinely great instincts."
- "Thanks for pulling the thread on ___ instead of assuming someone else had it. That instinct is worth a lot around here."
- "You noticed something that was easy to not notice. That's the part I want to call out."
When Someone Dropped Their Work to Unblock Yours
Deceptively costly — they paid a context-switching tax so you didn't have to. Say so.
- "You dropped what you were doing to unblock me, and I know that cost you your afternoon. It saved my week."
- "Thank you for jumping in on ___ without me having to ask twice."
- "I was completely stuck until your message. Thirty seconds of your time, four hours of mine."
- "You're the person on this team who always answers the 'quick question' that isn't quick. Noticed and appreciated."
- "Thanks for taking ___ off my plate so I could focus on ___. That was exactly the right call."
When Someone Did the Boring, Necessary Thing
Documentation, cleanup, the migration, the spreadsheet nobody wanted. High value, zero glamour, and almost never recognized — which is precisely why it stops happening.
- "Nobody was going to volunteer for ___, and you did it anyway. That's the least glamorous and most useful thing that happened this month."
- "Thank you for the ___ documentation. Every person who joins this team for the next two years is going to benefit from an afternoon of your time."
- "You cleaned up something that wasn't yours and never mentioned it. I mentioned it."
- "That migration was tedious, thankless, and now permanently done. Thank you for absorbing all three."
- "'Someone should really fix that' — and then you just did."
When Someone Was New and Got Their First Win
Early recognition disproportionately shapes whether a new hire feels like they belong. The first ninety days set the pattern, so don't wait for something impressive.
- "Week two and you already shipped ___. Genuinely fast start."
- "Thanks for asking the question everyone else was too embarrassed to ask. Fresh eyes are a feature."
- "You found a gap in our onboarding docs by falling into it, then fixed it. That's the best possible outcome."
- "Watching you pick this up has been a pleasure. Welcome — you're clearly going to be great here."
- "First win on the board. There will be many more, but this one counts."
When Someone Went Through a Grind
A long push, a hard quarter, an incident that lasted three days. Acknowledge the cost, not just the output.
- "That was a long, unglamorous stretch and you never once made it someone else's problem. Thank you."
- "I want to name how hard the last few weeks were, not just that they're over. You carried a lot."
- "You stayed steady through something genuinely difficult. That's not a small thing, and I noticed."
- "Thanks for the ___ push. Now please take the time back — that's an instruction, not a suggestion."
- "The result is great. The way you held it together while getting there is what I'll remember."
When Someone Helped Someone Else Look Good
Mentoring, prep work, the review that made the presentation land. Invisible by design.
- "___ crushed that presentation, and I know a lot of that was your prep. Passing the credit back where it belongs."
- "You made someone else better at their job this week. That's the highest-leverage thing anyone here can do."
- "Thank you for the code review that turned a working solution into a good one. That kind of patience teaches."
- "You could have done it yourself in half the time. You taught it instead. That was the right call and I noticed the cost."
- "Every time someone on this team levels up, you're somewhere in the story."
When Someone Handled a Difficult Customer or Stakeholder
- "That conversation could have gone badly in six different ways and it didn't, because of how you handled it."
- "You absorbed a lot of frustration that wasn't yours to absorb and kept the relationship intact. Thank you."
- "Watching you de-escalate that was a genuine masterclass."
- "You said the hard true thing kindly. That's a rare combination."
- "Thanks for holding the line on ___ when it would have been easier to just agree."
When Someone Disagreed With You and Was Right
Almost nobody recognizes this, and it's the phrase with the highest cultural return in the entire list. Recognize it once in public and you buy yourself a year of honest pushback.
- "You pushed back on ___ and you were right. Thanks for not letting me walk into that."
- "I disagreed with you in that meeting and I was wrong. Publicly noting it because you were right publicly."
- "Thank you for being the person willing to say the uncomfortable thing. It changed the decision."
- "You made the argument nobody else wanted to make, and it was the correct argument."
- "Disagreeing well is a skill. You have it."
When Someone Owned a Mistake
- "You flagged it before anyone asked, fixed it, and wrote up what happened. That's exactly how this is supposed to go."
- "Thank you for the honest postmortem. No spin, no defensiveness — that makes everyone safer."
- "The mistake cost us a day. The way you handled it bought us trust. Net positive."
- "Anyone can be right. Saying 'that was mine' out loud is the harder skill."
When It's a Work Anniversary or Milestone
The trap here is generic longevity language. Name something specific from the actual years. (More at work anniversary messages.)
- "Five years. In that time you've ___, ___, and quietly become the person everyone checks with first."
- "Happy work anniversary — this place is measurably different because you've been in it."
- "Three years of ___. Thank you for staying, and for the version of this team you helped build."
- "A year in and you've gone from asking the questions to answering them. Great to have you."
When You're Writing to the Whole Team
- "This quarter had exactly one easy week in it. Thank you all for the other twelve."
- "We shipped ___ because seven different people did unglamorous things at the right moment. Naming all of them: ___."
- "Proud of this team. Not for the outcome — for how we got there."
- "Whatever the number says, the way this team worked together this quarter was the actual result."
When It's Peer to Peer
Different rules apply between colleagues: skip the evaluative framing ("you demonstrated strong ownership" from a peer reads as strange), keep it concrete and short. More peer examples here.
- "You saved me from myself on ___. Thank you."
- "Stealing your approach to ___ permanently. It's better than mine."
- "Genuinely don't know how I'd have gotten through this week without you. Not being dramatic."
- "You're the reason I like working here. Felt like saying it out loud."
Three Habits That Beat Any Phrase List
Say it within 48 hours
Appreciation decays fast. A specific thank-you on Tuesday for a Monday save lands ten times harder than a polished paragraph at the quarterly review. If you're choosing between well-worded-and-late and clumsy-and-immediate, choose immediate every time.
Say it where other people can see it
A private DM is good. The same words in a team channel do two jobs — the person feels seen, and everyone else learns what "good" looks like here. Public recognition is how norms get transmitted without a values deck. If you don't have a place for that yet, a dedicated Slack channel takes about five minutes to set up.
Watch who you're not saying it to
This is the one that catches good managers. Appreciation naturally flows toward the visible — the people in the meetings, the ones who present, the ones whose work has a demo. Meanwhile the person keeping the unglamorous system running gets nothing for eight months and then resigns, and it reads as sudden. It wasn't. Recognition inequality is measurable, and it's usually invisible until you look at the distribution rather than the total.
That's the gap peer recognition tools exist to close — and yes, we make one, so read this with appropriate suspicion. Propsly lives in Slack: people give each other props with /props, every give posts publicly in a feed channel, and the analytics show you who's being recognized and who's been quiet for a month. The point isn't the leaderboard. It's that colleagues see the work managers structurally can't, and the data tells you where appreciation isn't reaching.
The One-Sentence Version
If you remember nothing else from this page: name the specific thing, then name what it made possible. "Thanks for staying late to fix the export bug — the client demo went off without anyone knowing there was ever a problem." That's it. That's the whole craft. Every phrase above is just that formula wearing different clothes.
The words matter less than the noticing. Get in the habit of noticing and the words show up on their own.