What is an employee spotlight, exactly?

A piece of recognition that names one employee, names something specific they did, and is sent or posted to an audience the employee actually inhabits. It is shorter than a performance review and more public than a private thank-you note. The format can be a Slack post, a group card, a forwarded customer email, an all-hands mention, or a printed certificate. The shape matters less than whether the post names a real thing the employee did.

How often should we run employee spotlights?

More frequent and smaller is usually better than less frequent and larger. A weekly Friday spotlight in a team channel outperforms a monthly company-wide one in almost every case we have watched. The exception is genuine company-level news such as a big launch or a major customer save, which deserves a slower and larger format. The trap is using the company-wide cadence for work that belongs in a team channel, because the specificity gets sanded off by the time it reaches a large audience.

Some of our best people hate public recognition. What do we do?

Ask them, privately, and believe them when they tell you. The version that works for these employees is private and specific and stays private. A note in their inbox, a forwarded customer email, a line in their 1:1 with a manager-once-removed. If a public version is unavoidable for paperwork reasons such as a promotion announcement, keep it to two factual sentences and put the real recognition in the private message that goes alongside it.

Are employee-of-the-month programs worth running?

Usually not in the classic shape. Monthly cadence is too slow to connect to actual behavior, the zero-sum framing makes everybody else feel passed over, and the top-down selection only measures what managers happened to see. A weekly or ad-hoc peer-spotlight system tends to outperform employee-of-the-month on every measure we have been able to track. If you have one already, the smaller move is to add peer nominations and a same-week cadence rather than scrap the whole program.

Should the employee be told before the spotlight goes out?

For anything bigger than a one-line Slack post, yes. Show them the draft. Check that the dates are right, that the people they want named are named, and that the photo is one they approve of. A five-minute heads-up prevents the situation where a post goes live with the dates wrong or the wrong project credited, which leaves the employee doing internal-explanation work for the rest of the week.

What is the single most overused phrase in employee spotlights?

Rockstar, with ninja a close second. Both signal that the writer reached for vocabulary instead of for specifics. The fix is to name a thing the rockstar or the ninja actually did, in plain words, and then notice that you no longer needed the rockstar word. Going above and beyond, true team player, and always willing to lend a hand are next on the list, for the same reason.

All articles

Workplace & Recognition

Employee Spotlight Ideas (That Actually Land)

Emily Hartwell

May 27, 2026

The first employee spotlight I ever ran was a Notion doc called Monthly Standouts. We started it in February 2022 at a company in Oakland, fifty-something people, mostly remote, hybrid mid-week. The idea was that on the first Monday of every month, two or three team leads would write a paragraph about someone on their team. The paragraph would get linked in the all-hands deck and then everyone would clap in their Zoom squares for about four seconds. By June the spotlights had become a thing a designer named Hana told me, kindly, over coffee at a place on Grand Avenue, made her wish she had not been on the receiving end of one in April. The April one for her was three paragraphs long, written by somebody two layers up who had read her launch retrospective and gotten the dates wrong. The Slack reactions to it included a single sparkle emoji from the CEO and twenty-eight nothing-at-all from the rest of the team. She did not tell me to stop running them. She just said, lightly, that maybe a quieter version would have worked better for her. I did not stop running them. I should have changed the shape. The rest of this is what I would tell a younger version of myself before that April.

Start a group card in 30 seconds

Free. No signup needed.

Jump to section8 sections

The default employee spotlight is a drawer of small failures

The shape almost every company defaults to looks like this. Someone, usually a manager or a People-team person, writes a hundred-word blurb about a chosen employee. The blurb goes out on a regular cadence, monthly or weekly. It uses the word rockstar at least once. It mentions hard work, dedication, and going above and beyond. It includes a photo the employee did not have time to approve. It runs in a channel where most readers scroll past it, react with a single low-effort emoji, and forget the name by Thursday.

The employee who was spotlighted reads it, smiles politely, screenshots it for their partner or their mom, and then files it in a mental folder that fills up with similar pieces of well-meaning company stationery. Inside that folder the spotlights accumulate. None of them name the specific work. None of them name the people who were actually helped. None of them sit on the channel the employee checks. Six months later the employee leaves for another job, and on the way out cleans the folder without rereading any of it. I once did exactly that with my own folder when I left a job in 2019. I read maybe two of the dozen-odd spotlight posts before recycling the rest.

