Employee recognition

What employee recognition is

Employee recognition is the acknowledgement of a person’s effort, behaviour or results by the people they work with. That acknowledgement can take almost any form: a sentence posted in a team channel, one handwritten note, the mention at an all-hands, an award on a work anniversary, or a bonus. What makes it recognition rather than a nice atmosphere is specificity. It points at a thing somebody did.

A useful test: if you could swap the recipient’s name for a colleague’s and the message still reads correctly, it is praise in general. Recognition would stop making sense, because it describes one person’s work.

Two words get used together and mean different things. Recognition responds to what someone did. Appreciation responds to who they are. A team needs both, and this guide is mostly about the first, because the first is the one companies find hard to do at scale.

Recognition also differs from feedback and from reward. Feedback includes what should change; recognition is about what should continue. Reward attaches something of value; recognition can carry a reward and usually does not need to. The confusion between recognition and reward is where many programs go wrong, which is covered below.

Why it matters

The case rests on a simple observation about people: they repeat what gets noticed, and they leave places where nothing does.

Gallup’s research puts the share of US employees who strongly agree they received recognition or praise in the last seven days at about one in three. Employees who do not feel adequately recognised are twice as likely to say they will quit within the year. The same body of work finds that recognition is a driver of engagement, that engaged teams have materially lower turnover, and that the most effective recognition is honest, individual and specific.

The numbers below are the ones Evergreen cites across this site, with their sources.

Two things about these figures are worth holding on to. The first is that the effect size is large relative to the cost. Recognition given by a peer in a team channel costs a minute. The second is the 39 percent who do not feel appreciated at work. That is a very large number of people doing work nobody has said anything about, and in most companies they are concentrated in the same roles: the ones whose work is only visible when it fails.

The effects also compound. A person who is recognised for a habit does more of it. Colleagues who see the recognition learn what the team values without a slide. Managers who read a channel full of recognition learn things about their team’s work they would never have seen in a one-to-one. The posts on the effects of recognition on retention and morale and on why recognition matters go further into the research.

The types of employee recognition

Recognition is usually sorted along three lines. They are independent: a single act of recognition sits somewhere on each.

Who gives it

Peer-to-peer recognition comes from a colleague at the same level. It carries weight for a reason that has nothing to do with hierarchy: a peer has nothing to gain by giving it and sees work that managers do not. It is also the only kind that scales, because there are far more peers than managers. Evergreen is built around it, and the post on peer-to-peer recognition has examples and templates.

Manager recognition comes from the person who assesses your work, so it is read as an assessment. That makes it valuable and makes it rarer than it should be, because managers save it for reviews.

Company recognition comes from leadership or from the organisation as a whole: an award, a mention at an all-hands or the celebration of a milestone. It is the most visible form and the least frequent, and a program that relies on it alone recognises a handful of people a quarter.

How structured it is

Formal recognition runs through a program with criteria, timing and often a reward: employee of the month, service awards, quarterly values awards, a nomination process. It is fair in the sense that everybody knows the rules, and it is scarce by design. You can only name one employee of the month.

Informal recognition is unscheduled and immediate: a message after a hard week, a thank-you in a meeting, or the note left on a desk. It is where most of the value lives, because it can happen every day and be given by anyone. The weakness is that it depends on people remembering to do it, which is what a tool like Evergreen exists to fix.

Whether money is attached

Monetary recognition attaches cash or something with cash value: a bonus, a gift card, points redeemable for goods. It is easy to understand and, in most countries, taxable as income. It also changes what the recognition means. A gift card says the company noticed; a sentence about what you did says a person did.

Non-monetary recognition is everything else: public thanks, time off, a better project or a tree planted in your name. A majority of employees say they prefer it, which surprises companies that assumed the opposite. The glossary entries on monetary and non-monetary recognition cover the trade-offs in more detail.

A fourth axis is sometimes added: whether the recognition is public, where colleagues can see it, or private. Public recognition does two jobs at once, since it also tells everyone else what the company treats as valuable. Private recognition is right for people who would rather not be singled out, and their preference should win.

How to build an employee recognition program

A program is the set of decisions that make recognition happen when nobody is thinking about it. Companies that skip the decisions end up with a channel that was busy for a fortnight. These are the seven that matter, in the order to make them.

1. Decide what you want more of

Write down the behaviours the program should surface. If the company has stated values, these are the values translated into things a colleague could observe on an ordinary Tuesday. If it does not, this step will produce them. A program without this list recognises whatever is loudest, which is usually sales numbers and heroics.

2. Make it available to everyone

Recognition that only managers can give reaches the people managers see. Give every employee the means to recognise any colleague, in the place they already work, with no approval step. The gap between a program that includes peers and one that does not is the gap between a few recognitions a month and a few a day.

3. Set the criteria loosely and the format tightly

Criteria should be broad, because the point is to catch work that would otherwise go unnoticed and you cannot list that in advance. The format should be tight: a good recognition names the person, names the thing they did and says what it changed. Prompts in the tool, examples on the wall and the first few weeks of leadership modelling it are how the format spreads.

4. Choose the reward, if any, last

Decide whether anything is attached to recognition only after the first three steps. Many programs work with no reward at all. If you add one, keep it small enough that nobody games it and consistent enough that nobody feels cheated. Evergreen’s reward is a tree: three seeds received plants one, which gives the recognition a physical consequence without turning it into compensation.

5. Put it where the work is

