Recognition Campaigns: 5 Ready-Made Scenarios for the Year Instead of 'Thanks Team' in the Chat

The year-end "thanks team" boils down, nine times out of ten, to one post in the chat channel under the CEO's name. The team reads it to the end, drops a heart, and forgets it. By January 10, no one remembers the post. That's not a recognition campaign — it's a box-ticking gesture. You can do better, and it's no more expensive.

December is the best month for a recognition campaign: the year is done, there's something to discuss, and there's an energetic occasion. But at most companies that occasion is wasted — on the holiday party, on a group email, on "5,000 points for everyone" style gifts. We've seen dozens of attempts at a "December recognition campaign," and only a few worked. Let's break down how to run one that works — without an agency budget and without buying new software.

A Campaign vs the Everyday Flow — Two Different Things

First, a quick discipline on terminology.

The everyday flow is peer-to-peer thank-yous throughout the year: colleagues thanking colleagues, managers thanking reports, with no special occasion, in the moment. This flow runs constantly and meets the baseline need for recognition.

A campaign is a short (1–3 weeks) focused event around a specific occasion, with a clear theme, a deadline, and a visible ritual payoff. A campaign has a beginning, a middle, and an end — it isn't smeared out.

Why you need both. Flow without campaigns is water without a stream: everything moves, but nothing accumulates into events. Campaigns without flow are rare fireworks in the dark: bright, but forgotten within a week. A healthy recognition culture rests on their balance: 80% of the energy is the everyday flow, 20% is 4–5 campaigns a year.

Now — which campaigns work.

Five Ready-Made Scenarios for the Year

#1. Quarter close. Theme: "who helped us close Q4 — across team boundaries." Duration: 2 weeks after quarterly results are announced. The focus is on cross-team contribution: the 5–10 people from other departments who quietly helped your team close its OKRs and are usually forgotten. Run once a quarter, four times a year, and it becomes a ritual.

#2. New Year cycle. Duration: 3 weeks in December. The theme is annual, usually specific to the company's culture: "Thank you for the strongest moment of the year," "The most unusual 'thank you' I want to say." Unlike the usual December correspondence, the campaign gathers all these thank-yous in one place and ends with a ritual — for example, a group email on December 31 with excerpts of the best ones.

#3. Successful release. Duration: 1 week right after a major release or project close. The theme is the "positive post-mortem" (analyzing success instead of failure): instead of the classic "what went wrong," the team does the reverse exercise — "who unblocked things, who carried the load, whose 30 minutes saved a week." This works especially well in engineering and product teams, where the focus is usually only on problems.

#4. Anniversary. Duration: 3–5 days. Occasions: a round tenure milestone (5/10 years), a department or product anniversary, the company's founding date. The focus is on one person or one team, with participation from everyone who crossed paths with them. Don't turn it into a perfunctory "Ivan's been with us 5 years, congrats" — gather 10–15 short stories from colleagues with specific memories.

#5. Soft launch of a new role or structure. Duration: 2 weeks. Run during significant organizational changes: a new manager, a new team, a new area of responsibility. The goal is to help people in new roles integrate, and to explicitly support those who help them get up to speed. This greatly eases organizational changes, which usually come with anxiety and sabotage.

These five scenarios are enough for most companies. Don't try to run a campaign every month — the campaign will get devalued, and the flow will live in its shadow.

Building a Campaign in 30 Minutes

Many people think a recognition campaign is a complex project requiring a quarter of HR's time. It isn't. The basic build takes 30 minutes.

Step 1 — the theme (5 minutes). Narrow, specific, with a time horizon. "Who helped us with release X," not "thanks for everything good." A narrow theme provides clarity: whom to praise and for what.

Step 2 — the kickoff post (10 minutes). From the HRBP, the team lead, or the event owner — not from the CEO as an impersonal company voice. A good kickoff: 3 sentences explaining the theme, 1–2 examples of a good thank-you, and an explicit invitation to participate. Don't write "it's important to us that…" and "we value…"; write concretely.

Step 3 — the cadence (10 minutes). One reminder post mid-campaign, around day 5–7: "here are the 3 best thank-yous that have come in so far" — this both sustains interest and models the format. No more than two reminders for a 2-week campaign, otherwise it becomes spam.

Step 4 — the close (5 minutes). The most important and most often skipped step. A digest of the best thank-yous, a public thank-you to all participants, an explicit end point. Without a close, the campaign turns into a gradually fading feed — and next time people treat it skeptically.

That's it. 30 minutes of net time from the HRBP or team lead, no budget and no CEO sign-off.

Antipatterns That Kill Campaigns

We've seen enough campaigns that don't work to single out a short list. If you recognize yours, it's worth a rethink.

"Thanks to HR from the CEO" as the only post. That's not a campaign, it's a news item. If the CEO wants to take part — great, but a top-down flow doesn't, by itself, kick off peer-to-peer.

A campaign with no deadline. "Let's all just thank each other more from now on" isn't a campaign, it's a wish. Without a deadline there's no focus, no closing ritual, and the flow smears out.

A vague "thanks for everything" theme. If you can thank people for anything, it's harder for them to start, because they don't know what counts as appropriate. A narrow theme lowers the barrier to entry.

Forcing participation. "Every employee must write at least 3 thank-yous by Friday" burns trust in the whole system. Better 30 sincere ones than 300 perfunctory ones.

Recognition with money attached. If every "thank you" earns points convertible to a bonus, the campaign turns into bargaining. If you want to give a bonus, give it explicitly, not through recognition.

Only one scenario a year. If you only do the New Year cycle, the campaign becomes "the mandatory December tree." At least 3 different scenarios a year, otherwise the seasonal tie-in kills the freshness.

How to Measure the Effect

The most common mistake is measuring the number of thank-yous. That metric is easy to inflate: you can ask managers to write more, and the number goes up. A campaign's real effect is measured differently.

Quantitative metrics.

• Unique participants (not the total number of thank-yous). How many people wrote at least one. The target is above 50% of the campaign's potential audience.
• % of new senders. How many people who never wrote thank-yous in the portal before wrote their first during the campaign. This shows whether the campaign is expanding the base.
• Distribution across departments. If thank-yous concentrate in one or two departments, the campaign isn't cross-team.

Qualitative metrics.

• A post-campaign survey (3 questions, 2 minutes): "Were you recognized in this campaign?", "Did you find the campaign useful?", "What would you change?"
• A retention check at 30 and 60 days. Especially for those who received recognition for the first time. Per Workhuman, peer recognition has a measurable effect on retention within 90 days.

Anti-metric. "Total number of thank-yous." Don't use it as your headline — it's misleading and creates an incentive for fake participation.

The Bottom Line

A recognition campaign is a short, focused event that amplifies the everyday flow of peer recognition — it doesn't replace it. Five ready-made scenarios for the year plus the everyday flow is the healthy structure of a recognition culture. 30 minutes to build a campaign, no budget and no new software.

And, in short: "thanks team from the CEO in the shared chat" is a post, not a campaign. Don't confuse them. And don't write that post on December 31 unless you want the team to smile once and forget.

Next, we'll dig into eNPS — how to calculate it correctly, what to show the CEO, and why 40 isn't "excellent." The most popular and, at the same time, most frequently confused metric in HR.

If you want the ready-made playbook of 5 campaigns with kickoff-post templates and closing rituals, it's linked in the card. No signup, in Google Docs, copy it and adapt it to your company.