You've seen it happen. Someone in leadership announces a #kudos channel with great fanfare, three people post a dutiful "great job team!" in week one, and by week three the channel is a museum. The instinct was right — people genuinely want to be appreciated, and Slack is where work actually happens — but the execution had all the warmth of a compliance training. If you've ever wondered how to give kudos in Slack without it landing like a forced icebreaker, the good news is that the difference between cringe and connection comes down to a handful of learnable habits.
This isn't a small-stakes skill, either. Gallup and Workhuman found that employees who don't feel adequately recognized are about twice as likely to say they'll quit within a year, and Deloitte's research links strong recognition cultures to up to 31% lower voluntary turnover. The gap between a team that appreciates each other out loud and one that doesn't shows up in retention numbers, not just vibes. So let's get the craft right.
Why Most Slack Kudos Feel Forced
Forced-feeling kudos almost always share one of three flaws:
- They're generic. "Great job, Priya!" could describe literally anything Priya did this quarter. Generic praise reads as obligation, because it carries no evidence that the giver actually noticed anything.
- They're late. Praise delivered at the monthly all-hands for something that happened three weeks ago has the emotional temperature of a tax receipt. The moment has passed; everyone knows it.
- They're performative. When kudos only appear right before review season, or only flow toward whoever leadership is watching, people notice. Recognition that looks strategic stops feeling like recognition.
Every fix below is just the inverse of one of those flaws: be specific, be fast, and be genuine even when nobody important is watching.
The Specificity Formula: What + Impact + Person
Here's the single highest-leverage upgrade to any kudos message. Instead of praising the person in the abstract, name three things:
- What they did — the specific action, not the job title. "Rewrote the onboarding doc," not "being awesome."
- The impact it had — who was helped and how. "The new contractor got productive in a day instead of a week."
- What it says about them — the quality the action demonstrates. "You always spot the friction the rest of us have gone blind to."
Compare "Thanks Marcus! 🎉" with: "Marcus stayed on the deploy last night until the checkout bug was actually confirmed fixed, not just probably fixed — that's why support woke up to zero tickets instead of forty. That's what ownership looks like." The second one takes twenty extra seconds to write and lands roughly a hundred times harder, because it's unfakeable. You can only write it if you were paying attention — and being noticed is the entire point of recognition. If you want a stockpile of worked examples across different situations, we've collected a big batch in our peer recognition message examples.
A shortcut when you're stuck
Can't find the words? Finish this sentence: "Because you did ___, I didn't have to ___." It forces both the specific action and the concrete impact, and it works for almost anything — "Because you documented the API quirks, I didn't have to spend my afternoon in the debugger."
Timing: Kudos Have a Half-Life
Recognition decays fast. Praise delivered within a day of the moment feels like someone saw you; the same words two weeks later feel like someone was reminded of you, probably by a calendar. A good rule of thumb: give kudos within 48 hours or give context. If you're late, say why it's still on your mind — "I keep coming back to how you handled that escalation last week" turns lateness into a compliment about staying power.
The best kudos-givers don't rely on memory at all. They fire the message the moment the thought occurs — mid-meeting, mid-code-review, mid-scroll. Slack makes this trivially easy: you're already in the room where it happened. The whole trick is lowering the gap between noticing and saying to near zero, because every hour in between is an hour for "I should mention that" to quietly become "someone probably already did."
Emoji Culture: Amplifier, Not Substitute
Slack emoji deserve their own paragraph because teams get this both wrong in both directions. A 🎉 reaction on someone's ship announcement is a genuinely good, low-friction signal — a pile of reactions is the digital equivalent of a round of applause, and watching the count tick up feels great. Custom emoji are even better; a team-specific :ship-it-parrot: on a launch carries more affection than any stock icon.
The failure mode is letting the emoji do all the work. A reaction says "I saw this." A written kudos says "I saw you." If a teammate pulled off something that actually mattered, the 🙌 react is the appetizer, not the meal. A decent personal rule: anything you'd mention in their performance review deserves a sentence, not just a symbol. (For the broader do's and don'ts — threads vs. channels, over-tagging, praise inflation — see our guide to Slack recognition etiquette.)
Public or Private? Read the Person, Then Default to Public
Public kudos do double duty: the recipient feels valued, and everyone watching learns what this team celebrates. That broadcast effect is why public recognition builds culture in a way DMs can't. So default to public — a shared channel, visible to the team.
But it's a default, not a law. Some people are genuinely mortified by public attention, and kudos that make someone squirm have failed at their one job. If you're unsure, ask once ("mind if I shout this out in the team channel?") and remember the answer. And some appreciation is simply private by nature — "thanks for talking me off the ledge before that meeting" belongs in a DM. The channel is for celebration; the DM is for gratitude. Teams need both.
From Ad-Hoc Praise to an Actual Habit
Everything above makes individual kudos better. The harder problem is consistency — because recognition that depends on people spontaneously remembering will always concentrate on the loudest projects and evaporate during crunch. A few structural moves change that:
1. Give kudos a home
A dedicated channel (#kudos, #props, #wins) beats scattering praise across project channels, because it creates a place people actually visit when they need a morale boost, and a visible norm that recognition happens here. Setting one up well is its own topic — we wrote a full walkthrough on building an employee recognition channel in Slack.
2. Attach kudos to existing rituals
Habits stick when they piggyback on things already happening. End sprint retros with two minutes of shout-outs. Add a "who helped you this week?" prompt to Friday updates. The prompt feels forced for exactly two weeks, and then it becomes the part of the meeting people would riot over losing.
3. Add a tiny bit of structure and stakes
This is where a lightweight tool earns its keep — and yes, full disclosure, Propsly is ours, so season accordingly. With Propsly, everyone gets 200 props points a month to give away with a quick /props command, every give lands in a public recognition feed, and leaderboards make generosity visible. The monthly allocation matters more than it sounds: because points are finite and reset monthly, giving them is a real choice rather than an infinite free resource, which quietly solves the praise-inflation problem. The free tier covers unlimited users, and setup takes about five minutes via our getting started guide. Tools don't create sincerity — that's still on you — but they remove every excuse between the sincere thought and the sent message.
The Forced Feeling Is a Fluency Problem
Here's the reframe worth leaving with: kudos feel forced when the giver is out of practice, not when the format is wrong. The first few specific, well-timed kudos you write will feel slightly awkward — like the first few times you do anything in public. By the tenth, you'll have a voice. By the thirtieth, teammates will have started copying your format, because good recognition is contagious in a way that "great job team!" never was.
So start embarrassingly small: one teammate, one specific thing they did this week, one sentence about why it mattered. Post it today, while the 48-hour clock is still running. That's the entire skill — everything else is repetition.