Praise loses meaning when the daily obstacles never get removed.
Praise matters.
I have seen a sincere thank-you change the temperature of a difficult week. People want to know their effort was noticed, especially when the work was messy and the customer pressure was real.
But I have also seen recognition used as a substitute for fixing the thing that exhausted everyone.
A leader thanks the team for another heroic recovery. Lunch arrives. An email celebrates resilience. Somebody uses the phrase “above and beyond.”
Then Monday arrives, and the same broken workday is waiting.
Recognition feels hollow when the same preventable obstacle is waiting tomorrow.
Consider a Service Desk that spends three days clearing a surge of tickets after a software rollout. Analysts stay late, Deskside joins the queue, and team leads postpone coaching sessions to handle escalations. They recover the service level, and leadership sends a generous note praising their commitment.
Good. They earned it.
Yet the routing rule that misclassified hundreds of tickets is not corrected. The knowledge article still describes the previous software version. The deployment team receives no useful analysis because reporting counts closed tickets but does not show why the demand arrived.
Two weeks later, another rollout creates the same surge.
This time the thank-you message lands differently. Employees do not hear appreciation. They hear confirmation that leadership has accepted heroic recovery as the operating model.
That is what bothers me about recognition programs when they become detached from management action. The words may be sincere, but employees judge the message partly by what follows. If speaking up, staying late, and rescuing the customer produce praise but no improvement, people learn that their extra effort is useful to the organization while their experience of the work is negotiable.
Some will keep stepping in because they care. Some will become more selective. Others will stop offering ideas because the evidence says ideas are welcomed more warmly than they are acted upon.
Do not praise people for carrying a system you are unwilling to repair.
This is where engagement connects directly to first-line management systems.
The problem is not that managers should stop saying thank you. It is that recognition should complete a loop, not close the conversation. What did the team have to overcome? Which part was genuine complexity, and which part was avoidable friction? What does the incident reveal about roles, process, tools, reporting, or continual improvement?
In the Service Desk example, recognition becomes credible when the routing logic is fixed, the knowledge is updated, the rollout feedback reaches the deployment team, and the next release produces less preventable demand. The team can then see that leadership did more than notice the effort. Leadership learned from it.
There is room for accountability here too. Not every difficult day is a system failure, and not every employee contribution is equally effective. Leaders still need standards, judgment, and honest feedback. But employee obsession, attentiveness, and continuous improvement become real only when leaders are curious about what the praise is telling them.
The best recognition is sometimes the removal of work that should never have existed.
So thank the people. Celebrate the recovery. Buy the lunch.
Then fix Monday.
Discussion question: What recurring obstacle are you still thanking employees for overcoming?
If your recognition efforts are not changing the day-to-day environment people work inside, the missing piece may be management architecture. My book, The 7 Essential First-Line Management Systems, explores the practical systems behind clearer work, better execution, and a healthier employee experience: imadlodhi.com/flm1.
