The best employee shout-out examples don't read like greeting cards. They read like something a real person typed into Slack at 4:47pm because a colleague did something great and they couldn't not say so.
A shout-out that lands has three parts: a specific act (not "great work," but "you rewrote the flaky test suite"), an impact (why anyone else should care), and an audience (it's said in front of people). Drop one and it's noise.
That's also what separates a shout-out from a thank-you note. A thank-you note is private; its job is gratitude. A shout-out is public; its job is to make the work visible to everyone else. For the private kind, see our employee thank-you messages, and if you're fuzzy on kudos vs. props vs. shout-out, here's what kudos actually means. Below are 75 of the public kind, grouped by situation.
A handful are written as /props commands, the syntax of our own Slack recognition bot, Propsly (yes, it's ours). The plain-English ones paste anywhere; the command shape is worth seeing because the amount and the hashtag force you to say what the recognition is for.
Shout-Outs for Shipping Something Big
- Shout-out to Priya for shipping the billing migration with zero downtime. The rollback plan she never needed was still the best doc I read this year.
/props @marcus +20 for getting the onboarding flow out a week early and writing the release notes himself #shipit- Huge one for Dana: the search rewrite is live and p95 latency dropped by half. Scary project; she owned every piece.
- Theo shipped the mobile redesign that's been "next quarter" since 2024. It's out, and it's good.
- Props to Lena for landing the SOC 2 evidence collection. Nobody wanted it and she treated it like it mattered.
- Ravi took the analytics dashboard from wireframe to customer-facing in six weeks without cutting the point.
- Shout-out to Jo for the pricing page launch. Copy, design, A/B setup, all hers.
/props @sam +15 for the API v2 launch and a migration guide that meant zero angry tickets #shipit
Shout-Outs for Unblocking a Teammate
- Kai spent his afternoon pairing with me on that flaky test instead of doing his own work. It's green now.
- Shout-out to Nadia for the "quick question" that became a 45-minute whiteboard session. I'd still be stuck without it.
/props @omar +10 for reviewing my PR within the hour every single time this sprint #teamwork- Ines noticed I was spinning on the deploy config and quietly sent a working example. Ten minutes of hers saved a day of mine.
- Big thanks to Wes for taking my on-call shift so I could make my kid's recital. No questions, just "go."
- Props to Yuki for writing the debugging runbook after walking me through the same issue twice. Now nobody has to ask.
- Shout-out to Dev for the 11pm reply that unblocked the release. Don't make a habit of it, but thank you.
- Mia got on a call with a stranger from another team to untangle my permissions problem. That's the good kind of "not my job."
Shout-Outs for Quiet Consistency and Invisible Work
- Shout-out to Carlos, who has triaged the support queue every morning for a year and never mentioned it. I checked. Every morning.
/props @grace +20 for keeping the CI pipeline green for six months straight, which nobody notices until it's gone #ownership- Props to Amara for the weekly status doc everyone reads and nobody thanks her for. Consider this the thanks.
- Ben has answered every question in #help-engineering since before I joined. He's why new people feel safe asking.
- Shout-out to Zoe for the invisible work: calendar juggling, agenda prep, follow-ups that actually get followed up.
- Tomás does the dependency upgrades nobody wants, on time, every month. That's why we're not stuck on 2023 versions.
- Props to Hana for the meeting notes. Yes, the meeting notes. Accurate, fast, and they've settled three arguments.
- Shout-out to Leo, who maintains tooling that saves each of us an hour a week and never asks for credit.
Shout-Outs for a New Hire's First Win
- Shout-out to Aisha for shipping her first PR in week two, and fixing a bug in the onboarding docs on the way.
/props @noah +10 for his first solo customer call, which the customer emailed about afterward #newhire- Props to Elena for presenting at sprint review in week three. Clear, calm, and she handled the hard question better than I would have.
- Welcome-and-well-done to Jonah, who fixed a race condition that's been lurking since before he joined.
- Shout-out to Sofia for asking the stand-up question half the room was too proud to ask. Keep doing that.
- Malik too: Priya is productive in week three because her onboarding buddy made asking for help easy.
- Props to Arjun for closing his first deal inside 30 days. Small deal, real customer, big milestone.
Shout-Outs for Cross-Team Collaboration
- Shout-out to Fatima in Marketing for sitting in on engineering planning so the launch copy matched what we actually built.
/props @luca +15 for translating "the customer is upset" into three specific bugs, then verifying every fix #teamwork- Props to Kenji in Finance for turning our vague "can we afford this" into a real model in a day, in plain English.
- Shout-out to Rosa in Support and Ivan in Product for writing the FAQ before launch instead of after. Ticket volume says thanks.
- Props to Sasha in Design for joining the backend sync every week, uninvited and extremely welcome.
- Shout-out to Tariq in Sales for sending engineering the recording of the demo that went sideways. Uncomfortable, and exactly what we needed.
- Props to Nina in Legal for turning the contract change around in an afternoon so the deal didn't slip past quarter-end.
Shout-Outs for a Customer Save
- Shout-out to Diego for staying on with a furious customer for 90 minutes and turning a cancellation into a renewal.
/props @maya +20 for catching the data export bug before the customer did, and calling them first #customerfirst- Props to Ola for rebuilding a customer's broken integration on a Friday afternoon when it wasn't even our fault.
- Shout-out to Femi for the apology email to the enterprise account. Honest, specific, no weasel words. They wrote back to say thanks.
- Big one for Chloe: she spotted a churn signal in the usage data, reached out, and the account is now expanding.
- Props to Andre for turning a 40-message support thread into one clear bug report. The fix took ten minutes because of it.
- Shout-out to Isla for walking a customer through the migration on a screen share instead of sending the doc. They'll remember that.
Shout-Outs for Handling a Crisis or Incident
/props @maria +20 for staying on the incident bridge until 2am and writing the postmortem before anyone asked #ownership- Shout-out to Ezra for being the calm voice in the incident channel on Saturday. Clear updates every 15 minutes, no blame, no panic.
- Props to Lucia for spotting that the outage was DNS (it's always DNS) twenty minutes before the rest of us.
- Big thanks to Hugo for handling customer comms during the outage so the engineers could actually fix it.
- Shout-out to Bea for the postmortem that named the process failure instead of a person. That's how we get better.
- Props to Kwame for running the incident retro and making it useful instead of a blame session.
- Shout-out to Ana for status page updates that were honest about what we didn't know yet. Customers noticed.
Shout-Outs for Leadership From a Non-Manager
- Shout-out to Mateo for running the architecture review nobody scheduled. He saw the drift and got us aligned in an hour.
/props @june +15 for mentoring two interns on top of a full workload, and both of them shipped #leadership- Props to Ravi for pushing back on the deadline with data instead of complaints, and for being right.
- Shout-out to Tessa for starting the Friday demo ritual. Nobody asked her to. It's now our best meeting.
- Props to Sam for saying "I think we're solving the wrong problem" in planning. He was right, and it saved a month.
- Shout-out to Ade for writing the coding standards doc, then actually getting everyone to agree to it.
- Props to Vera for noticing a teammate was drowning and quietly redistributing work before it became a crisis.
- Shout-out to Ilya for the hiring loop overhaul. Better questions, faster decisions, and candidates keep saying it felt respectful.
Shout-Outs for Managers to Give
- Shout-out to the whole platform team for a quarter with zero missed commitments. That doesn't happen by accident.
/props @chen +20 for taking the project I asked her to own and turning it into something better than I'd scoped #ownership- Props to Nadia for the feedback she gave me last week. Direct, fair, and I changed the plan because of it.
- Shout-out to Marcus for leading the retro while I was out. I read the notes. Better than mine.
- Props to Aisha for the growth over six months. Same title, completely different scope, and she earned every bit of it.
- Shout-out to Leo for the 1:1 where he told me what the team needed instead of what I wanted to hear.
- Props to Dana for representing the team in the exec review with more clarity than I manage.
One-Liners for Stand-Ups
- Shout-out to Kai for the fastest code review of my career.
- Props to Ines for the test coverage bump. We're above 80% now.
- Quick one for Hugo: yesterday's demo was flawless.
- Shout-out to Zoe for catching the pricing page typo before it went live.
/props @wes +5 for the deploy that just worked #shipit- Props to Femi for the customer quote in Friday's recap. Nice find.
- Shout-out to Tomás for the bug fix that closed three tickets at once.
- Props to Elena for making the sprint board finally match reality.
Where to Post a Shout-Out (and When)
A feed channel like #wins or #props is the default home for nearly everything above. It's public, ambient, and searchable, so the shout-out still exists at review time. If you don't have one, our guide to setting up a recognition channel in Slack covers naming and norms.
A DM is right when the thing was personal, when the person genuinely hates the spotlight, or when the context involves someone else's mistake. That's really a thank-you note, and that's fine.
Stand-up is for the one-liners. Ten seconds, one name, one specific thing. The ritual matters more than the eloquence.
The company newsletter is for the monthly best-of: the customer save, the big ship, the crisis handled well. Don't write these fresh. Scroll the feed channel, pick the three that made you nod, and paste them with attribution.
Three Mistakes That Make Shout-Outs Fall Flat
Vague praise. "Great job, team!" names nobody, describes nothing, and lands on no one. If you can't say what someone did, you haven't noticed it yet.
Only praising output, never effort. Ships get shout-outs. The person who kept CI green for six months gets nothing, because a thing that didn't break isn't an event. If your last twenty shout-outs were launches, the next five should be maintenance, support, and documentation.
The same three people every time. Recognition drifts toward visible work and loud channels, and everyone else quietly concludes the program isn't for them. Before you post, ask who hasn't been named this month. The patterns and the remedies are in fixing recognition inequality.
Making It a Weekly Habit
Examples last about a month. After that, structure keeps shout-outs flowing, and two mechanics do most of the work.
A giving streak: consecutive weeks in which you recognized someone. Streaks aren't zero-sum, so the whole team can be winning at once. Propsly celebrates them at 4, 8, 12, 26, and 52 weeks; more on why that beats leaderboards alone in our guide to Slack gamification.
A monthly points budget: everyone gets a fixed number of points to give away (200 a month on our free tier), and they reset on the first. Use-it-or-lose-it turns "I should really say something" into "I have 140 props left and it's the 28th." Giving kudos in Slack is easy; the budget is what makes people do it.
Both matter because peer shout-outs catch what managers miss. Gallup puts about 70% of the variance in team engagement on the manager, which is exactly why peer recognition beats top-down appreciation: one person can't see everything, but thirty people can. And employees who feel inadequately recognized are about twice as likely to say they'll quit within a year (Gallup/Workhuman).
Pick five from the list, change the names, and post them this week. For longer messages, our peer recognition message examples go deeper; for program design, start with these employee recognition examples. But the hard part was never the words. It's noticing, and saying it out loud.