The Done-and-Seen Log
Generic recognition doesn't scale. Specific recognition doesn't happen often enough. One five-minute Friday practice solves both at once.
Managers want to recognize specifically and frequently. Neither happens often, because each instance takes thought, and thought is the resource you have least of by Friday afternoon.
The fix is batching.
Every Friday, in your team's shared channel or doc, post one line per direct report. Three to five bullets total. The format is fixed: name, one specific thing they did this week, why it mattered. Not "great work this week." Not "appreciate everything you do." One concrete moment, one sentence on consequence.
Five minutes of work. A permanent record on a public surface.
The mechanism is twofold. Batching collapses the per-instance friction (you decide once, not five times). Posting publicly creates two kinds of accountability: your team sees who got specific recognition this week and who didn't, and you see the same pattern when you scroll back over a quarter. The log reveals the people you've been quietly under-noticing.
After ten weeks, you'll know more about your team's contributions than any quarterly review delivered. After a year, you'll have a 50-entry record of what actually got done, attributed to who did it.
