Appreciating Good Work

Introduction

There is a strange imbalance in how most leaders think about feedback. They prepare carefully for the hard conversations. They rehearse difficult messages. They worry about tone, timing, and word choice when something has gone wrong. They spend hours thinking about how to address a missed deadline, a behavior pattern, or a performance concern. But when something goes right, they often say nothing. Or they say something brief in passing. Or they assume the person already knows. They treat appreciation as optional, as a nice-to-have, as something you do when you have time left over after the real work of leadership is done. And in doing so, they miss one of the most powerful tools they have.

Appreciating good work is not a soft gesture. It is not a reward to be handed out occasionally. It is not flattery, and it is not cheerleading. It is a serious act of leadership. It is the way you tell people that their effort is seen, that their contribution matters, that the work they did mattered to someone who was paying attention. It is the way you build the kind of trust that makes the harder conversations possible later. It is the way you shape the culture of the team without giving a single speech. And it is one of the most underused, undervalued, and misunderstood practices in the entire toolkit of giving feedback.

When appreciation is done well, it lands deeply. People remember it for years. They quote the exact words a manager said to them ten years ago about a piece of work. They hold those moments as anchors during difficult times. They carry the sense that someone saw what they did and named it. When appreciation is done poorly, or not done at all, the opposite happens. People begin to wonder if their work is noticed. They start to believe that only failure gets attention. They stop bringing their best effort because there is no signal that anyone is watching. And slowly, quietly, engagement erodes, not because anything dramatic went wrong, but because nothing felt seen.

This article explores what it really means to appreciate good work as a leader. Why it matters more than most leaders realize. What separates appreciation that lands from appreciation that feels hollow. How to deliver it with the same care you would bring to constructive feedback. The common mistakes that make appreciation feel cheap or performative. And the quiet truth that the leaders who are best at giving difficult feedback are almost always the ones who are best at appreciating good work, because the two are not separate skills. They are two halves of the same practice: the practice of telling people honestly what you see. By the end of this article, you should be able to appreciate good work in a way that is genuine, specific, timely, and meaningful, and to make appreciation a regular part of how you lead.

Simple Meaning: What Is Appreciating Good Work?

Appreciating good work is the practice of noticing what someone has done well and telling them clearly, specifically, and genuinely. It is the act of naming the contribution, naming the impact, and naming what you saw that made it meaningful. It is not generic praise. It is not "good job." It is not a quick "thanks" tossed over your shoulder. It is a thoughtful, intentional acknowledgment that says: I saw what you did, I understand why it mattered, and I am telling you so.

Appreciating good work means recognizing a specific contribution, naming the behavior or outcome that made it valuable, connecting it to the impact it had, and delivering that acknowledgment in a way that feels genuine to the person receiving it. It is the discipline of catching people doing things right and saying so, clearly and meaningfully. It is the practice of treating positive feedback with the same care, specificity, and attention you would bring to constructive feedback. It is not about handing out compliments to make people feel good. It is about telling the truth about what you see when what you see is worth naming. Done well, appreciation creates a culture in which people know their efforts are visible, in which good work is reinforced, in which the relationship between leader and team member is built on a foundation of being genuinely seen. Done poorly, appreciation becomes either absent or performative, and either of those failures slowly corrodes the relationship and the culture. The leaders who appreciate well are not the ones who say nice things often. They are the ones who say true things specifically. They are the ones who notice the work that others might overlook. They are the ones who take the time to articulate why something mattered. And in doing so, they build teams where people give their best because they know their best will be seen.

Appreciating good work can be understood through four essential elements:

Why Appreciating Good Work Matters More Than Most Leaders Realize

Appreciation is often dismissed as a soft practice that has its place but is not central to leadership. That dismissal is one of the most expensive mistakes a leader can make. Here is why appreciating good work matters more than most leaders realize.

What Separates Appreciation That Lands from Appreciation That Feels Hollow

Not all appreciation works. Some appreciation lands deeply and is remembered for years. Other appreciation evaporates the moment it is spoken and may even leave the person feeling worse. The difference is not subtle.

The Anatomy of a Strong Appreciation

Strong appreciation has structure, just like strong constructive feedback. You do not have to follow the structure rigidly, but understanding the components helps you avoid the trap of generic praise.

The Five Parts of a Strong Appreciation

