The kudos channel in most company Slacks is a graveyard of vague enthusiasm. "Amazing work team!" "You're crushing it!" Three fire emojis. A bowing person. A clap. The intent is good. The signal is zero.

The reason these messages fail is the same reason most thank-you cards fail: they could be addressed to anyone. The recipient reads them, smiles politely for half a second, and moves on. Nothing about the message tells them what specifically they did, why it mattered, or what it said about them as a teammate. The recognition is real, but the memory of it disappears before lunch.

The fix isn't more enthusiasm. It's more specificity. A short kudos that names the actual moment — "the way you spotted the env-var mismatch in five minutes saved us a real outage" — sticks for weeks. The recipient takes a screenshot. They show it to their partner. They reference it in their next 1:1. That's what a kudos is supposed to do.

Below are 30+ kudos messages organized by the moments they're written for. Each one is meant to be adapted, not copied. Swap in the real names, the real project, the real moment. The specificity is the whole point.

7 days
Optimal recognition frequency, per Gallup
4x
More likely to be engaged when employees feel recognized
82%
Of employees wish they were recognized more often

Why Specific Kudos Land and Generic Ones Don't

There's a neat experiment researchers have run on recognition. Two groups of employees received the same number of thank-you notes from their manager. One group got generic notes ("Great job this week!"). The other got notes that named the specific work and the specific impact. Both groups felt appreciated — right after reading. A week later, only the specific group could remember what they were appreciated for, and only that group reported a sustained increase in motivation.

The mechanism is straightforward. Specific kudos teach the recipient something about how their work is perceived. Generic kudos teach them nothing. Recognition that teaches sticks. Recognition that doesn't, fades.

This matters most for the people you most want to keep — the high-context senior engineers, the quiet contributors, the operators who hold things together. They've heard "great job" a thousand times. What they haven't heard often enough is exactly what you noticed and exactly what it meant.

The kudos formula

Every effective kudos has three beats: (1) The specific thing they did — not "your work" but the actual move, decision, or behavior. (2) What it produced — the outcome, the saved hours, the avoided outage, the customer who walked away happy. (3) What it says about them — the quality, instinct, or working style it reflects. Most kudos skip straight to step three. That's why they feel hollow.

For Shipping a Feature or Hitting a Deadline

For the moments when something actually went out the door. These messages work for product launches, sprint commitments, hard release deadlines — anywhere the team needed to land something on a specific day and did.

Message 01 "The way you owned the [feature name] launch from spec to ship was exactly the bar we want to set on this team. You didn't just deliver code — you held the timeline, ran the demo, and unblocked three other people along the way. Big kudos."
Message 02 "Watching you get [project] across the line this week was a masterclass in focus. You stripped scope where it didn't matter, fought for it where it did, and never let the team lose the plot. That's senior judgment in action."
Message 03 "Kudos for the rollout plan you wrote for [feature]. It wasn't flashy — just three pages of clear thinking about staged release, rollback criteria, and metrics to watch. That's the kind of doc that prevents an incident, and it deserves to be called out."
Message 04 "You shipped [feature] a full sprint early and the quality didn't drop. I know what trade-offs that usually requires, and you found a way to make them without the usual cost. Thank you — that was visible to everyone who was paying attention."

For Owning an Incident or Outage

The bar for kudos goes up during incidents. People who stayed up late, kept their head, and led the room through a hard moment deserve more than a generic "thanks for the hustle" the next morning.

Message 05 "I want to specifically call out how you ran the incident last night. You kept the channel calm, asked the right diagnostic questions, and didn't let anyone go off chasing dead ends. The customer never saw the worst of it because you held it together. That was leadership."
Message 06 "The way you spotted the env-var mismatch within five minutes of the page firing — that's the difference between a 90-minute outage and a five-minute blip. Your instincts under pressure are something the team is lucky to have."
Message 07 "Your postmortem on the [incident] is going to outlive the incident itself. It's the rare doc that explains what actually happened without blame, gives the team something to learn from, and ends with actions you can actually track. Big thanks for that piece of work."
Message 08 "You picked up the page at [time] and didn't drop it until the fix was deployed and verified. The team got their sleep because you didn't. That's not lost on me, and it shouldn't be lost on anyone here."

