Employee recognition: praise with facts, not badges or rankings

Good recognition means telling a person what they did, when, and what it changed, in your own voice. A badge, a score or a leaderboard says none of that. A tool's role is limited to reminding the manager of the facts, because managers forget the good things faster than the bad ones. The thank-you itself stays human.

What nobody told Inès

On a Monday, the manager of the third site goes back over his week. He easily recalls the dish pit that was swamped on Friday, the late delivery and the plating mistake at dinner service. He struggles to recall what went well. Yet on Wednesday, Inès redid the labeling of the walk-in on her own before the chef arrived, and on Thursday she warned the floor that a dish was sold out before tickets started to pile up.

Nobody told Inès. That is not ingratitude: the manager had twenty other things on his mind and nothing put those two facts back in front of him.

Why recognition gets lost along the way

• The manager's brain holds on to alerts. An incident sticks; a job done right goes unnoticed.
• Good work leaves few traces. The absence of a problem generates no message and no ticket.
• Recognition gets pushed to the annual review. It arrives too late and too general: "you do good work."
• Off-the-shelf solutions ring false. Automatic badges and team leaderboards assume motivation can be manufactured with game mechanics, which does not hold up with adults doing a real job.

Badge, generic comment, specific fact: three ways to say thank you

Form	Example	What the employee understands
Automatic badge	"Star of the week"	That the system drew a name, not that anyone saw them work
Generic compliment	"Great work this week"	That the manager is in a good mood
Compliment on a fact	"On Wednesday, you redid the labeling before the chef arrived. It spared us a shaky inspection on Thursday."	That their action was noticed, understood and matters

The third format takes thirty seconds of preparation. That is exactly what a manager's memory alone does not provide.

A five-minute routine on Friday

1. Ask the question the other way around. Instead of "what didn't work?", ask "what worked without anyone noticing?"
2. Look for traces. Tasks signed off before the deadline, an incident handled all the way through, an instruction applied without a reminder, help given to a colleague.
3. Pick one or two facts per week. No more: a compliment to everyone every day stops meaning anything.
4. Write the fact down with its date. One line is enough: who, what, when.
5. Say it yourself, within 48 hours. Out loud, at the end of service, or in a message written by your own hand.
6. Tie it to what the team is expected to deliver. "This is what we are trying to hold across every site": recognition reinforces the standard.

Sentence template

"[First name], on [day], you [specific action]. Result: [concrete effect]. Thank you, that is exactly what we expect in this role."

The traps of tool-driven recognition

• The pre-written message signed by the manager. The employee senses it from the first sentence.
• The weekly ranking. It turns a team into internal competition and penalizes people whose work is less visible.
• Praising volume rather than the action. The number of tasks ticked off does not tell you who did well.
• Forgetting the behind-the-scenes roles. Dish pit, receiving, morning prep: they are the first to never be mentioned.

What you can observe

• The number of people on the team who have received no specific positive feedback in a month (not to turn it into a score for them, but for you).
• The gap between the number of corrective and positive comments you give each week.
• The share of compliments backed by a dated fact, as opposed to general phrases.

Recognizing a team, not only one person

The same principle applies to a whole shift. After a busy Saturday, "well done, everyone" says nothing. Say instead what the team held together: tickets going out without unusual waits at the start of service, the dish pit cleared before closing, the allergen instruction applied at every table. A collective fact also names the behind-the-scenes roles, so that thanks do not go only to the visible positions. Keep one simple rule: no comparisons between colleagues in the same message. A compliment describes what was done; it does not put anyone above anyone else.

Where Tsuno comes in

Tsuno keeps the facts observed and the actions taken, dated and attributed, and never grades a person. You can ask it, for example: "What went well this week at site X?" and get specific items, with their source, which the manager then takes up in their own way. Tsuno does not write the thank-you, does not hand out badges or rankings and does not measure motivation: those uses are refused by design. The principles are detailed on the trust page.

Going further

The same fact-based logic helps you prepare an employee conversation with facts rather than impressions. It also explains why weekly manager reports teach you nothing and why AI should not judge your employees. The broader frame is in managers do not need another dashboard.

Key takeaway

A useful thank-you is specific, dated and said in person. The tool can recall the fact; it cannot say it for you. Five minutes on Friday is enough for Inès to know that what she did on Wednesday counted.