• What You Noticed: The specific behavior, action, or contribution you observed.
• When and Where: The context that makes the observation concrete and real.
• Why It Mattered: The impact on the work, the team, the customer, or you personally.
• What It Says About Them: The strength, value, or capability the work reflects.
• What You Hope For: An invitation, when appropriate, to keep doing it or build on it.

An Example of Each Part

• What You Noticed: "In yesterday's design review, you walked us through the trade-offs between the two architectures with real clarity."
• When and Where: "Especially the moment when the team was getting stuck on the latency question and you pulled out the diagram and reframed it."
• Why It Mattered: "That reframing was what unlocked the discussion. We left the meeting with a real decision instead of another open question."
• What It Says About Them: "It showed me how strong you have become at facilitating technical conversations, not just contributing to them."
• What You Hope For: "I would love to see you take that role more often in cross-team reviews. You are ready for it."

Put together, this is appreciation that is specific, timely, impactful, sincere, and developmental. It is the kind of appreciation people remember.

Different Forms of Appreciation and When to Use Each

Appreciation is not one thing. It comes in different forms, and choosing the right form for the moment makes a real difference.

The most thoughtful leaders use multiple forms over time, choosing the one that fits the moment and the person. Some people value private appreciation deeply and find public recognition uncomfortable. Others come alive when their work is named in front of others. Knowing your people well enough to choose the right form is part of the practice.

What Appreciation Sounds Like in Practice

Here are examples of appreciation in various situations. Notice how each one is specific, names the impact, and feels like the leader was actually paying attention.

For Quality of Work

• "The report you sent yesterday was unusually clear. The way you separated assumptions from conclusions made it easy for me to follow your reasoning, and I want you to know that level of clarity is rare and valuable."
• "Your code review on the migration PR was exceptional. You caught two edge cases I would have missed, and the way you explained them in the comments will help the rest of the team learn from it."

For Collaboration

• "I noticed how you handled the disagreement with the product team yesterday. You stayed open, listened to their concerns, and found a path forward that worked for both sides. That kind of bridge-building is exactly what we need more of."
• "Thank you for stepping in to help the new joiner yesterday. You spent thirty minutes walking them through the codebase, and they told me later it was the most helpful conversation they have had since joining."

For Effort and Resilience

• "I know the last two weeks have been hard. The way you kept showing up, kept moving the work forward, and kept supporting the team even when you were stretched, did not go unnoticed. I am grateful for it."
• "You took on the production incident at 2 AM and stayed with it until it was resolved. I want to acknowledge the personal cost of that and tell you that the team is in better shape because of what you did."

For Growth and Development

• "I want to name something I have been noticing for a few months. The way you handle stakeholder conversations now is completely different from where you were a year ago. You have grown into a much more confident communicator, and it shows in every meeting."
• "The presentation you gave today was a real step up from your last one. The structure was clearer, your delivery was calmer, and you handled the tough question at the end with poise. I saw real growth there."

For Quiet Contributions

• "I noticed that you have been quietly maintaining the team documentation for months without anyone asking. That work is mostly invisible, but the team relies on it every day. I want you to know I see it and I value it."
• "You are the reason our standups run smoothly. You prepare the agenda, you keep us on time, and you make sure everyone gets a chance to speak. None of that happens by accident. Thank you."

Common Mistakes Leaders Make in Appreciating Good Work

Most leaders want to appreciate well. But several patterns get in the way, often without us noticing.

How to Make Appreciation a Habit, Not a Gesture

Appreciation that happens occasionally has limited impact. Appreciation that becomes part of how you lead transforms a team. Here is how to make it a habit.

• Start with attention: You cannot appreciate what you do not notice. Build the habit of actively looking for good work, not just problems to solve.
• Keep a running list: Maintain a short, ongoing note of contributions you have observed. It helps you appreciate in the moment and in formal reviews.
• Set a low bar for sending a note: If you notice something worth naming, send a short message. Do not wait for the perfect moment.
• Build it into your routines: Use one-on-ones, team meetings, and weekly reviews as natural opportunities to acknowledge specific contributions.
• Vary the form: Mix private notes, public mentions, written messages, and verbal acknowledgments to keep appreciation feeling fresh.
• Appreciate across the team: Make sure quiet contributors get as much attention as visible ones over time.
• Tell the truth: Only appreciate what genuinely deserves it. The integrity of your appreciation is what makes it valuable.
• Connect appreciation to growth: When possible, name not just what they did but what it says about how they are developing.
• Pass appreciation upward: Tell your boss, your skip-level, and other senior leaders about the strong work you see on your team.
• Receive appreciation well too: Modeling how to receive appreciation gracefully shapes how your team learns to give and receive it.

