Kudos Kickoff

It measures recognition.given events, counted as the number of peer recognitions a person sends during the contest window. The standings are based on verified system actions, not manual tallies or self-reported activity. That makes it a clean fit for a recognition relaunch or culture campaign where you want to reward people for noticing good work out loud.

This is usually run by HR, People Ops, Internal Comms, or a culture program owner. A team lead can also run it if the goal is to spark participation inside one department. Because the contest is opt-in and individual, it works best when the organizer can explain the rules clearly and keep the tone appreciation-first.

This template is designed for a 14-day burst, which is long enough to build momentum without turning recognition into a permanent leaderboard. It works well as a relaunch, a quarterly culture nudge, or a short campaign tied to onboarding or manager training. If you run it too often, people may start gaming the cadence instead of giving genuine kudos.

Yes, because it is an individual contest rather than a team contest, so team size does not distort the standings. That said, it still rewards volume, so it is best for a population where everyone has a reasonable chance to participate. If you need fairness across very different work patterns, consider pairing it with participation messaging or a separate most-improved format.

The template does not exclude managers, so they can join if that fits your culture. In some organizations, keeping managers in the contest helps model the behavior and normalize peer recognition. In others, you may want to set a separate internal rule so the campaign feels peer-led rather than top-down.

The biggest mistake is rewarding raw volume without any guidance, which can lead to low-quality or repetitive kudos. Another common issue is making the contest too long, which turns it into background noise instead of a focused campaign. It also helps to avoid vague rules and to explain that only verified recognition events count.

This template uses points as the prize type, so you can award points to the top finishers or convert them into your own reward structure. The default ranking is highest score, which fits a simple most-recognitions-given race. If you want a softer rollout, you can keep the standings but frame the prize as bragging rights or a small appreciation reward.

Yes, that is the main use case. The contest is built around recognition.given events, so it naturally sits on top of an existing recognition workflow rather than replacing it. That makes it a good icebreaker for a relaunch because people can participate using the same behavior they already know.

An ad-hoc leaderboard usually runs forever and can quietly discourage participation once the same people keep winning. This template has a fixed 14-day duration, clear scoring, and a defined prize structure, so it behaves like a contest instead of a permanent ranking. The time box is what makes it feel like a campaign people can actually join.