Two specific recognitions per manager, per week
A 90-day plan to help each manager deliver two specific employee recognitions per week, while tracking recognitions per 100 members to verify sustained adoption.
Trusted by frontline teams 15 years of frontline software
Built for: Retail · Hospitality · Customer Service · Warehousing And Logistics · Healthcare Operations
Overview
This operational improvement plan turns a broad recognition goal into a measurable manager habit: each manager delivers two specific recognitions per week. The template defines recognition as the tracked activity, uses recognitions per 100 members as the primary metric, and provides a 90-day measurement window for checking whether adoption changes over time.
Use it when frontline managers have regular contact with employees but recognition is inconsistent, overly generic, or difficult to compare across teams. Start with a baseline, prompt managers at a predictable point in the week, capture the recipient and the specific behavior or result, and review the normalized metric rather than relying only on anecdotal feedback. The suggested target is a 100% increase from baseline, but the target should be adjusted for team size, seasonality, and current recognition volume.
This is not a compensation, performance-rating, employee-relations, or disciplinary template. Do not use recognition counts as the sole measure of manager quality or employee value. It is also not appropriate to manufacture praise, recognize protected characteristics, or reward behavior that conflicts with safety, service, attendance, or employment policies. Pair the plan with qualitative review so high activity does not mask low-quality or uneven recognition.
Standards & compliance context
- Keep recognition language job-related and consistent with applicable equal employment opportunity and anti-discrimination requirements.
- Do not require employees to disclose health, family, disability, immigration, or other sensitive information to receive or validate recognition.
- Follow applicable privacy and employment-record policies when storing recipient names, recognition text, timestamps, and manager activity.
- Have HR review whether recognition data may influence performance, promotion, compensation, or disciplinary decisions before linking the plan to those processes.
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
- Set the baseline by counting valid recognitions and active members for a defined pre-launch period, then calculate recognitions per 100 members.
- Configure the weekly prompt for every participating manager and define the required recognition fields, including recipient, date, and specific behavior or result.
- Assign each manager a weekly target of two recognitions and have them record each one immediately after the interaction or observation.
- Review submissions at the end of each week for missing entries, duplicate records, generic wording, and uneven participation across teams.
- Calculate recognitions per 100 members at the agreed cadence and compare the result with the baseline and target without changing the metric definition midstream.
- Discuss quality and distribution with managers, correct gaps, and decide whether to continue, refine, or extend the plan after the 90-day review.
Best practices
- Define a valid recognition as a specific description of an observable behavior, contribution, or result rather than a generic compliment.
- Prompt managers at the same point each week and provide a short example that shows the expected level of specificity.
- Photographing defects is not relevant to this plan; instead, record recognition close to the moment the contribution is observed so details are accurate.
- Check that recognition opportunities are distributed across the team rather than repeatedly directed toward the most visible employees.
- Separate recognition volume from performance ratings, pay decisions, and disciplinary records so employees are not pressured to participate.
- Review both the normalized rate and the underlying counts, member roster, manager participation, and seasonal context before interpreting movement.
- Audit a sample of entries for specificity and respectful language instead of assuming that every submitted recognition has equal value.
- Reinforce the habit with manager coaching when activity drops, rather than treating a missed week as evidence that the program has failed.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this operational improvement plan measure?
It measures recognitions per 100 members, using a consistent rate rather than a raw count. The plan is designed to track whether managers are giving two specific recognitions per week and whether recognition activity increases over the measurement window. The target direction is upward, with a suggested 100% improvement target to customize to your baseline.
Who should run this plan?
A people leader, operations manager, or recognition program owner should set the baseline, configure prompts, and review the metric. Each frontline manager is responsible for delivering the recognitions and recording them promptly. Assign one owner to resolve missing data and coordinate follow-up when participation falls.
How often should managers give recognition?
Each manager should provide two specific recognitions every week. Recognition should describe the behavior or result being acknowledged, rather than using a generic thank-you. Review activity weekly, then evaluate the overall metric across the 90-day window.
Can this template be used for every department?
It fits frontline teams, service operations, retail, hospitality, healthcare operations, and other groups with identifiable managers and members. It is less suitable when recognition must remain confidential, when managers do not directly observe work, or when the organization has no reliable member and manager roster. In those cases, adapt the workflow or use a different measure.
Does this plan satisfy any specific recognition or employment regulation?
Recognition programs are generally not a substitute for requirements covering wages, scheduling, leave, safety, or discrimination prevention. Keep recognition voluntary, job-related, and inclusive, and avoid tying it to protected characteristics or sensitive personal information. Have HR or legal reviewers check local employment policies before rollout.
What is the most common pitfall?
The most common pitfall is counting generic messages as completed recognition, which can inflate activity without changing manager behavior. Require each entry to identify the recognized action, result, or contribution and the recipient. Also re-check the metric after the initial launch so activity does not drift back to baseline.
Can I customize the target and prompts?
Yes. Set the baseline period, target delta, measurement window, manager population, and recognition channels to match your operation. You can also add required fields for the behavior recognized, business context, and follow-up. Keep the core metric definition stable so comparisons remain meaningful.
Can this plan connect to existing tools?
It can be adapted to a recognition platform, employee directory, survey workflow, team chat, or reporting dashboard that records the recipient, manager, date, and recognition content. If integrations are unavailable, use a shared form or structured tracker with controlled fields. Reconcile the roster and duplicate entries before calculating recognitions per 100 members.
How does this compare with asking managers to recognize people ad hoc?
An ad-hoc approach depends on memory and produces inconsistent activity that is difficult to compare across teams. This template adds a weekly expectation, prompts, a defined metric, and a review cadence. It does not replace thoughtful judgment; it makes the desired habit visible and easier to inspect.
Related templates
Go deeper on the topic
-
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...
-
A performance management platform is the software that supports how a company sets goals, gives feedback, conducts reviews, and makes decisions on pay and...
-
Learn how to improve retail execution with smarter task management, real-time monitoring, and frontline communication tools that drive store-level results.
-
Discover how a mobile-first employee app transforms retail staff training—streamlining onboarding, standardizing SOPs, and reaching every frontline worker.
-
Boost retail workforce engagement with mobile-first communication, recognition, and training that improves retention and performance.
-
10 strategies to reduce burnout among retail associates with smarter scheduling, training, and engagement tools that cut turnover and stress
Ready to use this template?
Get started with MangoApps and use Two specific recognitions per manager, per week with your team — pricing built for small business.
