Recognition Is Evidence of Attention

In a journal entry from 2021, I complained about the “constant noise of recognition.” I wrote that people build up a tolerance to praise and that we needed to become more precise and surgical about when and why we recognized someone.

I still think that is mostly right, although “surgical” sounds a little intense for saying thank you.

What I was reacting to was not recognition itself. It was recognition that had become detached from observation.

“Great job.”

“Amazing team.”

“Thank you for everything you do.”

All pleasant. Almost no information.

The person may feel appreciated for a moment, but they do not know what you saw. They do not know what mattered. After enough repetition, the praise becomes part of the wallpaper.

Precise recognition is operational feedback

Useful recognition usually contains three things:

• What the person actually did
• What was difficult or easy to miss about the situation
• What became better because they did it

For example:

I noticed that you called the family before they had to ask for an update. You did it during a day when several other cases needed your attention. That kept them from spending the afternoon wondering whether anyone was working on their problem.

That is not only praise. It is information.

It tells the person that anticipation mattered. It tells the rest of the team, if the recognition is public, what kind of work the organization values. It gives the employee something concrete they can repeat.

This is why I have started thinking that recognition is evidence of attention.

It tells someone: I saw the work itself, not merely the result attached to your name.

A lot of important work is nearly invisible

Someone notices that a coworker is overloaded and quietly takes a task. An experienced employee catches a problem before it reaches a supervisor. A person gives honest feedback in a room where silence would have been easier. Someone brings steadiness into a difficult day and the emotional temperature of the whole team changes.

None of that is likely to appear on a dashboard.

If leaders recognize only the loudest wins, people learn that the quieter work does not count. Worse, leadership loses information about what is actually keeping the operation together.

This is related to the limits of formal metrics. What can be measured matters. What cannot be measured still exists.

Recognition can make some of that invisible work legible—but only if the leader is close enough to notice it.

The exercise changed when I asked why

Years later, I facilitated a gratitude discussion with a leadership team. The ground rule was specificity: something from the last 30 days, large or small, whether the person knew they had done it or not.

The first answer was rarely the interesting part. The useful part came from asking:

• Why did that stay with you?
• What would have happened if they had not done it?
• What made the moment meaningful?
• What, specifically, did they do?

Those questions turned compliments into a description of how the team functioned.

People talked about reliability under pressure, anticipation, honest feedback, energy, trust, and the small things that make difficult work sustainable. None of it was heroic. That was the point.

The operation was being held together by consistent acts of attention.

Recognition without the gaps becomes performance

The gratitude discussion became more useful when we turned the lens around and asked where leadership had created extra burden, uncertainty, or silence for somebody else.

I went first.

That part matters to me because recognition can become another leadership ritual where leaders perform warmth without becoming more accountable to the work. If I am willing to tell someone exactly what they did that helped, I should also be willing to hear exactly what I did that made their job harder.

Recognition and accountability are not opposites. Both begin with noticing accurately and being specific enough that another person can act on what you noticed.

That is also why praise should not be used as a cushion around feedback. People can feel when the compliment is merely the bread in a criticism sandwich. Say what was good because it was good. Say what needs to change because it needs to change. Give both the dignity of precision.

Public or private?

Not every recognition should happen in front of the team.

Some people enjoy public attention. Some hate it. Some contributions involve details that should remain private. Sometimes the most meaningful version is a quiet sentence after a difficult shift: I saw what you did there. It mattered.

The goal is not visibility for its own sake. The goal is for the person to know that the work was seen and understood.

This is one reason recognition belongs beside hard conversations and debriefing in my head. All three depend on a leader paying close enough attention to describe reality without making the conversation about themselves.

What I am still trying to understand

Recognition can make hidden work visible. It can also accidentally reward people for continuing to absorb work the system should fix.

If I repeatedly praise the person who stays late to rescue a broken process, am I recognizing commitment—or teaching the organization to depend on their sacrifice?

I do not think the answer is to withhold recognition. I think the answer is to let the recognition produce a second question:

Why did this require someone to step up in the first place?

That question links recognition back to system design. See the person. Thank them precisely. Then pay attention to what their effort is telling you about the operation.

Connected notes

• Leadership Philosophy — trust, warmth, and the emotional temperature of a team
• Hard Conversations — feedback with dignity and specificity
• The Debrief — paying attention without taking over the person’s experience
• Build the Sprinkler System — when admirable effort is concealing a preventable gap