What is a kudo card? A practical guide for Scrum and Agile teams
A kudo card is a short, written note that names something specific a teammate did well and the effect it had. It's usually a few sentences long, addressed to one person, and shared in a place the whole team can see: a physical card on a wall, a sticky note on a retro board, or a message in a tool built for it. The point isn't to praise. It's to make a specific contribution visible to people who wouldn't otherwise have known about it.
That distinction, specific and visible, is what separates a kudo card from ordinary workplace praise. It's also why the format has stuck around in Agile teams for over a decade.
Where the format came from
Kudo cards trace back to Management 3.0, the practice framework Jürgen Appelo developed for managing in complex, self-organizing teams. Appelo introduced the "kudo box" as a physical prop: a box of blank cards sitting in the team room, next to a slot where anyone could drop a filled-in card for a colleague. At the next team gathering, cards got pulled out and read aloud.
The mechanic was deliberately low-friction. No manager approval, no point budget, no HR system. Just a card, a pen and a habit of noticing. Scrum teams adopted it because it fit naturally into ceremonies that already existed: open the retro by reading a few cards, or pin them to the board during the sprint as they happen.
What makes a kudo card different from "great job"
Most workplace praise is vague, delayed and private. A manager says "nice work this quarter" in a one-on-one three months after the work happened. A kudo card is built to avoid those problems:
| Generic praise | Kudo card | |
|---|---|---|
| Specificity | "Great job this sprint" | "Your debugging session on the payment timeout saved us from shipping a bug on release day" |
| Timing | Often delayed to a review cycle | Given close to when it happened |
| Visibility | Usually private, one-on-one | Shared with the team, not just the recipient |
| Source | Almost always manager to report | Anyone to anyone, peer to peer included |
The peer-to-peer part matters more than it might seem. In most recognition programs, praise flows downward: manager to employee. Kudo cards flow sideways. A tester can thank a developer, a developer can thank a product owner and nobody needs sign-off to do it.
Where kudo cards fit into Scrum ceremonies
Teams that stick with kudo cards tend to use them in one of a few recurring spots rather than randomly.
Retrospective opener. Read two or three cards before the retro gets into what went wrong. It sets a tone of "we also did good work" before the team digs into problems.
Daily standup. A quick card read at the end of standup keeps recognition frequent instead of saving it all for sprint end.
Sprint review. Pair a kudo with the specific deliverable being demoed, tying recognition directly to the work being shown.
Async, between ceremonies. For remote and hybrid teams, a shared Slack or Teams channel, or a dedicated kudos tool, replaces the physical card slot so recognition doesn't have to wait for the next meeting.
How to write one that actually lands
Most weak kudo cards fail for the same reason. They describe the person instead of the action. "Sarah is a great teammate" tells the reader nothing they can picture. A strong card has three parts: what happened (the specific action, not a trait), why it mattered (what it prevented, unblocked or improved) and who it affected (you, the team, a customer, the sprint goal).
A few examples across common situations:
- Technical: "Thanks for catching the race condition in the checkout flow before we deployed on Friday. That would have been a rough weekend on-call."
- Collaboration: "You pulled in the design team early on the onboarding redesign instead of waiting until it was 'ready to review.' It saved us a full rework cycle."
- Mentorship: "Your pairing session on the auth module this week is the reason I shipped my first PR without needing three rounds of review."
- Resilience: "You kept the standup focused and calm during the outage yesterday instead of letting it turn into a blame session. That's why we fixed it in twenty minutes instead of two hours."
Each one names the action, the effect and who benefited. None of them could be copy-pasted onto a different person without losing meaning, which is a decent test for whether a kudo card is specific enough.
Common mistakes teams make with kudo cards
Only recognizing output, never effort. The person who spent two days on a dead-end investigation that ruled out a bad approach did useful work, even though nothing shipped.
Letting it become manager-only. If leads are the only ones writing cards, it's a performance review with extra steps, not a kudo system.
Writing them and never reading them. A stack of cards nobody looks at again isn't recognition, it's clutter. Read them out loud or keep them visible somewhere the team actually passes by.
Going quiet after the first few weeks. Novelty carries a kudo habit for about a sprint or two. After that it needs a fixed slot in a ceremony, or it disappears.
Physical cards vs. digital tools
The original kudo box works well for co-located teams. There's something to a physical card on a corkboard that a Slack message doesn't replicate. But it breaks down the moment a team goes remote or hybrid: there's no shared wall, no box to walk past and cards written in a private DM never become visible to the rest of the team.
Digital kudo tools, including esteam.life, exist to solve that gap. They keep the peer-to-peer, low-friction, publicly visible spirit of the original kudo box, but in a place a distributed team can actually see it: during a video retro, in Slack, or as a shareable card sent directly to a teammate.
Want to try the format before bringing it to your team? The free kudo card maker lets you write a card and download it as an image, no account needed.
FAQ
Who invented kudo cards?
The format comes from Jürgen Appelo's Management 3.0 practices, first described as the "kudo box," a physical box of cards used to recognize colleagues in a team space.
Are kudo cards only for Scrum teams?
No. They started in Agile/Scrum contexts because they fit naturally into existing ceremonies like retros and standups, but any team that wants low-friction, peer-to-peer recognition can use the format.
How often should a team give kudo cards?
Most teams that sustain the habit tie it to an existing recurring event: a sprint, a standup, a weekly sync, rather than leaving it open-ended. Attaching it to something that already happens regularly is what keeps it from fading out.
Do kudo cards need to come with a reward?
No. The original format is deliberately reward-free. The visibility and specificity are the point. Points or monetary rewards can be layered on, but they're not what makes a kudo card work.