Practical Workplace Scenario

Scenario

A team lead named Ishaan had been running an engineering team for over a year. One of his engineers, Meera, was a steady, reliable contributor. She rarely missed deliveries. She mentored new joiners without being asked. She kept the team's testing infrastructure healthy through quiet, consistent work that nobody noticed because it never broke. She was not flashy. She did not push for visibility. She just did her job well, week after week.

Ishaan had not given Meera any meaningful appreciation in months. He had thanked her in passing for small things. He had mentioned her positively in a review. But he had never sat down and told her clearly what he saw in her work. He assumed she knew. He assumed her steady promotions and good ratings spoke for themselves. Then one day, in a one-on-one, Meera said quietly: "I have been thinking about whether to stay on this team. I am not unhappy, but I do not always feel sure my work is noticed. I wanted to be honest about that."

Approach 1: Generic Reassurance (What Could Have Happened)

Ishaan could have responded with a quick reassurance: "Meera, of course your work is noticed. You are one of the strongest people on this team. Everyone knows that. Do not worry about it. I will make sure to call out your work more often."

Meera would have nodded, said thank you, and walked out. She would have appreciated the kindness but would not have felt seen. The conversation would not have shifted anything because the reassurance was generic. Within a few months, she would have started looking elsewhere. Ishaan would have been surprised when she resigned.

Approach 2: Specific, Sincere Appreciation (What Actually Happened)

Ishaan paused. He realized that Meera had named something important, and a generic response would not honor it. He said:

"Meera, thank you for telling me that. It matters that you said it, and it matters that I respond honestly. The truth is, I have been taking your work for granted, and I want to fix that, starting right now."

He continued:

"Let me name a few things I have noticed. The testing infrastructure on this team is in better shape than any team I have led before. That is because of you. You have rebuilt the integration tests, you have kept the CI pipeline healthy, and you have done it quietly. Most of the team does not even know how much of that is your work. I know it, and I should have said so long before today."

"Second, the way you mentor new joiners is something I have come to rely on. When Karthik joined last quarter, you spent hours helping him understand the codebase. He told me last month that you were the reason he ramped up so quickly. That is not in your job description. You did it because you care about the team. I see it."

"Third, I want to be clear about how I see your trajectory. You are ready for more scope. I have been slow to give you a stretch project because you make everything you touch look easy, and I have not pushed you. That is on me. I would like to talk in our next one-on-one about what a bigger role for you could look like."

Meera was quiet for a long moment. Then she said: "That meant a lot. I did not realize you saw all of that. Thank you."

What Happened After

Ishaan made a change in how he led after that conversation. He started keeping a short note of specific contributions he saw across the team. He sent short messages to people the same day he noticed strong work. He made appreciation a regular part of his one-on-ones, not just performance issues. He stopped assuming that good work spoke for itself.

Meera stayed on the team. Six months later, she led a major architectural project that became one of the team's most important deliveries that year. In her own one-on-ones with the new joiners she mentored, she modeled what Ishaan had shown her: specific, sincere, timely appreciation. The culture of the team began to shift.

Result

A year later, Ishaan reflected: "I almost lost one of the strongest people on my team because I had not been telling her what I saw. The fix was not complicated. It was not expensive. It was just paying attention and saying so. I think about that conversation often. It taught me that appreciation is not a luxury. It is one of the most important things a leader does."

Learning

This scenario illustrates a quiet truth: people leave teams not just because of bad treatment but because of the slow erosion of feeling unseen. Appreciation is not optional. It is one of the primary ways a leader signals that someone's contribution matters. And it is rarely too late to start, but it is much easier to make it a habit than to recover after the damage is done.

Appreciating Good Work Checklist

Self-Reflection Questions

Use these questions to think about your own practice of appreciating good work.

