Recognition that only happens in December isn't recognition. It's paperwork.

There's a story that gets told in People teams sometimes, as a cautionary tale.

A high-performing engineer stays up until 2am to fix a production issue that would have cost a major customer. They fix it. They write up what happened. They hand it off. The next day, they get a "thanks" in Slack and life moves on.

Six months later, their annual performance review comes around. The manager writes "strong technical judgment and commitment" in the review form. The engineer reads it and doesn't feel much. The moment that mattered was six months ago. This feels like a box being ticked.

Two months after the review, the engineer leaves. In their exit interview they say they didn't feel valued.

Why annual recognition fails.

The problem with annual recognition is not that it's insincere. Most performance reviews are written by managers who genuinely mean what they say. The problem is timing.

Recognition works when it's connected to the thing being recognised. The closer to the moment, the more it registers. A "this was excellent and here's why" the same week something happens lands completely differently from the same words written six months later as part of a templated review process.

This is not complicated psychology. It's how appreciation works in every other context. A birthday card that arrives a week late still counts, but it's not the same as the one that arrives on the day.

The recognition that disappears.

The most common alternative to the annual review is the Slack shoutout. Someone does something good, a manager or colleague notices, they post in the team channel: "Huge thanks to Priya for saving the launch last night."

Priya sees it. A few people react with a thumbs-up. By tomorrow it's scrolled off the screen. By next week it's gone.

The intention was right. The execution was real. But it evaporated.

The problem with Slack recognition is that it has no memory. It happens in a feed designed for ephemeral communication. There's nowhere for it to live - no profile it attaches to, no record it builds, nothing that accumulates over time into a picture of what this person contributes and is known for.

What recognition looks like when it compounds.

Recognition that works is recognition that stays.

When a shoutout is tied to a company value - not just "great job" but "great job, and this is exactly what 'customer first' looks like in practice" - it does more than make one person feel good. It signals to the whole company what the values actually mean in day-to-day work. Values alignment stops being a slide in the all-hands deck and becomes something people can point to.

When a shoutout appears on someone's profile - visible to anyone who looks them up, part of the picture of who they are in this company - it accumulates into something meaningful. It's not just "Priya is great." It's "Priya has been recognised fifteen times in the last year, predominantly for technical excellence and cross-team collaboration, and here's the pattern."

When a manager can see, before a 1:1, that this person hasn't been publicly recognised in three weeks - that's a nudge to change something, not a discovery made during an annual review.

Culture is what you repeat.

Culture is not what a company says it values. Culture is what a company repeatedly does. And repeated recognition - timely, specific, tied to the things that matter - is one of the most powerful tools for making a culture real rather than aspirational.

The companies that are genuinely good at this don't have more caring people. They have better systems. Recognition is easy, it's frequent, it's connected to the values they actually want to reinforce, and it doesn't evaporate at the end of the day.