Praising Work That's Done Well

In a small team, praise is not a ceremony. It happens in the middle of an ordinary Tuesday, in a hallway, on a call, or in a short message after a meeting. Prai

Level: Team lead
Setting: Small team
Core skill: Specific appreciation
Common pitfall: Vague or rare praise
Practice to try: A what-and-why thank-you

What this looks like in real work

In a small team, praise is not a ceremony. It happens in the middle of an ordinary Tuesday, in a hallway, on a call, or in a short message after a meeting. Praising work that is done well means noticing a particular piece of work and saying something true about it. It is not about being effusive or making a speech. It is about being accurate. A team lead might say, "The way you laid out the options in that document made the decision much easier for everyone." That sentence names the work and names why it mattered.

Specific appreciation sounds different from general encouragement. General encouragement says, "Great job." Specific appreciation says what was great and what effect it had. In a small team, people often wear several hats, so their contributions can blur together. One person may quietly keep a project moving by asking good questions, another may catch details everyone else misses, and another may stay calm when a deadline shifts. If you only praise the loudest or most visible moments, you miss most of the work that holds the team together.

Real work also includes the unglamorous parts: cleaning up a messy handover, rewriting a confusing message, testing something twice, or helping a colleague understand a tricky step. Praising these moments tells the team what good work actually looks like here. It turns your values into something people can see and copy. Over time, specific appreciation becomes a quiet form of teaching, because people learn which behaviors you notice and value.

Why it trips people up

Most team leads believe they give plenty of praise. In practice, praise often gets squeezed into the edges of the day, if it happens at all. When work is going well, there is a natural pull to move on to the next problem. The urgent item wins attention, and the solid work that prevented a crisis goes unmentioned. This is not usually a lack of goodwill. It is a lack of a habit. Without a deliberate pause, praise becomes rare, and rare praise feels heavier and more awkward when it finally arrives.

The other trap is vagueness. "Nice work" feels safe because it cannot be wrong, but it also cannot be useful. The person receiving it does not know what to repeat. Did you notice the careful analysis, the clear writing, the patience with a difficult conversation, or the speed? If the praise could apply to anyone on any day, it lands as politeness rather than recognition. Vague praise also creates uncertainty in a small team, because people start guessing what you really meant. Some may assume you are just being nice, while others may read it as faint praise.

There is also a timing problem. Praise saved for a quarterly review loses its connection to the work. By then, the details have faded and the moment has passed. In a small team, people want to know that their effort was seen while it still feels fresh. Delayed praise can even feel like an afterthought, as if you only remembered because a formal occasion required it. The fix is not to praise constantly. The fix is to praise specifically and close to the work, so the link between action and recognition stays clear.

The mistake that quietly hurts

The quiet mistake is letting praise become both vague and rare. It looks harmless because nothing dramatic happens. No one complains. The team keeps working. But over time, people stop knowing whether their best efforts matter. They may keep doing good work out of professionalism, but they lose the signal that tells them what to invest in. In a small team, where there is less formal structure to fall back on, that signal matters even more.

When praise is rare, it can also become distorted. People may start to associate recognition only with big visible wins, so they neglect the steady work that prevents problems. Or they may compete for the few moments when you notice something. Meanwhile, the person who quietly fixes a recurring issue, mentors a new colleague, or keeps careful records may feel invisible. That feeling rarely shows up as an open complaint. It shows up as disengagement, shorter answers, or a willingness to do only what is asked.

Vague praise can hurt in a different way. If you say "great job" to everyone, the words lose weight. People cannot tell whether you actually saw their work or whether you are just being pleasant. In a small team, that ambiguity can breed quiet resentment, especially when effort is uneven. The person who carried more of the load may wonder why the same phrase is used for everyone. Specific appreciation avoids this because it is tied to observable work. It does not require comparison or ranking. It simply tells the truth about what someone did and why it helped.

A practice you can repeat

Try a what-and-why thank-you. It is a short, repeatable way to give specific appreciation without turning it into a performance. The practice has two parts: name what the person did, and name why it mattered. Keep it to one or two sentences. Do it close to the moment, while the work is still visible to both of you. You do not need a formal setting or a long speech. A brief message, a quick word after a meeting, or a comment in a one-to-one conversation is enough.

