Social recognition

The audience is the mechanism

Recognition given in private does one thing: it tells one person their work was seen. Recognition given in a channel does that and then several other things at once. It tells the recipient’s manager, who may not have known. It tells the recipient’s colleagues what kind of work earns thanks here. It tells the person scrolling past at eleven at night, who has been quietly doing similar work, that there is a chance of being noticed.

That second set of effects is what the term social recognition points at. The praise is the same; the broadcast is what changes.

Where it came from

The phrase arrived with the tools. Company intranets in the 2000s added “wall” features that let staff post thanks, and the vendors that grew out of them needed a term for what the wall did that the old service-award scheme did not. Social recognition was the answer, borrowing the “social” from social media, which was becoming the model for how a feed of small acknowledgements might feel.

Chat tools finished the job. Once the whole company was already reading the same channels all day, a recognition post no longer needed its own destination. It could sit between the deploy notification and the lunch order, which is where the Slack-based programs put it.

What it does well

It surfaces behind-the-scenes work. Work that produces no artefact, such as the incident that did not happen or the handover that went smoothly, has no natural way to be seen. A colleague writing it down in public gives it one.

It also builds a record. A year of social recognition in a searchable channel is a history of who did what, written by the people who were there, and it is more useful in a review than anything reconstructed from memory.

What it does badly

Volume without variety. A feed that fills up with the same five names becomes a leaderboard, and leaderboards make everyone else feel worse. Whether a feed is working shows in its reach rather than its length.

Reactions as a substitute for content. A post with forty emoji reactions and no detail is a signal that something happened, and nobody reading it a month later can say what. The message has to name the thing before the audience can learn anything from it.

And it does not suit every message. Some feedback belongs in private, and the public versus private choice deserves a moment of thought each time rather than a default.