Employee recognition: making thanks visible and measurable

Recognition is the cheapest and most neglected tool in company culture. In most organisations thanks stays in a private message: the sender is pleased, the recipient is pleased, and nobody else knows. The single function of a recognition wall is to make that thanks visible — and visibility is the only mechanism that multiplies behaviour.

Why peer recognition?

A performance rating given once a year by a manager doesn't capture daily contribution. A colleague's weekend support, another team picking up an urgent request, half an hour spent with a new joiner — none of these reach an appraisal form.

Peer recognition fills that gap and produces two extra benefits. Contribution the manager can't see becomes visible. And culture turns into measurable data: who recognises whom, and for which behaviour?

Badge design: few and clear

The most common mistake is defining fifteen badges. Too many options make the decision harder, and the burden of choosing lowers participation. Three to five badges are enough for most companies, and they should name the behaviours the company genuinely cares about: teamwork, problem solving, customer focus.

Copying badge names from the corporate values document is tempting but rarely works; a label that doesn't match the employee's own language goes unused.

The points and rewards balance

Tying recognition to points and points to rewards raises participation — but if it isn't set up carefully it distorts the purpose. Two rules help:

1. Points must be produced server-side, not in the client. If a balance can be written from the browser, the system isn't trustworthy. In our product points are written only by database triggers.
2. The reward threshold must be reachable. Rewards that require a year of saving don't motivate; small and frequent works better.

Preventing gaming

The first question is always the same: won't people write each other points and exploit the system? In practice that risk is overstated, because recognition is visible — meaningless recognition on a wall everyone sees is socially expensive.

Still, a few plain safeguards are sensible: a mandatory message field (so empty recognition can't be sent), a reasonable daily cap, and the ability for an administrator to remove inappropriate recognition. That removal right sits deliberately with administrators only: letting the sender withdraw it unilaterally would mean quietly erasing something the other person already saw.

Not reversing the points on a deleted recognition is also deliberate — so that reward claims made in the meantime don't become invalid.

Visibility: where should the wall live?

A recognition wall on its own page isn't enough. The most impact comes from a feed on the homepage and visibility on shared-area screens. A thank-you rotating on the break-room display is far stronger than an email that is never opened — especially for teams that don't work at a desk.

That's why it makes sense to think about recognition together with digital signage.

From recognition to rewards

Points sustain participation when they have a payoff. A reward catalogue makes that concrete: a day off, a gift card, a training budget or company merchandise. The claim should be approved by a manager and the balance deducted server-side.

Two traps when designing the catalogue: rewards that are too expensive don't motivate because they're unreachable, and rewards that are too cheap devalue the recognition itself. A practical start is a first threshold reachable with two or three months of steady contribution.

Measurement: what to look at

Total recognition count alone is misleading. Three more meaningful indicators:

• Spread — senders as a share of all employees. A few people sending a lot signals habit, not culture.
• Departmental balance — teams that receive no recognition are usually the ones doing invisible work.
• Continuity — is there still a flow in the third month after launch?

The third is the harshest test. Recognition systems spike in launch week and then fade; what keeps them alive is a regular rhythm and managers setting the example.

Where to start

We recommend switching recognition on in the second wave rather than the first: after announcements, the directory and documents have become a daily habit. An empty recognition wall leaves the worst possible first impression in a newly opened intranet.

The reasoning for that order is in the 90-day plan, and ways to sustain participation are in our engagement article.