To make it repeatable, attach it to something you already do. For example, at the end of each day, pick one piece of work you noticed and send a short note about it. Or, in your regular check-ins, start with one what-and-why thank-you before moving to tasks. If you keep a running list of projects, add a small column for "noticed this week" so you have a prompt when your memory is thin. The goal is not to praise everything. The goal is to make specific appreciation a normal part of how you lead, not a special event.

A useful test is whether the person could repeat your sentence to someone else and have it still make sense. If you say, "Thanks for your help," that fails the test. If you say, "Thanks for rewriting the handover notes so clearly; it saved the next person from asking the same questions," that passes. The what-and-why thank-you works because it is concrete, brief, and easy to believe. It gives the person something to hold onto and something to repeat. Over time, it also teaches the whole team what you value, because your thanks become a visible record of good work.

What to say and do

The words matter, but so does the delivery. Keep your tone plain and direct. Avoid overpraising, because it can feel hollow. Aim for the same tone you would use when describing a useful piece of work to a colleague. For example: "The way you summarized the customer's concerns in three lines made the whole discussion sharper. Thank you." Or: "You caught that inconsistency before it reached anyone else. That saved us a confusing round of questions." Or: "I noticed you stayed late to help the new person get set up. That kind of patience makes a real difference here."

When you say it, be specific about the work and the effect. You can mention the person's name, the task, and the outcome in one breath. If you are in a group, you can still be specific without turning it into a public ranking. For example: "Before we move on, I want to thank Maya for the way she organized the notes from yesterday's session. It made today's decisions much faster." That sentence names the person, the work, and the benefit. It does not compare her to anyone else, and it does not require a round of applause.

Finally, follow through with attention. If you thank someone for careful analysis, ask about the analysis later. If you thank someone for helping a colleague, notice when they do it again. This shows that your praise is not a one-off tactic. It also gives you a chance to reinforce the same behavior without repeating the same words. Specific appreciation works best when it is part of a pattern of noticing, not a single moment of good manners.

When the stakes get higher

When a project is under pressure, praise can feel like a luxury. It is tempting to focus only on risks, gaps, and next steps. But high-stakes moments are exactly when specific appreciation matters most. People are working harder, making more trade-offs, and feeling more exposed. A clear what-and-why thank-you can steady the team and remind people that their effort is seen, even if the outcome is still uncertain. It does not replace honest feedback about problems. It sits alongside it.

In a small team, high stakes often mean fewer people carrying more weight. That is when vague praise becomes especially unhelpful. If you say "great work" during a difficult week, people may not know what you mean. They may wonder whether you noticed the extra coordination, the calm handling of a tense call, or the careful checking that prevented a mistake. Specific appreciation cuts through that uncertainty. It tells people which of their many efforts actually helped, so they can protect that effort when they are tired.

Higher stakes also raise the cost of rare praise. If you only thank people when something goes perfectly, you teach them that only flawless results deserve recognition. That is a hard standard to live with. Instead, praise the work that was done well within the situation, even if the situation itself was messy. You might thank someone for raising a concern early, for keeping a record clear, or for asking a question that saved time. These are real contributions, and naming them helps the team keep its footing when the pressure is on.

Questions new leaders ask

Q: How often should I praise someone? A: There is no fixed number, but a useful guide is to aim for specific appreciation close to the work, not saved for special occasions. If you notice good work and say nothing for weeks, the moment fades. A short what-and-why thank-you once or twice a week, spread across the team, is often enough to keep the signal alive without becoming noise.

Q: What if I praise one person and others feel left out? A: Keep the praise tied to specific work rather than to general worth. When you name what someone did and why it helped, it is harder for others to read it as favoritism. You can also make a habit of noticing different people for different contributions. Over time, the team sees that appreciation is about the work, not about a popularity contest.

Q: What if the work was only partly good? A: You can still appreciate the part that was done well. For example, you might thank someone for the clarity of their update even if the project hit a snag. Specific appreciation does not require you to ignore problems. It simply means you name what worked before you discuss what needs to change. That order often makes the harder conversation easier, because the person knows you saw their effort, not just the gap.