Launch a recognition program in 30 days
A week-by-week plan for starting peer recognition at a small or midsize company, with who does what, messages you can copy, and the questions to ask at the end of the month.
On this page
When a recognition program stalls, the tool is rarely the reason. Usually nobody owns it, the launch is one email, and by week three the only kudos come from the person who set it up. This plan spreads the work across a month so the habit has a chance to form before anyone judges it.
It's written for a company of roughly 20 to 500 people with one person who can spend an hour or two a week on it. Adjust the timings to your size; keep the order.
Before you start: decide three things
Settle these in a short conversation with whoever leads the company. They're hard to change after launch.
- Who owns it. One named person, usually in People or Operations, who checks in weekly for the first two months. Not a committee.
- What you're recognizing. Three to six values or behaviors people already talk about. Generic categories like "Thank you" are fine to start with; company values make kudos more specific. You can rename them later.
- Whether coins and rewards are part of it, now or later. Starting with recognition alone is fine. If you add rewards, decide the monthly budget per person and who approves redemptions before anyone earns a coin.
Week 1: set up quietly
The goal this week is a working setup that a handful of people have tried.
| Task | Owner | Done when |
|---|---|---|
| Sign up, name your company, and set its time zone | Program owner | Reminders and celebrations go out at local times |
| Add your values as kudos types | Program owner | Each has a one-line description of what it looks like in practice |
| Connect Slack or Microsoft Teams, or decide to stay web-only | IT or your Slack admin | Kudos post in one public channel |
| Invite five to ten early testers across teams | Program owner | Each tester has sent at least one kudos |
| Turn birthdays and work anniversaries on or off | Program owner | Your choice is made; people can still keep theirs private |
Ask the testers to send real kudos, not test messages. Their examples become the first things everyone else sees, so a few specific, warm ones set the tone better than any instruction.
Pulsido's setup guide covers each step.
Week 2: launch to everyone
Invite the whole company in one go, with a short message from a leader, not from the tool. Then make sure the first few days aren't quiet.
| Task | Owner | Done when |
|---|---|---|
| Send the launch message (below) | A company leader | Posted in your main channel and sent by email to anyone not in Slack |
| Send invites | Program owner | Everyone has an invite link or can join with Slack |
| Recognize three people publicly on day one | Each leader and manager | The feed has visible, specific examples |
| Answer questions in the channel | Program owner | Nobody's question waits more than a day |
A launch message you can copy
Starting today, we're making it easier to say thanks.
A lot of good work here goes unnoticed, not because nobody cares, but because there's no easy moment to say so. From today, you can give kudos to anyone, for anything that made your week better, right here in Slack or on the web.
Be specific: say what they did and why it mattered. One sentence is plenty.
I'll start: [one real example of recognition].
Your invite is in your email. Questions go to [program owner].
There's a longer version, and versions for people who don't use Slack, in the help center's launch message article.
Week 3: make it a habit
By week three the launch has worn off. A weekly rhythm is what keeps kudos coming.
- Turn on a weekly moment. A recurring kudos round (for example every Thursday, with a short reminder) gives people a reason to stop and think about their week. See the weekly round.
- Ask managers for one kudos a week each. Not a quota for everyone; a visible example from the people whose attention matters most.
- Show the people who haven't been recognized yet to their managers, as a prompt to look around, not a scorecard.
- Share one good kudos in a team meeting. Read it out. It takes thirty seconds and shows what "specific" sounds like.
Resist adding everything at once. Rewards, awards, and challenges can wait until the basic habit is there.
Week 4: review and decide what's next
Book thirty minutes with the program owner, one leader, and two or three people who aren't managers.
Review agenda
- What happened (5 minutes). How many people gave kudos at least once? Which teams are quiet? Look at the trend across the four weeks, not a single number.
- What it felt like (10 minutes). Ask the non-managers directly: did any kudos feel forced or performative? Were people left out?
- What to change (10 minutes). Pick at most two changes: a value that nobody uses, a reminder at a bad time, a team that needs its manager to model it.
- What's next (5 minutes). Decide whether to add anything, such as coins and rewards or a short pulse survey, and who owns it.
Write down what you decided and share it in the channel you launched in.
What to avoid
- Turning kudos into a leaderboard of people. Counts are useful for spotting who's overlooked, not for ranking anyone. Recognition that feels competitive stops feeling like thanks.
- Making it mandatory. Encourage and model it; don't require a number.
- Generic praise. "Great job" teaches nothing. "Your summary of the customer call saved me an hour of reading" does.
- Going quiet after launch. Most programs that stall do it in weeks three to six. That's when the weekly check-in matters most.
Sources and limits
This plan comes from how we've seen recognition launches go, not from a controlled study. For the evidence on why frequent, specific recognition matters, see How often should people be recognized? and What a thank-you does, which link the underlying research.