Karl · 12 September 2026

24 Slack kudos examples for the work worth noticing

A useful shoutout names a person, describes what they did, and explains why it mattered. Copy an example below, then replace the names and details with something you actually observed.

These are original, illustrative templates, not customer quotes or measured outcomes. They work as ordinary Slack messages; use Karl when you want to record the kudos and connect it to values.

The message formula

Thanks @person for [specific action]. It helped [person or team] [concrete result].

Keep the result proportionate. “The handoff was clearer” is better than claiming that someone “transformed the company.” Recognize the contribution without revealing private customer details or personal circumstances.

Project launches and delivery

A clear handoff

Kudos to @Sam for turning the launch decisions into a checklist with owners. Support could pick up the release without another handoff meeting.

A careful review

Thanks @Priya for spotting the billing edge case in review and explaining how to reproduce it. We fixed it before customers ran into it.

Unblocking a teammate

Shoutout to @Alex for pairing with me on the deployment issue and documenting the fix. I can handle that step myself next time.

Cross-team delivery

Kudos to @Jordan and @Lee for agreeing the API changes together before implementation. Both teams knew what to build and when.

Customer support and customer impact

Closing the loop

Thanks @Morgan for following up with the customer after the fix shipped. They knew what changed and how to try it again.

Making feedback useful

Kudos to @Taylor for collecting three concrete examples from support tickets. Product could see the problem without asking customers to repeat themselves.

A thoughtful escalation

Thanks @Casey for including the reproduction steps and customer impact in the escalation. Engineering could start investigating straight away.

Improving an explanation

Shoutout to @Jamie for rewriting the setup instructions after noticing repeated questions. The next customer has a clearer place to start.

Mentoring and onboarding

Teaching the reasoning

Kudos to @Avery for explaining why we chose that approach, not just what to do. I felt confident making the next decision on my own.

Welcoming a new teammate

Thanks @Riley for making time for my setup questions and introducing me to the right people. My first week felt much less confusing.

Sharing useful feedback

Thanks @Sam for giving specific feedback on my draft and showing an example. I understood what to change and why it helped.

Creating a reusable guide

Kudos to @Priya for recording the walkthrough and adding a written checklist. New teammates can learn at their own pace.

Behind-the-scenes contributions

Maintaining documentation

Thanks @Alex for updating the runbook after the incident. The next person on call will have the steps we wished we had.

Catching a small discrepancy

Kudos to @Jordan for reconciling the numbers before the report went out. We could share the results with confidence.

Making a process accessible

Thanks @Lee for adding captions and written notes to the training. More teammates can use it in the way that works for them.

Keeping work organized

Shoutout to @Morgan for closing the stale tasks and clarifying the remaining owners. We can see what still needs attention.

Company values in action

Ownership

Kudos to @Taylor for noticing the missing handoff owner and staying with the issue until it was resolved. That is ownership in practice.

Customer focus

Thanks @Casey for checking the proposed fix with the customer before we expanded it. Their feedback changed what we built.

Learning

Kudos to @Jamie for sharing what did not work in the experiment and what you would try next. The rest of us can learn from it too.

Inclusion

Thanks @Avery for asking for written input before the meeting. Teammates in other time zones could shape the decision.

Remote teamwork and everyday support

An async update

Thanks @Riley for leaving a clear update with the decision, open question, and next owner. I could continue the work when my day started.

Protecting focus time

Kudos to @Sam for gathering the questions into one useful briefing. We got the answers we needed and kept the afternoon free to finish the work.

Offering a second pair of eyes

Thanks @Priya for reviewing the proposal when I was stuck. Your question helped me see the trade-off I had missed.

Supporting a shared deadline

Shoutout to @Alex for agreeing a manageable handoff with me when priorities changed. We kept the work moving without leaving anyone guessing.

Send one of these examples with Karl

In a channel where Karl is installed and invited, type /kudos, select your teammate from Slack’s mention picker, and add the reason.
Review the confirmation, select a company value if appropriate, and choose a GIF or None.
Submit the kudos to share it in the channel. Simply pasting a template as an ordinary message does not run the Karl command.

/kudos @Sam for turning the launch decisions into a clear checklist. Support could pick up the release without another meeting.

Replace @Sam using Slack’s actual mention picker. Read the step-by-step kudos walkthrough for setup and troubleshooting.

Help the habit spread

Put two or three examples in your channel topic or onboarding guide. Invite people to describe work they noticed; avoid asking everyone to hit a message quota.

Use the company values guide to agree what each value looks like, then follow the 14-day Slack recognition launch plan.

Start free 30-day trial