You notice everything. That's not a figure of speech for you — you are genuinely tracking who hit the deadline, who cut the corner, who handled the difficult client cleanly, and who is half a step behind where they should be. You evaluate execution the way other people breathe. But here is the strange asymmetry in how you operate: almost all of that noticing gets converted into correction, and almost none of it gets converted into praise. When someone falls short, you tell them, because that is your job and standards matter. When someone does well, you log it privately and move on. The good performance gets a silent nod inside your own head and nothing more.
Your reasoning feels airtight. Doing the job well is the baseline — that's what the role requires, so why hand out applause for meeting the requirement? Praise feels soft, possibly inflationary, maybe even a little embarrassing to deliver. And some part of you treats your approval as something that should be earned and rationed, because if you praise everything, praise stops meaning anything. The logic holds together right up until you notice the actual result: the people around you cannot tell the difference between you being satisfied and you being on the verge of replacing them. You have built a system where the only signal you send is a problem signal, and people are working in the dark.
You think praise lowers the bar. It does the opposite.
Your core fear about encouragement is that it breeds complacency. If you tell someone they did a good job, they'll ease off; if you celebrate competence, you've redefined competence as something exceptional and the standard slides downward. So you stay quiet to keep the pressure on. It feels like rigor. But look at what actually happens to a person who never hears that they're doing well: they don't relax, they get anxious. They stop taking initiative because every move might be the one that draws your correction, and the safest play under a boss who only speaks up to criticize is to do the minimum and avoid notice. You wanted high performance and you accidentally engineered defensive caution.
Specific encouragement does the precise thing you actually want, which is to lock in the right behavior. When you tell someone exactly what they did well — "you escalated that to me before it blew up, that's exactly the call I needed you to make" — you have just defined the standard far more clearly than any criticism could. You're not lowering the bar; you're showing them where it is and confirming they cleared it, so they'll do it again deliberately instead of by accident. Praise, done your way, is not softness. It's reinforcement. It's the most efficient tool you have for making good performance repeatable, and you've been refusing to use it.
"They already know" is an assumption you'd reject anywhere else
One of your favorite reasons for staying silent is that the person obviously knows they did well, so saying it is redundant. You hate redundancy. Stating the obvious wastes time, and you assume a competent adult can read the situation and self-assess. But notice that this is the one place you let an assumption stand without checking it. In every other part of your operation you verify; you don't trust that something is handled just because it should be. Yet here you're trusting that a person has correctly read your internal, unspoken approval — the approval you took deliberate care never to express.
They do not know. Your neutral face is the same face you wear when you're displeased, and your silence reads as the absence of approval, not the presence of it. People are not running an accurate internal scoreboard of your opinion; they're guessing, and under an undemonstrative boss they tend to guess low. The fix is not warmth you don't feel — it's information you already have. You already concluded the work was good. Closing the loop and actually transmitting that conclusion is just completing a process you left half-finished. For someone who prizes accuracy, leaving people with a wrong read of where they stand should bother you more than the cost of one sentence.
You ration approval like a budget. It isn't one.
There's a quiet conviction underneath all this: that approval is a finite resource, and if you spend it freely it loses its value. You treat a word of praise like a raise or a promotion — a scarce thing to be released only at the right moment for maximum effect. That instinct comes from a real place. You're responsible for the system, and you don't want to be the leader whose praise is meaningless because it's constant and indiscriminate. Cheap, vague flattery genuinely does devalue itself, and you're right to refuse it.
But specific, accurate encouragement does not follow scarcity economics. When you tell someone precisely what they did and why it mattered, you're not spending a limited reserve — you're describing reality, and reality doesn't run out. The thing that makes praise worthless isn't frequency; it's vagueness and dishonesty. "Good job, team" said to everyone means nothing. "You caught the error in the third quarter numbers that the rest of us missed" said to one person means a great deal, even if you say something equally specific to someone else tomorrow. You don't have to choose between standards and generosity. You have to make your encouragement as precise as your criticism already is, and then you can give as much of it as people earn — which, in a team you've built well, should be a lot.
Make it a deliverable, not a feeling
You won't get there by waiting to feel moved to praise someone, because that feeling rarely arrives on its own and you don't trust it when it does. So don't rely on it. Treat encouragement the way you treat anything else that matters: build it into the process. Make it a standing item. At the end of a review, the report-out, the project close, you owe the team not just a list of what to fix but an explicit account of what was done well and by whom. Put it on the agenda if you have to. You respect a checklist; let this be on the checklist.
Keep it concrete and keep it timely, the same way you'd want a correction delivered. Name the specific action, name the impact, name the person, and do it close to when it happened so it actually lands. "The way you handled the angry client on Tuesday — you stayed calm and got the order back on track — that's the standard" takes ten seconds and does more for that person's performance than a vague annual nod ever will. You're not becoming a softer leader. You're becoming a more complete one, the kind whose people know exactly where they stand because you tell them — when they're failing and when they're winning.
You already do the hard half of this job: you notice, you evaluate, you hold the line. The only thing missing is transmission. Say the good thing out loud, name it precisely, and do it on schedule — not as a reward you ration, but as information you owe. The people you lead don't need you to go soft; they need to be able to read you. Close the loop, and watch them rise to the standard you finally let them see.