Recognition tools vs. habit campaigns: different jobs

Good work disappears. Someone stays late to unblock a launch, covers a colleague through a bad week, or sits patiently with a new joiner while they learn the codebase. The work leaves no trace beyond the memory of the people who happened to see it, and memory is a poor record.

A recognition tool gives that work a record, a witness and a manager's attention. It also fixes a fairness problem that gets worse as a company grows: without structure, recognition flows to whoever sits closest to the person handing it out, or to whoever is loudest about their own contribution. A prompt with a name field and a public wall nudges the distribution flatter, and at two hundred people no founder can see enough of the work to do it manually.

So this is not a category to talk anyone out of. Recognizing above-and-beyond individual work is a real job, and recognition tools do it well. The mistake is assuming that a tool shaped around the exceptional case can also carry a campaign about the ordinary one.

A habit campaign asks about things too small to be achievements. Whether you took a walk at lunch. Whether you drank water between calls. Whether you thanked someone for something minor. If those actions get put on the same wall as exceptional work, one of two things happens: either the currency of recognition inflates until it means nothing, or the small actions quietly stay off the wall and out of the campaign.

The structural difference matters more than the feature list. Recognition is event-driven, individual and retrospective: it answers who did something notable this month. A habit campaign is cadence-driven, collective and forward-looking: it answers whether the whole team is still doing the small thing a few weeks in, including the people who will never win an award.

Stretch one tool into the other and you get a pattern most People teams will recognize. The same five names occupy the top of the wall, everyone else reads it and stops posting, and the campaign looks like it failed when it was really just wearing the wrong shape.

Running both is normal and sensible. The question is where the habit campaign lives, so that it does not inherit the recognition tool's incentives.

The specific risk is currency. If the points that count a walk can also be redeemed for something of value, the walk becomes an earning scheme. People start comparing the small action against the reward, someone optimizes the logging, and the people who joined because it felt like a team thing quietly leave. A counting system that cannot be spent, and that only ever moves one number for the whole group, avoids that without asking anyone to trust a promise about fairness.

The second choice is placement. A recognition tool is somewhere people visit when something notable happens. A habit campaign needs to be somewhere people already are, every day, in the flow of ordinary work. If logging the action requires opening a second application, the campaign is competing with the job rather than living beside it.

And keep the recognition tool. A habit campaign is a poor substitute for it in the other direction: small daily actions do not make up for a team whose exceptional work goes unrecorded all year.

Feature lists make everything look interchangeable. Both shapes will advertise points, both will advertise rewards, both will advertise Slack integration. What separates them is what they are for.

• The job: make extraordinary work visible, versus make an everyday action normal.
• The unit: one person's moment, versus the whole team's total.
• The cadence: triggered by an event, versus repeated every day for a fixed window.
• Success: nothing notable goes unrecorded, versus more people taking part in week three than in week one.
• The pull it creates: wanting to be seen, versus wanting the team to get there.
• The failure signal: the same names every month, versus a channel that has gone quiet.

The most common bad outcome is not picking the wrong category. It is buying the largest suite so that no category is left out, then running one campaign a year inside it and wondering why it feels like a compliance exercise. Recognizing exceptional work and normalizing a small daily action are two jobs, and naming which one you are doing this quarter is most of the decision.

Before comparing products, write the answers to these questions down. If two people on the buying team answer differently, no tool will resolve it.

• What behavior are we trying to make ordinary, in one sentence?
• Who has to take part for this to feel like a team thing, and what would make that group opt out?
• Does the reward belong to the team or to a winner?
• Can someone take part in under a minute without leaving the tool they already use?
• What will we look at on day 30, and what will we do if that number is bad?
• If we switched it off next quarter, what would still be normal?