Peer recognition dies the moment it needs its own app

Most recognition programs start with good intentions and a real budget. A kudos channel gets created, a points system gets explained in an all hands, someone builds a nomination form for the quarterly award. Six months later the channel has gone quiet and the form has three responses, two of them from the person who built it. The actual thank yous never stopped. They just moved back to where they were before the program existed, in a DM, in a passing comment before a meeting, in a reaction nobody is counting.

Where recognition programs go to die

The pattern repeats often enough that it's worth naming plainly. A few habits show up again and again in teams whose recognition efforts fizzled out:

• Recognition only flows one direction, from manager to report, so peers who see the actual work never get to weigh in.
• The tool that tracks it lives somewhere nobody opens unless HR sends a reminder email.
• Giving credit requires a form, a dropdown, a reason field, so the two seconds it takes to notice good work turns into a two minute chore.
• The record and the work are in different systems, so nobody connects a shipped fix to the praise it earned.

None of these are failures of character. They're friction, and friction wins over good intentions almost every time.

The moment that actually mattered

Think about the last time you genuinely appreciated something a teammate did. A gnarly bug got fixed at eleven at night. Someone caught a mistake in a deploy before it went out. A teammate covered a shift with no drama. In each case, the appreciation showed up right there in the thread, a reaction, a quick reply, sometimes just an emoji that meant more than it looks like it should. That instinct is the real recognition program. It already runs, for free, without anyone scheduling it.

The formal program asks you to take that instinct and re-enter it somewhere else, later, in a different tab, once the feeling has already faded. Most people do it once, for the launch announcement, and then quietly stop.

Letting the reaction be the record

Viably's medal leaderboard starts from the assumption that the reaction is already the recognition, so the system shouldn't ask for a second one. React to a message with ++ and the person gets a point, tagged with whatever attribute fits, shipped fast, helped a teammate, caught a bug before it landed. React with -- and it goes the other way, useful for tracking recurring friction as honestly as recurring wins. Nothing about the workflow changes. The habit that already existed just stops evaporating.

Over a few weeks, that adds up to something a manager could never produce from memory alone:

🥇  @samuel                      77 ██████████  Just now
🥈  @evelyn ong                  52 ███░░░░░░░  13 hours ago
🥉  @aurelliachristie             41 ██░░░░░░░░  9 hours ago
4.  @mulia                       31 █░░         4 days ago
5.  @calvin                      13 █░░         >1 week ago

It isn't a leaderboard in the competitive sense, though it can be read that way if a team wants that. It's closer to a ledger of who kept things moving when nobody was measuring it, made visible without asking anyone to fill out a form to earn their place on it.

Recognition that has to be logged twice mostly doesn't get logged the second time.

Why it has to stay inside the workspace

A recognition tool that lives apart from the work competes for attention against everything else on someone's screen, and it loses. The version that works is the one that was never really a separate tool at all, just a second meaning attached to a reaction people were already sending. Recognition that has to be remembered gets forgotten. Recognition that rides along with the work it's rewarding doesn't need remembering.

If your team's version of a thank you already lives in a Slack reaction, add Viably and let it start counting, or read more about how the medal leaderboard works.