Everyone likes being recognized for their work. This is not controversial, not particularly insightful, and not the interesting part.

The interesting part is what happens when recognition is present but doesn't land. When someone is told, regularly, that their work is excellent, and feels nothing. Not because the words are insincere. Not because the relationship is broken. But because the person saying it doesn't quite understand what the work actually involved.

This came into focus through a coaching conversation. The presenting issue was one thing; what emerged was something more precise. Recognition wasn't absent, managers gave it. But they lacked the technical understanding to grasp what made the work difficult, what the good decisions were, where the real skill had been applied. So the appreciation arrived and went nowhere. Heard but not felt. Present but weightless.

The problem wasn't the frequency of recognition. It was the competence behind it.

There's a version of this that people rarely name directly, perhaps because it sounds ungrateful. Receiving a compliment and thinking: you don't actually know enough to say that. Not as arrogance. As an accurate read of the situation. The person speaking hasn't demonstrated the understanding that would give their words any real force. They're saying the right thing without having earned the position to say it.

Recognition works a little like currency. Its value depends on the perceived solvency of whoever issues it. The same words, said by someone who clearly understands what went into the work, carry an entirely different weight than when said by someone who doesn't. Not because intent differs, intent might be identical, but because the receiver can tell the difference between appreciation that's grounded in comprehension and appreciation that's essentially decorative.

What makes recognition land is not just that someone noticed, but that someone understood.

This creates a practical difficulty that doesn't get enough attention. In most organizations, the people responsible for recognizing work are not always the people best positioned to evaluate it. Managers oversee domains they may not fully master. Seniority and technical depth don't always coincide. A person can spend years producing excellent, complex work inside a structure where no one above them is genuinely equipped to see it.

The question that follows is real and open: what can someone do when they want to give meaningful recognition but lack the specific authority that would make it land?

A few things seem to matter more than others.

Specificity is the first. Generic praise signals exactly what it is, that the observer hasn't looked closely. The more specific the observation, the more it demonstrates that something real was seen. Not "great work on the project" but "the way you navigated the client relationship in the third week, when everything was uncertain, was exactly the right call." Specificity doesn't require technical mastery. It requires attention.

Curiosity is the second. Someone who doesn't fully understand a domain but asks genuine questions about why something was hard, what the options were, where the real decision points were, that person signals something important: they're trying to see. That effort is legible. It changes the quality of the recognition that follows, because the receiver knows it came after actual engagement.

Honesty about the limits of one's own perspective is the third, and perhaps the most underused. There's something disarming about a recognition that includes an acknowledgement: I don't fully understand all the technical dimensions of what you did, but what I can see is this. That framing doesn't diminish the appreciation. It makes it more credible, precisely because it doesn't overclaim.

None of this solves the deeper structural problem, which is that sustained recognition from people who don't understand your work eventually becomes a kind of professional loneliness. Being seen from a distance, however warmly, is not the same as being seen. At some point, people need to encounter someone in their professional world who genuinely gets what they do and can say so with the weight that understanding carries.

But in the meantime, there's work to do on both sides of that exchange. Recognition is not just an output to increase. It's a practice that requires something from the person giving it, enough curiosity, enough attention, enough honesty to make the words mean what they're supposed to mean.