When should a startup start an employee recognition program?

Before the founder stops being able to do it personally, which is usually between fifteen and twenty-five people. A habit started at twelve people costs a Slack channel and survives the growth. One started at sixty reads as HR arriving.

Does equity replace recognition at a startup?

No. Options pay out in years or never, and they tell nobody which thing they did this week was valuable. A specific thank-you on Friday is the only recognition most startup employees will receive this quarter, and it costs nothing.

How do you recognise work that a pivot made irrelevant?

In public, by name, and soon. Say that the work was the right bet at the time, name the people who did it well, and explain what the company learned. Without that, four months of good work reads as failure to the people who did it and to everyone watching.

How does a startup keep recognition going as it grows?

By making it peer to peer early and reviewing it monthly. When the founder cannot thank everybody personally, the team has to, and a weekly reminder with values tags gives the all-hands a recap to read from. The recap is what stops the habit fading at fifty people.

Recognition for teams

Employee Recognition for Startups: What Works

In a ten-person startup the founder is the recognition program. Somewhere around twenty-five people that stops working, and nobody notices for a year.

The founder is the program until they aren’t

For the first year, recognition at a startup is easy and nobody thinks about it. The founder sits three metres from everyone, sees everything, and says thank you because they are grateful and because the whole company fits in one conversation.

Then the seed round closes, headcount doubles, and the founder’s week becomes investor calls, hiring and the two customers who might churn. The people hired in that period never had the founder at the next desk. They have never been thanked by anyone with authority, and the company does not notice, because from the founder’s chair the culture still feels like it did at eight people.

The moment to fix this is before it happens. A peer recognition habit started at twelve people costs a Slack channel and a Friday reminder, and it survives to sixty because it was there before growth. The same habit introduced at sixty feels like a process.

What launches and pivots do to credit

Startups organise time around launches, and a launch post is a specific kind of document: it names the feature and the people who built the visible part. It does not name the billing migration, the support macros written in advance, or the pricing page somebody rewrote at midnight. Those people are forgotten by the time the post goes up, sometimes by themselves.

Pivots are worse. A team builds for four months, the company changes direction, and the work counts for nothing. Everybody knows the pivot was right. Nobody says that the discarded work was also right, at the time, and done well. Left unsaid, that silence teaches the team that effort is only valued when it survives, which is precisely the wrong lesson for a company that expects to change direction again.

Recognise before the launch post, and recognise the work the pivot discarded, by name, from the founder, in public.

Values as a record rather than a slide

Startup values live in a pitch deck and a careers page. Tagging each recognition with one, ownership, adaptability, courage, turns the words into a record of what the team actually did this month, and the monthly recap becomes the honest version of the culture slide. Evergreen does this inside Slack or Teams and costs $3.99 per active user, which at twenty people is less than the coffee budget. If the recap shows nobody was thanked for courage in the month the company pivoted, that is the most useful thing the founder will read all quarter.

This week

Post one thank-you about the work that will not be in the next launch announcement. Ask the newest hire to post one about whoever helped them most in week one. Then stop for a month and see whether the team keeps going without you; the answer tells you where the culture actually is. The taking initiative messages cover the most common startup occasion, which is somebody doing a job that did not exist yet.

What gets in the way

Founder attention does not scale: Early on, everyone hears from the founder when they do something good. At thirty people the founder is in investor meetings, and the people hired after the seed round have never been thanked by anyone with authority.
Launches erase the month before them: The launch post names the feature. The three weeks of unglamorous work that made the launch possible, migrating the data, rewriting the pricing page and drafting the support macros, have already been forgotten by the people who did them.
Pivots throw work away: A team builds something for four months and the company changes direction. The work was correct at the time and now counts for nothing, and nobody says so.
Equity is treated as the thank-you: Founders assume that options make gratitude redundant. Options pay out in seven years or never. A thank-you on Friday is the only recognition most startup employees will receive this quarter.

What works

Make peer recognition the default before the founder stops being able to do it. A habit started at twelve people survives to sixty; one started at sixty feels like HR arriving.
Recognise the work a pivot discarded. Say in public that the four months were the right call at the time and name the people who did it well.
Thank the first hire in each function for the process they wrote. The first salesperson’s playbook and the first support hire’s macros are the company’s infrastructure and never appear in a demo.
Keep it inside the tool the team already lives in. A startup will not open a separate app for gratitude; a message in Slack, with a reminder, gets done.
Let new joiners give recognition in week one. It is the fastest way for them to learn who does what, and it tells them the habit is real.

5 messages written for this team

Imogen built the whole billing migration in the two weeks before launch and it moved 1,400 accounts with zero support tickets. Tomorrow’s announcement will be about the new plans. Today is about her.
Founder, the day before launch
Thanks the invisible work before the launch post overwrites it.
Thanks, Arjun, for writing the first sales playbook when you were also the only salesperson. Two new hires closed deals in their first month by following it and have no idea who wrote it.
Peer
Credits process written by a first hire, which becomes infrastructure.
The team that built the marketplace we just shut down did four months of careful work on the right bet at the time. Mei, Sam, Oluwaseun: this is a thank-you, and it is the reason we can pivot in a fortnight instead of a quarter.
Founder, at the all-hands
Recognises work a pivot discarded, which otherwise reads as failure.
Zoë, you asked the question in Monday’s planning that killed the feature nobody wanted to build. That saved us a month. Please keep being the one who asks.
Peer
Rewards courage in a room where agreement is easier.
Thank you for being the person who set up the on-call rota before we had an incident, Piotr. The incident arrived last night and it was boring, which is the highest compliment I know.
Manager
Recognises prevention with a specific, recent proof.

A program that fits

Start now, at whatever size you are: The cost is a channel and a weekly reminder. The cost of waiting is that the founder’s thank-yous stop and nothing replaces them.
Write down three values, tag every message: A startup’s values usually live in a pitch deck. Tagging each recognition with one turns them into a record of what the team actually does, which is what the next hire will read.
Set the reminder for Friday, and let the founder go first for a month: The founder posting one specific thank-you a week models the standard. After four weeks, stop and see whether the team continues without you.
Recognise before the launch post: The day before a launch, thank the people whose work will not be in the announcement. The announcement will look after itself.
Review the recap at the monthly all-hands: Who was thanked, for what, tagged with which value. If nobody was thanked for courage in a month where the company pivoted, that is worth saying aloud.

Questions people ask

When should a startup start an employee recognition program?: Before the founder stops being able to do it personally, which is usually between fifteen and twenty-five people. A habit started at twelve people costs a Slack channel and survives the growth. One started at sixty reads as HR arriving.
Does equity replace recognition at a startup?: No. Options pay out in years or never, and they tell nobody which thing they did this week was valuable. A specific thank-you on Friday is the only recognition most startup employees will receive this quarter, and it costs nothing.
How do you recognise work that a pivot made irrelevant?: In public, by name, and soon. Say that the work was the right bet at the time, name the people who did it well, and explain what the company learned. Without that, four months of good work reads as failure to the people who did it and to everyone watching.
How does a startup keep recognition going as it grows?: By making it peer to peer early and reviewing it monthly. When the founder cannot thank everybody personally, the team has to, and a weekly reminder with values tags gives the all-hands a recap to read from. The recap is what stops the habit fading at fifty people.