For Picking Up the Slack

For the teammates who quietly absorb the work that nobody else wanted — the unglamorous, the unscoped, the "we'll get to it later" that someone has to actually get to.

Message 09 "You took on the [boring but important task] without anyone asking, and now nobody else has to think about it. That's the kind of contribution that doesn't show up in a sprint demo but holds the team together. Thank you."
Message 10 "When [coworker] went on leave, you absorbed their on-call, their oncalls, and half their PRs without ever making it a thing. The team didn't feel a gap because you closed it. That's the quietest kind of generosity at work."
Message 11 "Kudos for taking on the migration nobody wanted. You scoped it honestly, told us where it was going to hurt, and delivered it with fewer surprises than anyone expected. Hard, undramatic work that mattered."
Message 12 "I noticed you've been picking up the runbooks and the on-call docs nobody had time to update. Future-us is going to thank present-you for that, and present-me already does."

For Mentoring a Junior or Onboarding a New Teammate

Mentorship is one of the most consistently undercredited contributions in engineering. Time spent pairing, reviewing, explaining, and answering questions is invisible in commit history. Kudos here go a long way — especially for senior engineers who do it well.

Message 13 "The way you paired with [junior name] this week on the [project] was the kind of mentorship that actually changes someone's career. You let them drive, you asked good questions, and they came out of it more confident, not more confused. That's hard to do."
Message 14 "Your code review feedback on [PR] was a tutorial. You didn't just point out the bug — you explained the underlying principle in two sentences that I'll carry with me. Thank you for taking the time to teach instead of just correct."
Message 15 "I noticed how you rewrote the onboarding doc after [new hire] went through it. You used their actual stumbling points as the structure, not the structure you wished they'd had. That's a thoughtful piece of work and the next five hires are going to benefit."
Message 16 "Kudos for being the person [new teammate] feels safe asking questions of. You've made yourself approachable in a way that makes the whole team better. That's a real cultural contribution."

For a Senior Engineer or Tech Lead

Senior engineers chronically under-receive specific recognition because their teams assume they don't need it. Wrong. A specific kudos to a staff or principal engineer often lands harder than the same kudos to a mid — it tells them their judgment is visible and valued, which is the currency they actually care about.

Message 17 "Your call to push back on [architectural decision] in the design review saved us a quarter of work down the line. I didn't see it at the time, but it's clear now. The team is lucky to have someone with that kind of pattern recognition."
Message 18 "Watching you run the [tech debt] discussion this week was a clinic. You held space for every perspective without losing the thread, and the team walked out with a real decision instead of another open question. That kind of facilitation is its own craft."
Message 19 "The bar you set on [system / project] raised the standard for everyone working in that area. People reference your work when they argue about what 'good' looks like here. That's a contribution to the culture, not just the codebase."
Message 20 "Your strategy doc on [topic] is going to define how we think about this for the next year. Clear, specific, and honest about the trade-offs. Big kudos for putting that on paper."

For a Manager Who Got It Right

Managers also rarely receive specific kudos. If yours just did something genuinely good — protected the team, made a hard call, gave you feedback that helped — tell them. It signals what works.

Message 21 "I want to say specifically: the way you protected the team from [external pressure] this quarter was felt. We could focus on the work because you absorbed the noise. That's not a small thing."
Message 22 "The feedback you gave me in our last 1:1 about [topic] was direct, kind, and exactly what I needed to hear. I've already started doing the thing you suggested and it's working. Thank you for being honest with me."
Message 23 "You made the call to deprioritize [project] this week and it was clearly the right one. I know it wasn't easy because [stakeholder] wanted it. The team noticed and respects you for it."

For Cross-Team or Adjacent Contributions

Recognition that crosses team boundaries signals something important: good work travels. Kudos from outside the recipient's own team often lands harder than internal ones because it tells them their work is visible across the org.

Message 24 "I'm on [other team] and just wanted to flag — the API you shipped last week made our integration shockingly easy. Clean naming, good docs, sensible defaults. We finished in a day what we'd budgeted a sprint for. Thank you."
Message 25 "Kudos for the way you handled the [cross-team] discussion. You came in representing your team's position but stayed open to the broader trade-offs. That's how productive cross-functional work actually happens."
Message 26 "Your demo at all-hands today was the clearest explanation of [topic] I've seen from anyone. I'll be sharing the recording with my team this week. Genuinely well done."