1. When did I last give someone specific, sincere appreciation? What did I say?
2. Are there people on my team whose contributions I have been taking for granted?
3. Is my appreciation usually specific, or does it default to generic phrases like "great job"?
4. Do I appreciate quiet contributors as much as visible ones?
5. How often do I appreciate good work in the moment, rather than waiting for reviews?
6. Have I ever followed appreciation with "but" and turned it into criticism? How can I separate the two more cleanly?
7. Do I match the form of appreciation to the person? Some prefer private. Some value public.
8. Am I telling senior leaders about the strong work happening on my team?
9. If I asked my team whether they feel their work is seen, what would they say honestly?
10. What is one specific contribution I have not yet acknowledged that I could appreciate today?

Key Takeaways

• Appreciating good work is the practice of noticing what someone has done well and telling them clearly, specifically, and genuinely. It is not flattery. It is not generic praise. It is a serious act of leadership that signals what you see and what you value.
• It has four essential elements: specificity, sincerity, impact, and timeliness. Together, they create appreciation that lands and is remembered.
• Appreciation matters because it reinforces what you want more of, builds trust for harder conversations, tells people they are seen, strengthens engagement, shapes culture without a speech, develops people, builds resilience, costs nothing and gives much, sharpens your own attention, and honors the person as well as the work.
• Appreciation that lands is specific, timely, connected to impact, sincere, personal, proportionate, honest, appropriately public or private, and leaves the person feeling clearly seen. Appreciation that feels hollow is generic, delayed, inflated, performative, or strategic.
• A strong appreciation often has five parts: what you noticed, when and where, why it mattered, what it says about the person, and what you hope for going forward.
• Appreciation comes in different forms: private verbal, public verbal, written notes, public written messages, quick acknowledgments, storytelling to others, structural recognition, and formal review documentation. Different forms fit different moments and different people.
• Common mistakes include being too generic, waiting too long, praising indiscriminately, praising too rarely, using appreciation strategically, focusing only on visible contributors, appreciating output but not the person, choosing the wrong public or private form, following praise with "but," and praising effort when impact matters or impact when effort matters.
• To make appreciation a habit, build the habit of attention, keep a running list, set a low bar for sending a note, build it into routines, vary the form, appreciate across the team, tell only the truth, connect appreciation to growth, pass it upward, and model how to receive it gracefully.
• The leaders who give difficult feedback well are almost always the same leaders who appreciate good work well. The two are not separate skills. They are two halves of the same practice: telling people honestly what you see.
• People rarely leave teams because of one big problem. They often leave because of the slow erosion of feeling unseen. Appreciation is one of the most powerful tools a leader has to prevent that erosion and to build a team where people give their best because they know their best will be noticed.

Conclusion

Appreciating good work is not a soft practice tucked at the edge of leadership. It is one of the central acts of leading people well. It is the way you tell someone that their effort is visible, that their contribution matters, that the work they did mattered to someone who was paying attention. It costs nothing. It takes only a small amount of time. And it has a return that few other leadership practices can match.

A leader who appreciates well notices what others miss. They see the quiet work, the steady contributions, the small acts of care that hold a team together. They name what they see, clearly and specifically. They connect the work to the impact it had. They deliver appreciation when it is fresh, in the form that fits the person. They never use appreciation strategically, and they never let it become routine or generic. They make appreciation a habit, woven into how they lead every day. And they extend the same care to constructive feedback, because in their hands, both kinds of feedback come from the same practice: telling the truth about what they see.

The most important lesson is this: People remember how they were seen. They remember the specific words a leader said about a piece of work they cared about. They carry those words for years. They draw on them in hard moments. They tell their own teams later, when they become leaders themselves, the stories of the leaders who noticed them and said so. And they pass that practice forward. If you want to build a team where people give their best, appreciate their best when you see it. If you want to build trust strong enough to handle difficult conversations, build that trust on a foundation of being seen. If you want to shape a culture where good work is the norm, name the good work and let everyone learn what it looks like. Do not save appreciation for special occasions. Do not assume people know what you think of their work. Do not let strong contributions pass unnoticed. Notice them. Name them. Say so. Specifically, sincerely, in the moment, in the form that fits. It is one of the simplest practices in leadership. It is also one of the most powerful. And the leaders who make it a habit build teams that other leaders only wish they could lead. That is the quiet truth about appreciating good work. It looks small. It is not. It is one of the great gifts a leader can offer, and one of the great responsibilities of leading people well.