Every Slack workspace has unwritten rules. Nobody documents when it's okay to use @channel, but everyone knows. Recognition works the same way: the difference between a kudos channel people love and one they quietly mute comes down to norms nobody wrote down. So let's write them down. This is our guide to Slack recognition etiquette — the do's and don'ts that keep peer recognition genuine, inclusive, and worth the notification.
Why does etiquette matter this much? Because recognition only works when people believe it. 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 — but that hinges on the word adequately. Hollow, performative, or cliquish shout-outs don't count as recognition in anyone's brain; they count as noise. Good etiquette is what keeps the signal strong.
The Do's
Do: Be specific — name the action and the impact
"Great job, Priya! 🎉" is a nice gesture. "Priya rewrote the onboarding docs over two days and the new hire went from zero to first deploy in one afternoon" is recognition. The formula is simple: what they did + why it mattered. Specificity does three jobs at once — it proves you actually noticed, it tells Priya exactly which behavior to keep doing, and it teaches everyone reading the channel what excellence looks like on your team.
A useful self-test: could your message be copy-pasted onto anyone else on the team? If yes, it's not specific enough yet. If you want a stockpile of before-and-after rewrites, we've collected dozens in our peer recognition message examples.
Do: Praise in public, correct in private
The oldest rule in the management book, and Slack makes it easier to break than ever. Praise belongs in the open — the public channel, the recognition feed, the place where the person's peers and manager will see it. Criticism, correction, and "hey, quick feedback" belong in a DM or a 1:1, full stop.
The sneaky violation isn't public criticism — most people know better. It's the backhanded public compliment: "Huge props to Marcus for finally getting the release out 😅" or "Kudos to the API team for fixing the bug they shipped last week." If a shout-out contains a barb, an inside joke at the recipient's expense, or the word "finally," delete it and start over. Recognition with an asterisk is worse than none.
Do: Recognize the work nobody sees
Left alone, Slack recognition drifts toward the visible: launches, demos, big numbers. But the teammate who spent Thursday untangling a flaky CI pipeline, the one who onboarded two new hires between meetings, the one who wrote up the incident postmortem at 9pm — that's the glue work that keeps teams running, and it's chronically under-thanked. Make a habit of scanning for it. Bonus etiquette points for recognizing people outside your immediate team; cross-team props do more for collaboration than most offsites.
Do: Keep it timely
Recognition has a half-life. Props given the same day land with full force; props given three weeks later in a monthly roundup feel like an accounting exercise. When you see something great, say something great — it takes thirty seconds. This is exactly why recognition works better in Slack than in quarterly review cycles, a case we make at length in our guide to giving kudos in Slack.
Do: Receive recognition gracefully
Etiquette runs both ways. When someone recognizes you publicly, the move is a simple thank-you — an emoji reaction, a "thanks, that means a lot," a redirect of credit to collaborators who helped. What kills recognition culture from the receiving end: arguing with the praise ("oh, it was nothing, honestly the code is a mess"), or worse, ignoring it entirely. Deflecting a compliment feels humble; to the person who gave it, it reads as a returned gift.
The Don'ts
Don't: Pad your streak
Any recognition system with points, streaks, or leaderboards will tempt someone to game it — the 11:58pm "props to the whole team for being awesome!" that exists purely to keep a streak alive, or the end-of-month burst of generic kudos to empty a points balance. Everyone can tell. Streak-padding is the recognition equivalent of watering down the coffee: one person does it and the whole pot tastes worse, because now every shout-out carries a whisper of did they mean this, or did they need this? If you don't have anything genuine to give this week, give nothing. Silence is honest; filler is corrosive.
Don't: Be a reply-guy kudos-giver
You've seen it: someone posts a thoughtful, specific shout-out for Dana's work on the migration, and within minutes three people pile into the thread with "+1!" "Dana's the best!!" "so true 🙌". Reactions and thread replies are lovely — genuinely, pile on the emoji. The etiquette foul is when piggy-backing replaces original recognition: the person who never initiates a shout-out but reliably appears in every thread, harvesting visibility from other people's gratitude. If you agree Dana crushed it, the strongest move isn't a reply — it's your own recognition, with the specific thing you saw that the first person missed.
Don't: Turn recognition into a transaction
Recognition-for-recognition is the fastest way to hollow out a program. That means no "I'll props you if you props me" pacts, no recognizing your work best-friend every single week regardless of what happened, and — managers, this one's for you — no using kudos as a soft instruction ("Big thanks to Jordan for staying late to hit the deadline! 😊" reads to everyone else as staying late is expected now). Recognize outcomes and behaviors you'd genuinely want repeated, not favors you want returned.
Don't: Let recognition become a clique
Watch who gets recognized on your team for a month and you'll usually find a pattern: the same handful of names, typically the loudest, most central, most manager-visible people. That's rarely malice — it's proximity bias — but the effect is exclusionary all the same. The people who never appear in the feed notice, and what they learn is that the recognition system isn't for them. This is worth actively auditing, not just vibing: distribution data will show you gaps that memory won't. We dig into the fix in recognition without playing favorites.
Don't: Weaponize the leaderboard
Leaderboards are great for celebrating generosity — who gives the most recognition — and dangerous when treated as a performance ranking. The moment a manager cites props counts in a review, or a team starts side-eyeing whoever is "behind," recognition stops being a gift and becomes a metric to hit. Keep leaderboards playful and public-facing, keep performance conversations separate, and never, ever punish someone for a quiet month.
A 30-Second Etiquette Checklist
Before you hit enter on a shout-out, run the quick scan:
- Specific? Names the action and the impact, not just the vibe.
- Genuine? You'd say it to their face, unprompted, with no streak on the line.
- Clean? No barbs, no "finally," no inside jokes at their expense.
- Timely? Days, not weeks, after the thing happened.
- Yours? Original recognition, not a piggy-back on someone else's.
Five yeses and you're clear to post. Confetti away.
Do Norms Need a Tool?
Honestly? The norms matter more than the software — a team with great etiquette and a bare #kudos channel beats a team with fancy tooling and hollow habits. But the right tool makes the etiquette easier to keep. This is where we disclose our bias: Propsly is ours, and we built it around exactly these norms. The /props command requires a hashtag, which nudges every give toward naming what the recognition is for. A monthly allocation of 200 props per user makes each one feel spent rather than sprayed, which quietly discourages filler. Every give lands in a public recognition feed — praise in public, by default. And the free tier covers unlimited users, so nobody is excluded by a seat count.
The etiquette still has to come from your team. But if you want rails that make the good habits the easy habits, getting started takes about five minutes and one Slack install.
Write the Rules Down (Gently)
One last move separates teams where recognition thrives from teams where it fizzles: they make the norms explicit. Not a policy document — a pinned message. Three do's, three don'ts, a couple of great example shout-outs from your own history, posted in the channel where recognition happens. New hires absorb it in ninety seconds, and when someone drifts into streak-padding or backhanded kudos, there's a friendly artifact to point at instead of an awkward conversation.
Recognition etiquette isn't about being precious. It's about protecting something genuinely valuable: a team where people notice each other's work out loud. Companies with strong recognition cultures see up to 31% lower voluntary turnover, per Deloitte's research — but "strong" was never about volume. It was always about people meaning it.