When recognition becomes a popularity contest
The signs that a recognition program is rewarding visibility rather than contribution, a quarterly review rubric, and the safeguards that keep it fair.
On this page
Peer recognition works because anyone can notice anyone. The same openness lets it drift: the people who are most visible, most online, or most liked collect the kudos, and steady, quieter work goes unnoticed. Once people feel that, recognition stops meaning much.
This guide is about spotting that drift early and correcting it without turning recognition into an audit.
Five warning signs
- The same few names, every week. A handful of people receive most of the kudos, and they're mostly the ones who are loud in channels.
- Whole teams are quiet. Some teams neither give nor receive, often the ones furthest from where the tool lives, such as frontline, night shifts, or remote staff.
- Kudos circle inside teams. People only recognize their immediate teammates, and work across teams goes unthanked.
- Coins become a currency. Pairs of people trade coins back and forth, or kudos read like payment.
- Leaderboard talk. People mention their rank. Recognition has become a competition.
None of these needs a crisis. Spotting one is a reason to look, not proof that the program is failing.
A quarterly review rubric
Thirty minutes, once a quarter, with the program owner and one or two people who aren't managers. Pull these numbers for the quarter first. In Pulsido they're on Manage → Recognition insights, which can be filtered by team and date range.
| Question | Look at | Healthy looks like | Act when |
|---|---|---|---|
| Is recognition reaching people? | Recognized: the share of people who received any kudos | Most people, rising over time | A large group received none |
| Who's being missed? | Who might be overlooked, newest joiners first | A short list that changes each quarter | The same people stay on it |
| Does it cross teams? | Across teams: kudos to someone outside the giver's teams | A steady share | It's falling, or near zero |
| Is giving spread out? | Active givers and participation by team | Every team has givers | One team gives nearly all of it |
| Do values show up? | Kudos by value | Several values in use | One value is all of it, or one is never used |
Then discuss two questions with the non-managers in the room: does recognition feel fair? Is anyone left out who shouldn't be?
Write down one or two changes, not a new program. "Ask the warehouse lead to recognize one person a week" beats "improve frontline engagement".
Safeguards that help
- Don't rank people. Use counts to find who's overlooked, never to score anyone. Pulsido's insights deliberately show the overlooked and the cross-team share, and it never ranks people by how much they're recognized.
- Keep leaderboards in proportion. Pulsido's leaderboard shows the most recognized and most generous for a period. If it's driving competition, stop posting it to the channel and leave it as a page people can choose to visit.
- Draw the MVP, don't award it. If you run a weekly round, Pulsido's MVP is a draw from the day's top receivers and givers, and recent winners sit out for four rounds. The same people can't win every week.
- Cap coins between pairs. A per-person limit (50 coins a month by default) stops two people trading coins back and forth. If a kudos would go over it, it still sends, with the coins left under the cap.
- Ask managers to look around. A manager recognizing one overlooked person a week does more than any setting.
- Thank the invisible work. Share examples of kudos for the work nobody sees: the runbook, the patient answer, the bug caught before release. Write recognition that says what mattered has eight.
What not to do
- Don't set quotas. "Everyone must give two kudos a week" produces two kudos a week of nothing.
- Don't name the overlooked publicly. The overlooked list is a prompt for managers, not a list to announce.
- Don't tie kudos to performance reviews. As soon as kudos count toward pay or promotion, people start asking for them, and they stop being thanks.
Sources and limits
The insights and settings described are Pulsido's, as documented in the help center on 7 November 2026. The warning signs come from how recognition programs commonly drift, not from a controlled study. For research on frequency and specificity, see How often should people be recognized?