Most recognition programs I have seen reward what is visible. The launch gets the announcement. The demo gets the applause. The engineer who was up at 2am putting out the fire gets thanked in the all-hands. All of that is fine. What bothers me is what it misses, and I think it misses most of the work that matters.
The valuable work is often invisible
The fire that never started, because someone fixed the fragile thing in March, has no moment attached to it. The review comment that caught the bug that would have corrupted a week of data looks like a sentence in a pull request.
Engineers know which of their colleagues' work was hard and which merely looked hard, and they notice when recognition goes consistently to the second kind. It tells them what the organization can see, and they adjust.
What I think engineers actually want
I think what engineers want is to be seen for the right thing by someone who understood it. Both halves matter.
The right thing means the work they are proud of, which is often not the visible work. In a one-on-one, what did you do this quarter that nobody noticed gets honest answers.
Someone who understood it means the recognition is specific enough to prove the giver knows what was done. Great job on the migration lands differently than I read the plan you wrote for the migration and the rollback section is why I slept that week.
The forms I think land
Specific over general, always. A sentence that names what was done and why it mattered is worth more than any award.
The invisible work, named out loud. When something does not go wrong, I think a manager should say so, and say whose work made it so. Nothing broke during the migration because of the compatibility layer recognizes work that would otherwise go unmentioned.
Recognition from peers who know the code. A note from the engineer who inherited your module and found it easy to work in carries weight a manager cannot match, because the peer has no reason to be polite.
Recognition that changes something. The person who has been quietly carrying the hardest part of the system gets asked to design the next one. That is recognition with consequences, and the kind people remember.
The public thank you is not always the right instrument
Not everyone wants to be named in the all-hands. Some engineers find it uncomfortable, and for them the public thank you is a cost dressed as a reward. I think a manager should know which of their people this applies to, and find the private form instead. The point is that the person feels seen.
None of this costs anything but attention. That is why I think it is rare. Attention is the most expensive thing a manager has, and recognition that works is made of it.
Photo source: https://photos.robertstowe.com/bengaluru
