How to Give Recognition That Lands

Most of us were never taught how to praise the people we work with. So we default to “great job” and hope it counts. It rarely does. This guide walks through how to give employee recognition that actually registers — specific, timely, and true — so your team feels seen instead of managed.

What’s inside

• Why generic praise falls flat

• Be specific about what they actually did

• Timing: recognize close to the moment

• Name the impact, not just the effort

• Match the recognition to the person

• Public vs. private: read the room

• Recognize progress, not just outcomes

• Make it a habit, not an event

• Common mistakes that quietly backfire

Why generic praise falls flat

“Nice work on that” feels good for about half a second, then evaporates. The problem isn’t the sentiment — it’s that vague praise could apply to anyone, so it lands on no one. When people can’t tell whether you actually noticed what they did, recognition reads as a reflex rather than a response.

Worse, generic praise handed out constantly loses value fast. If everything is “amazing,” nothing is. Your team learns to discount the word the same way they tune out a manager who says “we’re a family” in every all-hands.

Recognition works when it proves you were paying attention. That’s the whole mechanism. The person needs to walk away thinking, “they saw the specific thing I did, and they understood why it was hard.” Everything in this guide is really just a way to make that feeling reliable — to move from noise to signal, so that when you say something, it carries weight.

Be specific about what they actually did

Specificity is the single biggest upgrade you can make. Instead of “great presentation,” try “the way you reframed the pricing question in the middle of that deck saved us from a twenty-minute detour — that was sharp.” Now the person knows exactly what to do again.

Specific recognition does double duty: it makes people feel seen, and it teaches. You’re quietly reinforcing the behavior you want more of. Generic praise can’t do that because it names nothing.

A simple test: could this sentence have been said to anyone on the team? If yes, it’s too vague. Name the decision, the moment, the choice they made that a less capable person wouldn’t have. You don’t need flowery language. “You caught the error in the client contract before it went out — that mattered” beats a paragraph of adjectives. Precision reads as sincerity, because faking it takes attention you obviously spent.

Timing: recognize close to the moment

Recognition has a half-life. Praise delivered three weeks later in a formal review feels like paperwork. The same words said the afternoon of the win feel like you were genuinely there for it.

You don’t need a ceremony. A two-line message the same day — “just saw how you handled that escalation, really well done, more on it tomorrow” — often lands harder than anything saved for a quarterly cycle. Proximity to the moment is what makes it feel real rather than administrative.

This is also why waiting for the “right venue” is usually a mistake. The right venue is often now. If you catch yourself thinking “I’ll mention it in our 1:1 next week,” ask whether next week’s version will still carry the same energy. Usually it won’t. Recognition is perishable. The instinct to batch it up for efficiency is the same instinct that lets good work go unacknowledged until people stop expecting to be noticed at all.

Name the impact, not just the effort

Effort matters, but impact is what tells someone their work mattered to something bigger than themselves. “You worked so hard on this” can accidentally imply the outcome was in doubt. “Because of the way you scoped this, the launch shipped a week early and support tickets dropped” tells them their work moved something real.

Connect the dots out loud. People rarely see the downstream effect of their own work — the meeting they made smoother, the customer they quietly saved, the standard they raised for everyone around them. When you narrate that impact, you’re giving them a story about their own value they can carry.

This matters even more for the unglamorous work. The person who keeps the documentation current or defuses tension in a tense thread almost never gets recognized, precisely because their impact is invisible when it’s working. Seeing it — and saying it — is one of the highest-leverage things a manager does. It’s also, not coincidentally, part of how leaders decide who’s ready for more, which is worth understanding from both sides of the table.

Match the recognition to the person

Not everyone wants the same thing. Some people light up at public shout-outs; others feel exposed and would trade the spotlight for a quiet “I noticed” and a stretch project. If you recognize everyone the same way, you’re optimizing for your own comfort, not theirs.

Pay attention to how people respond. Did they deflect when you praised them in the team channel? That’s data. Some of your strongest performers are quietly uncomfortable with fanfare and far more motivated by being trusted with something harder.

The same is true across experience levels and generations. It’s easy to assume everyone values what you value, but the mix on most teams is wider than that — and the assumptions we make about, say, younger colleagues are often wrong. The fix is unglamorous: ask. “How do you like to hear when something’s gone well?” is a slightly awkward question the first time and a genuinely useful one forever after. Tailored recognition tells people you see them as individuals, not slots on an org chart.

