The first quarter I ran a team, I did everything the leadership books said to do about recognition. I sent the Slack message after the big launch. I called out two people by name at the all-hands. I bought the team lunch when we hit the milestone. The visible boxes were checked.
Six months later, one of my best engineers gave notice. In her exit conversation, when I asked what I could have done differently, she said something that has stayed with me through every team I have built since: “You only ever noticed me when I shipped something big. I would have stayed for someone who noticed me on a normal Tuesday.”
That sentence reorganized how I think about recognition. The launch lunch was theater. The all-hands shout-out was theater. None of it was wrong, exactly. It was just all loud, all event-driven, and all completely silent on every Tuesday in between. Which meant the team was reading my recognition correctly: it was a performance I gave on a schedule, not a habit I lived.
This article is one cluster under the Team Trust hub. The foundation lives in the broader guide to giving recognition as a new manager, which covers the basic formula (what + why + impact) and the public-versus-private decision. The article you are reading right now is the practice library: thirty specific rituals you can implement this week, every one of them free, with a sample script, when each one works, and when not to use it.
If you suspect your best people are quietly running the math on whether they should leave, the Am I About to Lose My Best Employee? free assessment takes about three minutes and surfaces the early signals you might be missing. Recognition gaps are usually one of the top three flags it catches. Take it before or after this article. Many of the thirty rituals below land differently when you know which person on the team you are losing first.
Why most “recognition” is performance theater
Three reasons, in order of how often they show up. Every manager I have ever coached on this has been doing at least two.
1. It is loud where it needs to be quiet, and quiet where it needs to be loud. The instinct most managers have is exactly inverted. They go loud on the launch (the public Slack post, the all-hands shout-out) because the work was visible. They go silent on the Tuesday catch (the quiet save that prevented a customer call) because the work was invisible to anyone but them. But the Tuesday catch is the recognition the team is starving for. The launch shout-out is what the company expects. One produces loyalty. The other produces compliance.
2. The unit of recognition is the deliverable, not the behavior. Most managers recognize outputs. “Great launch.” “Strong quarter.” “Nice deck.” These are valid but generic. The recognition that compounds names the behavior underneath the output: the moment the engineer pushed back on a spec that would have caused trouble downstream, the moment the analyst flagged a number that did not look right, the moment someone offered to take notes when nobody else volunteered. Behaviors are repeatable. Outputs are not. Recognize behaviors and you get more of them. Recognize outputs and you get teams that wait for the next visible deliverable to feel seen.
3. The recognition is about the manager, not the person. This is the one nobody admits. Half the recognition I have watched managers give is structurally about themselves. “I am so proud of this team.” “I really appreciate when you do X.” The person delivering the recognition stays at the center of every sentence. The grammatical move that fixes this is small but real: the subject of the sentence should be the employee, not the manager. “You held the line on the spec that would have caused us a month of rework. That is the kind of judgment that compounds.” Not “I really appreciated that you held the line.” The first lands as recognition of the person. The second lands as the manager performing gratitude. The team can tell the difference.
The thirty rituals below assume you have done the work on all three. If you have not, the best ritual in the world will still feel like theater.
What recognition that compounds actually does
Before the thirty examples, the test. Recognition that compounds satisfies four conditions in roughly this order:
- It names a specific behavior at a specific moment. Not a pattern in the abstract (“you are always so reliable”). A moment (“the way you stayed on the call last Thursday after the customer escalated and walked them through the rollback step by step”). Patterns are inferred from moments, not asserted instead of them. The Gallup research on engagement, summarized across multiple State of the Global Workplace reports, has consistently found that employees who receive specific recognition at least weekly are roughly four times more engaged than those who receive generic recognition or none. The word doing the work in that finding is specific.
- It puts the employee at the center, not the manager. Recognition is data about the employee, not a confessional about the manager’s feelings. The grammatical test: count the I-statements and the you-statements in your draft message. If “I” outweighs “you,” it is about you. Rewrite.
- It is delivered close to the moment. Not three weeks later in a review. Not at the next all-hands. Within hours of the behavior, ideally same day. Recognition has a half-life. Twenty-four hours later the moment is fresher in the receiver’s memory than at the all-hands two weeks from now. The Tuesday catch recognized on Tuesday is roughly five times more potent than the same Tuesday catch recognized at Friday’s team meeting.
- It does not ask for anything back. The hardest one. Most “recognition” carries an implicit ask: now keep doing this. Now ramp up. Now train others. Recognition with strings attached is not recognition. It is a manipulation dressed as recognition, and the team always reads it correctly. The cleanest test: would you say this sentence if the person were leaving tomorrow? If yes, it is recognition. If no, it is a performance review.
When all four are present, recognition compounds. When any one is missing, it leaks. The examples below are organized into four groups (daily, weekly, milestone, peer), but every single one is structured around these four conditions.
Group A: Daily in-the-flow rituals (10 ways)
These are the ones that build the floor. They take thirty seconds to two minutes each. You should be running multiple of these every week per direct report. If you are not, no quarterly recognition ritual will save you.
1. The same-day specific Slack DM
When it works. Someone did a small thing well that was not visible to anyone else. The window is the same business day.
Sample script:
“I saw you re-routed the Acme escalation to Maya instead of trying to handle it yourself. That was the right call. You knew you were already at capacity and you protected the timeline by getting it to the right person fast. That is good judgment under pressure.”
When NOT to use. When the behavior is so small the recognition feels disproportionate. The bar is: was this a judgment call where they could have gotten it wrong? If yes, recognize. If it was muscle memory, save it.
2. The “I noticed” two-liner in the next 1-on-1
When it works. A pattern you have been watching for two or three weeks that you want to surface without making it a Big Deal.
Sample script:
“Quick thing before we get into the agenda. I have noticed over the last three weeks that every time a meeting goes sideways, you are the one who pulls it back to the actual question. I do not think you are doing it consciously. I am calling it out because I want you to do it consciously.”
When NOT to use. When you have not actually been watching and you are inventing a pattern to fill recognition airtime. The team can tell when the recognition is real and when it is filler.
3. The hand-off thank-you
When it works. When you have asked someone to take on something outside their normal scope and they have done it without complaint.
Sample script:
“Thanks for picking up the vendor coordination this week while Priya is out. I know that was not on your plate and you did not push back when I asked. The fact that the contracts are still moving is because of that.”
When NOT to use. When the hand-off was actually within their normal scope and the thank-you would read as condescending. Save these for genuine stretch moments.
4. The visible-to-the-room callout in a meeting
When it works. When someone did something in the meeting that should be named in front of the people who were there to see it.
Sample script:
“Before we move on, I want to flag something Daniela just did. She pushed back on the timeline I proposed and gave us a more honest read on what is actually achievable. I want this team to do more of that, and I want everyone to see it modeled.”
When NOT to use. When the person is shy and would experience public callout as exposure rather than recognition. Default to private unless you know the person prefers public.
5. The forwarded-with-a-line external email
When it works. When a customer, partner, or stakeholder said something positive about someone on your team in an email, and the person they said it about does not normally see those threads.
Sample script (forwarding the original email):
“Forwarding this from the client. The line about your response time on Tuesday is what they remember from the whole project. They are renewing in part because of you.”
When NOT to use. When the original email was politeness rather than substance. Forward only when the praise was specific and meant.
6. The “saved me from” admission
When it works. When someone caught something you would have missed. Most managers are uncomfortable acknowledging this. The discomfort is exactly why the recognition lands so hard.
Sample script:
“I am going to admit something. I was about to ship the version with the broken filter logic until you flagged it. You saved me from a customer support fire next week. I owe you one.”
When NOT to use. When the catch was trivial enough that the admission would feel manufactured. Reserve this for moments where they genuinely saved you.
7. The end-of-day “today you did” note
When it works. As a closing-the-loop ritual, especially for a person who tends to feel invisible. Three sentences max, end of day, no reply expected.
Sample script:
“Quick note before I log off. Today you held the customer call together when the demo broke, then turned around and shipped the fix before lunch. Two unrelated saves in one day. Logging it because I noticed.”
When NOT to use. When you are sending it because you forgot to recognize them earlier and you are trying to back-fill. They can tell.
8. The shared-credit correction
When it works. When you got credit in a leadership meeting for something a direct report actually drove, and you have the chance to set the record straight.
Sample script (in the next leadership meeting, or as a follow-up email):
“One correction from last week. The customer health dashboard I walked you through was not my work, it was Lin’s. I wanted to make sure that landed properly.”
Tell the person you did it.
“Quick FYI: I made sure leadership knew the dashboard was your work, not mine. They asked good questions about it. The credit belongs with you and I wanted you to know I made that clear.”
When NOT to use. When you would be re-attributing in a way that creates political mess for the employee. Some employees prefer the manager to absorb visibility. Ask once if you are not sure.
9. The “I quoted you” callback
When it works. When something a direct report said in a 1-on-1 or team meeting stuck with you enough that you referenced it in a different setting.
Sample script:
“I quoted you in the staff meeting today. The thing you said about how customer onboarding is actually three different problems wearing one hat. People nodded. It is becoming the way I think about the work.”
When NOT to use. When you did not actually quote them. Never invent recognition. It always backfires within weeks.
10. The “thanks for the disagreement” line
When it works. When someone pushed back on you and they were right, or when they pushed back on you and the disagreement made the work better even if you did not change your mind.
Sample script:
“Thank you for fighting me on that. You changed my mind on the rollout sequence and the plan we are running now is better because of it. I want you to keep doing that.”
When NOT to use. When you are saying it through gritted teeth because you still think you were right. The team will smell the resentment and learn that disagreement gets thanked but punished. The thank-you must be sincere or it should not happen.
Group B: Weekly and recurring rituals (8 ways)
These are the structured systems. They take five to fifteen minutes per week and they keep recognition from being something you do when you remember to.
11. The Friday “this week you” three-line ritual
When it works. As a closing-the-week practice across the full team. Friday afternoon. Three lines per direct report. Total time: about fifteen minutes for a team of six to eight.
Sample format (one per person, sent as separate DMs):
“Closing the week. Two things you did this week worth naming: (1) the rewrite of the onboarding email that lifted activation by what looks like four percentage points, and (2) the way you handled the Pierre call when he was upset. Have a real weekend.”
Why it compounds. Done weekly, this ritual produces roughly 40 specific recognition moments per direct report per year. That is more recognition than most employees receive across their entire career. It also forces you to notice things during the week, because you know you have to come up with two things on Friday. The act of looking for the recognition changes how you see the work.
When NOT to use. When you are doing it to check the box rather than to notice the work. The ritual only works if the looking is real.
12. The 1-on-1 opener question
When it works. As the first thing said in every 1-on-1, before the agenda. It changes the texture of the entire meeting.
Sample question:
“Before the agenda, one thing. What did you do this week that you are proud of?”
Why it works. It teaches the employee to notice their own work. Over six months, this question changes how the person sees their own contribution, which in turn changes how visible they make their work to others. It is recognition by way of asking the person to recognize themselves.
When NOT to use. When you are not willing to listen to the answer with full attention. If you are skimming your phone while they answer, you have damaged the ritual past usefulness.
13. The end-of-month “stand on” message
When it works. Last week of the month, one message to each direct report naming what you are going to stand on the next time their work comes up in a leadership conversation.
Sample script:
“End-of-month note. The next time your work comes up in a leadership conversation, the thing I am going to stand on is the prep you put into the executive review. You took it from a status update to a strategic conversation. That is the work I will defend.”
When NOT to use. When you are not actually going to stand on it. Empty promises corrode trust faster than no recognition at all.
14. The recurring “thing I have noticed” calendar block
When it works. As a calendar discipline, not a feeling. Block thirty minutes per week, scan your week, write three “things I noticed” about three different people. Send the messages. Done.
Sample block on calendar: “Friday 4:00-4:30 — Recognition pass.”
Why it works. It removes the false constraint that recognition has to be felt to be given. The calendar block converts the practice from inspiration to discipline. The recognition is still real; you just stopped relying on memory and inspiration to deliver it.
When NOT to use. When you are using the calendar block as cover for going through the motions. The minimum standard is that what you write has to be true.
15. The “I am tracking” private spreadsheet
When it works. As a manager-side artifact, never shown to the employee. One row per direct report, one column per month. Each cell holds two or three specific things they did that month. The artifact serves you, but the byproduct is that you cannot help noticing more.
Sample row entry for one month for one person:
“April: Re-architected the cache layer (Apr 3). Handled the angry customer on the support line for 90 minutes (Apr 11). Mentored Olu through their first on-call rotation (Apr 22-28).”
Why it works. It changes the manager. Once you maintain the spreadsheet, you cannot give a generic review again. The specificity is already in your notes. It also makes the annual review a synthesis exercise rather than a remembering exercise.
When NOT to use. Never share it with the employee. The moment the spreadsheet becomes performative for the employee instead of operational for you, it corrupts. Keep it private.
16. The “what would you brag about” question in skip-levels
When it works. In your skip-level conversations (your boss’s 1-on-1s with your direct reports’ direct reports, or your 1-on-1s with the people two levels below). The question creates a structured channel for recognition to travel up.
Sample question:
“If you had thirty seconds with my boss and you had to brag about your manager, what would you say?”
Why it works. It teaches everyone in the chain to look for the recognition-worthy behavior. It also produces specific data you can then close the loop on. (“Three of my reports independently mentioned how you protected them during the reorg. I wanted you to know that.”)
When NOT to use. When the manager you are asking about has been struggling. The question can land cruelly if the answer is “nothing.” Use it when you suspect there is good work going unnoticed, not as a test.
17. The “first time you” benchmark
When it works. When a direct report did something for the first time that they were nervous about. The benchmark is the discomfort, not the polish.
Sample script:
“Yesterday you ran your first leadership review. You walked into a room of senior people and held the floor for forty minutes. I watched you do something for the first time that took me three years to do for the first time well. That counts.”
When NOT to use. When the first time was a normal expectation of the role. Reserve this for first times where the person had to push past genuine discomfort.
18. The “you owned it” close
When it works. When a project completes and the post-mortem reveals one person carried disproportionate weight at a critical moment. Recognition delivered in the post-mortem, in front of the project team.
Sample script:
“Before we close out the retro, one thing. When the data migration broke at 11pm on the Wednesday before launch, Aida stayed online until 4am rolling forward, then came back at 9am to brief us. The project landed because of that night. I want everyone here to know what owning something looks like.”
When NOT to use. When the person who carried the weight would experience the callout as resentment-triggering for teammates who did not put in the same effort. Read the room. Sometimes the recognition belongs in a private channel even when the work was team-visible.
Group C: Milestone and narrative recognition (6 ways)
These are the rituals that recognize an arc rather than a moment. They land especially hard because most employees never get them.
19. The “one year ago” comparison
When it works. On a work anniversary, or at a natural inflection point. The format is concrete: what they were doing one year ago versus what they are doing now, named in specifics.
Sample script:
“You hit your first year today. A year ago you were asking me what counts as a normal turnaround on a customer ticket. Today you are setting the standard the rest of the team measures against. The growth is not abstract, I can name the specific calls where I watched the change happen.”
When NOT to use. When you cannot actually name the specific changes. Generic anniversary congratulations are worse than no anniversary congratulations.
20. The promotion narrative recap
When it works. When someone gets promoted, in the message announcing it (or in the conversation with them privately about it). The recognition is not “you got promoted.” The recognition is the story of how.
Sample script:
“Many of you know that Yusuf is moving into the senior role on the team starting next month. What I want everyone to know about that decision is what it is grounded in. Yusuf has run the technical reviews on the last six product launches. He has mentored Priya and Olu through their first quarters. He has pushed back on me, in writing, twice in the last six months on calls that I would have made wrong. The promotion is the recognition of work that has been visible for months. He did not become a senior person yesterday. We just made it official.”
When NOT to use. When the promotion was political and the narrative would feel manufactured. Do not write a narrative recap for a promotion you cannot honestly defend.
21. The “I bet on you and you proved it” close
When it works. When someone has come through on a stretch assignment you gave them as a bet. The closing recognition acknowledges the bet was real.
Sample script:
“Six months ago I gave you the EMEA expansion because I thought you could handle it and I did not know for sure. I am closing the loop now to tell you that you proved the bet. The way you handled the Berlin rollout in week three is the moment I stopped having doubts. I will make that bet on you again on the next thing.”
When NOT to use. When the bet did not pay off. Do not retroactively dress up a struggle as a win.
22. The “you taught me” admission
When it works. When you genuinely learned something from a direct report. The admission inverts the normal recognition flow and lands disproportionately hard because it is so rare.
Sample script:
“Something you said in our last 1-on-1 has changed how I think about customer escalations. You said the angry customer is almost always trying to tell you something about the product that the calm customers cannot articulate. I have used that framework three times this month. I learned that from you.”
When NOT to use. When you have not actually changed your thinking. The admission must be true. Manufactured intellectual humility reads as condescension.
23. The “year-shaped” review of a long arc
When it works. Annually, or at the close of a multi-quarter project. The format names the entire arc in one paragraph, with a specific moment from each quarter or phase.
Sample script (delivered in writing, two weeks before the annual review, so the review itself becomes a synthesis):
“Closing out the year on your work. Q1 you stabilized the platform after the migration: the most memorable moment was the Friday you stayed late to walk Customer Success through what changed. Q2 you took over the analytics rebuild and shipped it three weeks ahead: the moment that defines that quarter is the design review where you pushed back on my over-scoping. Q3 you mentored two new hires through onboarding: I watched Priya light up the first time she shipped something on her own and I know that was you. Q4 you carried the on-call burden through the holidays: the team is intact going into Q1 because of that. Four quarters, four arcs, one year. The review next week will go fast because I have already said the things that matter.”
When NOT to use. When you cannot remember the specific moments. Make the private tracking spreadsheet (#15) the upstream practice that makes this downstream ritual possible.
24. The “you helped shape this team” naming
When it works. When a team practice, norm, or process exists because one person pushed for it. Most teams cannot name where their norms came from. The recognition is the naming.
Sample script (in a team meeting, or in onboarding for a new hire):
“The way we run retrospectives, with the blameless framing and the rotating facilitator, exists because Sofia pushed for it eighteen months ago when we were doing it badly. I want new people on the team to know that the practice has a person behind it.”
When NOT to use. When the practice was actually a team effort and you are over-attributing to one person. Get the attribution right.
Group D: Peer and system rituals (6 ways)
These are the rituals that decentralize recognition. The team starts recognizing the team. Done well, peer rituals produce recognition density that no single manager can match.
25. The “name the person who made your week” round-robin
When it works. As a closing ritual for a weekly team meeting or retro. Each person names one specific thing one teammate did that made their week. The manager goes last, not first.
Sample structure (announced once, then run weekly):
“Before we close, one round. Each of you, name one specific thing one person on this team did this week that you are grateful for. Specific, not general. Behavior, not personality. I will go last.”
Why it works. Peer recognition compounds across the team. Two effects: (1) the receiver experiences recognition from someone whose opinion they care about as much as or more than the manager’s, and (2) the giver practices the discipline of noticing teammate behavior, which makes them better collaborators.
When NOT to use. When the team is in a low-trust phase and the round-robin would feel performative. Build trust first; introduce the ritual later.
26. The “kudos channel” with rules
When it works. A dedicated Slack channel for peer recognition, with one explicit rule: every kudos must be specific. Generic kudos are gently redirected. The rule does the work, not the channel.
Sample channel pinned message:
“#kudos. One rule: specific over general. ‘Thanks for the help today’ is fine for DMs. In here, say what they did and why it mattered. ‘Thanks for the help today’ becomes ‘thanks for jumping on the production fire with me at 4pm; I would still be debugging that without you.’”
When NOT to use. Without the specificity rule. An unstructured kudos channel decays into “thanks team!” noise within four weeks. The rule is the channel.
27. The “shout-out a teammate to me” 1-on-1 question
When it works. As a recurring question in your 1-on-1s. The peer recognition surfaces upward, you act on it.
Sample question:
“Before we close, one thing. Tell me one teammate who made your work easier this month, and what specifically they did.”
Then you close the loop. You go to the teammate and tell them. Recognition travels up to you and then back down to the right person, with the source named.
When NOT to use. When you are going to forget to close the loop. The ritual is broken if the recognition stops at you.
28. The cross-team callout to another manager
When it works. When someone outside your team did something that helped your team, and their manager does not know. Write to the manager. Cc the person.
Sample message:
“Quick note. Lin from your team unblocked us this week on the data pipeline integration. She walked our most junior engineer through the API patterns for two hours on a Thursday afternoon. I wanted you to know because I doubt she told you, and the gesture is the kind of work that does not show up in tickets.”
When NOT to use. When you are doing it transactionally to bank a favor. The other manager can read the difference between a real cross-team callout and politics.
29. The “I told your reference” later note
When it works. When a former teammate has moved on to another company and asked for a reference, after the reference call, you tell them what specifically you said.
Sample script:
“Wanted to close the loop. The reference call went well. The specific thing I told them about you was the rollback you led during the database migration two years ago. I told them you were the person who kept calm when everyone else was panicking, and that you would do the same for them on their worst day. They asked good questions. I told the truth.”
When NOT to use. When the reference call did not go that way. Never inflate a reference report.
30. The “I would work with you again” close on departure
When it works. On someone’s last day, in their last 1-on-1 with you. The format is a sentence, not a speech. The sentence is what it sounds like.
Sample script:
“Last thing before you go. I would work with you again. If you ever want a reference, a recommendation, or a backchannel intro, my line stays open for you. The way you handled the second half of last year is something I will carry into how I run teams from here. Thank you.”
When NOT to use. When you would not, in fact, work with them again. Saying it untrue is worse than saying nothing. The departing employee can tell, and they will remember the lie for a decade.
The discipline most managers skip: specificity comes from data, not memory
Here is the gap I see when I coach managers on recognition. They know the formula. They have heard “be specific.” They want to do it. And then on a Friday afternoon, sitting down to write the weekly recognition messages, they cannot remember anything specific that any of their direct reports did that week. So they fall back on generic praise, the message goes out, the team mentally discards it, and the manager wonders why their recognition is not landing.
The problem is not skill. The problem is data. You cannot recognize specifically what you did not actually see. And most managers see roughly 20% of what their direct reports actually do.
The fix is to widen the input. There are three layers.
The first layer is the private tracking spreadsheet (#15 above). You write down what you see as you see it. Two minutes a day. Over a month you have a data set that makes specificity possible.
The second layer is the 1-on-1 opener question (#12). When you ask “what did you do this week that you are proud of,” the answer is data. Write it down. The person is telling you what to recognize.
The third layer is structured peer input. This is the layer most managers skip, and it is the one that makes recognition stop being one-direction-from-the-top. The simplest version is the round-robin (#25), which you can run for free starting Monday. The more structured version is a 360-style tool that surfaces what teammates say about each other in an anonymous, organized way. I have used mirorly.com for this with teams I have advised — it is a leadership feedback tool that runs structured 360s and produces a report of specific behaviors teammates noticed in each other. The output is recognition raw material: dozens of specific moments per person that the manager could not have seen alone. You walk into the next 1-on-1 with three things you could not have known without it.
The point is not the tool. The point is the principle: you cannot give specific recognition without specific data, and the manager’s own eyes are not enough data. Whatever method you use to widen the input is the upstream practice that makes the thirty rituals above actually work. Skip this and the rituals become theater again, just better-scripted theater.
If you want to put a number on what the under-recognition pattern is currently costing you (turnover risk reduction, productivity uplift, departures prevented), the Recognition ROI calculator does the math in about three minutes. The headline finding holds even when the program cost is zero. Specific, free recognition delivers roughly 80% of the ROI of paid programs. Paid programs without specificity deliver roughly 20% of theirs. The compound variable is specificity, not money.
Frequently asked questions
How much time per week should I actually spend on recognition?
For a team of six to eight, about forty-five minutes per week, distributed. Fifteen minutes on the Friday three-line ritual. Twenty minutes across the week on in-the-flow same-day Slack DMs. Ten minutes on the calendar-blocked recognition pass. Less than one hour. The opportunity cost of not doing this is roughly one resignation per twelve to eighteen months that you could have prevented. The hour-per-week math is favorable by an order of magnitude.
What if my team is fully remote and I do not see the work?
Then you have to widen the input even more aggressively. The private tracking spreadsheet becomes essential, not optional. The 1-on-1 opener question becomes essential. Structured peer input becomes essential. Remote managers who recognize well are running three sources of data into their tracking; remote managers who recognize badly are running one (their own eyes, which see almost nothing in a remote setup). The remote work is the same work; the data collection has to be more deliberate.
What if I recognize someone and they react awkwardly or push back?
Most adults who receive specific recognition for the first time do not know how to receive it. The discomfort is information about the recognition gap, not about your delivery. Stay in the room. Do not retract the recognition or apologize for it. A simple “I just wanted you to know, no response needed” closes the loop without forcing them to perform gratitude. The next time you recognize them, the awkwardness will be smaller. By the fifth time, it disappears.
Does public recognition damage team dynamics if some people get more of it than others?
It can, if the pattern of who gets recognized publicly maps onto a pattern the team already suspects (favoritism, in-group dynamics, recognition concentrated in the loudest performers while quiet contributors are skipped). The fix is not to stop public recognition. The fix is to widen the population who gets recognized publicly. Run the Am I Playing Favorites? assessment on yourself first to surface whether the pattern is real. Then adjust.
How do I recognize someone who is underperforming without sending mixed signals?
Recognize the specific behaviors you want more of, even on a struggling employee. “I noticed you took the feedback from last week’s review and rewrote the doc from scratch instead of patching it. That is the right move.” The recognition is not a verdict on overall performance; it is data on a specific behavior you want repeated. The mixed-signals worry is usually a manager who has not yet had the underperformance conversation directly. Have that conversation separately, in plain language. The pillar guide on coaching an underperforming employee covers how. Once the underperformance is named, behavior-specific recognition no longer reads as mixed signals.
Is there such a thing as too much recognition?
Yes, and the failure mode is identifiable: when recognition is given so generously and so generically that any individual instance carries no weight, the team learns to discount it. The fix is not to recognize less. The fix is to make every recognition specific. Frequent specific recognition does not lose weight. Frequent generic recognition does.
What if my manager does not recognize me and I am modeling something I do not receive?
This is one of the most common patterns. Most first-time managers do not get recognized by their own manager and have to give recognition without a model for receiving it. Two moves help: (1) explicitly tell your manager what kind of recognition would help you (“when something goes well, a one-line note from you means more than I can say”); and (2) ask peers and former colleagues for the recognition you are not getting from above. Your team is not waiting for you to feel recognized before they need it. Run the practice for them while you separately work on the upstream gap.
How does this work for senior individual contributors who do not want public recognition?
The thirty rituals above are roughly half private and half public for a reason. Senior ICs typically prefer the same-day specific Slack DM (#1), the I-noticed two-liner (#2), the I-quoted-you callback (#9), and the year-shaped review (#23). They often actively dislike the visible-to-the-room callout (#4) and the public kudos channel (#26). Read the person. Default to private for senior ICs unless they have told you otherwise.
What to do next
Three concrete moves, in order:
- Take the Am I About to Lose My Best Employee? free assessment if you suspect one of your strongest people is quietly running the math on whether to leave. Three minutes. The output names which of the early warning signals are showing up, and recognition gaps are usually in the top three. The thirty rituals above will land differently when you know which specific person you are trying not to lose.
- Pick two rituals from above to run this week. One from Group A (daily, in-the-flow) and one from Group B (weekly, structured). The Friday three-line ritual (#11) plus one same-day specific Slack DM (#1) per direct report this week is a strong default. Five minutes total per person. Do it once. Notice what changes in the next 1-on-1.
- Block thirty minutes on your calendar this Friday for the first recognition pass. Not as inspiration. As discipline. Sit down, look at the week, write three things you noticed about three different people, send the messages. Then put the same block on every Friday for the next eight weeks. After eight weeks, the practice has become a habit and you do not need the calendar block anymore. Most managers never get past the first three weeks because they did not put it on the calendar. The calendar is the difference between recognition being a value you hold and a practice you run.