Most managers know that recognition matters. Engagement surveys say it, leadership books say it, and common sense says it: people who feel appreciated do better work, stay longer, and bring more energy to what they do. Yet recognition remains one of the most inconsistently practised parts of management. It either comes too rarely, too generically, or in a way that feels more like a corporate reflex than a genuine human response. The result is that people who are doing good work often have no idea that anyone has noticed.
Recognition is not about grand gestures or employee-of-the-month schemes. It is about noticing what someone did, naming it specifically, and telling them why it mattered. That is what makes it land.
Why most recognition falls flat
There is a particular kind of recognition that does more harm than good. It is the "great job, team" message dropped into a group chat with no context. It is the annual awards ceremony where the criteria are opaque and the winners are predictable. It is the manager who only remembers to praise someone during a performance review because HR asked them to include a strength. These are not acts of recognition. They are acts of compliance.
The problem is not that managers are insincere. Most genuinely do appreciate their teams. The problem is that the appreciation stays internal. They notice someone handling a difficult client well, think "that was impressive", and then move on to the next meeting without saying anything. Over time, this creates a gap between how a manager feels about someone's work and how that person feels about their own contribution. That gap is where disengagement lives.
- Too genericSaying "well done" without specifying what was done well tells the person almost nothing. It does not reinforce the behaviour, and it does not feel personal. It could have been said to anyone.
- Too infrequentRecognition that only arrives at review time or during a crisis feels transactional. People need to know they are valued in ordinary weeks, not just extraordinary ones.
- PerformativePublic praise that is clearly designed to make the manager look good, or to tick a box, is easy to spot. People can tell the difference between genuine acknowledgement and corporate theatre.
- One-size-fits-allNot everyone wants the same kind of recognition. A public shout-out that energises one person may deeply embarrass another. Managers who do not know the difference end up undermining the very people they are trying to celebrate.
What makes recognition land
Recognition that actually resonates shares three qualities: it is specific, it is timely, and it connects the behaviour to its impact. When you tell someone exactly what they did, shortly after they did it, and explain why it mattered, you are doing something powerful. You are showing them that you were paying attention, that you understand what good looks like, and that their contribution made a real difference.
Compare "thanks for your help on the project" with "the way you restructured the timeline after the scope change meant we kept the client informed at every step, and they specifically mentioned it in their feedback". The first is forgettable. The second is something a person remembers for months. It tells them which behaviour to repeat, and it reinforces that their judgement was sound.
This is where your catchups become invaluable. When you log wins and positive observations during your regular 1-1s, you build a record of what each person does well. You are not relying on memory when review season arrives. You have a running thread of specific, timestamped recognition that you can draw on, and your team member can see that their contributions have been noticed consistently, not just when it was convenient.
- Be specificName the exact behaviour or action. "You handled that escalation really well" is better than "good job", but "the way you de-escalated the client by acknowledging their frustration before presenting the solution" is better still.
- Be timelyRecognition loses its power with distance. Telling someone they did something great three weeks ago feels like an afterthought. Say it the same day, or the next morning at the latest.
- Connect to impactExplain why it mattered. Did it save the team time? Did it improve a relationship? Did it set a standard? When people understand the ripple effect of their work, recognition becomes motivating rather than merely pleasant.
- Make it personalReference the individual, not the team. Team-wide praise has its place, but it should not replace direct, personal acknowledgement. People want to know that they, specifically, were seen.
Public vs private recognition
One of the most common mistakes managers make with recognition is assuming that more visible means more impactful. Public praise, whether in a team meeting, a company Slack channel, or an all-hands, can be genuinely motivating for some people. For others, it is acutely uncomfortable. Getting this wrong does not just waste the gesture; it can actively make someone feel worse.
Public recognition works best when the achievement is clearly shared or visible, when the person is comfortable with attention, and when it sets a useful example for the wider team. It is particularly effective for reinforcing team values: if someone went above and beyond to help a colleague, naming that publicly signals what your team culture rewards. Use your meeting notes to capture these moments when they come up in team meetings, so you have a record of the wins your team has celebrated together.
Private recognition, on the other hand, is almost always appropriate. A quiet word in a 1-1, a short message after a meeting, a note in a catchup that says "I noticed what you did there, and it was excellent". This is the foundation. It works for introverts and extroverts alike, and it carries a different kind of weight: it says "I am telling you this because I mean it, not because I want others to see me saying it".
- Public suitsTeam-visible achievements, culture-reinforcing behaviours, and people who are comfortable with the spotlight. Use it to set examples and celebrate shared wins.
- Private suitsPersonal growth, quiet contributions, sensitive individuals, and any recognition where the sincerity matters more than the visibility. This should be your default.
- Ask the personIf you are unsure, ask. "I want to recognise what you did with the migration - would you prefer I mention it in the team meeting, or would you rather I keep it between us?" This question alone is an act of respect.
- Do bothThe strongest recognition often happens privately first, then publicly with permission. The person feels genuinely valued in the moment, and the public acknowledgement becomes a bonus rather than a performance.
Building a recognition habit
Recognition should not be something you have to remember to do. It should be woven into the rhythms you already have. The best managers do not set calendar reminders to praise their team. They have systems that naturally prompt them to notice and name what is going well.
Your regular catchups are the most natural place for this. Before each 1-1, spend two minutes reviewing what the person has been working on and ask yourself: what went well? What did they handle that I should acknowledge? When you log these observations in your catchup notes, you create a pattern of recognition that is consistent, specific, and impossible to forget. Over time, you can use Key Themes to track what each person excels at, spotting patterns in their strengths that might inform development conversations, stretch assignments, or promotion cases.
Recognition also has a follow-through dimension. If someone has done exceptional work, saying so is the minimum. The next step might be creating an Action to nominate them for an award, share their work with senior leadership, or give them a visible opportunity that builds on the strength you have observed. Recognition that leads to something tangible, whether that is visibility, opportunity, or simply a documented record of excellence, carries far more weight than words alone.
- Prep your 1-1sBefore each catchup, identify at least one thing the person did well that week. Write it down. If you cannot think of anything, you may not be paying close enough attention.
- Log itRecord recognition in your catchup notes so it becomes part of the permanent record. When review season arrives, you will have months of specific examples rather than a vague sense that someone "did well".
- Spot patternsUse Key Themes to track recurring strengths. If someone consistently handles stakeholder communication well, that is a theme worth naming and developing, not just a series of isolated compliments.
- Follow throughCreate Actions from recognition moments. Nominate someone for an award. Share their work in a leadership update. Give them a stretch project that builds on the strength you observed. Make recognition the start of something, not the end.
Recognition across different personalities
People differ enormously in how they want to be recognised, and managers who treat recognition as a uniform activity will get inconsistent results. Some people light up when praised in front of the team. Others find it excruciating. Some value words; others value actions, opportunities, or simply being trusted with more responsibility. Understanding these differences is not optional: it is the difference between recognition that motivates and recognition that alienates.
The simplest approach is to ask. Early in your working relationship, or during a catchup, ask each person how they prefer to be recognised. Some will know immediately. Others will need to think about it. Either way, the question itself communicates something important: that you care enough to get it right. Log their preferences in your catchup notes so you do not have to rely on memory, and revisit the question occasionally as people's preferences can shift as they grow in confidence or take on new roles.
Pay attention to the quieter contributors as well. In most teams, the loudest voices attract the most recognition by default. The person who presents the work gets praised, while the person who did the analysis behind it goes unmentioned. Deliberately look for the people whose contributions are less visible, and make sure they hear from you. This is where your meeting notes become useful: when you record who contributed what in team meetings, you create a more accurate picture of where value is coming from, not just who spoke the most.
- Ask preferencesDuring a catchup, ask: "When you do good work, how do you most like that to be acknowledged?" Some want public praise, some want a quiet word, some want more autonomy. Knowing this is essential.
- Watch for introvertsQuieter team members often do critical work without drawing attention to it. If your recognition only flows to the visible contributors, you are reinforcing a system that undervalues depth in favour of volume.
- Adapt your approachOne person might appreciate a message in the team channel. Another might prefer you mention their work to their skip-level manager. Another might simply want to be given a harder problem to solve. Recognition is not one thing.
- Revisit regularlyPeople change. Someone who was uncomfortable with public praise six months ago may feel differently now. Check in periodically and adjust your approach as your team members grow.
Never forget what went well
Log wins in your catchups so recognition is specific, timely, and part of the conversation.