We pay well. Why does the team feel undervalued?
Effort That Goes Unnoticed
Pay, recognition and progression are three separate things. Organisations that provide the first frequently supply neither of the others.
Procedure
Reward covers more than compensation, and the non-financial components are cheaper and more often missing.
The three components
Material reward. Pay, benefits, security. Necessary, and it does not compensate for absence of the other two beyond a point.
Recognition. Specific acknowledgement that the work was seen and mattered.
Progression. A believable sense that the effort leads somewhere.
All three can fail independently. A well-paid person whose work is invisible and whose role has no future is in a reward mismatch, whatever the salary says.
Why recognition fails
Generic praise. "Great work, team" acknowledges nothing and everyone knows it.
Recognition for visible work only, which systematically overlooks maintenance, support, coordination and the people who prevent problems rather than solving them.
Recognition flowing upward. The manager thanked for the team's output.
Programmes that formalise it into a currency, which converts a human act into an administrative one.
Silence when things go well combined with attention when they do not, which teaches people that being noticed is bad.
What works
Specific and prompt. Name what was done, and why it mattered, close to when it happened.
Private and public, which serve different purposes โ private is more credible, public confers status.
Peer to peer, which is frequently more meaningful than manager to report.
Acknowledgement of invisible work, deliberately, because it will not surface on its own.
Acting on suggestions, which is a stronger form of recognition than any statement. Someone whose idea was implemented has been recognised in a way no message achieves.
Progression when there is no promotion
Many roles have limited advancement, and pretending otherwise is worse than acknowledging it.
Say what is actually possible. A false promise of promotion is more damaging than a clear statement that the role is a plateau with other compensations.
Offer growth that is not vertical: depth, breadth, mentoring others, ownership of a domain, exposure to different work.
Make skills portable. People stay longer when they are learning things that would be valuable elsewhere, which is counter-intuitive and holds up.
Review the plateau honestly at intervals, rather than letting someone discover it after five years.
The fairness link
Reward mismatch becomes severe when combined with perceived unfairness.
Opaque pay invites the least generous assumption.
Promotion decisions without stated criteria are read as political.
Inconsistent recognition across teams doing similar work is noticed immediately.
The process matters as much as the outcome, and a transparent process producing a disappointing outcome is far better tolerated than an opaque one producing the same.
The cheapest available action
Ask managers to name, for each person reporting to them, one specific thing that person did in the last month that mattered.
Managers who cannot answer are not seeing their people's work, which is the finding.
Then have them say it, to the person, specifically.
That exercise costs an hour and addresses a mismatch that no benefits budget reaches.
Recognising the work nobody sees
Recognition follows visibility, and the most valuable work is frequently the least visible.
Prevention. Nothing went wrong because someone made sure it would not.
Maintenance. The system kept running.
Coordination. Two teams worked together because one person made it happen.
Absorbing difficulty so that colleagues did not have to.
Teaching. Someone else is better at their job now.
Ask about these specifically, in one-to-ones and in team discussion, because they will never surface in a nomination process built around achievements.
Naming one instance of invisible work publicly does more for a team's sense of being seen than a month of general appreciation.
Saying it in a way that lands
Specific recognition has a shape, and generic praise fails for identifiable reasons.
Name the thing. Not "great work" but the actual action.
Say what it made possible, which is the part that converts acknowledgement into meaning.
Say it close to when it happened.
Say it to them directly, and separately to others if it warrants.
Do not attach a request to the same message, which converts recognition into a preamble.
One sentence, correctly constructed, outperforms any scheme, and it costs nothing but attention.
Also in this section
- Everyone is at capacity all the time. How did that happen?
- Why is my team stressed when the workload is not extreme?
- The team is fine individually but something is wrong collectively.
- Why does one promotion decision damage a whole team?
- Good people are leaving and saying the culture changed.
- Nobody is required to work evenings, so why does everyone?