Why recognition programmes fail, and what holds up
Echipa HR 365 · reviewed 2026-09-09 · 5 min read
Recognition programmes fail, almost always, for the same reason: they turn appreciation into a competition with one winner and a fixed cycle. By the third “employee of the month”, everyone has understood it is a rotation, and the award no longer means anything to anyone.
The three causes of failure
| Cause | What it looks like | Why it kills the programme |
|---|---|---|
| Competition with a single winner | Employee of the month, by vote or by decision | In a team of ten, nine lose every month |
| A fixed, mandatory cycle | Somebody has to be picked every month | It becomes a rotation, and the rotation is noticed |
| Invisible criteria | Nobody knows what it was given for | It cannot be repeated and nothing can be learned from it |
What holds up
Three characteristics, all of which run against the instinct to build a formal programme:
- No fixed number. Recognition happens when there is something to recognise, even if that means three in one month and none in the next.
- With the reason written. Not “for commitment”, but what they did and what it produced. It is also the only form others learn from.
- From colleagues, not only from above. The people who work with you daily see what the manager does not.
The third changes the dynamic most. Appreciation from a manager is an assessment; appreciation from a colleague is an observation. They carry different weight, and in a company where both circulate, the second is the one told at home.
With money or without
A small sum attached to appreciation does no harm, but it shifts the attention: from the moment there is a prize, people start comparing amounts and calculating who got more. Recognition without money, but public and concrete, produces a more durable effect in practice.
The exception worth making: a reward for an exceptional, one-off effort — a very hard stretch, an intervention over a weekend. There a sum or a day off communicates something words do not cover, precisely because a cost to the company is visible.
What actually gets recognised
| Deserves it | Often rewarded and should not be |
|---|---|
| Someone who prevented a problem | Someone who fixed a crisis they created themselves |
| Someone who trained a colleague | Someone who does everything alone and never delegates |
| Someone who documented what only they knew | Someone indispensable, for being indispensable |
| The invisible work that keeps things standing | The visible work, which is seen anyway |
The right-hand column describes, in most companies, exactly what gets rewarded. The effect over time is that people learn which behaviours are rewarded — and those are not the ones that make the organisation more resilient.
The cheapest form, and the most neglected
A manager saying, concretely, what they observed, on the day it happened. No programme, no budget, no announcement. It costs thirty seconds and is, in most internal surveys, the thing people say they miss most.
The reason it does not happen is not ill will but that good things generate no request. Problems find their own way to the manager; what goes well has to be noticed deliberately — and that requires a routine, not a programme.
Do I need a tool, or is saying it enough?
For small teams, saying it is enough and better. A tool becomes useful past about thirty people, when the manager no longer sees everything and peer appreciation would otherwise stay invisible.
What if someone never receives anything?
That is information, not a fairness problem with the programme. Either they do invisible work nobody notices — and then it is your job to see it — or genuinely nothing remarkable is happening, and that is a performance conversation.
Where to start
With no programme. This week, notice one concrete thing about two people in your team and tell them, that day, what you saw and what it produced. If that does not happen naturally, no programme built on top of it will work.
If you already have a programme with a monthly winner, the best change is to remove the cycle obligation and the fixed number. The rest repairs itself almost on its own.
The fairness problem
Any form of recognition inevitably produces a comparison. The risk is not that someone gets more, but that a visible pattern forms: the same people, from the same roles, from the same teams. Usually the ones with visible work — sales, projects — at the expense of the ones who keep things standing.
The check is worth running once a year: who received something, from which teams. If half the company never appears, it does not mean they do not deserve it — it means their work produces no visible events, and the programme is measuring visibility.
What does not substitute for recognition
- A fair salary. It is a condition, not a form of appreciation; its absence cancels any programme, its presence does not replace one.
- Team events. They are about belonging, not about anyone’s particular contribution.
- Promotion. It comes rarely and cannot cover two years of good work between promotions.
- Review feedback. It arrives once every six months, long after the moment has passed.
Peer appreciation, with the reason written and visible to the team
Recognition travels sideways rather than only downwards, and the reason stays written — so others see what was appreciated, not merely who.
You can create an account in a few minutes and use every module for 7 days, no card required.