One commercial disclosure up front. RecoCards is a group-card platform, and the back half of this article points at our product as a way to turn a manager-driven spotlight into a team-driven one. The ten idea shapes in the middle do not depend on the platform. Paste them into a Notion doc, a Slack post, a printed certificate, or a hand-written note. The product pitch is at the bottom and clearly labeled.

What actually makes a spotlight land

Three things, in this order. Specificity, audience-fit, channel-fit. If a spotlight gets any one of these wrong, it produces the smile-and-file response. If it gets all three right, the recipient remembers it years later, sometimes in detail the writer would not have predicted.

Specificity means the spotlight names exactly what happened. Not the person's general qualities. Not their work ethic. Not their growth this year. The Tuesday email they wrote that closed a stalled deal. The bug they found in the analytics pipeline that had been silently halving our retention numbers since last August. The Slack message they sent at 7pm to talk a teammate out of shipping the version with the broken edge case. If you cannot write a single sentence that names the specific thing, the spotlight is not ready yet. You have an instinct that the person deserves attention. You have not done the noticing.

Audience-fit means the spotlight is written for the people who would actually care. The company-wide all-hands audience does not care that the analytics fix was elegant; the engineering team and the analytics consumer care. The customer the support rep saved does not show up in the engineering channel; she shows up in the support channel and to the rep's manager. Some spotlights deserve the whole company. Most deserve a smaller room. Sending every spotlight to the largest possible room is what makes the recognition cheap.

Channel-fit means the format matches both the work and the recipient. A printed certificate in a Slack-first company reads as ironic. A buried Slack post for a launch the whole company watched reads as undershooting. A LinkedIn shout-out for an engineer who hates LinkedIn is a small punishment dressed up as praise. The honest move is to ask the recipient, in advance and in private, where they want a spotlight to live. If you cannot ask without telegraphing it, guess based on the channels the person voluntarily participates in.

One honest concession before the ideas

Some employees actively dislike being spotlighted in public. They are not being modest, they are not fishing for the manager to insist, they are telling you the truth. Hana told me later that the April spotlight had made her week worse, not better. She had a customer call the next morning where the customer had read the post and asked a question about a project the post had named, and she had to explain that the post had the dates wrong. The spotlight had cost her thirty minutes of customer-explanation work and zero internal credibility. It would have helped to ask her first.

The fix here is not to skip the recognition. It is to deliver it in a shape the person can absorb. A private note from the manager. A forwarded customer email to her inbox. A line in her next 1:1 with the CEO with no audience attached. There is a section below specifically on the introvert exception, because it is the single most common shape this article gets wrong in practice. For the broader habit of catching this earlier, our piece on employee recognition ideas that actually work covers the related question of why peer recognition usually outperforms top-down recognition.

Ten employee spotlight ideas, organized by trigger

These are shapes, not templates. Each one names a trigger (the moment that justifies the spotlight), a format (what the spotlight actually is, mechanically), and an audience (who reads it). Pick the one that matches the work you noticed. Resist the urge to use the same shape for every spotlight you do, because the format itself signals what the company values, and using one format for everything signals that you have not actually been paying attention.

1. The post-launch spotlight (named contributors, not the team)

The trigger is a project shipping. The failure mode is the bundle: "huge thanks to the launch team for crushing it." Six people, four months, no verbs, no faces. The fix is a spotlight that names two or three specific people inside the team and what each of them did. Audience is the company-wide channel, because launches are company-level news. Format is a single post with a paragraph per named contributor, written by the project lead and not by the People team. Length: one paragraph each, ideally with the bug they squashed or the call they took. Read out at the next all-hands only if the named people opted in.

2. The quiet-stretch spotlight (for work between launches)

