Kudos examples for coworkers: 30 messages you can copy
A good kudo names the person, says what they did and says what it changed. "Priya, you rewrote the deploy checklist and the Friday release took 20 minutes instead of two hours" works. "Great job this sprint" does not. Below are 30 examples you can copy and adapt, grouped by the moment they fit.
The formula for a kudo that lands
Use three parts and keep it to one or two sentences.
- Who. Start with the name, so the message cannot be read as general praise.
- What. Describe the specific thing they did. Use a verb, not an adjective.
- Effect. Say what changed for you, the team or a customer.
"Tomas, you stayed on the call until the payment bug was reproduced. We shipped the fix the same day and support stopped getting tickets."
If you only have time for two parts, drop the effect, never the action. For a longer guide to the format, read what a kudo card is. To write one right now, use the kudo card maker.
Kudos examples for finishing hard work
- "Amara, you untangled the billing migration and wrote down every step. The next person will not start from zero."
- "Jonas, you cleared the test backlog nobody wanted. Our pipeline is green for the first time in a month."
- "Lena, you took the support rotation on a bad week. The rest of us kept our focus."
- "Sam, you shipped the search fix before the demo. The client noticed and said so."
- "Ines, you refactored the checkout code and added tests first. We changed it twice since without a single bug."
Kudos examples for helping a teammate
- "Marco, you spent an hour pairing with me on the caching issue. I understand it now and fixed the next one alone."
- "Fatima, you answered my question in the channel with an example. Three other people used it the same afternoon."
- "Ravi, you reviewed my pull request the day I asked. It unblocked the release."
- "Chloe, you covered my on-call shift at short notice. I made it to my daughter's recital."
- "Ben, you explained the roadmap to the new hire without being asked. She was productive in week one."
Kudos examples for communication and meetings
- "Noor, you wrote the meeting notes while facilitating. We had decisions and owners before we left the room."
- "Elif, you said the unpopular thing about the deadline politely. We moved it and avoided a weekend of rework."
- "Kai, you cut the demo to ten minutes. People asked better questions because they were still awake."
- "Sofia, you asked the stakeholder what success looked like. The ticket got much smaller."
- "Dmitri, you turned a long thread into a three-line summary. I could finally catch up."
Kudos examples for Scrum Masters and product owners
- "Hannah, you protected the sprint goal when three new requests arrived. We finished what we promised."
- "Omar, you rewrote the stories with acceptance criteria. Refinement dropped from two hours to 45 minutes."
- "Julia, you ran a retro that ended with two owned actions. We completed both."
- "Pedro, you said no to a feature and explained why. The team trusted the backlog more afterwards."
- "Aisha, you noticed the team was tired and moved the planning session. Nobody had to ask."
Short kudos for chat and quick thanks
- "Thanks for the clear bug report, Ahmed. Fixed in ten minutes."
- "Nina, your doc saved me an hour today."
- "Luca, that demo script was perfect. Thank you."
- "Mei, thanks for staying late on the release. It meant a lot."
- "Eva, your review comments made the code simpler. Thanks."
How do you avoid a generic kudo?
Check for three things before you send. Does it contain a name? Does it contain a verb that describes something the person did? Does it say what happened because of it? If any answer is no, add one sentence.
Avoid praise that applies to anyone, such as "great job" or "you're a rockstar". It is pleasant and forgettable. The same teammate on a different sprint would get the same words.
What is the difference between a kudo and feedback?
A kudo recognises something that already happened. Feedback asks for a change. Mixing them weakens both, so send them separately. The post on recognition vs. feedback explains how.
Who should give kudos?
Everyone on the team, and mostly peers. Kudos from peers feel different from praise from a manager because the person giving them saw the work up close. More on this in peer-to-peer recognition in Agile teams.
FAQ
How long should a kudos message be?
One or two sentences. A kudo with a name, an action and an effect usually fits in 20 to 40 words.
Should kudos be public or private?
Public by default, because other people learn what good work looks like. Make it private if the person prefers that. Ask once and remember the answer.
How often should I give kudos?
When you see something worth naming. For many teams that is once or twice per sprint per person. A fixed moment such as the retrospective makes sure it happens.
What do I write when I cannot think of anything specific?
Describe the last thing the person did that helped you. If you cannot recall one, you are probably not paying attention to their work, and that is useful to know.