Most lists of employee engagement contest ideas are lists of things HR wishes people would do, with a prize stapled on. Everyone can smell it: the trivia nobody signed up for, the wellness challenge one marathon runner tops on day two. The contest isn't the problem. Forced is the problem.
Forced comes from three places. Mandatory fun: participation is expected, so it's another meeting. Zero-sum prizes: one winner, and the people who know they'll lose check out before it starts. Participation theater: the contest exists so a slide can say "we ran a contest."
The contests that don't feel forced are the inverse. They're opt-in. They're non-zero-sum or team-based, so most participants finish feeling like they won something. And they're tied to something people already value: recognizing a colleague, learning a skill, shipping a fix, helping a cause. The contest is scaffolding for a thing people wanted anyway.
This is the sequel to our guide to Slack gamification and when it backfires. That post covers mechanics; this one is the idea bank. Twenty-five contests, each with the mechanic, how to run it in Slack, a prize, and how it goes wrong.
Recognition-Driven Employee Engagement Contest Ideas
The highest-leverage group. Employees who feel inadequately recognized are about twice as likely to say they'll quit within a year (Gallup/Workhuman), so a contest that gets people recognizing each other pays rent.
1. Peer-nomination leaderboard month
For one month, the "most props received" board comes with a spotlight: the top five get a write-up in #wins quoting the actual messages people sent them. Prize: the write-up itself, maybe a coffee card. Failure mode: the same three visible people win, which is why you pair it with idea 4.
2. Hashtag challenge week
Pick one theme hashtag (#customer-love, #unblocked-me, #quiet-hero) and ask people to tag recognition with it for a week, with a daily tally in the feed channel. Prize: whoever receives the most tagged props picks next month's hashtag. Failure mode: a theme so narrow half the company has nothing to tag.
3. Cross-team recognition bingo
Every team gets a 3x3 card of other teams; you mark a square when someone on your team gives props to someone on that team. Full card wins, every row gets a shout-out. Prize: winning team picks the all-hands playlist. Failure mode: drive-by "thanks!" to strangers. Require a specific reason. Cross-team gives are the highest-signal event in the system, as we argued in breaking down silos with recognition data.
4. Most unique givers
Celebrate the person recognized by the largest number of different people, not the most points. Breadth over volume, and the direct antidote to "same winners every month." Prize: a small gift card or lunch. Failure mode: almost none, which is why this should be your default.
5. Giving-streak challenge
Give recognition at least once a week for eight consecutive weeks. Non-zero-sum: the whole company can succeed at once. Post a weekly "streak club" roster. Prize: a custom emoji for everyone who hits eight. Failure mode: Friday-afternoon filler props to keep the streak alive; a one-week grace period removes the pressure to fake it.
6. Spotlight-the-invisible week
One week where props go only to work nobody would otherwise see: the fixed flaky test, the updated runbook, the covered shift. Prize: a collected "seen" post in #wins. Failure mode: people can't think of examples. Seed day one with five from managers who know where the unglamorous work lives.
Learning and Skill Contests
7. Lunch-and-learn series with a vote
Six weeks, six volunteer talks, recorded, then a company vote on the most useful. Sign-ups in a thread, recordings in a channel. Prize: book budget or a conference ticket. Failure mode: the same senior people volunteer every time. Reserve half the slots for first-time presenters.
8. Bug bash
A half-day where everyone, non-engineers included, hunts bugs, with a pinned team tally in a channel. Prize: finder of the most embarrassing bug gets naming rights on the fix. Failure mode: it becomes engineering-only. Pair each non-engineer with an engineer who can reproduce what they find.
9. Docs day
One day, the only goal is fixing documentation; every merged fix posts to a thread, scored by team. Prize: pizza for the top team and a "most-needed doc" award voted by support. Failure mode: typo fixes to inflate counts. Weight by hours saved.
10. "Teach me something" thread
A weekly thread where anyone posts a two-minute tip. Reactions are votes. Prize: monthly winner picks the next theme. Failure mode: it dies when the organizer forgets. Schedule the prompt with a Slack reminder so it doesn't depend on one person.
Wellness and Habit Contests
Where "forced" shows up fastest, because these touch bodies and private lives. Team totals and opt-in are non-negotiable.
11. Step challenge with team totals
Teams of five, self-reported weekly steps, team average posted so one runner can't carry the group. Prize: a paid walk-and-talk lunch. Failure mode: shaming the low count. Show team numbers only, and let people join or leave silently.
12. Hydration or sleep streak
One boring habit (eight glasses, seven hours), tracked with a daily emoji check-in thread. Everyone who hits 20 of 28 days wins. Prize: a nice water bottle, or nothing. Failure mode: any hint of surveillance. Never ask why someone missed, never connect it to anything HR sees.
13. Walking meetings week
Any 1:1 that can be a walk becomes one; a checkmark in a thread counts it. Prize: the team with the most walked meetings picks a charity for a small donation. Failure mode: penalizing people who can't walk. Count "away from the desk" broadly: a stretch, a standing call, a coffee outside.
Creative and Culture Contests
Low-stakes and easy to overdo. One at a time. Several double as remote ice breakers for distributed teams.
14. Desk or video-background decorating
A theme, a week, a photo in a channel, emoji voting. Prize: the winner's setup becomes the default video background for a month. Failure mode: it rewards money and square footage. Add a "best under $10" category.
15. Photo challenge
Five daily prompts ("your workspace from your chair," "the view from your nearest window"). Prize: a printed photo book of everyone's best shot. Failure mode: exposing home situations people didn't want to share; every prompt must be answerable without showing your home.
16. Playlist battle
Each team builds a collaborative playlist on a functional theme (focus music, Friday wind-down); the company votes. Prize: the winner plays at the next in-person event or gets pinned in #random. Failure mode: taste wars. Keep themes functional, never "best music."
17. Custom emoji design contest
Everyone submits one emoji for a specific use: celebrating a deploy, "I'm blocked," the props reaction. Vote, install the winners. Prize: your emoji lives in the workspace forever. Failure mode: inside jokes that exclude new hires. Require one line explaining each submission.
18. Guess the baby photo
Volunteers DM a childhood photo to the organizer; photos go up numbered and everyone guesses. Prize: shout-outs for the best guesser and the most-misidentified person. Failure mode: pressure to submit. Guessing without submitting is normal; say so.
19. Two truths and a lie tournament
Bracket-style, one matchup a day, emoji voting on the lie. Prize: whoever fooled the most colleagues gets "professional liar" in their Slack title for a month. Failure mode: it drags; cap at 16 people and two weeks.
20. Workspace trivia league
Five questions every Thursday about the company itself: oldest open ticket, first customer, the codebase's original name. Team points over a quarter. Prize: a trophy that moves between desks. Failure mode: tenured people dominate. Mix in questions only new hires would know, like what's in the current onboarding doc.
Customer and Product Contests
21. Customer story of the month
Anyone who talked to a customer nominates a story (a win, a surprising use, a painful moment) in a thread; the company votes. Prize: the nominator tells it at all-hands. Failure mode: only sales and support nominate. Let engineers nominate secondhand and credit the source.
22. Feature naming contest
A feature is shipping and the codename is bad. Open a thread, collect names, vote. Prize: the winning name goes on the changelog with credit. Failure mode: the winner is unusable; marketing vetoes before the vote, not after.
23. Demo day
Monthly, anyone shows anything they built in five minutes: a feature, a script, a spreadsheet that saves an hour a week. Vote for "most useful" and "most surprising." Prize: a paragraph in the company newsletter. Failure mode: it becomes a status report. Ban slides; live demos or nothing.
Community Contests
24. Volunteer hours challenge
Teams log volunteer hours over a quarter in a shared channel, any cause, team totals. Prize: the company donates to the winning team's organization. Failure mode: it becomes a hidden expectation of unpaid time. Offer paid volunteer hours as part of the contest, or don't run it.
25. Donation matching leaderboard
During a giving month, the company matches donations up to a cap, and the leaderboard tracks participation rate by team, not dollars. Prize: the highest-participation team directs an extra company gift. Failure mode: ranking by dollar amount, which just ranks salaries.
How to Run Any of These Without It Backfiring
- Score by team wherever you can. It turns "I'll never win" into "my team might," and makes carrying each other the point.
- Keep it short. A week or a month. Longer than a quarter and it's a policy, and policies don't have energy.
- Publish the rules before day one. What counts, how it's scored, who judges, what the prize is. Mid-contest rule changes cost you the next five contests.
- Celebrate participation, not just winners. The closing post names everyone who played, then the winners. One hero and forty extras is a lottery, not a contest.
- Retire it before it's stale. If you're wondering whether to run it a fourth time, you already know. For the program these fit into, see our strategies for employee engagement and the lower-effort team morale boosters.
How to Tell If It Worked
Three numbers, no survey required. Participation rate: what share of eligible people played at least once? Under 30% is a clique, not a contest. Repeat participation: how many came back next time? That's the real signal, because it's purely voluntary. And for the recognition contests, whether recognition volume stays up after the contest ends. A spike during hashtag week and a crater after means you bought a spike; a higher baseline means you built a habit. Keep prizes small and symbolic; if you do use gift cards, our guide to employee recognition gift cards covers doing it without turning "thanks" into a transaction.
Where Propsly Fits (Yes, It's Ours)
We build Propsly, a Slack recognition bot, so weigh this paragraph accordingly. Several of the recognition contests above are settings, not projects: everyone gets 200 props a month that reset on the 1st, leaderboards and a feed channel cover ideas 1 and 2, hashtags are built into the /props command, and giving streaks are celebrated automatically at 4, 8, 12, 26, and 52 weeks, which is idea 5 running itself. On the $50/month Pro tier the monthly gift-card rewards are automated and map onto these contests directly: Props Superstar (most received), People's Champion (most unique givers, idea 4), Bridge Builder (most cross-team, idea 3), and Hashtag Hero (most props for a chosen hashtag, idea 2). The system picks the winner, issues the card, and announces it in the feed. We built it that way because peer recognition beats top-down appreciation, and formats that reward breadth are the ones that survive past month three.
Pick one. Not five, one. Run it for a month, count who played and who came back, and let that decide the next. The best contest is the one people would notice if you stopped.