The trigger is the absence of a launch. Most of the year is the stretch between visible shipping moments, and most spotlights ignore this entirely, which is why the people doing the steady maintenance work feel invisible. The format is a Friday Slack post in the relevant team channel, written by the manager, naming one specific thing the person did this week that nobody publicly noticed. Three sentences, no formatting, sent at 4pm on Friday so it sits at the top of the channel through the weekend. Audience is the team itself. The point is not company-wide visibility. The point is internal acknowledgment that the maintenance work is the work.

3. The customer-saved spotlight (forward the actual email)

The trigger is a customer email that says, in their own words, that an employee made a difference. The format is to forward the customer email, with the customer's identifying details optionally redacted, to the audience that would care, with three lines of context above it. The three lines name the employee, the situation, and the specific behavior the email is praising. The audience is usually the support or success channel, or the relevant team. Format note: do not paraphrase the customer's words. The customer wrote a better sentence than you would have. Use theirs.

4. The cross-functional spotlight (in the helper's channel, not yours)

The trigger is somebody from another team helping yours. Designer who fixed your dashboard, ops person who unblocked your release, finance partner who got the contract through. The instinct is to thank them in your own team's channel, where the people who would care about this kind of internal credibility cannot see it. The fix is to post the spotlight in the helper's channel, where their teammates and manager will see it. Tag the helper's manager directly. Two sentences. Specific.

5. The under-noticed spotlight (the person nobody else would have written)

The trigger is your own observation that somebody has been quietly carrying work for a while and is not on anybody's radar for a more obvious spotlight. The format is a longer note, written by you personally, sent on a Wednesday morning to a small audience. Maybe the team. Maybe the team plus their manager. Maybe just their manager, if a public version would embarrass them. Length is whatever it needs to be. Specificity is non-negotiable. This is the spotlight most likely to land hard, because the recipient has been waiting for somebody to notice for months and had stopped expecting it.

6. The contractor spotlight (do it before they leave)

The trigger is a contractor or freelancer doing work that an employee would have been spotlighted for. The failure mode is treating contractors as invisible labor and only thanking them in the offboarding email after they are already gone. The fix is to spotlight them in the same channel and the same format you would use for an employee, while the contract is still active. The audience is your team and the contractor's manager at their agency, if applicable. A two-line public spotlight from a client lead to a freelancer's agency manager can change that freelancer's career trajectory. Costs you ninety seconds.

7. The hard-quarter spotlight (after the quarter, not during)

The trigger is a quarter that nearly broke the team. Layoffs in the room next door. A reorg. A product launch that doubled the load for ten weeks. Spotlights run during a hard quarter often read as hollow, because the team is too tired to absorb them. The fix is to wait until the dust settles, then write longer paragraphs naming what each person carried. The audience is the team itself. The format is a Notion doc or a posted-once-and-pinned Slack post, not an all-hands moment. The all-hands moment for a hard quarter belongs to the leader who got the team through it, not to the team that needs the rest.

8. The peer-to-peer spotlight (with explicit permission to forward)

The trigger is somebody on the team noticing somebody else. The format is the most underrated shape in the entire genre. A team member writes a paragraph in a peer-spotlight channel, tagging another team member. The original poster has explicit permission to forward the spotlight to the tagged person's manager. The audience is initially small (the team) but the forwarded version reaches the manager. The peer voice is harder to fake than the manager voice. The forwarded version reaches the right ear without going through the leadership-validation theatre.

9. The anniversary spotlight (a real one, not a Workday auto-message)

The trigger is somebody hitting a work anniversary, especially the years that nobody celebrates with a card (year three, year seven, year twelve). The default Workday-generated anniversary message lands in nobody's heart. The fix is a brief note that names something specific from the past year of the person's work, not their whole tenure. Audience is the person's team, plus their manager's manager. If you have run the company for the entire stretch, name the moment three years ago that the team would not have survived without them. Use the moment, not the year count, as the spotlight's center. Worth reading next to the dedicated piece on work anniversary messages, since the shape is adjacent.

10. The send-them-off spotlight (write it before they leave, not after)

The trigger is somebody resigning, retiring, or moving on. The failure mode is the LinkedIn-post farewell where their old manager writes a generic tribute to a person they have not worked closely with for two years. The fix is a private group card from the people who actually worked alongside them, written in the last week, where each contributor writes one specific moment they remember. Audience is the leaving employee, full stop. This is the closest the genre gets to a portrait. Done right, it is the spotlight the recipient keeps. Done in the manager-eulogy shape, it is the spotlight they delete from their inbox in a year.

The introvert exception (and how to make it land anyway)

Some of your strongest contributors will hate every shape above. They will appreciate the noticing and dread the audience. Hana is not the only one I remember. There is also the engineer who told me, with apologetic body language, that the company-wide birthday Slack thread for her last year had made her not want to come into the office for two days. There is the salesperson whose biggest deal of the year landed during a personal-loss quarter she had not made public, and a generic well-done spotlight would have rubbed salt where there was already a wound.

The version that works for these people is private and specific and stays private. A note in their inbox. A line in their 1:1 from the manager or, better, from the manager's manager. A forwarded customer email with two lines of context. A reference in a recommendation letter six months later that quotes the specific work. If you absolutely need a public spotlight (compensation paperwork, promotion announcement, board update), keep the public version to two sentences of factual content and put the real recognition in the private message that goes alongside it. The principle is the same as the broader rule on workplace gratitude: a specific sentence in the right ear beats a generic paragraph in the wrong room. The dedicated treatment of one of these shapes is in our piece on how to write a shout-out that actually lands, which goes deeper on the channel question.

What to skip on every spotlight

Some phrases and shapes have been on enough recognition posts that they signal the writer did not look closely. Skip them. The phrase rockstar is the canonical one, and ninja is its slightly later cousin. "Going above and beyond" without naming what above and what beyond. "A true team player" with no team named. "Always willing to lend a helping hand" when the helping hand showed up at 11pm on a Thursday and the post does not mention the Thursday. Photos taken at the company offsite where the employee is mid-bite or mid-laugh and clearly did not approve the shot. The corporate brand-template graphic with the employee's name dropped in a font two sizes too large.

One more pattern to skip. Spotlights that are mostly about the writer. The opening sentence that begins with "as a leader, I believe in the power of recognizing excellence" has buried the recipient under three sentences of leadership philosophy before they appear by name. The post starts at the employee. If you cannot make the post about the employee from the first word, you are not ready to write it, and the post that runs anyway will land as theatre.

The channel question (Slack vs all-hands vs printed vs group card)

The channel is half the spotlight. The four most common channels each work for different shapes, and using the wrong channel for the right work undoes the work.

Slack (or your team chat) is fast, low-formality, high-frequency. Good for the customer-email forward, the cross-functional thank-you, the quiet-stretch acknowledgment. Bad for the under-noticed spotlight that has been waiting six months for visibility, because the Slack post will be gone from the channel by Friday afternoon.

All-hands is high-formality, low-frequency, large audience. Good for genuine company-level news (the launch, the new patent, the customer save that changed the quarter). Bad for individual maintenance work, because the audience is too large and the specificity gets sanded off by the time it reaches the back row of the Zoom grid. Also bad for the introvert exception. The all-hands version of an introvert's spotlight is a slow walk through Slack DMs for the rest of the week.

Printed certificates are slow, physical, archival. Good for milestones that the person will want to keep. A first major sale, a long-stretch retirement, a board-level recognition. Bad for anything weekly or monthly, because printing weekly certificates produces a wall of paper that nobody looks at after week four. The single best printed certificate I once saw was a one-line hand-written note framed in a thrift-store frame, given by a CEO to an engineer who had stayed seven years. The frame was forty dollars. The framing was the spotlight.

A group card sits between Slack speed and printed permanence. Multiple voices, one collected place, asynchronous contribution, durable artifact. Good for send-offs, big milestones, hard-quarter wraps, and the under-noticed spotlight where the manager's voice alone is not enough. Bad for fast acknowledgment of a quick win, because the collection-and-delivery cycle takes longer than the moment.

Turn the spotlight into a card the team signs

The manager-written spotlight is one voice. A spotlight where ten teammates each write one specific line is ten voices. The geometry of that shift is the whole point of using a group card for recognition: the recipient gets to read what each colleague actually noticed about them, in their own words, in one place, on their own time. The bigger the moment (a send-off, an anniversary you actually want to mark, a hard-quarter wrap), the more the multi-voice version outperforms the solo one.

A kudos board the whole team signs is the format that fits most of these cases. One link, dropped in the team channel, and each person adds their own line. Hybrid teams, remote teams, teams in three time zones. You can create a card online in a couple of minutes, set delivery for the morning of the day you want the spotlight to land, and let people contribute on their own time instead of crowding around a clipboard between meetings. If the spotlight is for a send-off, the group card with multiple signatures format is more natural. For the seed lines you might want under any of these, the thank-you messages for your team bank covers most adjacent shapes, and the administrative professionals day messages piece is adjacent in register for any spotlight aimed at the people whose work usually goes unseen.

Seed the card with one specific opening line before sharing the link. The first signer's tone sets the register. If the first line reads "thanks for all you do", the next twelve signers will paraphrase that. If the first line reads "the Tuesday in October when you stayed on the customer call until midnight", the next twelve will reach for their own specific moments. The card lands or fails on the first sentence as much as on the cover photo.

One last thing, off-topic and probably just for me. Hana left the company in late 2022 for a smaller place where, she told me later over a different coffee at a different cafe in Berkeley, the recognition was almost invisible from the outside but landed for her in a way the Notion-doc spotlights never did. Her new manager, on her second Friday, walked over to her desk, said "the way you handled the customer call this morning saved us", and walked away. That was the whole spotlight. One sentence, one moment, no audience, no emoji. She told me about it three months later and was still bringing it up. I have built some of how I try to recognize people on the back of that conversation, and the lesson I keep coming back to is that the spotlight that lands is almost never the loudest one in the room. It is the one that arrived at the right ear on a specific Tuesday with the specific thing named. That is a much harder thing to systematize than a monthly Notion doc. It is also the only kind of spotlight worth running.

Frequently asked questions

What is an employee spotlight, exactly?: A piece of recognition that names one employee, names something specific they did, and is sent or posted to an audience the employee actually inhabits. It is shorter than a performance review and more public than a private thank-you note. The format can be a Slack post, a group card, a forwarded customer email, an all-hands mention, or a printed certificate. The shape matters less than whether the post names a real thing the employee did.
How often should we run employee spotlights?: More frequent and smaller is usually better than less frequent and larger. A weekly Friday spotlight in a team channel outperforms a monthly company-wide one in almost every case we have watched. The exception is genuine company-level news such as a big launch or a major customer save, which deserves a slower and larger format. The trap is using the company-wide cadence for work that belongs in a team channel, because the specificity gets sanded off by the time it reaches a large audience.
Some of our best people hate public recognition. What do we do?: Ask them, privately, and believe them when they tell you. The version that works for these employees is private and specific and stays private. A note in their inbox, a forwarded customer email, a line in their 1:1 with a manager-once-removed. If a public version is unavoidable for paperwork reasons such as a promotion announcement, keep it to two factual sentences and put the real recognition in the private message that goes alongside it.
Are employee-of-the-month programs worth running?: Usually not in the classic shape. Monthly cadence is too slow to connect to actual behavior, the zero-sum framing makes everybody else feel passed over, and the top-down selection only measures what managers happened to see. A weekly or ad-hoc peer-spotlight system tends to outperform employee-of-the-month on every measure we have been able to track. If you have one already, the smaller move is to add peer nominations and a same-week cadence rather than scrap the whole program.
Should the employee be told before the spotlight goes out?: For anything bigger than a one-line Slack post, yes. Show them the draft. Check that the dates are right, that the people they want named are named, and that the photo is one they approve of. A five-minute heads-up prevents the situation where a post goes live with the dates wrong or the wrong project credited, which leaves the employee doing internal-explanation work for the rest of the week.
What is the single most overused phrase in employee spotlights?: Rockstar, with ninja a close second. Both signal that the writer reached for vocabulary instead of for specifics. The fix is to name a thing the rockstar or the ninja actually did, in plain words, and then notice that you no longer needed the rockstar word. Going above and beyond, true team player, and always willing to lend a hand are next on the list, for the same reason.