You’ve seen it happen. A company launches a recognition program with enthusiasm. Leadership sends messages. HR creates guidelines. The first month, participation spikes. Then it plateaus. By month six, it’s a ghost town – a forgotten Slack channel, an unused feature, a line item in an HR report that no one reads.
This isn’t a failure of intention. It’s a failure of design. Recognition programs stall for predictable reasons, and understanding those reasons is the first step to reviving them.
The Three Killers of Recognition Momentum
After analyzing hundreds of recognition programs, three patterns emerge consistently. Each is fixable, but only if you recognize it early.
1. The Manager Bottleneck
When recognition depends entirely on managers, it dies with their bandwidth. Managers are pulled in dozens of directions. Recognition becomes another task on an endless list, easily deferred until “later” – which never comes.
The fix: Shift to peer-to-peer as the primary channel. When colleagues recognize each other directly, you remove the bottleneck. A 2025 Gallup study found that teams with peer-driven recognition show 23% higher engagement than those relying solely on manager-led programs.
2. The Vagueness Trap
Generic praise – “Great job!” – feels good for about five seconds. It doesn’t tell the recipient what to repeat, and it doesn’t give anyone else a model to follow. Over time, vague recognition degrades into noise.
The fix: Require specificity. Not in a heavy-handed way, but through prompts and templates. Instead of just “Thanks,” encourage the format: “Thanks for [specific action] because [specific impact].” This makes recognition learnable and repeatable.
3. The Visibility Vacuum
When recognition happens in private channels or one-on-one messages, it disappears. The recipient feels appreciated, but the team misses the cultural signal. There’s no ripple effect.
The fix: Make recognition public by default. Public channels, visible feeds, team celebrations. The goal isn’t to embarrass introverts – some people prefer private acknowledgment – but to build a shared understanding of what “good” looks like in your organization.
How to Restart a Stalled Program
If your recognition program has already lost momentum, don’t try to reboot everything at once. Small, visible changes work better than big announcements.
Week 1: Model the behavior
Leadership should recognize someone publicly every day for a week. Not performative praise, but genuine, specific acknowledgment. This signals that the channel is alive.
Week 2: Reduce friction
Check your tools. Is it easy to recognize someone? If it takes more than 30 seconds, people won’t do it. Simplify the workflow. Add shortcuts. Remove unnecessary fields.
Week 3: Celebrate the recognizers
The people who give recognition deserve acknowledgment too. Highlight top contributors. Show that giving is as valued as receiving.
Week 4: Connect to values
Tie recognition to specific company values. When someone demonstrates a value through their work, call it out explicitly. This reinforces what matters and gives recognition structural meaning.
The Long Game
Recognition isn’t a campaign. It’s a habit. Programs stall because they’re treated as launches rather than practices. The goal isn’t a spike in activity – it’s a sustainable rhythm of appreciation woven into daily work.
If your program has stalled, you’re not alone. Most do. The difference between organizations that recover and those that don’t is simple: they treat the stall as a design problem, not a people problem. Fix the design, and the behavior follows.
Quick Diagnostic
Ask yourself these three questions:
- Can anyone recognize anyone, or does it flow through managers?
- Does recognition include specific details, or just general praise?
- Is recognition visible to the team, or hidden in private channels?
If you answered “no” to any of these, you’ve found your restart point.
How to Build a Recognition Ritual That Sticks