Recognition is somebody saying, in front of other people, that what you did mattered. Rewards are the thing you can spend. Most platforms sell them together, which is fine, but it obscures which one is actually producing the result you are paying for.
They Fail Differently
| Recognition | Rewards | |
|---|---|---|
| Marginal cost | Near zero | Real money |
| Best frequency | Weekly | Monthly or on a milestone |
| Fails when | It becomes automatic and unspecific | The catalogue is irrelevant or unreachable |
| Who drives it | Managers and peers | The employer's budget |
| Visible to | The team | Only the individual |
The most common pattern we see is a program with a generous reward budget and no recognition volume. It costs a lot and produces very little, because the points arrive without a story attached and are experienced as a small, irregular discount rather than as being noticed.
Why A Reason Field Is Not Optional
Recognition with no reason attached degrades within a month. It becomes a habit — a thumbs up, a generic thanks — and once it is a habit it carries no information and no weight.
Making the reason mandatory has a second effect that is easy to miss: it produces a written record of what good work looks like in your business, in the words of the people doing it. That record is more useful at review time than anything a manager will reconstruct from memory.
"Thanks for your hard work" is not recognition. "Stayed back to close after the function ran over" is.
The Visibility Question
Recognition that only the recipient sees is worth a fraction of recognition the team sees. This is the whole mechanism — the value is social, not private.
It is also the part most likely to be switched off during implementation, usually because someone worries about people feeling left out. In practice the fix for that is a cap on how much any one person can send, not hiding the feed.
How To Diagnose Your Own Program
Three numbers, pulled for the last full quarter.
- Recognitions per employee per month. Below 0.5 and the recognition half is not running. Above 2 and it is healthy.
- Share of points from recognition versus other sources. If recognition is under a fifth of issued points, the program is a discount scheme with a recognition feature bolted on.
- Redemption rate. Below 70 per cent and the reward half is broken — usually the threshold is too high or the catalogue does not suit the workforce.
| Recognition volume | Redemption rate | What it means |
|---|---|---|
| High | High | Working. Leave it alone. |
| High | Low | Catalogue or threshold problem, not a culture problem. |
| Low | High | An expensive discount scheme. Brief the managers. |
| Low | Low | Nobody is using it. Go back to the rollout basics. |
Where To Put The Next Dollar
If recognition volume is low, the next dollar should not go into the reward budget. It should go into whatever gets managers sending recognitions — usually fifteen minutes in a team meeting and a target for the month, which costs nothing.
If recognition volume is healthy and redemption is low, the money is not the problem either. Lower the minimum redemption threshold and check the catalogue actually contains places your workforce shops.
The reward budget is the right place for the next dollar in exactly one case: both numbers are healthy and you want more of what you are already getting.
Not sure which half is broken?
Send us the three numbers and we will tell you where the next dollar should go.