For Quiet, Everyday Excellence

The hardest kudos to write — and often the most important. For the teammate whose contribution doesn't fit any one moment but who keeps the whole thing running.

Message 27 "I want to take a second to recognize something easy to overlook: the consistency you bring to everything you touch. There are no surprises when your name is on a PR. That reliability is a real gift, and it's noticed."
Message 28 "You show up to standups with the same level of preparation every single day. That sounds small. It's actually rare, and it sets the bar for the rest of us."
Message 29 "You answer questions in [Slack channel] with the kind of patience and thoroughness that makes people feel safe asking. That has a compounding effect on team culture that I want to make sure you know is seen."
Message 30 "Thank you for being someone the team can rely on. I don't say it often enough and I should. You make this place better."
Message 31 "The thing about your work that I appreciate most is that it's never about you. You make other people look good, surface what's working without grandstanding, and keep the focus on the outcome. That's senior craft."

A Few Rules That Make Kudos Land

Beyond the templates, a few principles that separate kudos that land from kudos that fade.

Why This Matters at the Culture Level

Companies don't have great recognition cultures because they pay for it once a year at the awards dinner. They have great recognition cultures because the cadence of specific, public kudos is high enough that everyone knows when their work is landing. The signal is everywhere, all the time, in the way teammates talk to each other.

This shows up in the data. The companies in our culture directory that rank highest on psychological safety and team health tend to also be the ones where engineers report frequent, specific peer recognition. The two are not separate phenomena. Recognition is how safety gets built.

If you're hiring engineers and want to compete on culture, the team-by-team recognition habits inside your company are doing more of the work than the perks page on your careers site. The fix is free, immediate, and sitting in your Slack right now.

Frequently Asked Questions

What is a good kudos message for a coworker?+
A good kudos message is specific, timely, and personal. It names the exact behavior or contribution, explains why it mattered, and acknowledges something about the person's character or working style. "Thanks for the help on the deploy yesterday — the way you spotted the env-var mismatch in five minutes saved us a real outage. That's the kind of attention to detail I trust you for." That's a kudos. "Great job, team player!" is not.
What's the difference between kudos and appreciation?+
Kudos is the everyday, low-stakes version of recognition — a quick, public acknowledgement for a specific moment or contribution. Appreciation is broader and more sustained — it speaks to who someone is over time. Both matter. Kudos creates the cadence of recognition. Appreciation creates the depth.
Where should I send kudos to a coworker?+
Where it'll be seen. Public Slack channels, team standups, and all-hands meetings amplify recognition and signal to the team what good work looks like. For something personal or sensitive, a 1:1 message or hand-written note can land harder. The choice depends on the person.
How often should I send kudos to coworkers?+
More often than feels comfortable. Gallup research suggests the ideal recognition frequency is every 7 days. Most teammates and managers give it far less often. There's effectively no risk of over-recognizing as long as the kudos stay specific and genuine.
Can I send kudos to a coworker who's senior to me?+
Yes — and you absolutely should. Senior engineers and managers chronically under-receive specific recognition because their teams assume "they know" or "they don't need it." A specific, well-observed kudos from someone junior often lands harder than the same kudos from a peer.
What kudos sound fake or hollow?+
The ones that could apply to anyone. "Great job!", "You're amazing!", "Thanks for everything!" — these read as effort but contain no observation. Also avoid kudos that are really about you ("I'm so lucky to work with you!"). The recipient should learn something about how their work was perceived.
How do I write kudos for someone I don't work with closely?+
Reference the specific surface where you saw their work — the PR you reviewed, the design doc they wrote, the demo they gave, the customer call you sat in on. Generic kudos from someone the recipient doesn't know well can feel performative. Specific kudos that name how you saw their work feel earned.

Find companies that actually celebrate good work

Recognition culture isn't a perk — it's an early signal of how a team treats its people. Use our directory to find companies that rank high on psych safety and team health.

Browse Safe-to-Fail Cultures → Browse All Jobs →