Loading...
culture

Kindness Rush

Kindness Rush is a 7-day department contest where the first team to reach 100 peer recognitions wins. It turns everyday appreciation into a fast, visible sprint with points for the top finishers.

See it in MangoApps

Trusted by frontline teams 15 years of frontline software

Built for: Healthcare · Retail · Saas · Manufacturing · Education

Overview

Kindness Rush is a team contest template for running a short, high-energy peer recognition sprint. The structure is simple: departments compete to be the first to reach a target number of recognition.given events, and the winning team earns points or another configured prize. Because the scoring is based on verified platform actions, it avoids the ambiguity of manual tallying and keeps the contest focused on real appreciation behavior.

Use this template when you want to create a burst of positive visibility around recognition, especially during culture campaigns, onboarding pushes, manager engagement efforts, or seasonal morale lifts. It works best when departments are large enough to generate recognitions quickly and when you want a clear finish line rather than an open-ended leaderboard. The 7-day duration fits the natural cadence of an episodic contest and helps keep momentum high.

Do not use this exact setup if you need size-adjusted fairness across very uneven teams, if you want a cooperative all-hands goal instead of a race, or if your program requires a different verified action such as safety inspections or course completions. It is also not the right fit for manual external KPIs like sales or fundraising. The template is strongest when the behavior you want is simple, visible, and already tracked by the platform.

Standards & compliance context

  • Because scoring is based on verified recognition.given events, the template supports Goodhart-resistant measurement better than manual self-reporting.
  • This contest is designed as a short episodic program, which aligns better with workplace gamification research than an always-on leaderboard.
  • If your organization has works-council or employee-representation requirements, keep the format cooperative in tone and avoid punitive public ranking of individuals.
  • Use department teams rather than individual ranking if the goal is to encourage shared participation instead of singling out employees.
  • Do not repurpose this template for regulated metrics or external KPIs unless the scoring model is changed to match the data source and governance rules.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

How to use this template

  1. 1. Confirm the contest target, duration, eligible departments, and prize before launch so everyone understands how the race will be won.
  2. 2. Invite the participating departments and make sure recognition.given is the only scoring action tied to the contest.
  3. 3. Publish the start announcement with the target value, the 7-day window, and a reminder that only verified peer recognitions count.
  4. 4. Monitor standings during the week and share progress updates that encourage participation without pressuring teams to game the system.
  5. 5. Close the contest when a department reaches the target, award points to the ranked finishers, and review whether the target and cadence felt realistic.
  6. 6. Capture any rollout notes, such as participation gaps or unclear rules, so the next Kindness Rush can be tuned more cleanly.

Best practices

  • Keep the target high enough to feel like a sprint, but low enough that at least one department can realistically finish within the 7-day window.
  • Use department-level teams only when the groups have similar headcount or similar access to recognition opportunities.
  • Make the rules explicit about what counts as a recognition so participants do not try to stretch the definition.
  • Share standings during the contest to build momentum, but avoid public callouts that shame teams trailing behind.
  • Encourage authentic recognition tied to real work moments rather than generic praise posts.
  • Treat this as an episodic contest, not a permanent leaderboard, so the behavior stays fresh and meaningful.
  • Review the number and quality of recognitions after the run to spot whether the target encouraged genuine participation or rushed submissions.

What this template typically catches

Issues teams running this template most often surface in practice:

The target is set too high for a 7-day window, so the contest loses energy before anyone can finish.
One large department dominates the race because the template is not normalized per-capita.
Participants post low-quality or repetitive recognitions when the rules do not define what a valid recognition looks like.
Managers forget to announce the contest in enough channels, so only a small subset of employees participates.
Teams treat the contest like a leaderboard and stop engaging once they fall behind.
The organizer realizes too late that the chosen prize is not motivating enough to sustain participation.
Recognition volume rises, but the content is generic because the contest did not include examples of specific, work-based appreciation.

Common use cases

HR Culture Lead: Department Appreciation Sprint
An HR lead launches Kindness Rush across several departments during Culture Week to create a short burst of peer recognition. The goal is to make appreciation visible without asking managers to manually track shout-outs.
Retail Operations: Store Team Morale Push
A regional operations manager uses the template to encourage store teams to recognize helpful shifts, customer saves, and cross-coverage. The department race format keeps the contest simple for frontline staff.
Healthcare Admin: Unit-to-Unit Recognition Challenge
A hospital administrator runs the contest across administrative units to reinforce gratitude during a busy season. The verified recognition count keeps the program easy to audit and easy to explain.
SaaS People Team: Onboarding Month Engagement
A people team uses Kindness Rush during onboarding month to prompt new hires and managers to recognize helpful peers. The short duration makes it easy to fit into a broader culture calendar.

Frequently asked questions

What is Kindness Rush designed to measure?

It measures verified peer recognition events, specifically recognition.given actions inside the platform. The template counts how many recognitions a department gives during the contest window, and the first team to reach the target wins. It is meant to reward visible appreciation, not vague sentiment or manual scoring.

Who should run this contest?

A culture lead, HR partner, or department manager can run it, as long as they can announce the rules and monitor progress. The organizer should confirm the target, duration, and eligible teams before launch. Because the scoring is automatic, the main job is communication and follow-through.

How often should Kindness Rush run?

This template is built as a short episodic contest, so a 7-day run is the natural cadence. It works best as a periodic burst rather than an always-on leaderboard. Running it too often can make recognition feel forced, so leave enough time between rounds for the behavior to stay genuine.

Is this fair for departments of different sizes?

As configured, it is a raw first-to-target race, so larger departments may have an advantage because they can generate more recognitions faster. If you need fairness across mixed-size groups, consider changing the format to per-capita or using team normalization. For this exact template, it fits departments with similar headcount or a culture where speed matters more than size.

Can I use this for safety, sales, or other metrics instead of recognition?

Not without changing the template structure. Kindness Rush is built for the recognition.given action, so it should stay focused on appreciation behavior. If you want to run a sales or safety contest, use a template that matches those verified actions or use manual mode only for external KPIs the platform does not track.

What are common mistakes when launching this contest?

The biggest mistake is setting the target too high for the time window, which makes the contest feel impossible. Another common issue is unclear eligibility, such as not saying which departments can enter or whether self-recognition counts. It also helps to avoid public shaming of teams that fall behind, since the goal is positive participation.

Can we customize the prize and scoring?

Yes. The template uses points as the prize type, but you can adjust the reward structure to fit your culture program. You can also change the target value, duration, and eligible team scope, while keeping the core mechanic of verified peer recognitions.

How does this compare with an ad-hoc appreciation challenge?

An ad-hoc challenge usually depends on manual tracking, inconsistent rules, and unclear finish conditions. Kindness Rush gives you a defined target, a fixed duration, and automatic scoring from verified recognition events. That makes it easier to launch, explain, and repeat without reinventing the rules each time.

Go deeper on the topic

Related concepts
  • Recognition is the practice of naming specific good work so it gets seen, remembered, and repeated. It is separate from reward (money, points, prizes) and...
  • An employee recognition program is a structured practice for acknowledging good work — peer-to-peer, manager-to-report, or public — often supported by...
  • Engagement is the observable connection between an employee and their work — how much discretionary effort they're putting in, how likely they are to still...
  • Feedback is the practice of giving and receiving information about work — what's going well, what isn't, what should change. At scale, it takes the form of...
Related guides

Ready to use this template?

Get started with MangoApps and use Kindness Rush with your team — pricing built for small business.

Get Started