There’s a particular silence that follows hollow praise. A manager finishes a thank-you in a team meeting, the room nods, and everyone moves on. Nothing bad happened. Nothing happened at all.
Most managers can sense when appreciation doesn’t land. What’s harder is identifying why, because the words were sincere and the intention was real. The problem is almost never intent. It’s that performative recognition vs real appreciation comes down to a set of specific, learnable differences, and most people have only ever seen the performative version modeled.
What Makes Appreciation Feel Performative
Performative appreciation isn’t insincere. It’s appreciation shaped more by the needs of the person giving it than the person receiving it.
It’s addressed to the room. When praise is delivered primarily so that others witness it, the recipient can tell. The acknowledgment is real, but they’re a prop in it rather than the subject of it.
It’s interchangeable. If the same sentence could be said to any of six people on the team without editing, it communicates that a thank-you was required, not that anything specific was noticed.
It arrives on schedule. Appreciation tied to a calendar — the weekly shout-out, the quarterly award, Employee Appreciation Day — reads as procedure. People don’t experience procedure as being valued.
It’s attached to something else. Praise immediately followed by a request converts the appreciation into preamble, and employees learn to hear it that way.
It skips the work. “You’re such an asset to this team” is about a person’s standing. “The way you handled that client call in March kept the account” is about something they actually did. The second one proves you were watching.
The common thread is distance. Performative appreciation is generic enough that it could have been produced without paying close attention, and people are remarkably good at detecting that.
The Cost of Getting This Wrong
Hollow appreciation isn’t neutral. It can leave people feeling less valued than silence.
Silence is ambiguous; an employee can assume their manager is busy. Generic praise removes the ambiguity. It demonstrates that acknowledgment was on the agenda and that nobody looked closely enough to make it specific.
This helps explain a contradiction that shows up consistently in workplace data. 94% of companies operate a recognition program, and engagement has continued to decline. At the same time, 79% of employees who leave voluntarily cite lack of appreciation as a factor — many of them departing organizations with active, well-funded programs. Meanwhile 89% of managers assume those exits were about compensation.
Programs are running. Appreciation isn’t reaching people. Volume was never the missing variable.
Four Things That Make Appreciation Feel Real
Specificity
This is the single highest-leverage change available, and it costs nothing.
Name the action, then name what it made possible. Not “thanks for your hard work on the launch” but “you caught the pricing error two days before we went live — that would have cost us the enterprise renewals.”
Specificity works because it functions as proof. It tells someone you were present for their work, not just aware of it. A short specific sentence outperforms a long general one every time.
If constructing these feels awkward at first, working from appreciation scripts is a reasonable place to start — the phrasing gets easier with practice, and the structure is more learnable than most managers expect.
Fit
The same message delivered to two people can land completely differently, because people don’t receive appreciation through the same channel.
Research behind The 5 Languages of Appreciation in the Workplace found that roughly 45% of employees name words as their preferred way of receiving appreciation. The remaining majority feel valued more through time, practical assistance, or something tangible. For those people, an eloquent public message isn’t undervalued — it simply isn’t the currency.
Personalizing appreciation is what separates a manager who says the right thing from one who does the right thing for that particular person.
Privacy, where it belongs
Public recognition is the default in most organizations and a genuine risk for a substantial portion of any workforce. For people who dislike attention, being praised in front of a group is an experience they’d rather avoid — which means the appreciation is delivered and the net effect is negative.
Private acknowledgment carries no such risk, and for many people it carries more weight. Match the setting to the person, not to the org chart.
Separation from the ask
Appreciation that consistently precedes a request stops being appreciation. Employees learn the pattern quickly, and once learned, it contaminates the sincere instances too.
Let it stand alone. Say the thing, and don’t follow it with anything.
Why the Mechanism Matters
Understanding why these differences matter makes them much easier to apply consistently.
Appreciation functions as information. It tells someone that a specific person observed something they did and judged it to matter. That’s why specificity is load-bearing and generality is inert — one carries information, the other carries only the fact that something was said.
It’s also why frequency alone doesn’t help. Adding more instances of a message that carries no information produces more noise, not more meaning. The science of workplace appreciation consistently points in the same direction: what changes how people feel is whether the acknowledgment is specific, attributable, and shaped to them.
A Test You Can Apply Immediately
Before you deliver any appreciation, run it through three questions.
Could I say this exact sentence to someone else on the team? If yes, it isn’t specific enough yet.
Would this person want to receive it this way? If you don’t know, that’s worth finding out before you deliver it.
Am I about to ask them for something? If so, separate the two.
Anything that clears all three will land. Most appreciation fails at the first question.
Building Authentic Appreciation Into Organizational Culture
Making meaningful recognition consistent across an organization requires a shared framework—one that moves past generic corporate praise to focus on how each person uniquely feels valued.
Rooted in the research of Dr. Paul White and Dr. Gary Chapman (The 5 Languages of Appreciation in the Workplace), Appreciation at Work has spent over 15 years helping organizations bridge the recognition gap. The Appreciation at Work training kits provide managers with practical, direct tools to make authentic appreciation a regular habit during an ordinary workweek.