A recognition program that lives in its own portal is a recognition program people forget. Put it in the chat tool the team already has open. The post on setting up recognition in Slack walks through channel rules, prompts and a launch plan; the same logic applies to Microsoft Teams.

6. Launch it like a habit, not an announcement

An announcement produces a spike. A habit needs a first month of visible use by leaders and managers, a weekly nudge to anyone who has not given recognition, and a monthly recap that shows the team what was recognised. The step-by-step guide to creating a program covers the launch sequence in detail.

7. Review who is left out

Every quarter, look at who has not been recognised and who has not given recognition. Those two lists tell you more than any total. The section on measuring, below, says what to look at. The post on why recognition programs fail lists the ways programs stall, and almost all of them are visible in those two lists three months before anyone notices the channel has gone quiet.

For examples of programs that have lasted, see the five companies with the best employee recognition programs.

What to say

The hardest part of recognition for most people is the sentence. They know the colleague did something worth noticing and cannot find words that do not sound like a greetings card.

The fix is a rule: name the thing, then say what it changed. “Thanks for the great work on the launch” names nothing. “You caught the pricing bug in the release notes the night before launch, and we shipped clean” names a thing and a consequence, and only one person on the team could have received it.

Length matters less than people think. One to three sentences is usually right. Past four, most recognition starts restating itself.

Tone should match the relationship. A one-line note from a peer reads as warm. The same line from a manager on a ten-year anniversary reads as an afterthought.

The example messages on this site are written to that rule, grouped by occasion. Each one carries a note on why it works, because the reasoning is the transferable part.

For shorter formats, the posts on thank-you note templates and coworker shoutouts have examples for Slack, meetings and email. The 35 recognition ideas cover the non-verbal ones.

Recognising values as well as results

Results are easy to recognise because they are already counted. Values are harder, because “ownership” or “collaboration” on a wall does not tell anyone what to look for.

The way through is to describe each value as behaviour you could observe. Ownership looks like somebody chasing a problem into another team rather than filing it and considering the job done. Candour looks like somebody saying a date will slip in week two rather than week six. Once a value is written that way, recognising it is the same act as recognising a result: you saw a thing, you name it.

This is also where recognition does its quiet work on culture. A company whose recognition channel is full of results teaches people that results are what count. One whose channel names behaviours teaches people how the results are supposed to be produced. Tagging each recognition with the value it expresses, which Evergreen does, turns the channel into a record of which values are actually alive.

The post on building a culture of recognition covers the habits that make this stick, and the one on how recognition supports DEI covers what happens when recognition is spread fairly and what to check when it is not.

Recognition for your kind of team

The principles do not change from one team to another. What changes is what gets in the way. A remote team never shares a room, so recognition has to be written down or it does not happen. In a support team, the best work is a problem that never became a ticket, which nobody sees. Hospital wards run on shifts that rarely overlap. Sales teams already have a leaderboard and need recognition to cover everything the leaderboard does not.

The guides below take one kind of team each and work out what recognition looks like there: the specific obstacles, the habits that have worked, example messages written for that context, and a program shape that fits.

For teams that have gone remote or hybrid, the posts on virtual recognition ideas and on moving a program from in-person to virtual cover the transition.

Measuring employee recognition

The easiest number to collect is the total count of recognitions, and it is the least useful. A total goes up when people are recognising each other well and also when two people trade compliments every morning. It cannot tell the two apart.

Four measures can.

Participation rate: the share of people who gave at least one recognition in the period. This is the health of the habit. When it falls, the program is about to go quiet.

Reach: the share of people who received at least one recognition in the period. This is who the program is for. A program with high participation and low reach is a small group recognising itself.

Distribution: the gap between the most and least recognised people, and whether it lines up with role, location or team. The people at the bottom of this list are usually the ones whose work is invisible until it fails, and they are the people the program was supposed to catch.

Timing: the delay between the thing happening and the recognition. Recognition given the same day lands; recognition saved for a monthly meeting reads as an obligation met.

And then read the messages. A program can hit all four numbers and still be producing “great job, team”. A sample of twenty recognitions a month, read for whether each one names something specific, is the quality check no dashboard replaces. The post on recognition metrics that do not create bad incentives goes through each measure and the ways it can be gamed.

Where recognition happens: Slack and Microsoft Teams

Recognition happens where attention already is. For most companies that is a chat tool, which is why the recognition programs that survive their first quarter tend to be the ones that live inside Slack or Teams rather than beside them.

The tool’s job is small and specific: make recognition take a minute, make it visible to the team, remind people who have gone quiet, and keep a record so that reach and distribution can be reviewed. Anything beyond that, points economies, catalogues, leaderboards, should earn its place by making recognition better rather than by making the tool bigger.

Evergreen does the small job and adds one thing: every three seeds a person receives plants a real tree. It gives recognition a consequence in the world without turning it into pay, and it gives the company an impact figure it can publish.

The vocabulary

Recognition has picked up a vocabulary from HR, from vendors and from research, and the terms are used loosely. The ones below come up most on this site. Each links to a fuller definition.

Where to start

If you have read this far and have nothing in place, do three things this week. Pick one behaviour you want to see more of and write it down as something you could observe. Recognise one colleague for it, specifically, where the team can see. And notice who on your team has not been thanked for anything in a month, then fix that.

Everything else on this page is what to build once that habit exists. The reading list below is arranged by the question each article answers.