How long should a shout-out be?

One to three sentences is the right range for almost any channel. Shorter than that and you risk sounding glib; longer than that and the actual point gets buried in setup. The 'leadership philosophy' windup is what makes most shout-outs balloon past three sentences. Cut everything that is not the specific thing, the audience, and the name.

What's the difference between a shout-out and a thank-you note?

A thank-you note is private and complete. A shout-out is public and pointed. Both can be the right tool. The shout-out gets you peer-to-peer visibility and a culture signal about what kind of work gets noticed. The thank-you note gets you something the recipient keeps in a folder. Many situations call for both; few situations call for neither.

Where should I post a shout-out at work?

Match the channel to the work. A team-level contribution belongs in the team channel where the people who actually saw the work hang out. A cross-functional or company-wide contribution belongs in a wider channel, or in an all-hands moment. The most common mistake is overshooting and posting a small private win to a giant public room, which embarrasses the recipient and dilutes the message.

Is it weird to ask for a shout-out?

Asking for visibility on work you did is a normal professional skill, especially for people taught not to take up space. The honest move from the giver's side is to write the shout-out the way you would have if you had noticed, without pretending to have spontaneously come up with the praise. The person asked because they needed it, not because they wanted you to lie about how you arrived at it.

Can a shout-out backfire?

Yes, in three predictable ways. Bundling six people into one generic sentence; making the shout-out mostly about the writer's leadership philosophy; or arriving so late that it reads as a dutiful status report rather than a warm acknowledgment. Each of those is fixable by writing the smaller, sharper, faster version instead.

How do I write a shout-out for a whole team?

Either name two or three people inside the team with specific contributions, or post separate one-line shout-outs in the team channel over the course of a week. The 'shout-out to the whole operations team for crushing it' shape almost never lands because no one inside it can find their own face. For a real team-level moment, a group card where each member writes their own line works far better than one bundled sentence from a manager.

All articles

Workplace & Recognition

How to Write a Shout-Out That Actually Lands

Sarah Whitfield

May 27, 2026

The worst shout-out I ever watched happen was at an all-hands in a coworking space off Pike Street in early 2023. A VP read a slide that said "big shout-out to the operations team for crushing it this quarter" while the operations team sat in the back row checking their phones. None of them looked up. One of them, an analyst named Yusuf, told me afterward he had no idea what specifically had been crushed, who on the team had done what, or why this particular Tuesday was the day to say so. A shout-out is not the announcement that you appreciate someone. It is the specific thing they did, named in front of the right audience, while the moment is still warm. Most of them fail because they skip one of those three. The next five steps are how I have learned to not skip them.

Start a group card in 30 seconds

Free. No signup needed.

Jump to section6 sections

What a shout-out actually is

A shout-out is one to three sentences, said publicly, that names a specific thing one person (or a small named group) did, on a specific occasion, in front of the audience who would care about it. It is not a thank-you note, which is private. It is not a performance review, which is comprehensive. It is not a hype post, which is generic. The smallest possible shout-out is the most powerful kind: one sentence, one person, one verb, one beneficiary. Almost everything that goes wrong with shout-outs comes from inflating that sentence with adverbs and stretching it across too many recipients until no one inside it can find their own face.

I will say one inconvenient thing right at the start. Public shout-outs are not always the answer. Some of the best recognition I have ever seen was a manager forwarding one customer email to one engineer with three words above it. No audience, no platform, no badge. If your only reason to make it public is that you want credit for being the kind of leader who gives shout-outs, send the private version instead. The rest of this assumes you have actually picked the public format on purpose.

The five steps

This is the part the JSON-LD schema below mirrors exactly, so search engines can read it as a HowTo. The steps are not a checklist to follow once. They are five questions you answer in your head before you hit send.

Step 1: Name the specific thing they did

Not "great job". Not "crushing it". The specific verb on the specific noun. "You found the rounding bug in the invoice exporter that had been quietly billing two cents low on every order over a thousand dollars for the past nine months." That sentence could only be about one person. "Great job this sprint" could be about anyone in the building, which is the same as being about no one.

If you cannot name the thing, you do not have a shout-out yet. You have an instinct that someone deserves one. The fix is not to write a vaguer sentence. The fix is to go ask the person near them what actually happened, then write the sentence.

Step 2: Name who saw it or who it helped

This is the step most shout-outs skip and the one that turns the praise from social media into something with weight. "Saved the customer call with the team at Banfield on Friday afternoon" hits differently than "saved the customer call," because now the recipient knows their work was visible to a specific person, in a specific room, on a specific day. If the audience for the shout-out does not know who Banfield is, you can skip the name, but you cannot skip the principle.

The version of this that lands hardest is naming the person who would have been hurt if the work had not happened. "Saved our designer Marcus from having to redo a week of mocks" is more concrete than "saved a week of design work," because Marcus is now part of the story and Marcus is going to read it.

