Rewrote the returns SOP over a weekend so the counter team had it before the policy changed.
3 of 10 left: 7
.png)
Run an org-wide wall where praise links the actual SOP or checklist run, tagged with your company values and backed by a monthly points allowance.
Configure the values a recognition can carry, and the monthly points each member spends.
Name a colleague or a team, pick the value, attach the work, and spend up to ten points.
Colleagues endorse and comment, and the post is still there when review season arrives.
Every post names one or more colleagues and carries a company value. Only the product where the work lives can also link the thing that was actually done.
Evidence links the SOP, the process map, the module, the checklist run
Value tags, configured once, so praise rolls up to something
Endorsements one per person, counted in people rather than reactions
Scarcity is what makes praise mean something. Every member gets ten points each calendar month and spends one to ten of them on a recognition as they write it.
A hard budget: at zero the wall stops accepting posts until the month rolls
Never convertible: no catalogue, no cash value, no payroll event
Never a rank key, because volume numbers are farmable
A board with a hidden formula gets reverse-engineered and farmed within a quarter. The defence is to make the formula dull and print it on the board itself.
Ranked on distinct givers: ten thank-yous from one friend counts once
Self and recipient endorsements excluded, and posts per giver per day capped
Top-N and time-boxed: never a bottom, never a full ranked roster
Employee of the Month, run properly. A time-boxed round with nominations, one secret ballot each, and a human between the count and the announcement.
Two dates: nominations close, then voting closes; never yourself
Ballots are secret: the file stores a keyed, per-round hash of the voter
The tally never auto-decides, and losing nominations are never published
Every automatic signal in a review is a count, modules finished, checklists on time. None of them is a colleague saying this person unblocked my week.
Recognitions land on the review card as a list of links, dated and attributed
Managers see what they gave, because recognising the team is part of the job
Still never a rating: wired into the cycle without becoming a score
Instructors on split shifts rarely overlap, so the wall is where the person who covered a 6am class is still being thanked at Friday's team meeting.
A monthly award round gives a shift-based team something to vote on that isn't the rota — and the result is announced to everyone, not pinned in one WhatsApp group.
Quiet, unglamorous work gets recorded with a link to the document, and surfaces again as evidence when the review cycle opens.
The manager's coverage view flags the practitioners nobody has recognised in ninety days — which is a more useful number than knowing who is winning.
Emily
Small Business Owner
Because chat praise scrolls away and points at nothing. A recognition here carries a company value, links the SOP or checklist run it is about, and is still findable when the review cycle opens.
It ranks on distinct givers rather than raw count, so ten thank-yous from one friend count once. Self and recipient endorsements are excluded, posts per giver per day are capped, and the formula is printed on the board.
Every member gets ten points a calendar month and spends one to ten on a recognition. They buy nothing. No catalogue, no cash value, no payroll event, and they expire monthly, on purpose.
The wall stops accepting new posts from them until the month rolls over. An allowance nobody can exhaust is a suggestion with a counter beside it, and the scarcity is what makes a post mean something.
Yes. The file stores a keyed, per-round hash of the voter, so an Admin reading it cannot see who voted for whom. The tally never auto-decides either, a person confirms the winner.
They stay. A recognition is a record of what happened and who said it, and the wall is newest-first rather than a roster. Removing someone's history would rewrite everyone else's too.
Never. Recognition is visible to active members of your organisation and to nobody else, and portal guests are refused before any read.
