Write recognition that says what mattered
Before-and-after examples for the kinds of work people most often thank each other for, and a three-part framework you can copy into your launch message or onboarding.
On this page
Most kudos are warm and vague: "Great job on the launch!" The person feels noticed for a moment, and nobody else learns anything. The kudos that people remember, and that show the rest of the company what good work looks like, name what someone did and what it changed.
This is a template you can share as it is. It works for kudos in Pulsido, in Slack, or in a team meeting.
The framework: action, impact, thanks
A useful kudos answers three questions, usually in one or two sentences.
- Action: what did they do? Something specific enough that a colleague who wasn't there could picture it. A verb and an object: "rewrote the onboarding checklist", "stayed on the call with the customer until it was fixed".
- Impact: what did it change? For you, a customer, or the team. Time saved, a problem avoided, a person helped. A rough number is fine if you have one, and don't invent one if you don't.
- Thanks: say it plainly. "Thank you" is enough. Tie it to a value if one fits naturally.
[Name], thank you for [specific action]. It meant [impact], which [why it mattered to you or the team].
You don't need all three every time. A quick "Thanks for covering my shift on Friday, I got to see my kid's recital" is perfect. The framework is for when you're staring at the box wondering what to write.
Before and after, by kind of contribution
| Kind of work | Vague | Says what mattered |
|---|---|---|
| Helping a colleague | "Thanks for your help!" | "Thanks for walking me through the billing export on Tuesday. I'd have spent a day guessing, and the finance close went out on time." |
| Customer work | "Great job with that customer." | "You stayed on with the clinic until their import worked, past 7pm. They renewed this morning and mentioned you by name." |
| Behind-the-scenes work | "Thanks for all you do." | "The new on-call runbook is the first one I've used at 3am without calling anyone. Thank you for writing it." |
| Quality and care | "Nice attention to detail." | "You caught the wrong tax rate in the Canada invoices before they went out. That would have been 140 corrections." |
| Leading or teaching | "Great presentation!" | "Your 20 minutes on reading the engagement scores made our managers' meeting actually useful. Three people asked for the slides." |
| Courage | "Thanks for speaking up." | "Thank you for raising the deadline problem in the planning meeting. We moved the date, and nobody had to work the weekend." |
| Welcoming someone new | "You're a great teammate." | "You checked in on me every day in my first week and introduced me to half the office. It made starting here a lot less lonely." |
| Steady, reliable work | "Thanks for being awesome." | "Twelve months of payroll with zero errors. We never think about it, and that's because of you." |
A stranger could read any line in the right-hand column and understand what good work looks like at your company.
Tie it to a value, when it fits
If your company has values, kudos are where people use them day to day. In Pulsido, each value is a kudos type you pick when you write. Choose the one the action shows, not the one that sounds best. A kudos for staying late with a customer is "Customers first" and it doesn't need to be "Ownership" as well.
If nobody ever picks one of your values, that's useful information. Either it's not how people describe good work, or the name doesn't mean much in practice. Review it at your 30-day check-in.
Common traps
- Recognizing only visible work. Launches and big deals get thanked. Fixing the flaky test, onboarding the new hire, and answering the same question patiently for the fifth time often don't. Look for the work that kept things from going wrong.
- Praising the person instead of the act. "You're so smart" is about the person. "Your question about the edge case saved the release" is about something they did, and they can do it again.
- Inflating every kudos. If every kudos is "amazing" and "incredible", none of them are. Plain words carry more weight.
- Saying it in private when it could be public. Public kudos teach everyone. Use private kudos when the person would prefer it, or when the context is personal.
A checklist to paste beside the kudos box
Before you send, check:
- Could someone who wasn't there picture what they did?
- Did you say what it changed, for you, a customer, or the team?
- Would you be happy for them to read it out loud?
Add it to your launch message or your onboarding page. People rarely need more instruction than that.
Sources and limits
These examples are composites written for this guide, not quotes from customers. The idea that specific recognition matters more than frequent generic praise is discussed, with sources, in What a thank-you does.