If the kudos has no noun, it will not survive until review
Write the work, the effect, and the name. Skip "rockstar." Kudos Rally stores 500 characters. That is enough for one story and not enough for a speech.
A kudos message has a second reader: future you, filling a review form. "Thanks for being awesome" is a kind ping and a useless record. The fix is a noun. Name the pull request, the customer, the incident.
Kudos Rally will store whatever you type, including "awesome." The bot will not coach you in the modal. The formulas below are the coaching. If you lead a 20 to 120 person remote or hybrid company, peer notes are how dated examples show up without a form.
Name the work and the result
1) Work: what they did, in a thing you could find again. 2) Effect: what changed for a user, a teammate, or a metric you actually have. 3) Name: @person, not "the team" hiding one person.
Example: "@noura wrote the failover runbook and last night's page lasted 11 minutes instead of an hour."
Not: "@noura is a legend."
"The team crushed it" is a toast. It is not a record. If four people touched the work, write four notes or write one note that names the one action you saw. Hearsay belongs in a 1:1, not in a public note.
If you cannot point at a ticket, a doc, a customer, or a timestamped incident, you do not have a kudos yet. You have a mood. Wait until you have the noun.
Twelve frames you can paste
1) "@name shipped [thing] so [user] can [action]." 2) "@name caught [bug] before [event]." 3) "@name explained [system] in [doc], and I stopped asking in Slack." 4) "@name stayed on [incident] until [state], and I went to sleep." 5) "@name pushed back on [scope] and we cut [thing] instead of slipping [date]." 6) "@name onboarded [person] through [first ticket]." 7) "@name translated [requirement] into [ticket] the rest of us could work." 8) "@name told the customer [fact] instead of [hope], and we kept the account." 9) "@name reviewed [PR] with [N] comments that were about the logic, not the commas." 10) "@name owned [decision] in writing, so we stopped relitigating it." 11) "@name covered [shift / on-call / desk] so [name] could [leave / deep work]." 12) "@name wrote [doc / runbook / checklist] that I used during [event]."
What not to post
Birthdays, return-from-leave, and identity-as-praise ("you are so smart") belong in HR or a private note. PIPs and hearsay stay out of the public channel. The 52-week pack repeats this list.
Caps and storage
Free: 3 given per person per day. Team and Business: 5. Cap is 500 characters. Team and Business keep 365 days. Free keeps 90. See the Slack app for how the slash command and emoji path work.
Founding members get 30% off regular prices for as long as they stay subscribed. 30-day money-back guarantee once the product opens. No card needed to join.
When does it launch?
No public date yet. Founding members get the invite first, by email, before anyone else.