To give specific praise instead of generic praise, name the exact thing the person did, when they did it, and the effect it had: trade “great job this week” for “the way you rewrote the onboarding doc on Tuesday cut our setup questions in half.” The detail is what makes recognition land, because it points at something the person can actually repeat. And here is the part most advice skips: the detail is not available on demand. You will not remember on Friday exactly what someone did on Monday. So the real skill behind specific praise is capture: writing down the accomplishment, dated and concrete, shortly after you see it, so the specifics are still there when you go to say something.
Almost every guide to recognition agrees on the same two things. First, generic praise does not work: “good job” is pleasant, forgettable, and could apply to anyone. Second, the fix is specificity. What the guides rarely say out loud is that specificity has a memory problem. By the time you have a calm moment to recognize someone, the precise, praiseworthy detail has already blurred. This piece is about closing that gap: what specific praise looks like, a simple structure for it, and how to keep a record so your best lines are still there months later.
Why “great job” falls flat
Generic praise is not wrong so much as empty. “You’re doing great,” “nice work,” “thanks for everything.” The person hears that you are pleased, but not what pleased you. There is nothing in it to hold onto and nothing to repeat. Said often enough, it starts to sound like background noise, the verbal equivalent of a thumbs-up emoji.
Specific praise does the opposite. It tells someone exactly which behavior to do more of, which is the entire point of recognition. “The runbook you wrote for the deploy made onboarding the new hire trivial; she shipped on day three” is a sentence the person will remember, and it quietly tells them that writing things down is valued here. That is praise doing real work: it makes someone feel seen and it shapes what happens next.
The cost of getting this wrong is uneven, too. Your most visible people get recognized whether you are deliberate about it or not, because their wins are loud. Your quiet, reliable people, the ones who prevent fires instead of fighting them, are exactly the ones whose contributions are easy to overlook and impossible to recall later if you did not write them down. Specific praise, backed by a record, is how you make sure credit lands where it is actually owed.
One dated line now is worth more than an hour of remembering later.
A simple structure: situation, behavior, impact
You do not need a script for praise, but you do need three pieces. The same structure that makes feedback clear makes recognition clear: name the situation (when and where), the behavior you actually observed, and the impact it had. This is often called SBI, and it works because it forces out the vagueness on its own.
- Situation. “In Monday’s incident call…” Anchoring to a moment makes the praise feel real and reminds the person of the exact thing you mean.
- Behavior. “…you stayed calm and walked everyone through the rollback step by step…” This is the part they can repeat. Describe what they did, not a trait you are assigning to them.
- Impact. “…which got us back up in twenty minutes instead of an hour.” Impact is what turns a nice observation into a reason. It tells the person why the behavior mattered.
Put together: “In Monday’s incident call, you stayed calm and walked everyone through the rollback, which got us back up in twenty minutes.” Compare that to “you handled the outage well.” Same event, completely different effect. The first is a sentence the person carries with them; the second evaporates on contact.
Before and after: generic praise made specific
The fastest way to internalize this is to see the swap. The left-hand versions are things managers say every day. The right-hand versions are the same intent, made specific, and notice that every specific version depends on a detail you would only have if you had written it down.
- Generic: “Great work this sprint.”
Specific: “Mar 9: you led the billing migration with zero downtime and caught the timezone bug before it hit customers. That is the kind of careful work that does not get noticed unless someone says so, so I’m saying so.” - Generic: “Thanks for being so helpful.”
Specific: “Apr 2: you sat with the new hire for an hour on the auth flow when you had your own deadline. She shipped her first PR the next day, and that was mostly you.” - Generic: “Nice job on the presentation.”
Specific: “May 14: the way you opened the QBR with the customer’s own words instead of our metrics changed the room. Two execs referenced it afterward. Do that again.” - Generic: “You’re doing great.”
Specific: “Across Q2 you quietly took over the on-call handoff doc and kept it current every week. Nobody asked you to, and it is the reason the last three rotations were painless.”
Read those again and you will see the pattern: each one is built on a fact, a date, a specific action, a measurable or visible result. That fact is the asset. Lose the fact and you are back to “great work,” no matter how good your intentions are at the moment you speak.
Keep a dated thread of wins for each person, so the specifics are there when you need them.
When to praise: in the moment, and again later
Recognition has two windows, and the best managers use both. The first is right after the work, while it is fresh: a quick word in the moment is warm, credible, and costs nothing. The second is later, when it counts: a 1:1, a performance review, a promotion case, a rough week when someone needs reminding that they are good at this. The second window is where a record pays off.
This is the part timing advice usually misses. “Praise promptly” is true but incomplete, because the prompt moment is rarely the moment that matters most. The quiet save your strongest engineer made on a Thursday in March is exactly the thing you will want to cite in their mid-year review, and by then it is long gone from memory unless you wrote it down. Bring back a specific win from four months ago in a review and the person realizes you were paying attention the whole time. You cannot fake that, and you cannot reconstruct it. You can only have written it down.
So the working habit is simple: say something now, and leave yourself a dated note so you can say it again when it lands hardest. The note is not a substitute for in-the-moment recognition. It is what makes the later, higher-stakes recognition possible at all.
Public or private: match it to the person
Where you give praise matters as much as how. Public recognition, in a team channel, a standup, an all-hands, rewards visible wins and signals to everyone what the team values. Private recognition, in a 1:1, a direct message, a quiet word, reaches the behind-the-scenes work and suits people who find the spotlight uncomfortable.
The mistake is treating everyone the same. Praise a private person loudly in front of the team and you can turn a gift into an ordeal; bury a high-visibility win in a DM and you miss the chance to set an example. Which a person prefers is itself worth a note. A line like “hates public praise, recognize in 1:1s” on someone’s timeline means you get it right every time without having to remember it, the kind of small personal detail that good managing is actually made of.
Mistakes that make praise ring hollow
Most praise that fails to land fails for one of a few reasons. None of them are about how much you care.
- Vagueness. “Good work” with no detail. The single most common failure, and the easiest to fix, if you have the detail.
- The compliment sandwich. Wrapping a piece of criticism in two slices of praise teaches people that recognition is a warning sign. Keep praise and feedback as separate, honest things.
- Praising effort when you mean impact, or impact when you mean effort. Both matter, but name the one you actually mean. “You worked so hard” lands differently from “that worked,” and someone who tried hard on something that did not pan out can tell when you are reaching.
- Only recognizing the loud wins. If recognition only follows visible launches, the people who prevent problems quietly never hear it. Those are often your most valuable people, and their work is the easiest to forget.
- Letting wins die. The save that did not announce itself is the one you will wish you had at review time. Capture it the day it happens or it is gone.
Where the record lives
Every piece of this comes back to one habit: writing down the specific, praiseworthy thing shortly after it happens, so it is still there when you want to say it. That is exactly what Notivo is for. It is a private manager’s notebook: you write a quick note, tag the person with @ and their name and the topic with #, and it files into that person’s dated timeline. Type @Sam later and every win you logged is right there, dated and searchable, ready for a 1:1, a review, or a promotion case.
In practice it looks like five seconds of typing. You see someone do something good, you jot “@Priya nailed the QBR open with the customer’s own words, two execs referenced it #recognition” from wherever you are, whether the web app, WhatsApp, or the ChatGPT and Claude connectors, and it is filed. When review season comes, an AI assistant can draft a recap or answer a question from your own notes only. It reads what you wrote and never trains on your data, so “what were Priya’s wins this quarter?” returns the specific lines you captured instead of a blank. The praise was always going to come from you. Notivo just makes sure the details are still there when you give it.
On storage, the honest answer: your notes are private by default and scoped to your own account, and they are stored on secured infrastructure. That is platform-level security, the protections that come with reputable cloud storage. It is not a claim that your note content is encrypted end-to-end, and we are not going to pretend otherwise. (If you want a vault that is end-to-end encrypted, that is the separate, PIN-locked Black Box, overkill for recognition notes, but there if you need it.) So use the same judgment you would use with any cloud notes app: this is the right home for your working memory of who did what, and not the place for the most sensitive personal data you would never put in any cloud tool.
Walk into every 1:1 and review with the specific wins already written down.