Step 3: Pick the right channel

An all-hands slide for a quiet act of weekend support is overkill and slightly embarrassing for the recipient. A buried Slack thread for a launch that took six people three months is under-kill and quietly insulting. The channel has to match the magnitude and the temperament of the recipient. Engineers I have worked with often prefer #team channels over LinkedIn; salespeople I have worked with often prefer the opposite. Ask, or guess based on what they have done before.

Three channels worth knowing: the relevant team channel (small audience, high specificity, fast), the company-wide all-hands moment (large audience, low specificity, slow), and a written note in the platform the recipient checks (the cross-cultural default, asynchronous, reviewable). Each works for different shout-outs. None works for all of them.

Step 4: Send it while the moment is still warm

A shout-out has a half-life of about a week. After that it reads as a thing you remembered to do, not a thing you actually noticed. The two-day shout-out is the strongest version. The same-day one risks looking reactive ("oh you saw the email"), the two-week one risks looking dutiful ("oh you remembered"), the two-day one looks like you sat with it long enough to mean it.

The cheapest tool I have for this is a Sunday-evening note in my calendar where I write one sentence about anything I noticed on my team that week. Two of those become Monday-morning shout-outs. The other three become private thank-yous, or they fade, which is also fine. Not every noticing has to turn into a public sentence.

Step 5: Sign it as you, not as the role

"On behalf of the leadership team, we want to recognize…" reads like a press release. "I sat in the Banfield call and watched Yusuf turn the room around by the third question. That was the work" reads like a person. Signing as the role telegraphs that the shout-out is institutional, which makes it suspect. Signing as yourself, with a first-person verb, makes it real. Even when you genuinely are speaking for the leadership team, the personal voice carries more weight than the corporate one.

Ten worked examples

These are model lines, not templates. Each one names a specific thing, an audience or beneficiary, and a channel that fits. Steal the structure, replace the nouns. The names below are placeholders for someone real on your team.

For a coworker, in the team channel

Marcus, that catch you made on the rounding bug in the invoice exporter on Wednesday saved us from a quarterly restatement. The whole finance team owes you a beer. Posting in #engineering so the rest of the room knows what you did, because I am sure you would never have told them yourself.
Big thanks to Devin for staying late on Thursday to walk the new hire through the deploy pipeline. The new hire shipped her first PR on Friday. That is not an accident. That is two hours of patience you did not need to give and did anyway.

For a direct report, in the company-wide channel

I want to call out Sana for the work she did on the new onboarding flow over the past three weeks. The drop-off between step one and step two used to be forty-two percent. As of this morning it is nineteen. She did the user interviews, wrote the spec, and made every push request review. The numbers are real and the work behind them was hers.
Posting here for the company so everyone knows: Ahmed kept our staging environment running through the entire data-center cutover last weekend without a single page going to the on-call team. He slept four hours on Saturday. The fact that the rest of us got to sleep eight is downstream of that.

For a peer, in front of your manager

Putting this in our team-leads channel because our director should see it. Priya talked me out of shipping a feature that would have looked good and broken a lot of things downstream. She did it kindly, on a Friday afternoon, when she could have just let me find out. I owe her one.

For a vendor or contractor

Tagging this so the agency sees it: Renata at Northbank Studio re-cut our hero video forty-eight hours ahead of the deadline because we changed the brief at the last minute. We did not pay for the rush. She did it because she said the brand deserved the better version. That is the standard.

For a junior team member

Quick shout-out to Tom, who started six weeks ago. He noticed in his second standup that nobody could explain why our retry logic had a fixed eight-second delay, so he went and read the original commit message from 2019, found out the answer (it was a workaround for an API that no longer exists), and quietly removed it. Six weeks in and he is already making the codebase smaller. That is the right instinct.

For someone outside your team who helped you

Posting in the all-hands channel: the design team's Ji-eun spent two of her own afternoons last week pairing with our PM on the new dashboard layout. Design did not own the project. She helped anyway. We are shipping a better thing because she did.

For a quiet contributor nobody notices

I want to name something most people on this team will not have seen. Our office coordinator Bea has, every Wednesday for the last seven months, set up the all-hands room so that the standing desk works, the audio works, the snacks are out, and nobody has to think about any of it. The reason these meetings feel easy is that she does the hard part beforehand. Thank you, Bea, said in front of everyone so it is on the record.

For a customer-facing win

Calling out Alex on support: yesterday a customer who had emailed us in real distress about losing access to her account got it back in eleven minutes. Alex caught the ticket, recognized that the standard playbook would not work, escalated through three channels in parallel, and fixed it. The customer's reply was "thank you, I was crying." That is the work.

The three failure modes (and how to skip them)

Most shout-outs that land flat fail in one of these three ways. None of them require new skills to avoid. They require choosing not to send the lazy version.

