Ask most HR leaders whether their employee rewards system works, and you’ll get a careful answer. Something like: “It’s fine.” Or: “People like it well enough.” Rarely: “It’s changed how people behave.”
That hesitation is worth paying attention to. Rewards are one of the few levers where organisations spend real money and rarely measure real change. The budget goes out, the vouchers land, and engagement sits roughly where it was. So the question isn’t whether to reward people. It’s why the systems we build so often fail to move anything.
Table of Contents
The predictability problem
Most employee rewards systems share a design flaw: they are entirely predictable. Hit the target, get the bonus. Five years’ service, get the voucher. Employee of the month, get the certificate and the parking space.
Predictability feels fair, and fairness matters. But predictable rewards have a well-documented habit of turning into entitlements. The first voucher is a pleasant surprise. The fourth is expected. The fifth, if it doesn’t arrive, is a grievance. You have spent the same money and moved from goodwill to obligation without changing anything about the reward itself.
There’s a second problem, quieter but more damaging. Predictable rewards attach to outcomes — targets hit, years served, deals closed. That’s reasonable for sales commission. It’s poor design for engagement, because the behaviours that actually drive engagement aren’t outcomes. They’re small, repeated, and easy to skip: giving honest feedback, flagging a problem early, telling a manager something they’d rather not hear.
Nobody hits a quarterly target for candour.
It’s not that recognition doesn’t matter — it plainly does. Gallup’s research finds employees who don’t feel adequately recognised are three times more likely to say they’ll leave within the year. The gap is between recognition mattering and a rewards system being built in a way that delivers it.
What variable reward actually does
Behavioural psychology has been clear on this since Ferster and Skinner’s work in the 1950s: rewards delivered on a variable schedule sustain behaviour far more reliably than rewards delivered on a fixed one. It’s the difference between a salary and a slot machine — and while that comparison makes people uncomfortable, the underlying mechanism is neutral. It’s simply how anticipation works.
The practical implication for an employee rewards system is counterintuitive. If you want people to keep doing something small and regular, a smaller reward with an uncertain arrival often outperforms a larger reward with a certain one. You are not buying the behaviour. You are giving it a reason to stay top of mind.
This matters most for habits that have to survive past the novelty — and we’d include our own product in that. Any regular feedback programme is easy to sustain in week one and hard to sustain in month four. The first response was never the difficult one. The fortieth is, once the novelty has gone.
Two things keep it alive. The first is people seeing that what they said actually went somewhere, which is the whole argument for continuous feedback over annual engagement surveys — by the time you read an annual result, the moment that prompted it has passed. The second is a small, low-stakes reason to come back in the meantime. An employee rewards system is the second of those. It is emphatically not a substitute for the first.
The first is the harder problem, and it’s where most of the work sits. Feedback only feels worth giving if somebody can find the signal in it — which means surfacing the issues that actually need attention rather than handing a manager three hundred free-text comments and wishing them luck. It means making it obvious which team, which theme, and which week something started going wrong. And it means giving managers a way to respond to a specific piece of feedback without breaking the anonymity that made it honest in the first place.
Close that loop visibly and participation largely looks after itself, because people can see their input landing. Leave it open and no employee rewards system on earth will hold the habit together — you’ll just be paying people to shout into a void slightly longer than they otherwise would have.
Design for participation, not performance
The most useful shift is to stop rewarding results and start rewarding participation.
Rewarding results in an engagement context creates an obvious distortion: if a high score earns a reward, you have just given everyone a reason to report a high score. You’ll get the numbers you asked for and lose the signal you needed. Any employee rewards system tied to survey scores is quietly buying its own blind spot.
Rewarding participation has no such conflict. Whether someone answers positively or negatively is irrelevant to their eligibility — they simply answered. The organisation gets more data, more honest data, and the reward stays clean. This only holds if responses are genuinely anonymous; the moment people suspect a reward is linked to what they said, you’ve rebuilt the distortion you were avoiding.
A few principles that tend to hold when designing an employee rewards system around participation:
- Reward the act, never the answer. Eligibility should depend on taking part, not on what was said.
- Keep the individual reward modest. Large rewards raise the stakes enough that people start gaming them. Small ones keep participation habitual rather than strategic.
- Make the odds visible. Uncertainty motivates; opacity breeds suspicion. People should be able to see how they qualified and what their chances are.
- Let the organisation choose the prize. What lands well varies enormously. A £25 voucher works in one company and reads as insulting in another. An extra afternoon off works somewhere a voucher never would.
Worth noting that none of this replaces peer-to-peer recognition, which does a different job. Gallup’s work on recognition as a low-cost, high-impact lever is about being seen by the people you work with. A rewards system is about sustaining a habit. Confusing the two is how organisations end up with a prize draw where they needed a manager to say thank you.
A worked example
We built this into Wotter as a feature called the Wottery, and the design choices are worth walking through because each one maps to a principle above.
Employees earn tickets by answering their questions. Answer more, hold more tickets, improve your odds — but every participant has a genuine chance, so it never becomes a leaderboard where the same handful of people win repeatedly. The draw runs on a schedule the company sets.
Critically, the prize is not fixed. Each company decides what it’s drawing for, because we can’t know whether a team wants vouchers, a charitable donation in the winner’s name, or a Friday afternoon. Prescribing the reward would have undermined the point.
What it deliberately does not do: reward positive answers, publish who said what, or hand larger prizes to more senior people. The whole mechanism sits on top of anonymous employee feedback, and anything that compromised the anonymity would cost more than the engagement it bought.
Measuring whether your employee rewards system worked
Most rewards programmes are evaluated on redemption rates, which tells you people like receiving things. Not informative.
Better questions:
- Has response rate held up over time? Not week one — month four. Sustained participation is the thing you were buying.
- Has response rate risen in the groups that were quietest? If it only lifts among people already engaged, you’ve rewarded enthusiasm rather than created it.
- Has the content of feedback changed? More responses that say nothing is not progress. More responses that name real problems is.
- Would people notice if it stopped? Uncomfortable, revealing, and worth asking directly.
These are the same questions worth asking of any continuous feedback programme. A rewards system is one input into that, not a substitute for it.
Frequently asked questions
What is an employee rewards system?
A structured way of giving people something of value, such as vouchers, prizes or time off, for particular behaviours or milestones. Most link rewards to outcomes like targets hit or years served. One designed for engagement rewards small, regular behaviours instead.
Why do employee rewards systems fail?
Usually because they are predictable. Fixed rewards for fixed outcomes quickly turn into entitlements, and they attach to results rather than the small, repeated behaviours that drive engagement, such as giving honest feedback or flagging a problem early.
Should you reward survey participation or survey results?
Participation. Rewarding high scores gives everyone a reason to report high scores, so you lose the signal you needed. Rewarding the act of answering keeps the data honest, provided responses are genuinely anonymous.
How do you know if an employee rewards system is working?
Look past redemption rates. Check whether response rates hold up by month four, whether they rise in the quietest groups, whether feedback names real problems, and whether people would notice if the scheme stopped.
Is a rewards system the same as employee recognition?
No. Recognition is about being seen by the people you work with, usually peers and managers. A rewards system is about sustaining a habit. They do different jobs, and one cannot replace the other.
The honest caveat
An employee rewards system will not fix disengagement. If people are leaving because of a manager, a workload, or a pay gap, no draw will touch that — and using one to paper over it will be recognised for what it is, quickly.
What rewards can do is narrower and still valuable: keep a feedback habit alive long enough for the organisation to learn something. The reward gets people to speak. What happens next is what determines whether they keep speaking, and that has never been about prizes.
Build the employee rewards system to start the conversation. Then earn the right to keep having it.
