You have to stand up in front of people and say something about a colleague, and you'd rather do almost anything else. Good news: a recognition speech is one of the most formulaic pieces of public speaking there is, and the formula is short. Ninety seconds, four beats, one specific story.
Below is the structure, four complete speeches you can adapt for the common occasions, and the six mistakes that make otherwise-fine speeches land flat.
The 90-Second Structure
Almost every recognition speech that works follows these four beats in this order:
- The setup (10 seconds). What the award is and, briefly, what it's for. Not a history of the awards program.
- The story (45 seconds). One specific incident, told as a small narrative — a moment, a complication, a resolution. This is the entire speech; everything else is scaffolding.
- The meaning (20 seconds). Zoom out. What that story says about the person and about what you value here.
- The name (5 seconds). Say it last, say it clearly, and then stop talking and start clapping.
Ninety seconds feels short when you're planning and long when you're standing up. Trust the short version. Nobody in the history of the awards ceremony has wished a speech were longer.
Speech 1: Employee of the Month or Quarter
Every quarter we give this award to someone whose work made everyone else's work better. This quarter it wasn't a close call.
In March our billing export broke on a Tuesday night. The person receiving this award wasn't on call, it wasn't their system, and they had their own release shipping Thursday. They picked it up anyway. They sat with Support until one in the morning, found every affected account, and had a corrected file out before a single customer noticed. Three hundred invoices went out on time and nobody outside this room knows it almost didn't happen.
That's the thing about this kind of work — when it goes right, it looks like nothing happened. I don't want it to look like nothing happened. Stepping into a problem that isn't yours, at midnight, with your own deadline looming, is exactly the instinct that makes a team worth being on.
Our Employee of the Quarter is Daniel Reyes.
Speech 2: Years of Service
Twenty years ago, this company had forty employees, one office, and a maintenance process that lived entirely in one person's head. Tonight we have six hundred people, sites in four regions, and a checklist that every one of them runs on.
That checklist is the same one James wrote in 2009 because he was tired of explaining it. That's more or less his whole career in one anecdote: he sees something that only works because he's there, and he turns it into something that works whether or not he is.
In twenty years he's worked in four departments and trained more than thirty people. Eleven of them now run teams of their own. Several are in this room, and I'd bet most of you can still hear his voice when you're about to skip a step.
Twenty years is a long time to keep caring. Thank you, James Whitfield.
Speech 3: Team Award
This award usually goes to a person. This year it goes to nine of them.
Between July and September, ticket volume tripled. Headcount did not change. First-response time moved by eleven minutes — eleven — and satisfaction scores didn't move at all.
Here's the part I want to be specific about, because it's the part that impressed me. That didn't happen through heroics. Nobody worked themselves into the ground and nobody quietly lowered the bar, and under that kind of pressure either one would have been completely understandable. Instead this team reorganized its own queue, wrote its own triage guide, and covered each other's shifts before anyone had to ask.
They fixed the system instead of absorbing the pain. That's rarer and much harder. Our Team of the Year is Support.
Speech 4: Farewell or Retirement
Priya is leaving us on Friday, and I've been told I get three minutes, which is roughly one minute per four years.
She joined as our second support hire when "the support team" was two people and a shared inbox. She wrote the macros half of you use every day. She trained eleven people who now run their own teams. And one Christmas Eve, at two in the morning, she answered a ticket from a hospital because the alternative was a customer locked out of a system they needed.
She'll hate that I mentioned that. She's mentioned it exactly never in twelve years — I found it in an old thread.
That's who we're losing. Someone who did the right thing at 2am and then didn't tell anyone. Priya, thank you. Don't be a stranger.
Six Mistakes
1. Reading the résumé. Listing someone's roles, tenure, and responsibilities is biography, not recognition. One story beats a complete career summary every time.
2. Adjective stacking. "Dedicated, hardworking, always positive, a true team player." Four adjectives describe nobody. One incident describes exactly one person.
3. Saying the name first. Name last is a small trick with a real effect: it holds attention through the story instead of releasing it in the first sentence.
4. The inside joke. If a third of the room doesn't get it, it excludes more people than it charms. Save it for the team dinner.
5. Comparative praise. "The best engineer we have" makes one person glow and quietly stings four others. Praise the work absolutely, not competitively.
6. Overrunning. A speech that goes long converts warmth into restlessness. If you have five recipients, that's five ninety-second speeches, not one seven-minute meditation on excellence.
Delivery Notes
- Write it out, then speak from three bullets. Full text for the thinking, bullets for the delivery — reading verbatim kills the warmth.
- Know the pronunciation. Ask beforehand. Getting a name wrong on stage is a small permanent injury.
- Look at the recipient during the story, at the room during the meaning.
- Pause before the name. One beat. It does more work than any adjective.
- Have the written version ready to send. The words disappear from the room in ninety seconds; a follow-up email or a formal recognition letter is what they keep.
Where the Story Comes From
Every speech above is carried by one specific incident with a date attached. That's not a writing trick — it's the raw material, and it's the thing most people can't find when they need it.
The standard scramble is familiar: awards are next Thursday, you Slack three people asking "what has Daniel actually done this year?", and you get back a handful of half-remembered generalities. So you write "consistently demonstrates dedication," because that's what survives when the specifics have evaporated.
Full disclosure of bias — this is exactly why we built Propsly. It lives in Slack: anyone types /props to send recognition with a message and a hashtag, and it posts to a public feed like #wins. The free tier covers unlimited users, 200 props per person per month, leaderboards, and the feed. Come awards season, you don't interview people about the past year — you search it. The 2am billing story is already written down, by the person who watched it happen, on the day it happened. Your speech is a matter of picking the best one.
There's a harder-nosed argument too. Employees who feel inadequately recognized are roughly twice as likely to say they'll quit within a year (Gallup/Workhuman), and strong recognition cultures see up to 31% lower voluntary turnover (Deloitte). An annual speech is a wonderful moment and a weak system. It works best confirming something the whole team has already watched happening all year — which is also the difference between an award that feels earned and one that feels assigned. If you want the dollar version of that argument, our turnover cost calculator makes it on your own headcount.
So: one story, ninety seconds, name last, then stop. And start collecting the stories now, not next October.