Appreciations (Kudos)

When to use

Closing a sprint retro on a relational note, or wrapping a project where the work merits a real thanks. Skip it on teams over eight — round-robin appreciations on twelve people takes 25 minutes and the last few are exhausted. Skip it on a team in active conflict; the appreciation will land as fake or pointed. Skip it if the team won't commit to specificity — generic thanks teaches the wrong lesson.

How it runs

1. State the rule out loud

   'Name the person, name the specific thing they did, ten seconds.' Say it before the round opens. The rule is the format — without the specificity ask, the round defaults to performative gratitude inside two minutes.

2. Make it opt-in to receive

   Some people don't want public appreciation. Tell the team they can pass on receiving without explanation. Forced gratitude is worse than no gratitude — it makes the format coercive.

3. Round-robin, ten seconds each

   One appreciation per person. Senior person goes last so the bar isn't set by 'thanks Sam, great quarter' from the boss. People can pass either way (giving or receiving) without comment.

4. Watch the distribution

   Same three high-performers get appreciated every retro; the quiet senior engineer never does. The pattern is the diagnostic. Notice it, and quietly redirect the next round — 'today let's appreciate someone you haven't appreciated before' — but don't shame the giver.

Why it works

Specific, named appreciation is the cheapest signal in the workplace and most teams under-supply it. The format works when it surfaces gratitude that wouldn't otherwise be said. It collapses the moment 'thanks for being awesome' enters the round, because the team learns the format is shape without content. The specificity rule is the only thing standing between useful and theatre.

Variations

• Pair the appreciation with the action: 'Sam, the way you caught the off-by-one in code review on Tuesday.' The action is what makes it real.
• Async appreciations in a Slack channel — lower social cost, easier to pass without awkwardness, no round-robin tax. Better default for teams over eight.
• Quarterly anonymous appreciations — each person writes one for everyone they want to thank, facilitator delivers privately. Slower, deeper, fits long-running teams.
• Skip the round on a tough sprint. Forced gratitude after a brutal week reads as gaslighting; an honest 'we're not doing appreciations today, we just shipped' is the right move.

Facilitator notes

Go first with a sharp example so the bar is set. 'Maya, the migration plan you wrote on Friday — the rollback section saved us a Saturday' is a real appreciation; 'Maya, great work this sprint' is filler. If the round drifts toward filler, name it gently — 'let's name the moment' — once. Twice and you've turned the closer into a lecture.

Pitfalls

• 'Thanks for being awesome.' The classic failure mode. Worse than silence.
• Forcing the round on teams over eight. The last three appreciations are exhausted; the format scales badly.
• Same three people get named every time. Surface the pattern privately; don't shame the giver publicly.
• Running it on a team in conflict. Performative gratitude during a real disagreement makes the disagreement worse, not better.

Remote tips

Round-robin works on video for groups under eight. For larger groups, switch to a parallel chat dump — everyone posts one specific appreciation at the same time, sixty seconds, done. Reading aloud at scale wastes the format's main strength: low cost.

Example outputs

• 'Priya — the rollback runbook you wrote during the incident on Wednesday. We followed it word-for-word at 2am and got back up in 18 minutes.'
• 'Tom — you stayed on the call with the customer for an extra hour on Friday so I could go to my kid's school play. I owe you one.'
• 'Ana — the way you reframed the design review feedback on Tuesday. You made it land without anyone getting defensive. I learned something.'

FAQ

Appreciations or Plus/Delta?

Appreciations closes a sprint or project on a relational note. Plus/Delta closes a meeting on an operational one. Different scales, different jobs. Don't run both as the same closer — pick one. Appreciations for the long arc of work; Plus/Delta for the meeting that just happened.

Should I run it every retro?

Probably not. Weekly appreciations train the team to manufacture gratitude for the format's sake. Monthly or end-of-sprint cadence keeps the well full. Async-in-Slack works as a continuous version with much less overhead.

What if somebody doesn't want to participate?

Let them pass — both giving and receiving. Forced gratitude is worse than absence. If you've framed it opt-in and someone opts out, that's the format working as designed.

Related activities

Recommended use cases