Every peer recognition program has the same lifecycle if you leave it alone: a loud launch, a busy first quarter, then a slow slide into the same four people thanking each other for the same three things. Employee recognition themes are the cheapest fix we know of. A theme is just a monthly prompt — "this month, notice this" — but it changes who gets recognized and what for, which is the whole game.
This is a program-level playbook: one theme per month, each with a hashtag, an audience, a sample shout-out, and a tracking note. Looking for a five-day event instead? See our employee appreciation week themes. This post is about the other 47 weeks.
Why Recognition Themes Work
Two reasons, both about attention rather than motivation.
Themes point the spotlight at work that otherwise goes dark. Left alone, recognition clusters around visible wins: the launch, the big deal, the demo that got applause. The person who kept CI green or answered forty questions in #help gets nothing, because nobody was told to look there. A theme tells them to look there.
Themes give people a sentence when they can't think of one. The most common reason someone doesn't give recognition isn't apathy — it's a blank text box. "Who helped another team this month?" has an answer. "Who deserves props?" gets a shrug.
The mechanics are simple, and worth repeating every month:
- Announce the theme on the 1st, in the channel where recognition already lives, with the hashtag and two sentences on what counts.
- Give it a hashtag. One word, lowercase, no ambiguity. It's how you find the posts later.
- Track it. Count the gives carrying the tag. Zero on the 15th? Re-announce with an example.
- Celebrate a winner at month end. Whoever received the most tagged recognition gets named publicly — and, if there's budget, something small. Announce next month's theme in the same post.
12 Monthly Employee Recognition Themes
The calendar below is a suggestion, not a law — if your busiest incident season is January, move "Calm Under Fire" there. What matters is that each month has exactly one theme and everybody knows it.
January — Fresh Start #freshstart
Who it's for: anyone who helped a new hire land — the buddy, the person who rewrote the setup doc at 6pm, the manager who ran the first-week 1:1 properly. (The flip side, recognizing the new hires themselves, is covered in recognizing new hires in their first 90 days.)
Sample shout-out: "Props to @sam for pairing with our two new engineers every morning until their local builds worked #freshstart"
Tracking note: cross-reference tagged recipients against your onboarding-buddy list; the gaps show which buddies need a nudge.
February — Behind the Scenes #behindthescenes
Who it's for: invisible work. Dependency upgrades, meeting notes, the runbook nobody reads until 2am, the quietly fixed flaky test. This theme surfaces names that have never appeared in your feed before.
Sample shout-out: "@priya migrated our whole alerting config over a weekend and nobody noticed because nothing broke. That's the point. #behindthescenes"
Tracking note: count first-time recipients versus your monthly average — the clearest proof the theme did its job.
March — Bridge Builder #bridgebuilder
Who it's for: cross-team help. Recognition tends to stay inside teams, which is how silos calcify. We've written about what recognition data reveals about silos — March is where you act on it.
Sample shout-out: "Huge props to @dev on the data team for jumping into our support rotation to debug the export bug #bridgebuilder"
Tracking note: only count gives where sender and recipient sit on different teams; that share is your headline metric.
April — Teacher #teacher
Who it's for: knowledge sharing. The lunch-and-learn, the thoughtful code review, the person who answers questions in public instead of DMs.
Sample shout-out: "@marco's 20-minute walkthrough of our billing state machine saved me a week of reading #teacher"
Tracking note: three or more tagged gives from different senders means you've found someone who should run your internal training.
May — Customer Hero #customerhero
Who it's for: whoever made a customer's day — support, sales, the engineer who hotfixed one account, the PM who phoned the person who left angry feedback.
Sample shout-out: "Props to @jen for spending two hours recovering a customer's deleted workspace. They renewed the next day. #customerhero"
Tracking note: pair tagged posts with customer quotes; the month-end recap writes itself.
June — Calm Under Fire #calmunderfire
Who it's for: incident response. The on-call engineer who ran a clean incident channel, the comms person who kept the status page honest, the manager who took the blame in the retro.
Sample shout-out: "@alex ran the 3am outage as incident commander and had us at root cause in 40 minutes without anyone raising their voice #calmunderfire"
Tracking note: count tagged gives per incident, not per person — an incident with zero recognition afterward is a retro action item.
July — Bug Squasher #bugsquasher
Who it's for: quality work. Closing the long tail of small bugs, adding the test that catches the regression, reproducing the thing that "only happens on Tuesdays." Summer is quiet for many teams — the right month to reward cleanup.
Sample shout-out: "Props to @taylor for closing 31 bugs from the 'someday' column, including the date-picker one from 2024 #bugsquasher"
Tracking note: compare closed bugs by assignee against tagged gives — the two lists should overlap.
August — Mentor #mentor
Who it's for: longer-arc coaching, as distinct from April's one-off teaching. Weekly 1:1s with a junior engineer since spring, or giving someone their first shot at leading a project.
Sample shout-out: "@chris spent six months helping me get comfortable presenting to leadership. Did my first exec review today. #mentor"
Tracking note: rarer but heavier — share the giver-to-recipient pairs with people managers; it's promotion-packet material.
September — Fresh Ideas #freshideas
Who it's for: the suggestion that changed the plan, the Friday prototype, the "what if we just skipped that step" in planning. Ideas rarely get credited because they're absorbed into the work of whoever ships them.
Sample shout-out: "@nina suggested batching the nightly job by region and cut runtime 70%. Her idea, our win. #freshideas"
Tracking note: if tagged recipients skew senior, the theme is rewarding authority, not ideas — say so in the re-announcement.
October — Done Right #doneright
Who it's for: craft. The design tested with real users, the migration with a rollback plan, the doc that was actually proofread. Not the biggest thing shipped — the best-made thing.
Sample shout-out: "Props to @lee for a PR description so thorough the reviewer approved it in one pass #doneright"
Tracking note: read the tagged posts, not just the counts — they're a free catalog of what "quality" means on your team.
November — Gratitude #thankful
Who it's for: everyone. November is deliberately open-ended: thank the person who made your year easier, whatever they did. The one month the theme is a mood rather than a category.
Sample shout-out: "Just thankful @morgan has been my sounding board through every hard week this year #thankful"
Tracking note: participation rate is the number — distinct people who gave at least once. Aim for your annual high.
December — Year in Review #yearinreview
Who it's for: anything from earlier in the year that went unrecognized at the time. A built-in correction for everything the other eleven themes missed.
Sample shout-out: "Back in March @dana rebuilt our deploy pipeline and I never said thanks. Saying it now. #yearinreview"
Tracking note: pull the year's totals by hashtag and recipient; that's your program's annual report, already written.
Running Themes in Slack with /props and Hashtags
Hashtags are the load-bearing part of this system, and Slack alone can search for one but not count it, rank recipients by it, or reward it. A recognition app that treats hashtags as data closes that gap. Yes, this is where we mention ours: Propsly runs peer recognition inside Slack via /props, and every give requires a hashtag, so the theme tag is never forgotten — it's in the command.
- Someone types
/props +10 @priya for the weekend alerting migration #behindthescenes. It posts to your feed channel automatically (no channel yet? Here's how to set up a recognition channel in Slack). - Tags are tracked per workspace, so the dashboard shows how many gives carried the month's tag and who received them. No spreadsheet.
- On Pro, the "Hashtag Hero" monthly reward automatically sends a gift card to the top recipient for a hashtag you choose. Point it at the theme tag and step four — celebrate a winner — runs itself, feed announcement included.
The free tier covers unlimited users, 200 props per person per month, leaderboards, and the feed; Pro is a flat $50/month per workspace. Our roundup of employee recognition tools for Slack is honest about the alternatives.
Value-Based Themes: Mapping Months to Company Values
If your company has published values, the strongest version of this program uses them directly. Most values lists have four to six entries; give each a month and fill the rest with the behavioral themes above. "Customer obsession" is May. "Ownership" is October. "Bias for action" is September.
The payoff is that your values stop being lobby art and start having receipts: twelve months in, you can point to every tagged post and say "this is what collaboration looked like here this year, with names." We've collected concrete company values recognition examples for the common ones. One caution: never run a values theme and a behavioral theme in the same month — two hashtags means half the participation on each and a muddier winner.
What Themes Won't Fix
Themes redirect attention; they don't create it. If the same 20% give all the recognition, a new hashtag each month won't change who's typing — fix the friction first (put it where people already are, make it take ten seconds), then use themes to steer. Keep the stakes honest, too: a small monthly reward is a nudge; a large one turns the theme into a campaign people lobby for. Do it right and a year from now the group getting recognized is bigger and more varied than today.