Public vs. private: read the room

Public recognition scales a message: it tells the whole team what “good” looks like here. Private recognition builds trust: it says “this is between us, and I mean it.” Both are useful; using the wrong one does damage.

Public praise works best for behaviors you want to normalize — someone flagging a risk early, sharing credit, helping a teammate. You’re using one person’s example to set a standard. But be careful not to always crown the same hero; it curdles fast and quietly demoralizes everyone who wasn’t named.

Private recognition is right for the personal stuff: growth after a rough patch, a quiet act of integrity, effort during a hard season at home. Announcing those can feel like using someone’s vulnerability as content. When in doubt, go private first — you can always ask, “would it be okay if I shared this with the team?” That single question respects their agency and often earns you a yes anyway, which makes the eventual public version land cleaner.

Recognize progress, not just outcomes

If you only celebrate finished wins, you teach people that the messy middle doesn’t count. But the messy middle is where most of the growth happens — and where most people are tempted to quit.

Recognize the person who tried the harder approach even if it didn’t fully land. Recognize the improvement curve, not just the summit. “Six months ago this kind of problem would’ve stalled you for a week — you just moved through it in a day” is often more motivating than praise for a polished result, because it makes progress visible to someone who can’t see their own trajectory.

This also means being willing to let people struggle productively without rushing to rescue or over-praise. Growth needs room, and sometimes the most respectful thing is to let them work it out and then recognize what they learned. Recognizing your team’s progress — not just their trophies — is what keeps people invested through the long, unglamorous stretches where real capability gets built.

Make it a habit, not an event

The biggest failure mode isn’t giving bad recognition — it’s giving none, then overcorrecting with an awkward burst before reviews. Recognition works when it’s ambient: small, frequent, woven into how you already talk.

Build a lightweight habit. Some managers keep a running note of things people did well, so praise isn’t hostage to memory. Others end 1:1s with one specific thing that went well since last time. The mechanism matters less than the rhythm. Consistency is what turns recognition from an event into a culture.

Watch your own defaults, too. Many managers under-recognize simply because they’re heads-down and assume competent people know they’re valued. They don’t — or at least they stop being sure. Silence reads as indifference, especially to your quietest high performers, who are often the least likely to fish for validation and the most likely to leave when it never comes. A habit of noticing out loud is cheap insurance against losing exactly the people you can least afford to lose.

Common mistakes that quietly backfire

A few patterns undo good intentions. The compliment sandwich — praise, criticism, praise — trains people to brace every time you say something nice; keep recognition and feedback separate. Comparative praise (“you’re the only one who gets this”) wins one person and alienates the rest. And praise with a hook — “great work, so can you also take on” — teaches people that being recognized just means more gets loaded on.

Another quiet one: recognizing results that came from luck or from someone burning out to hit a deadline. You’ll get more of exactly what you don’t want. Be thoughtful about what you’re actually reinforcing.

Finally, don’t outsource all recognition to a points platform or a monthly award. Tools can support the habit, but a badge is not a substitute for a manager who noticed. The most valuable recognition still comes from a specific person saying a specific true thing at the right moment. That’s not a process you can fully automate — it’s a form of attention, and attention is the part your team can always tell is real.

How Blomma helps you get recognition right

Knowing all this and actually saying it well in the moment are two different skills. It’s easy to freeze, default to “good job,” and move on. Blomma is an always-on AI career coach you can think out loud with before the conversation happens — draft what you want to say, pressure-test whether it’s specific enough, and figure out whether this one should be public or private.

Unlike a one-off workshop, Blomma is there the afternoon you notice something worth naming, and again next week when you’re deciding how to recognize progress on a project that isn’t finished yet. Over time it helps you build the noticing-out-loud habit that separates managers people want to work for from ones they merely report to. You can see how Blomma works for individuals if you want the full picture.

Good recognition is a small skill with an outsized effect on how people feel about their work. It’s worth getting deliberate about.

Practice your next recognition conversation with Blomma free →

Related reading

• Let them fail: why rescuing your team too fast holds them back

• How execs actually make promotion decisions

• Gen Z is not the problem: managing across generations