The morale problem nobody puts in the sprint board
Distributed engineering teams have a blind spot. You can see build times, PR throughput, incident counts, and cycle time on a dashboard. You cannot see the senior engineer who quietly stopped caring three sprints before they resigned.
Recognition is the usual answer, and most teams do it badly. It lives in a Slack channel that goes quiet after two weeks, or in a once-a-quarter manager shoutout that everyone forgets by Monday. For engineers specifically, that gap is expensive: O.C. Tanner found 79% of people who quit cite lack of appreciation as a reason (source), and replacing a senior engineer runs 6 to 9 months of their salary before you count lost context (SHRM).
We are Mobile Reality, a distributed software house. We hit this exact wall on our own team, tried the off-the-shelf options, and eventually built the tool we wanted. This post is the honest version: what recognition tooling should do for an engineering org, what we learned, and where our own product fits. Disclosure up front so you can weight it accordingly: the tool at the end is ours.
What "recognition tooling" should actually do for engineers
