Praise and Recognition
Introduction
You have learned to build rapport, communicate with empathy, and give autonomy. These are the foundational practices that create trust, connection, and ownership on your team. But there is one practice that, more than any other, signals to team members that their work matters and they are valued: praise and recognition. How you acknowledge and celebrate contributions shapes whether your team feels seen or invisible, valued or taken for granted, energized or depleted by their work.
Yet praise and recognition are among the most poorly executed leadership practices in most organizations. Many leaders provide too little, providing recognition so rarely that it loses meaning when it does happen. Others provide too much of the wrong kind, offering generic praise that signals you have not actually paid attention to what they did. Some make recognition political, using it to reward people they favor or to shape behavior they want to see, which makes it feel manipulative. Others provide recognition only for outcomes, not for the effort, judgment, and craftsmanship that produces those outcomes. The result is that recognition, which should be one of the most powerful tools for engagement, often becomes routine, hollow, or even counterproductive.
The challenge is that good praise and recognition seem simple on the surface but are deceptively difficult in practice. They require you to actually notice what people are doing. They require you to understand why their work is valuable. They require you to communicate that understanding in ways that feel specific and authentic. They require you to do this consistently over time, not just when it occurs to you. And they require you to calibrate to what each person actually values, which varies more than most leaders realize.
Many leaders default to easy patterns of praise that they think are doing the job but actually fall flat. "Good job" is meaningless because it could apply to anything. Public recognition without specifics feels performative. Praise that focuses only on results misses the human effort behind them. Recognition that comes only during formal review cycles is too rare to matter daily. Acknowledgment that focuses on what serves the leader rather than what serves the recipient communicates that the leader does not really understand what would matter to this person.
Done well, however, praise and recognition become one of the most powerful engagement tools available. They communicate value, build confidence, reinforce excellence, deepen rapport, and create the kind of relationship where team members feel genuinely seen and appreciated. They cost nothing financially but produce enormous returns in engagement, motivation, and retention. And they are entirely within your control as a leader, regardless of organizational constraints around compensation, promotion, or perks.
This article explores what genuine praise and recognition are, why they matter so much for engagement, the difference between praise (focused on the person and their effort) and recognition (focused on the work and its impact), the multiple dimensions of recognition that go beyond simple verbal praise, what makes praise effective and what makes it fall flat, common mistakes leaders make, how to calibrate recognition to individuals who value different forms of acknowledgment, the role of timing and channel, how to give difficult recognition like recognizing recovery from struggle or growth from failure, the cultural dimension of public recognition, the challenge of recognizing hidden contributions, and the daily practices that build a culture where excellent work is consistently seen, valued, and celebrated.
The leader who masters praise and recognition creates a team where excellent work is visible, valued, and reinforced; where people feel known and appreciated for their unique contributions; and where the act of being recognized is itself energizing rather than performative or political. This is one of the highest-leverage engagement practices available to any leader, and it is entirely a matter of skill and discipline you can develop. Building this skill is the work of this section.
Simple Meaning: Praise and Recognition
Praise and recognition are the deliberate leadership practices of acknowledging and celebrating the contributions, efforts, growth, and achievements of team members in ways that communicate that they are seen, valued, and appreciated. They are how you make visible the often-invisible human work that produces team outcomes.
Praise and recognition are how leaders communicate that work matters and that the people doing the work matter as humans. They are the difference between being seen and being invisible, between being valued and being taken for granted, between energized work and depleted work. For team members, recognition is one of the most powerful signals about their place in the team: whether their efforts are noticed, whether their growth is valued, whether their unique contributions are appreciated, whether they are worth paying attention to. For leaders, praise and recognition are not soft skills or nice-to-haves. They are essential engagement tools that cost nothing but produce enormous returns. Done well, they create teams where excellent work is consistently seen and reinforced, where people feel genuinely valued, and where the work itself becomes more meaningful through being acknowledged. Done poorly or not at all, they create teams where excellent work is taken for granted, where people feel invisible, and where engagement slowly drains away. The investment in mastering praise and recognition is one of the most direct investments you can make in your team's engagement and retention.
Praise and recognition operate through three essential dimensions that work together:
| Dimension | What It Means | What It Looks Like in Practice | What Happens When It Is Missing |
|---|---|---|---|
| Attention | You actually noticed what they did. You were paying attention to the work, the effort, the choices, the contribution. You know what you are recognizing because you observed it. | You can describe specifically what they did, why it was valuable, what made it good. Your recognition reflects real observation, not generic appreciation. | Recognition feels generic because you did not actually pay attention. Team members sense that you did not really see what they did. The acknowledgment falls flat. |
| Understanding | You understand why the work matters. You grasp the value of what they contributed, the difficulty of what they accomplished, the significance of what they did. | You can articulate why something they did was valuable, not just that it was done. You connect their work to broader impact, to skill, to judgment, to growth. | Recognition feels superficial because you do not understand what made the work valuable. Team members feel that you recognize work without grasping it. |
| Communication | You communicate your attention and understanding to them in ways that land well. The recognition is delivered effectively given their preferences and the situation. | The recognition is specific, genuine, well-timed, and delivered in the right channel for the situation and the recipient. | You may notice and understand, but they do not feel recognized because you have not communicated it well. Internal appreciation that is not communicated does not register. |
All three dimensions must be present for praise and recognition to genuinely register with team members. Attention without understanding produces recognition that feels superficial. Understanding without communication remains private and does not serve the team member. Communication without genuine attention and understanding feels hollow or performative. Real praise and recognition require all three working together.
The Difference Between Praise and Recognition
Praise and recognition are often used interchangeably, but they serve different functions and work best when used together rather than confused for each other.
| Aspect | Praise | Recognition |
|---|---|---|
| Focus | The person, their qualities, effort, judgment, character, and growth | The work, what was accomplished, the value created, the impact made |
| Example | "You showed great judgment in how you handled that situation" or "Your dedication to quality is exceptional" | "The architecture you designed for the new service has reduced load times by 40%" or "Your work on the migration enabled us to ship on time" |
| What It Communicates | "I see who you are. I value your qualities. You as a person matter." | "I see what you did. I value what you contributed. Your work matters." |
| Best Used For | Building relationship. Reinforcing valued qualities. Supporting growth. Recognizing effort even when outcomes vary. Acknowledging character. | Reinforcing valued work. Acknowledging specific contributions. Celebrating accomplishments. Making impact visible. |
| Risk When Overused | Can feel hollow or performative if not anchored in specifics. Can become routine and lose meaning. | Can feel transactional or focused only on outcomes if not balanced with praise. Can miss the human behind the work. |
| Risk When Underused | Team members feel valued only for what they produce, not who they are. The human dimension of leadership is missing. | Team members feel that their contributions are invisible. The work is taken for granted. Their impact is not visible to them. |
| What Makes It Powerful | Specificity about what you observed. Genuine appreciation for who they are. Connection to their growth or character. | Specificity about the work. Understanding of the value. Connection to broader impact or excellence. |
| What Makes It Fall Flat | Generic compliments ("great job," "amazing work"). Praise that feels manipulative or politically motivated. Praise disconnected from specific observation. | Outcome focus without acknowledgment of effort or judgment. Recognition that misses the most valuable contributions. Recognition driven by visibility rather than value. |
Using Both Together
The most powerful acknowledgment uses both praise and recognition together: "The way you approached that problem (recognition of the work) shows the kind of analytical rigor you consistently bring (praise of the person)." This combination communicates both that you see specifically what they did and that you understand the qualities behind it. It honors both the work and the human.
What Recognition Is Not
Several practices are commonly mistaken for genuine recognition. Understanding what recognition is NOT clarifies what genuine recognition requires.
| What It Is Confused With | How It Differs from Real Recognition | Why the Confusion Matters |
|---|---|---|
| Generic Praise | Real recognition is specific to what was done. Generic praise ("good job," "great work") could apply to anything and recognizes nothing in particular. | Leaders think generic praise counts as recognition, but team members experience it as hollow because it does not reflect actual attention. |
| Politically Motivated Acknowledgment | Real recognition is driven by genuine value. Politically motivated recognition is driven by visibility, favoritism, or shaping behavior, and team members can detect this. | When recognition is political, it loses its power and can become counterproductive. The team trusts the leader less, not more. |
| Performance Review Comments | Real recognition happens in the moment, close to the work being recognized. Annual review comments are useful but too rare and too disconnected to function as ongoing recognition. | Leaders may believe formal review processes handle recognition, but they do not. Recognition must happen continuously, not annually. |
| Bonus or Promotion | Real recognition is regular, low-cost, and frequent. Bonuses and promotions are valuable but rare and tied to systems. They cannot substitute for ongoing recognition. | Leaders may think compensation is recognition enough, but compensation addresses different needs. Recognition is about being seen and valued, which money does not fully provide. |
| Routine Pleasantries | Real recognition is targeted at specific work or qualities. Routine pleasantries ("thanks for that," "appreciate it") are nice but do not constitute meaningful recognition. | Leaders may think their general pleasantness substitutes for recognition. It does not. Pleasantries are background; recognition is foreground. |
| Public Visibility | Real recognition reflects actual value. Public visibility may or may not align with real value, and what is most visible is not always what is most valuable. | Recognition driven by visibility rewards self-promotion rather than contribution. Quiet contributors get systematically under-recognized. |
| Backhanded Compliments | Real recognition is genuinely positive. Backhanded compliments ("you finally got that right," "for someone with your experience, that was good") undermine even valid recognition. | Leaders sometimes intend praise but deliver it in ways that diminish rather than honor. The recipient ends up worse than if nothing had been said. |
| Recognition Tied to Future Asks | Real recognition stands on its own. Recognition that is immediately followed by a request for more effort feels manipulative, like setup for the ask. | "You did great work on this... and now I need you to..." reduces the recognition to a manipulation technique. |
The Authenticity Test
Here is a simple test for whether your recognition is authentic: would the same recognition land well if delivered exactly the same way to anyone who did similar work? If yes, the recognition is generic and not really about this specific person and their contribution. If no, the recognition reflects what is specific about what this person did and what makes their contribution unique. Real recognition can only be delivered to the specific person it is for, because it reflects what they specifically contributed.
The Dimensions of Recognition
Recognition is not just verbal acknowledgment. It operates through multiple dimensions, and the most engaging recognition cultures use several of them in combination.
| Dimension | What It Means | Example | When It Matters Most |
|---|---|---|---|
| Verbal Recognition | Spoken acknowledgment of contribution or qualities, in person or in conversation. | "The way you handled that customer issue showed real judgment. The customer felt heard, and we kept the relationship intact." | For most everyday recognition. The most flexible and most personal form. |
| Written Recognition | Recognition documented in writing, where the recipient can save it and revisit it. | An email or message specifically calling out a contribution, what made it valuable, and the impact. | For significant contributions worth remembering. For things you want them to be able to share or reference. For things that matter for their professional reputation. |
| Public Recognition | Recognition delivered in front of others: in team meetings, in larger forums, in writing visible to others. | Acknowledging a team member's contribution in a team meeting or stakeholder update. | For contributions that benefit the whole team. For setting standards about what is valued. When the recipient is comfortable with public recognition. |
| Private Recognition | Recognition delivered just between you and the recipient. | A one-on-one conversation specifically acknowledging something they did. | For deeply personal recognition. For people who don't want public visibility. For acknowledgment that needs space for response and dialogue. |
| Tangible Recognition | Recognition through tangible expressions: small gifts, written notes, physical tokens. | A handwritten note thanking them for something specific. A small gift related to a known interest. | For exceptional contributions. For relationships where tangible expressions matter. For when verbal recognition has been frequent and something different is appropriate. |
| Opportunity Recognition | Recognition through opportunities: stretch assignments, visibility, leadership roles, learning chances. | Giving someone the lead on a high-visibility project specifically because of demonstrated capability. | For sustained excellence. For people who are growing. For acknowledging capability rather than just performance. |
| Advocacy Recognition | Recognition through advocating for them with others: telling your manager about their work, recommending them, defending them. | Talking about a team member's contributions with your manager in performance discussions. | For people whose work might otherwise be invisible to leadership. For supporting career advancement. For protecting against undeserved criticism. |
| Time Recognition | Recognition through dedicating your time: substantive one-on-ones, attending their presentations, engaging with their work. | Spending real time with their work, attending their demo, engaging substantively with their thinking. | Often the most powerful but most overlooked. Time is the scarcest leadership resource; spending it on someone shows they matter. |
| Defense Recognition | Recognition through defending their work and decisions when challenged by others. | Defending a team member's technical decision when stakeholders question it. | When their work is questioned by others. When they have made decisions that need backing. When they cannot defend themselves. |
Mixing the Dimensions
The most engaging recognition culture mixes dimensions thoughtfully. Some people respond most to public verbal recognition. Others find it uncomfortable but value written private notes. Some are most touched by time spent engaging with their work. Others most appreciate advocacy with leadership. Knowing your team members well enough to recognize them in the ways that land best is one of the marks of leadership skill.
What Makes Praise and Recognition Effective
Effective recognition is not random; it follows specific patterns. Understanding these patterns helps you give recognition that actually lands.
| Quality | What It Means | What Effective Looks Like | What Ineffective Looks Like |
|---|---|---|---|
| Specific | The recognition identifies exactly what is being recognized, with detail that could not apply to anything else. | "The way you structured your investigation of that issue, starting with the production logs, then narrowing to the specific service, then identifying the configuration bug, was excellent debugging methodology." | "Great debugging work on that issue." |
| Genuine | The recognition reflects actual appreciation and observation, not obligation or strategy. | Recognition that flows from genuine appreciation of the work, communicated in your authentic voice. | Recognition that feels scripted, performative, or like it's checking a box. |
| Timely | The recognition happens close to the work being recognized. Months-old recognition is much less powerful than recognition in the moment or shortly after. | "What you did yesterday in handling that situation was excellent. Here's why..." | "You know that thing you did three months ago? That was good." (Loses power through delay.) |
| Contextual | The recognition connects the work to broader context: why it mattered, what impact it had, how it fits into larger goals. | "Your refactoring of that module not only cleaned up the code but also made it much easier for the new team members to ramp up. That's a real impact." | "You refactored that module well." (Misses the why.) |
| Frequent Enough | Recognition happens often enough to be felt. Recognition that happens once a year does not register as continuous appreciation. | Regular small recognitions throughout the work, with deeper recognition for more substantial accomplishments. | Recognition only at formal moments like performance reviews. |
| Calibrated to the Recipient | The form and channel match what the recipient values. Some want public; some want private. Some respond to written; some to verbal. | Recognizing a private person privately. Recognizing a person who values written acknowledgment in writing. | Recognizing a private person publicly. Giving brief verbal recognition to someone who values substantive written acknowledgment. |
| Proportionate | The recognition matches the contribution. Small contributions get acknowledged; large contributions get more substantial recognition. | A thank-you for routine help. Substantial recognition for significant contributions. Major recognition for exceptional work. | Everything getting the same level of recognition. Either constant over-the-top praise for routine work or insufficient acknowledgment of major contributions. |
| Connected to Their Growth | The recognition acknowledges not just what they did but who they are becoming. It reinforces patterns of growth and development. | "This kind of work shows the technical leadership you've been building. You're not just executing; you're shaping direction." | Recognition that misses the development dimension and treats every accomplishment as isolated. |
| Standing Alone | The recognition is not immediately followed by criticism, requests for more, or other agenda items that diminish it. | Recognition that ends on the positive note, allowing it to land fully. | "Great work on X. Now I need you to also..." (Reduces recognition to setup for the ask.) |
| Backed by Action | The recognition is consistent with broader actions: what gets recognized aligns with what actually gets supported, developed, and rewarded. | Recognition that aligns with how the team is actually treated, what gets prioritized, who gets developed. | Recognition that contradicts other signals (recognizing what you say you value but actually punishing through other actions). |
What Makes Praise and Recognition Fall Flat
Equally important is understanding what makes recognition ineffective, often in ways leaders do not realize.
| Failure Pattern | What It Looks Like | Why It Falls Flat | How to Replace It |
|---|---|---|---|
| Generic Language | "Good job," "Great work," "Nice job," "Thanks for that" | Could apply to anyone doing anything. Communicates that you have not actually paid attention to specifics. | Always include what specifically was good. "The way you did X was particularly effective because Y." |
| Outcome-Only Focus | Recognition focused only on results, ignoring the effort, judgment, and craftsmanship that produced them. | Communicates that you only care about outputs, not the work behind them. Misses the human dimension. | Recognize the process and effort alongside outcomes. "The result was great, and the way you got there was even more impressive." |
| The Sandwich | Praise followed immediately by criticism, with the criticism diminishing the praise: "You did X really well, but..." | The recipient learns to brace for the criticism whenever they hear praise. The praise loses its power because it is associated with what follows. | Let praise stand alone. Address concerns in separate conversations, not as appendages to recognition. |
| Setup for the Ask | Recognition immediately followed by a request: "Great work. Now I need you to also..." | The recognition is reduced to a manipulation technique. The team member feels that the praise was strategic, not genuine. | Separate recognition from requests. If you need to ask for more effort, do it later, not as a follow-on to recognition. |
| Public Recognition That Embarrasses | Singling out a private person publicly. Effusive praise that makes the recipient uncomfortable. | What was intended as honor becomes discomfort. The recipient may avoid the kind of contribution that produces such recognition. | Know your team members' preferences. Use private recognition for private people. Save public recognition for those who welcome it. |
| Delayed Recognition | Recognition months or years after the fact, when it has lost connection to the work. | Loses the immediacy that makes recognition powerful. The recipient struggles to feel recognized for something so distant. | Recognize close to the work. If you missed the moment, acknowledge the delay: "I should have said this then, but..." |
| Recognition Driven by Visibility | Recognizing what was visible rather than what was valuable. The squeaky wheel gets the recognition. | The team learns that visibility matters more than contribution. Quiet excellent workers get systematically under-recognized. | Actively look for what was valuable, especially when it was not visible. Recognize the unsung work. |
| Routine Recognition | Praise that has become routine: the same words, the same situations, the same patterns, all the time. | Recognition that becomes routine loses meaning. Team members tune it out as background noise. | Vary your recognition. Find new ways to acknowledge. Match the recognition to what is actually distinctive about each contribution. |
| Backhanded Praise | "You finally got that right" or "That was good, for you" or "Even you couldn't mess that up" | Diminishes the recipient even while ostensibly recognizing them. The recipient remembers the diminishment more than the recognition. | Make praise unambiguously positive. If you have concerns about consistency or past performance, address them separately and constructively. |
| Inconsistent Recognition | Praising some people frequently while never recognizing others, despite comparable contributions. | The unrecognized notice. They wonder what is wrong with them. The favored learn that being favored means more than producing. | Track who you have recognized recently. Distribute attention to recognition deliberately. Make sure quiet contributors get their share. |
| Recognition That Misses What Matters Most | Recognizing the obvious or visible while missing the harder, more valuable work that the recipient knows was their real contribution. | The recipient feels that you do not actually understand their work. The recognition lands as evidence of your lack of comprehension rather than as appreciation. | Understand what they actually consider their best work. Recognize what they take pride in, not just what is most visible to you. |
| Public Recognition That Sets Expectations | Praising someone publicly in ways that imply this is now expected of everyone: "I wish everyone showed this level of commitment." | The recognized person becomes a tool to pressure others. The praise damages the relationship with everyone else without strengthening the relationship with the recognized. | Recognize without making comparisons. Praise what was done without using it to criticize others. |
Calibrating Recognition to Individuals
Different people respond to different forms of recognition. What energizes one person may embarrass another. What feels meaningful to one feels routine to another. Effective leaders learn what works for each team member and calibrate accordingly.
| Recognition Preference | What Energizes Them | What Falls Flat | How to Recognize Them |
|---|---|---|---|
| Public-Oriented | Recognition in front of others. Team announcements. Visible acknowledgment of their work to broader audiences. | Private recognition that they cannot share. Quiet acknowledgment that nobody else witnesses. | Recognize them publicly. Mention their work in team meetings. Make sure leadership knows what they did. Allow visibility to be part of the recognition. |
| Private-Oriented | Personal, private recognition. One-on-one acknowledgment. Written notes that they can save without others knowing. | Being singled out publicly. Effusive public praise. Visibility that makes them uncomfortable. | Recognize them privately. Take time in one-on-ones. Send written messages. Avoid putting them on the spot publicly. |
| Verbal Communicators | Spoken acknowledgment, especially substantive conversation about what they did and why it mattered. | Written-only recognition that they perceive as less engaged. Brief verbal acknowledgments that don't engage substantively. | Talk to them about their work. Take time to explain what you appreciated. Engage in substantive conversation about what made the work valuable. |
| Written Communicators | Documented recognition that they can save, share, or revisit. Detailed acknowledgment that shows real thought. | Brief verbal recognition that they cannot reference later. Recognition in passing that they cannot share with others or save. | Send written messages, emails, or notes. Make recognition tangible. Allow them to have a record they can revisit. |
| Achievement-Focused | Recognition of specific accomplishments and outcomes. Acknowledgment of results, impact, and metrics. | Recognition of effort that did not produce results. Process-focused acknowledgment that ignores outcomes. | Focus on what they accomplished and the impact it had. Make outcomes visible. Connect their work to results. |
| Growth-Focused | Recognition of their development, learning, and progress. Acknowledgment of how they have grown. | Recognition only of accomplishments without acknowledgment of the growth that produced them. | Frame recognition around growth and development. "The way you handled this shows how much you've grown in this area." Connect work to their development arc. |
| Craftsmanship-Focused | Recognition of the quality of their work, the elegance of their approach, the care they put into the craft. | Recognition only of outcomes, missing what they take pride in: how the work was done. | Recognize the quality and care in their work. Notice the elegance, the thoroughness, the craftsmanship. Show that you see how it was done, not just what was produced. |
| Impact-Focused | Recognition tied to broader purpose: how their work affected customers, the team, the company, or the larger mission. | Recognition that focuses only on the immediate work without connecting to broader impact. | Connect their work to its broader impact. "Because of what you did, X happened, which means Y for our customers/users/team." |
| Relationship-Focused | Recognition that comes through your investment of time and attention. The recognition is in being engaged with as much as in what is said. | Brief recognition that doesn't feel like substantive engagement. Recognition that feels efficient but transactional. | Spend real time engaging with their work. Have substantive conversations. Make clear through time investment that you value them. |
Discovering Their Preferences
You can discover what kind of recognition works for each team member through several means:
- Watch their reactions. When you recognize them, do they light up or become uncomfortable? What forms of recognition produce engagement vs. retreat?
- Notice what they remember. What recognition do they later reference? That is what landed.
- Ask directly. "How do you like to be recognized? Public, private? Written, verbal? What forms of acknowledgment matter most to you?"
- Observe what they value. What do they take pride in? What do they emphasize about their own work? These are clues to what they want recognized.
- Pay attention to how they recognize others. People often give recognition in the form they themselves value.
The Hidden Contributions Problem
One of the most common recognition failures is missing the contributions that are not visible. Some of the most valuable work happens out of sight: the careful judgment that prevented a problem, the relationship maintenance that kept things smooth, the deep technical thinking that made the implementation simple. Leaders who only recognize visible work systematically under-value the people doing this invisible work.
| Type of Hidden Contribution | What It Looks Like | Why It Is Hard to See | How to Recognize It |
|---|---|---|---|
| Prevention Work | The careful review that caught a bug before it shipped. The proactive maintenance that prevented an outage. The risk analysis that avoided a problem. | What doesn't happen doesn't get noticed. Successful prevention looks like nothing happening. | Look for what could have gone wrong but didn't. Ask team members about the problems they prevented. Make prevention visible by naming it. |
| Foundation Work | The careful architecture that enabled rapid feature development. The infrastructure work that made everything else possible. The documentation that helped others. | Foundation work is invisible because it appears in others' successful work. Credit flows to the visible work that built on it. | Explicitly trace successful work back to the foundations that enabled it. Recognize the foundation work that made later success possible. |
| Relationship Maintenance | The careful communication that kept stakeholders informed. The patience that maintained good working relationships. The diplomatic handling of difficult situations. | Successful relationship work looks like good relationships, which then are credited to general team culture rather than specific effort. | Notice who maintains key relationships. Recognize the specific work of keeping things smooth. Make visible the effort behind apparently easy collaboration. |
| Mentoring and Teaching | The time spent helping less experienced colleagues. The patience in explaining things. The investment in growing other team members. | Mentoring impact shows up in the mentees' work, not the mentor's. The development happens privately. | Recognize specifically the time and effort spent helping others. Ask team members about who has helped them. Make visible the work of growing the team. |
| Judgment Calls | The decisions to prioritize one thing over another. The choices about what to invest in. The judgment about what could wait and what couldn't. | Judgment shows up in what doesn't happen as much as what does. Good judgment looks like obvious choices in retrospect. | Recognize the specific judgment behind decisions, especially when the outcomes are good. "Your call to prioritize X was the right one and it wasn't obvious at the time." |
| Emotional Labor | The work of staying calm in difficult situations. The energy spent supporting team members through challenges. The effort of managing one's own reactions to enable others. | Emotional labor is invisible by design. It looks like easy professionalism. The work behind staying calm doesn't show. | Notice when team members do the hard emotional work of leadership or collaboration. Recognize the effort of staying steady when steadiness was hard. |
| Coordination Work | The work of keeping multiple efforts aligned. The communication across teams. The coordination of dependencies. | Successful coordination looks like nothing notable happening. Failed coordination is highly visible; successful coordination is invisible. | Recognize the coordination work specifically. "The way you kept these three workstreams aligned was excellent project leadership." |
| Quality Investment | The time spent on test coverage. The extra care in code review. The thoroughness that prevented future problems. | Quality investment pays off later. The immediate effort looks like slow delivery; the long-term payoff is invisible to those who don't see it. | Explicitly value the quality investment in recognition. "Your investment in test coverage on that module has made everything we've built on top of it more reliable." |
Making Hidden Work Visible
Leaders can systematically work to make hidden contributions visible:
- Ask the right questions. Not just "what did you accomplish?" but "what problems did you prevent? Whose work did you enable? Who did you help?"
- Trace credit back. When visible work succeeds, trace it back to the less visible work that enabled it.
- Name the categories. Explicitly recognize hidden categories of work: prevention, foundation, mentoring, judgment. This makes the team aware that these things are valued.
- Watch the team's responses. The people who consistently get less recognition than they deserve often deserve more attention to their hidden work.
- Ask for nominations. Ask team members to recognize each other. Often the people doing hidden work are best seen by their colleagues.
Recognition Through Difficult Situations
Some of the most powerful recognition comes in situations that are harder to handle than straightforward acknowledgment of success. How you handle these moments distinguishes leaders who give recognition skillfully from those who only recognize the easy stuff.
| Difficult Recognition Situation | The Challenge | How to Handle It |
|---|---|---|
| Recognizing Recovery from Failure | Someone made a mistake but handled the recovery well. How do you acknowledge the recovery without minimizing the original failure? | Recognize the recovery specifically: "The way you handled the situation after the issue was discovered was excellent. You took ownership, identified the root cause, and put preventive measures in place." Acknowledge both that the failure happened and that the response showed real character. |
| Recognizing Growth After Struggle | Someone has been struggling and is now showing real progress. How do you celebrate the growth without making them feel that you're surprised they're now performing? | Focus on the growth itself: "I can see how much you've developed in this area over the past few months. The thinking you brought to this is much stronger than even six months ago." Honor the work of growth. |
| Recognizing Effort That Didn't Succeed | Someone put in real effort, but the outcome wasn't what they hoped. How do you recognize the work without falsely celebrating failure? | Be honest about what didn't work, then recognize what did: "The outcome wasn't what we hoped, and we'll learn from that. But the effort, the thinking, the persistence you brought to this was real. That doesn't change based on this one outcome." |
| Recognizing Someone Who Disagreed and Was Right | Someone pushed back on a decision, you went forward anyway, and they were right. How do you acknowledge this without losing authority? | Honor it directly: "You raised concerns about this direction, and you were right. I should have weighted your input more heavily. I appreciate that you raised the concerns even when I pushed forward." This builds trust dramatically. |
| Recognizing Quiet Sustained Excellence | Someone has been consistently excellent over a long period without any single dramatic moment to recognize. How do you acknowledge sustained excellence? | Name the pattern: "I want to recognize something that doesn't have a single moment but is consistent. Your work over [time period] has been exceptional in [specific ways]. That sustained excellence is more valuable than dramatic peaks." |
| Recognizing Someone in a Difficult Phase | Someone is going through a hard time personally or professionally and isn't at their best. How do you find what to recognize? | Recognize what is real even in the difficult phase: their character, their effort despite difficulty, the way they've kept going. "I see how hard this period has been. What you've maintained even through this is real, and I see it." |
| Recognizing Work That Created Conflict | Someone did good work that nonetheless created conflict with stakeholders or other teams. How do you recognize them without endorsing the conflict? | Recognize the work and the situation honestly: "The work you did was genuinely excellent. The fact that it created some conflict reflects the difficulty of the situation, not a flaw in your work. I appreciate that you did what was right even when it was hard." |
| Recognizing Departing Team Members | Someone is leaving the team. How do you recognize their contribution meaningfully despite their departure? | Focus on what they contributed and what they meant to the team: "You've been important to this team in ways that will outlast your departure. Specifically, [what they contributed]. I'm grateful for what you've built here." Make the recognition real even though they're leaving. |
Daily and Weekly Practices for Recognition
Recognition becomes a leadership capability through consistent daily and weekly practices, not through occasional large gestures.
Daily Practices
- Notice something specific: Each day, deliberately notice at least one specific thing a team member did well. Pay attention to the work, the judgment, the effort.
- Acknowledge in the moment: When you notice something worth acknowledging, do it then. Don't wait. The proximity to the work makes the recognition more powerful.
- Be specific in language: Practice replacing "good job" with specific descriptions of what was good and why.
- Match recognition to person: Adapt how you recognize each team member based on their preferences.
- Avoid the recognition trap: Don't follow recognition with criticism or requests. Let it stand.
Weekly Practices
- Recognition audit: At the end of each week, review who you recognized and who you didn't. Are there team members who deserve recognition you haven't given?
- Hidden work check: What contributions this week weren't obvious? Whose work enabled others' success?
- Written recognition: Each week, send at least one written recognition to a team member: a note, email, or message that documents specific recognition.
- Public recognition: If appropriate, recognize someone's work publicly in a team meeting or written team update.
- One-on-one recognition: In each one-on-one, include specific recognition. Make this a consistent part of the conversation.
Monthly Practices
- Pattern review: Look at recognition patterns over the month. Who is getting recognized regularly? Who isn't? Are there structural patterns you should address?
- Calibration check: Are you recognizing the things that matter most, or have you fallen into patterns of recognizing what is easiest to see?
- Quality reflection: Read recent recognitions you've given. Are they specific? Authentic? Connected to broader context? Where can they improve?
- Recognition through other channels: What advocacy, opportunities, time investments, or defense have you given that recognize contributions in non-verbal ways?
Ongoing Mindsets
- Recognition is information, not just feel-good: What gets recognized signals what is valued. Recognize what you actually want more of.
- The frequency matters: Sparse recognition feels obligatory. Regular recognition feels natural.
- The specificity matters: Specific recognition demonstrates attention; generic recognition shows the absence of attention.
- The calibration matters: Recognition that lands depends on knowing the recipient.
- The authenticity matters: Performative recognition is worse than no recognition.
- The hidden work matters: The most important recognition often goes to what is least visible.
Recognition in IT and Agile Teams
Recognition has specific applications in IT and Agile environments.
- In Sprint Retrospectives: Build in time for specific recognition of contributions during the sprint. Make this regular and substantive, not perfunctory.
- In Sprint Reviews: When demonstrating work, recognize specifically who did what and what made their contribution valuable. Don't just show the work; honor the workers.
- In Daily Standups: When team members report blockers being resolved or significant progress, briefly acknowledge specifically what enabled the resolution.
- In Code Reviews: Recognition can be embedded in code review comments. "This is an elegant solution because..." or "I appreciate the thoroughness of your testing here."
- In Incident Response: When incidents are resolved, recognize specifically who did what well. Don't just discuss what happened; honor the response.
- In Architecture Discussions: When engineers contribute well-reasoned architectural perspectives, recognize the specific quality of their thinking.
- In Demos: When team members demo work, recognize specifically what they accomplished and what was difficult about it.
- In Cross-Team Recognition: Recognize team members to stakeholders and other teams. Make their work visible beyond your team.
- In Career Conversations: Use career conversations to recognize sustained patterns of contribution and growth, not just individual moments.
- In Performance Reviews: Build performance recognition on the ongoing recognition you've already given throughout the year, not as a separate annual exercise.
Practical Workplace Scenario
Scenario
A team lead named Rashmi managed a team of seven engineers building a customer analytics platform. By her own assessment, she was a fair and reasonable leader. But she noticed that engagement on her team seemed lower than it should be. Her team did good work, but they didn't seem energized by it. She wondered what was missing.
Then a senior engineer, Aniket, sat down for a casual conversation and said something that surprised her: "Rashmi, I want to give you some feedback that's hard to share. I don't feel particularly recognized on this team. I'm not asking for awards. But I've been working hard for two years here. I've contributed significantly. And I rarely feel that you actually see what I do. Other team members have told me they feel similarly."
Rashmi's Defense
Rashmi's first reaction was defensive. "I appreciate everyone's work. I say thank you all the time. I praise people in retrospectives." But Aniket pushed back: "When you say thank you, it's brief and generic. 'Thanks for that' or 'good job.' It doesn't feel like recognition; it feels like politeness. In retrospectives, you recognize people, but it's general. 'The team did great this sprint.' That doesn't recognize anyone specifically. I don't feel that you know what I specifically contributed."
The Honest Look
Rashmi paid attention over the next week to her own recognition behavior. What she noticed was uncomfortable:
- Most of her recognition was generic: "good job," "thanks for that," "nice work"
- She rarely connected recognition to specific contributions
- She mostly recognized in passing, never with focused attention
- She defaulted to recognizing the most visible work, often missing the deeper contributions
- She rarely wrote anything down, so recognition was forgettable
- She had favorites who got more recognition than others, partly based on visibility
- She gave recognition in patterns that ignored what different team members actually valued
The Recognition Audit
Rashmi did a deeper audit by team member. For each person, she asked herself: "Can I describe specifically what they contributed in the past month? Can I name specific examples of their best work? Have I told them, in specific terms, what makes their work valuable?" For three of her seven team members, she could not. For two more, she could only partially. Only two had received recognition that matched what she could see they had actually contributed.
The Conversations
Rashmi did something brave: she had individual conversations with each team member. "Aniket gave me feedback that I haven't been recognizing the team well. I want to hear from you directly. How does my recognition land with you? What would feel like real recognition?"
What she heard varied significantly:
- One engineer said: "I'd appreciate written acknowledgment that I can save and reference later. Brief verbal recognition doesn't stick for me."
- Another said: "I want recognition that connects to broader impact. Tell me how my work mattered to the customer or the team, not just that I did something well."
- A third said: "I want recognition that addresses the harder parts of what I do, not just the visible parts. The judgment calls I make matter to me; nobody recognizes those."
- A fourth said: "I prefer private recognition. Don't single me out publicly. But when you recognize me privately, please be specific about what you observed."
- A fifth said: "Time is what I value most. Spending real time engaging with my work is the recognition that matters to me."
- A sixth said: "I want recognition that connects to my growth. Tell me when you see me developing, not just when I produce outputs."
- Aniket said: "I want recognition that demonstrates you actually understand what I'm doing. I don't need praise; I need to feel seen."
The Plan
Rashmi developed deliberate practices:
- Specificity discipline: No more generic "good job." Every recognition needed to be specific about what was good and why.
- Calibrated to each person: Recognition for each team member adapted to what they had said they valued.
- Written recognition weekly: Send at least one written acknowledgment per week, rotating through the team.
- Attention to hidden work: Deliberately look for the contributions that weren't visible. Recognize prevention, foundation, judgment, and quiet excellence.
- Substantive engagement: Spend real time with team members' work. Don't just recognize from a distance; engage substantively.
- Recognition tracking: Keep a simple list of recognition given to ensure no one was being systematically overlooked.
The Process
The first weeks felt awkward. Rashmi had to consciously slow down her usual quick acknowledgments. She had to think about what specifically she wanted to recognize. She had to remember each person's preferences. She had to identify the hidden work that wasn't immediately obvious.
But the team noticed. One engineer, who had been receiving written notes, sent her a message: "I really appreciate the written feedback you've been sending. I've saved them. It's the best recognition I've received in years." Another, who valued engagement with her work, said: "Thank you for spending the time to actually understand what I was building. That meant more than any verbal praise." Aniket, who had started the conversation, said: "I see the difference. You're actually seeing what I'm doing now. I feel recognized."
The Result
Six months later, the team's engagement had visibly improved:
- Team members reported feeling more valued and seen
- Discretionary effort increased; people were bringing more to their work
- Voluntary turnover that Rashmi had been worried about did not materialize
- The team's energy in meetings and discussions improved
- Hidden contributions started to become more visible because team members felt safer surfacing them
- Rashmi's relationships with team members deepened significantly
Rashmi reflected: "I thought I was recognizing my team. Saying 'thanks' and 'good job' frequently. But it turned out I was checking a politeness box, not actually recognizing anyone. Real recognition required me to actually pay attention to what each person was doing, understand what made it valuable, calibrate to what they specifically valued, and communicate in ways that landed for them. That's much harder than saying 'good job.' But it's also dramatically more powerful. My team is now doing different and better work because they feel genuinely valued. And I've discovered that recognition is one of the most impactful and least expensive leadership tools available. It costs nothing in money or perks, but it pays back enormously in engagement, motivation, and retention. The discipline is in doing it well, not in doing it at all. Most leaders, including me before this, give recognition that doesn't really register because they don't take the time to make it specific, calibrated, and substantive. That changed my approach permanently."
Learning
Rashmi's experience teaches several important lessons:
- Many leaders think they're recognizing their teams when they're actually being politely generic
- Generic recognition doesn't register as recognition; it lands as politeness
- Real recognition requires specificity, calibration, and substantive attention
- Different team members value different forms of recognition
- Asking directly is one of the best ways to learn what works for each person
- Hidden contributions are often the most valuable and the most under-recognized
- The investment in recognition pays enormous returns in engagement
- It's never too late to develop better recognition practices, even after years of generic patterns
Praise and Recognition Reflection Checklist
| Practice | Yes / No |
|---|---|
| I give recognition that is specific to what was actually done. | |
| I give recognition that reflects genuine understanding of why the work was valuable. | |
| I calibrate recognition to each team member's preferences. | |
| I give recognition close in time to the work being recognized. | |
| I recognize both the work (results) and the person (effort, judgment, qualities). | |
| I avoid generic language like "good job" or "great work" without specifics. | |
| I let praise stand alone without immediately following with criticism or requests. | |
| I distribute recognition equitably, including to quieter team members. | |
| I make hidden contributions visible through deliberate recognition. | |
| I use multiple channels for recognition: verbal, written, opportunity, advocacy, time. | |
| I track who I have recognized recently to ensure I'm not overlooking anyone. | |
| I have asked team members directly how they prefer to be recognized. | |
| I provide recognition through difficult moments, including recovery from failure and quiet sustained excellence. | |
| I treat praise and recognition as deliberate leadership practices, not optional extras. |
Self-Reflection Questions
Use these questions to assess your praise and recognition practice and identify growth opportunities.
- If I audited my recognition over a week, would it be specific or generic? Would it reflect real attention or perfunctory politeness?
- For each team member, can I describe specifically what they have contributed in the past month and what makes their work valuable?
- Am I distributing recognition equitably, or am I disproportionately recognizing visible or favored team members?
- What hidden contributions am I missing? Whose foundation work, prevention work, mentoring, or judgment am I not seeing?
- Have I asked team members directly how they prefer to be recognized?
- Does my recognition fall flat or land well? What evidence do I have?
- Do I follow recognition with criticism or requests, undermining the recognition?
- What is the ratio of generic to specific recognition I give?
- Am I recognizing through multiple channels (verbal, written, opportunity, advocacy, time), or am I limited to one or two?
- How recently have I given each team member meaningful, specific recognition?
- Am I recognizing growth and process, or only outcomes?
- How do I handle the difficult recognition situations: recovery from failure, sustained excellence, growth after struggle?
- What is my biggest recognition gap right now: specificity, frequency, equity, calibration, or substantive engagement?
- What is one specific change I will make this week to improve my recognition practice?
Key Takeaways
- Praise and recognition are essential engagement tools that signal value, build confidence, reinforce excellence, and deepen rapport. They cost nothing but produce enormous returns when done well.
- Praise focuses on the person and their qualities. Recognition focuses on the work and its value. Both work best when used together.
- Recognition is NOT generic praise, political acknowledgment, performance reviews, compensation, routine pleasantries, public visibility, backhanded compliments, or recognition tied to future asks.
- Real recognition operates through three dimensions: attention (you noticed), understanding (you know why it's valuable), and communication (you express it well).
- Recognition has nine dimensions: verbal, written, public, private, tangible, opportunity, advocacy, time, and defense. The most engaging recognition uses multiple dimensions thoughtfully.
- Effective recognition is specific, genuine, timely, contextual, frequent enough, calibrated to the recipient, proportionate, connected to growth, standing alone, and backed by action.
- Ineffective recognition uses generic language, focuses only on outcomes, gets sandwiched with criticism, sets up requests, embarrasses through public visibility, is delayed, is driven by visibility rather than value, becomes routine, is backhanded, or is inconsistent.
- Different team members value different forms of recognition: public vs. private, verbal vs. written, achievement-focused vs. growth-focused, outcome-focused vs. craftsmanship-focused. Effective leaders calibrate to each person.
- Discover individual preferences through watching reactions, noticing what they remember, asking directly, observing what they value, and paying attention to how they recognize others.
- Hidden contributions are often the most valuable and the most under-recognized: prevention work, foundation work, relationship maintenance, mentoring, judgment calls, emotional labor, coordination, and quality investment.
- Some of the most powerful recognition comes through difficult situations: recovery from failure, growth after struggle, effort that didn't succeed, being right when you were wrong, sustained quiet excellence, difficult phases, work that created conflict, and departing team members.
- Recognition becomes a leadership capability through daily, weekly, and monthly practices, not through occasional large gestures. Specificity discipline, written recognition weekly, calibration to individuals, and attention to hidden work are key practices.
- The leader who masters praise and recognition creates a team where excellent work is consistently seen, valued, and celebrated. The investment in this skill pays back in engagement, motivation, and retention that no compensation alone can match.
Reflection Activity: My Recognition Audit
Complete the tables below to honestly assess your recognition practice and plan improvements.
Part 1: Recognition by Team Member
| Team Member | When Did I Last Give Specific Recognition? | What Was the Recognition? | Do I Know Their Preferences? | What Hidden Contributions Should I Recognize? |
|---|---|---|---|---|
Part 2: My Recognition Patterns
| Question | Honest Self-Assessment |
|---|---|
| How specific is my recognition usually? | |
| How often do I use generic language ("good job," "great work")? | |
| Do I follow recognition with criticism or requests? | |
| Am I recognizing equally across the team? | |
| What recognition channels am I underusing? (Written, public, opportunity, advocacy, time) | |
| What hidden contributions am I missing? | |
| How well do I know each team member's recognition preferences? |
Part 3: My Action Plan
| Reflection Area | My Plan |
|---|---|
| The team member I most need to recognize more substantively: | |
| One conversation I will have to learn recognition preferences: | |
| One specific recognition I will give this week: | |
| One hidden contribution I will deliberately recognize: | |
| One recognition channel I will start using more: | |
| How I will track and improve my recognition practice: |
Mini Case Study
A team lead named Vivek managed a team of nine engineers building a payment processing platform. By all external measures, Vivek was effective. The team delivered. People did good work. Stakeholders were satisfied.
But Vivek noticed something troubling: a senior engineer, Pooja, who had been consistently excellent for two years, seemed less engaged lately. Her work was still good, but the energy was different. She participated less in optional discussions. She seemed to be doing the work but not investing in it.
Vivek scheduled a conversation: "Pooja, I want to check in. I've noticed you seem less engaged lately, and I want to understand."
Pooja was honest: "Vivek, I've been doing exceptional work here for two years. I've shipped major systems. I've mentored junior engineers. I've prevented several major issues through careful design. I've defended this team's interests in stakeholder meetings. And in two years, you've never specifically recognized any of it. You say 'thanks' and 'good work,' but you don't seem to actually see what I've contributed. I'm starting to wonder if my work here is even noticed. I've started looking elsewhere because I want to work for a leader who actually sees my contribution."
The Painful Recognition
Vivek was devastated. Pooja was right. He had taken her excellence for granted because she was consistently excellent. He had relied on her without acknowledging her. He had recognized splashier work from less senior people while letting Pooja's sustained quality go without specific acknowledgment. He had failed her on recognition.
The Investigation
Vivek looked at his own recognition patterns over the past year. What he found was uncomfortable:
- He had recognized newer team members for individual moments more than Pooja for sustained excellence
- He had thanked everyone perfunctorily without recognizing anyone specifically
- He had not given Pooja a written acknowledgment in over a year
- He had not specifically recognized her mentoring, her preventive design work, or her advocacy
- He had advocated for her with leadership but never told her he had done so
- He had assumed she knew how valued she was without telling her
The Recovery
Vivek did several things quickly:
- He had a substantive conversation with Pooja specifically about what he valued in her work, two years of it
- He sent her a written note documenting specific contributions over recent months that he should have been recognizing
- He acknowledged his failure directly: "I've taken your work for granted, and I haven't recognized it the way I should have. That's on me."
- He committed to better practices going forward
Pooja was guarded but engaged. "I appreciate that you're acknowledging this. But it'll take time for me to feel valued again, and I'm not sure if I will."
The Broader Change
Vivek realized he needed to fundamentally change his recognition practice across the entire team. He committed to:
- Weekly written recognition: Send specific written acknowledgments to team members each week, rotating to ensure no one was overlooked
- Track recognition: Keep a simple list of who he had recognized recently, ensuring equity
- Hidden work focus: Deliberately look for and recognize contributions that weren't obviously visible
- Substantive engagement: Spend real time with team members' work, not just from a distance
- Sustained excellence recognition: Specifically recognize the people doing quiet consistent excellent work, not just dramatic moments
- Direct conversations: Ask each team member what recognition would feel valuable to them
The Outcome
Pooja did stay with the team. Six months later, she said: "I appreciate that you've made the changes you talked about. I see the difference. I feel valued now in a way I didn't before. The recognition you've given me, the specific written notes about my work, the time you spend engaging with what I'm doing, the way you defend my decisions, has rebuilt trust. I'm engaged again."
The broader team also benefited. Engagement scores improved. Other senior engineers who had been quietly under-recognized started feeling more valued. The culture shifted toward one where excellent work was specifically acknowledged rather than taken for granted.
Vivek reflected: "I almost lost Pooja, my most valuable team member, because I didn't recognize her. Two years of taking her excellence for granted nearly cost her departure. The lesson was painful but clear: leaders systematically under-recognize their best people because their excellence becomes the new normal. The flashy work of newer people gets recognized; the sustained excellence of senior people gets assumed. That's a profound recognition failure that drives away exactly the people you can least afford to lose. I'm now disciplined about recognizing sustained excellence specifically. I make sure my most consistent contributors hear specifically what makes their work valuable. I write things down so they can save them. I tell them when I've advocated for them with leadership. I make their work visible to them and to others. This is one of the most important practices I've developed, and I'm grateful Pooja was honest enough to tell me how I was failing her."
The Lessons
- Sustained excellence often gets recognized less than dramatic moments, leading to systematic under-recognition of the most valuable contributors
- Leaders take excellence for granted, especially from people who have been excellent for a long time
- Recognition needs to be active and specific, not assumed
- Written documentation of contributions is particularly valuable for sustained recognition
- The most valuable team members are at the highest risk of disengaging due to recognition failures because their alternatives are best
- Asking team members directly is one of the best ways to learn what recognition would be meaningful
- It's never too late to recover from recognition failures, but the recovery requires honesty about the failure and sustained changed behavior
- The investment in recognition is one of the most direct investments in retention of your best people
Conclusion
Praise and recognition are not soft skills or optional extras. They are essential leadership practices that signal value, build confidence, reinforce excellence, deepen rapport, and create the kind of engagement that no compensation alone can produce. They cost nothing financially but pay back enormously in motivation, performance, and retention. And they are entirely within your control as a leader.
Real recognition requires three essential elements: attention (you actually noticed what they did), understanding (you know why it's valuable), and communication (you express it in ways that land well). All three must be present for recognition to register as recognition rather than as politeness.
Praise focuses on the person, their qualities, effort, judgment, and character. Recognition focuses on the work, what was accomplished, the value created, the impact made. The most powerful acknowledgment uses both together: recognizing both what was done and who they are as the doer.
Recognition operates through multiple dimensions: verbal, written, public, private, tangible, opportunity, advocacy, time, and defense. The most engaging recognition cultures use multiple dimensions thoughtfully, calibrated to what each team member values most.
Effective recognition is specific, genuine, timely, contextual, frequent enough, calibrated to the recipient, proportionate, connected to growth, standing alone without immediate ask, and backed by consistent action. Generic recognition, recognition that becomes routine, recognition driven by visibility, recognition that is sandwiched with criticism, and recognition that misses what matters most all fall flat.
Different team members value different forms of recognition. What energizes one embarrasses another. What feels meaningful to one feels generic to another. Knowing your team members well enough to recognize them in ways that land is one of the marks of leadership skill. Discovering preferences requires asking, watching reactions, noticing what they remember, and paying attention to what they value.
Some of the most valuable contributions are hidden from immediate view: prevention work, foundation work, mentoring, judgment calls, emotional labor, coordination work, and quality investment. Leaders who only recognize visible work systematically under-value the people doing this invisible essential labor. Deliberately looking for and recognizing hidden contributions is essential.
The hardest recognition often comes through difficult situations: recovery from failure, growth after struggle, effort that didn't succeed, sustained quiet excellence. How you handle these moments distinguishes leaders who give recognition skillfully from those who only recognize easy successes.
The most important lesson is this: Your most valuable people are at the highest risk of disengaging due to recognition failures. Their excellence becomes your new normal, you take their contributions for granted, you assume they know how much they're valued without telling them, and meanwhile, they have the best alternatives in the market and the highest standards for being recognized. The flashy work of newer people gets recognized; the sustained excellence of senior people gets assumed. That's the recognition failure that drives away exactly the people you can least afford to lose. The discipline of specific, calibrated, frequent, substantive recognition is therefore not just nice to have; it's essential to retaining your best people and building the kind of team where excellent work is consistently seen and reinforced. Start today with one specific recognition to a team member whose work you have been quietly appreciating without saying so. Make it specific about what they did and why it was valuable. Make it the form they prefer. Make it stand alone without an immediate ask. Then do another tomorrow. Build the practice. Develop the discipline. The change in your team will be visible within weeks: people feeling more valued, more energized, more committed. The leaders who do this work, and the teams they build, are fundamentally different from those who don't. Be one of the former. Your team's best work is happening right now, often invisibly. The recognition you give or fail to give determines whether that work feels seen and valued, or whether it feels invisible and taken for granted. The choice is yours, and the impact is enormous. Make recognition not an afterthought but a central practice of how you lead. Your team is waiting for you to actually see them.