The bundle. "Huge thanks to the operations team for crushing it this quarter." Six people, four months, no verbs. Nobody on the operations team can find their own face in that sentence. The fix is to either name two or three of them with specific contributions, or post six separate one-line shout-outs in the team channel over a week. The bundle is what you write when you have not done the work of noticing what specifically happened.

The performance. A shout-out that is mostly about the writer. "As a leader, one of the things I care most about is recognizing excellence. That is why I want to highlight…" The recipient has been buried under three sentences of your leadership philosophy before they ever appear. Cut the windup. The shout-out starts at the name.

The late one nobody asked for. Praising someone in March for a thing they did in December reads as dutiful, not warm. The work has lived a whole quarter without the public sentence and survived. The sentence now arrives as a status report from HR. If the moment has passed, send it privately instead. The week-of shout-out is for the public version; the month-later one is for a one-on-one thank-you note.

The shout-out you write because someone asked for it

This is the case nobody talks about. A peer comes to you and says "can you say something in the next standup about what I did on the launch?" The instinct is to feel weird about it, like a real shout-out should be unsolicited. I used to think that too. I no longer do. Asking for visibility on work you did is a normal and healthy professional skill, especially for people who have been told all their lives not to take up space. If someone asks, they almost always deserve it and have already done the work of figuring out you would not have noticed without prompting.

What changes is how you write it. Do not pretend you came up with the praise on your own; that reads as patronizing. Just write it like you would have, if you had noticed. "Two weeks back, Sana shipped the onboarding redesign that has driven our step-one-to-step-two conversion from forty-two percent drop-off to nineteen. Calling that out here because the numbers deserve to be seen." The person who asked gets what they asked for, the audience gets the real thing, and nobody has to perform a fiction about how you spontaneously knew.

Turn it into a group shout-out card

Sometimes the right shout-out is not one sentence from you. It is twenty sentences, one from each member of the team, collected in one place. This is what a kudos board the whole team signs is actually for. The geometry is different from a Slack thread because the recipient gets to read every line in their own time, in one place, instead of scrolling through a channel with twenty other conversations interleaved.

The version I have seen work best is for the quiet leaving (someone moving roles, finishing a contract, retiring after eight years of unflashy work that nobody publicly named while it was happening). You can create a card online in a couple of minutes, send the link in the team channel, and let people add their lines whenever the moment hits them. There is more on the underlying habit in our piece on employee recognition ideas that actually work, and the broader rule about specificity in appreciation quotes worth stealing.

One last thing, off-topic and maybe just for me. The most useful shout-out I ever received was not at work. I was nineteen, working a summer job at a hardware store in a town I no longer live in, and the assistant manager, a woman named Linda who chewed Nicorette gum and never smiled at anything, walked past me one Saturday afternoon while I was helping a confused older customer find a specific size of toggle bolt. She did not say anything at the time. On Monday she pulled me aside, said "that was good with the bolt guy," and walked away. That was the whole shout-out. Three words and a noun. I have built a small piece of how I try to manage people on the back of it for going on twenty years now, and Linda has no idea. The specifics are what last. The volume does not.

Frequently asked questions

How long should a shout-out be?: One to three sentences is the right range for almost any channel. Shorter than that and you risk sounding glib; longer than that and the actual point gets buried in setup. The 'leadership philosophy' windup is what makes most shout-outs balloon past three sentences. Cut everything that is not the specific thing, the audience, and the name.
What's the difference between a shout-out and a thank-you note?: A thank-you note is private and complete. A shout-out is public and pointed. Both can be the right tool. The shout-out gets you peer-to-peer visibility and a culture signal about what kind of work gets noticed. The thank-you note gets you something the recipient keeps in a folder. Many situations call for both; few situations call for neither.
Where should I post a shout-out at work?: Match the channel to the work. A team-level contribution belongs in the team channel where the people who actually saw the work hang out. A cross-functional or company-wide contribution belongs in a wider channel, or in an all-hands moment. The most common mistake is overshooting and posting a small private win to a giant public room, which embarrasses the recipient and dilutes the message.
Is it weird to ask for a shout-out?: Asking for visibility on work you did is a normal professional skill, especially for people taught not to take up space. The honest move from the giver's side is to write the shout-out the way you would have if you had noticed, without pretending to have spontaneously come up with the praise. The person asked because they needed it, not because they wanted you to lie about how you arrived at it.
Can a shout-out backfire?: Yes, in three predictable ways. Bundling six people into one generic sentence; making the shout-out mostly about the writer's leadership philosophy; or arriving so late that it reads as a dutiful status report rather than a warm acknowledgment. Each of those is fixable by writing the smaller, sharper, faster version instead.
How do I write a shout-out for a whole team?: Either name two or three people inside the team with specific contributions, or post separate one-line shout-outs in the team channel over the course of a week. The 'shout-out to the whole operations team for crushing it' shape almost never lands because no one inside it can find their own face. For a real team-level moment, a group card where each member writes their own line works far better than one bundled sentence from a manager.