Recognition, Appreciation & Reward System

Why recognition, appreciation and reward?

However well processes are designed, improvement does not last unless the effort of the people who run them is seen. A well-built recognition and reward system makes desired behavior visible, feeds the suggestion and kaizen flow, raises participation and shifts the culture from 'hiding the problem' to 'solving the problem'. A poorly built one breeds perceptions of favoritism and loss of motivation — which is why the design itself is critical.

Three tiers: recognition, appreciation, reward

The three are different things and must not be confused. The distinction is made by trigger, evidence requirement, frequency and reward. Moving left to right, frequency falls while the evidence requirement and the reward's value rise. An event enters only one tier.

Design principles

The system is built on four principles; every design decision rests on them. The principles are the guarantee that the system is perceived as fair and trustworthy.

• Known in advance — criteria, rewards and decision bodies are announced at the start of the year; no one is caught by surprise.
• Evidence-based — every proposal rests on a concrete event, data or observation; at the reward tier, the benefit is verified numerically.
• Transparent and traceable — all decisions are announced with their rationale; even a rejected proposal receives a written reason.
• Open to all — blue- and white-collar, shift and office employees have equal access; proposal channels work from the shop floor and from the screen alike.

Criteria architecture and tier decision

All achievements fall into one of five contribution areas: safety, quality, efficiency and cost, customer and delivery, people and culture. In the safety area, the tier starts one step higher. The tier itself is set by a three-question decision test: if the result can be verified numerically, reward; if there is effort beyond the job description, appreciation; if a right behavior was observed, recognition. The size of impact sets the tier — not who made the proposal or their title.

• Safety — near-miss and hazard reporting, safe behavior, accident prevention
• Quality — reducing scrap and rejects, customer complaints, surface and dimensional conformity
• Efficiency and cost — material yield, downtime, energy, setup and inventory
• Customer and delivery — on-time delivery, flexibility, internal-customer satisfaction, new products
• People and culture — knowledge transfer, teamwork, values, development and continuity

End-to-end process, roles and committees

The process has eight steps, each with a defined owner and time target: proposal, pre-check, verification, benefit calculation, evaluation, decision and approval, implementation and announcement, record and feedback. Roles are separated with RACI logic; the recognition tier sits outside this table and needs no approval. Two committees operate: the monthly Appreciation Committee and the quarterly Reward Committee, which decides with the General Manager's approval. A committee member does not vote on a proposal from their own direct report. An unanswered proposal is the fastest cause of system decay — hence a time target at every step.

• Proposal — anyone can submit via a form or board box (ongoing)
• Pre-check and verification — HR checks scope; the manager and technical unit confirm the event and data
• Benefit calculation — only at the reward tier, Finance computes the gain amount
• Evaluation and decision — the committee sets the tier via a scorecard; the committee approves appreciation, the General Manager approves reward
• Implementation, announcement and record — the reward is given, the decision is announced with rationale, the personnel record is updated, and a rejected proposal receives a written reason

Evaluation, rewards and budget

The committee scores each proposal on the same six criteria out of 100: size of impact (25), permanence (20), evidence strength (20), initiative and difficulty (15), scalability (10), team contribution (10). 75+ points is met with reward, 55–74 with appreciation, below 55 with recognition. Rewards vary by tier: for recognition, verbal/written thanks, a board and an 'I Noticed' card; for appreciation, a certificate, badge, personnel record and a thank-you letter to the family; for reward, a plaque, cash/in-kind bonus, extra leave and a development opportunity. The system is not unlimited — frequency, quota and budget are defined in advance tier by tier and reviewed annually. In team rewards, no person-by-person split is made; the share is distributed equally between the core and support teams.

• Routine work already required by the job description is not rewarded; it can only be recognized
• The same achievement is evaluated only once and in a single tier
• A benefit claim that cannot be verified cannot pass to the reward tier
• Fixing a problem one caused is not an achievement; a permanent solution preventing its recurrence is

Governance: transparency, measurement and integration

Criteria, quotas and the calendar are announced every January and stay posted on the boards; every committee decision is announced with its rationale within five working days; a rejected proposal receives a written reason and the decision can be appealed within ten working days. The system is measured too: participation, reach, speed, conversion, distribution balance and fairness perception are reported each quarter — distribution balance is the most critical indicator. The system is designed to work integrated with performance appraisal, suggestion/kaizen and OHS reporting systems, yet it can also run on its own. The most common cause of failure is not budget but the lack of feedback.

• Participation — share of employees submitting proposals (first-year target ≥ 30%)
• Reach — share of employees receiving recognition (first-year target ≥ 60%)
• Speed — average time from proposal to decision (target ≤ 25 working days)
• Balance — distribution by department and shift (no department above 40%)
• Perception — fairness perception in the employee survey (target: ≥ 3.8 out of 5)

90-day rollout

The system is rolled out in four phases, not all at once, and no tier is applied before the procedure is published. In the first 30 days the design-and-approval output — the HR-PRS-01 procedure and the eight-part form set (from the 'I Noticed' card to the quarterly system report) — is prepared. Running it verbally is the system's first loss of trust.

• 0–30 days · Design and approval — procedure and forms, selection of committee members, budget and quota approval
• 30–60 days · Announcement and training — briefing meetings, recognition training for managers, board and box setup
• 60–90 days · Pilot — recognition and appreciation pilot, first committee meeting, refinement of the forms
• 90+ days · Full rollout — activation of the reward tier, first quarterly committee, system revision at month 6