Is public or private recognition better?

Public, as a default, because it also teaches everyone watching what is valued. Private, whenever the person prefers it or the message concerns something they would not want discussed. Asking once removes the guesswork.

Do some employees dislike public recognition?

Yes, a meaningful minority. Some find being named in front of a large group uncomfortable regardless of the content. Recognition that makes the recipient wince has failed, however well intended, so find out before the first time.

Can recognition be both public and private?

Often the best version is. A short public message that names the work, followed by a longer private one with the detail and the personal note. The public one teaches the room; the private one is the one that gets kept.

Recognition glossary

Public versus private recognition

Public recognition is delivered where colleagues can see it, such as a channel or a meeting; private recognition is delivered to the recipient alone. Each has effects the other lacks, and the right choice depends on the person and the message.

The same sentence does different work depending on who else can read it. Choosing the audience is part of writing the message.

What each one does

Public recognition has an audience, and the audience learns. A message in a channel saying that a support agent’s write-up changed the roadmap tells the agent she was seen, and tells everyone else that write-ups are how support influences product here. That second effect is the whole argument for social recognition, and it does not exist in private.

Private recognition has no audience, and that is its advantage. It can be longer, more personal and more candid. It can address something the person would not want raised in front of colleagues. And it lands differently: a private message has no performative element, so the recipient does not have to wonder whether it was for them or for the room.

The case for public by default

Recognition is information about what the company values, and information that only one person receives does not change the culture. The team that never sees anyone thanked for behind-the-scenes work concludes that such work is not valued, whatever private messages are being sent. Public recognition is also visible to the recipient’s manager, who may not otherwise have known, and it creates a record.

The Slack recognition post on this site is largely an argument for putting recognition in the channel people already read, for exactly these reasons.

The case for asking

A minority of people find public praise uncomfortable regardless of content. Some cultures, professional and national, treat individual praise in front of the group as inappropriate. Some people have had bad experiences of being singled out. None of this is unreasonable, and recognition that makes the recipient wince has failed.

The solution is one question, once, early: “When you do something worth mentioning, would you rather I said so in the channel or told you directly?” Most people will say the channel. The ones who say directly will remember that you asked.

Getting the public version wrong

Public recognition amplifies mistakes as well as praise. The commonest is misattribution: praising one person in front of the team for work that others did, or did most of. The person praised is embarrassed, those not named are resentful, and both effects last. When the work was shared, name everyone or name the team. When unsure who did what, ask before posting.

The second is imbalance. Public recognition that goes repeatedly to the same people is recognition bias performed in front of an audience, and the audience notices. Private recognition can be uneven without anyone knowing; public recognition cannot.

Both

The strongest version is frequently the combination. A public line naming the work, so the room learns. A private message with the detail, the effect and the personal note, so the person has something to keep. The public one is for the culture; the private one is for them.

What it looks like

Public: a product manager posts in the company channel that a support agent’s write-up of a recurring complaint led directly to a fix shipping this week. Forty people learn that support write-ups change the roadmap.
Private: a manager messages a report who has said she dislikes being singled out, describing exactly what she did on the migration and why it mattered. She screenshots it and keeps it.
Wrong choice: a manager praises a junior engineer at length in the all-hands for work the engineer knows was mostly done by a colleague who was not named. The engineer is embarrassed; the colleague is angry.

Questions people ask

Is public or private recognition better?: Public, as a default, because it also teaches everyone watching what is valued. Private, whenever the person prefers it or the message concerns something they would not want discussed. Asking once removes the guesswork.
Do some employees dislike public recognition?: Yes, a meaningful minority. Some find being named in front of a large group uncomfortable regardless of the content. Recognition that makes the recipient wince has failed, however well intended, so find out before the first time.
Can recognition be both public and private?: Often the best version is. A short public message that names the work, followed by a longer private one with the detail and the personal note. The public one teaches the room; the private one is the one that gets kept.