recognition
Also called: employee recognition
Noticing and naming a specific contribution, soon after it happens, in a form the person values. It costs little, but it works only when it is sincere, specific and fairly spread across the team.
Recognition means noticing a specific contribution and saying so: soon after it happens, naming what the person did and why it mattered, in a form they value. It is one of the cheapest tools a lead has, and one of the most often wasted.
What makes it work is specificity and sincerity. "Great job, team!" says nothing anyone can repeat. "Your review of the first ten refund cases caught two wrong refunds before they went out" shows the person that you saw the work, understood it, and know what it prevented. Timing matters too: thanks a month later reads as an afterthought.
Recognition is also a fairness question. It has to be fairly spread: quiet, preventive or behind-the-scenes work (mentoring, catching a mistake, picking up an unowned inbox) is easy to miss, while loud wins get noticed by default. And the form is personal: some people like thanks in the team channel, others would rather hear it one to one, so ask. In a remote team, written thanks last longer than a passing remark on a call. Recognition complements fair pay; it doesn't replace it.
Example
In August, Klasna's Support lead looks at January–July before the review season. Ticket counts make some people visible by default; mentoring hours (onboarding and pairing with the seasonal hires) don't show up in any dashboard:
The working: 36 / 84 = 42.86%; 24 / 84 = 28.57%; 18 / 84 = 21.43%; 6 / 84 = 7.14%.
Bohdan has the fewest tickets and carried the most mentoring. Specific recognition names it: "Dmytro and Sofiia got up to speed in the spring peak largely through your pairing sessions. That's 36 hours that never showed up in the ticket count." Asked about the form, Bohdan prefers a one-to-one to a post in the team channel.
Common mistakes
- Generic praise. "Great job" can't be repeated or learned from; name the action and its effect.
- Thanking only what's visible. Ticket counts and loud wins get noticed; check who you never thank.
- Waiting too long. Recognition months later, at review time, has lost most of its value.
- One form for everyone. Public thanks can embarrass some people; ask how each person prefers to hear it.
- Using it instead of fair pay or workload. Thanks for overtime nobody fixes soon sounds hollow.
Learn it in the course
- Fairness and recognition · Pay, promotion, workload and praise that you can explain to everyone, and recognition that is specific and on time.
- Case: the "tickets closed" bonus · Four weeks of bonus data: closes are up, quality is down. Read the numbers and propose to Iryna what to change.
- Overload and burnout · Read eight weeks of workload data, spot the early signs the average hides, and use the levers you control, including on your own week.
- Development plans, handover and being away · Write growth plans with people, not for them, lower the bus factor, and leave a handover note so the team runs while you're away.