The recognition programs that thrive are not the flashiest, they are the most scalable.
Here is why one-size-fits-all and all the bells and whistles can quietly kill recognition.
Think about how much of your life is personalized now. Your Netflix homepage, your Spotify playlists, the feed that somehow knows your mood on a Tuesday afternoon.
We have been quietly trained to expect that the things built for us are actually shaped around us. Then we sit down to design an employee recognition program and reach for the one approach the consumer world abandoned a decade ago: one thing, for everyone, the same way.
Joey Price, CEO of Jumpstart HR and a recent guest on our HR on the Frontline podcast, named that disconnect better than anyone.
That instinct toward the lowest common denominator is the single most common reason recognition programs fail to scale, and failing to scale is exactly why many of them quietly slow down or fade out six months after launch. Most teams treat scalability as a technical afterthought, something the software vendor handles, and they pour their energy into making the program bigger and more impressive. The programs that last do the reverse. They treat scalability as the strategy itself, which in practice means building for flexibility, fit, and low friction from day one. Scalability, done right, is the secret weapon that separates recognition programs that sustain from the ones that fizzle.
To understand why growth can be so unforgiving, we sat down for a long conversation with Kwesi Thomas, Total Rewards Executive at Guusto. Kwesi has spent twenty-five years building and rebuilding these programs, from Director of Total Rewards at BlackBerry to leading Total Rewards and Engagement at Shopify. He has launched programs that stuck and watched expensive ones stall out. During our interview, the pattern in the failures was remarkably consistent.
There is hard data underneath the urgency. Gallup estimates that low engagement costs the global economy roughly $8.8 trillion in lost productivity, equivalent to about 9% of global GDP (Gallup, State of the Global Workplace).
Recognition is one of the most direct levers people leaders have to move that number, and Gallup's longitudinal research found that well-recognized employees were 45% less likely to have left their organization two years later (Gallup, Employee Retention Depends on Getting Recognition Right). Yet that same research found only 22% of employees say they get the right amount of recognition for the work they do. The appetite is real and the impact is measurable, so why does so much recognition still miss?
A big part of the answer is the lowest common denominator problem Joey described. When you design one gesture for everyone, you have to aim at the middle, and the middle satisfies almost no one meaningfully. The bigger the company gets, the wider the gap between that single middle and the actual, varied people you are trying to reach.
Here is the apparent paradox, and the heart of why scalability is so crucial. Personalization sounds like the enemy of scale, because personalizing by hand obviously does not scale past a few dozen people. The way through is to scale the freedom of choice instead of the gift. Rather than choosing one reward for ten thousand people, you give ten thousand people the ability to choose what matters to them, inside guardrails you set once. That single design decision is the difference between a program that breaks as it grows and one that gets stronger.
The second trap is the mirror image of the first. Where one size fits all under-serves people by being too uniform, over-engineering buries recognition under so many features, rules, and approvals that it stops flowing. Both feel like effort, and neither one scales.
Kwesi's advice when designing a program for growth is genuinely counterintuitive: subtract before you add.
"I would take all of my designs and all the rules and things I wanted to do, and I would try to cross off as many as I could. That may sound counterintuitive, but I'm probably gonna have too many budget approvals, too many restrictions.
What do I actually need to prevent and what do I need to police? I would strip it down to what I really need to police."
Every approval gate and clever feature you add can turn into friction, and friction is what kills recognition at scale. A program with a beautiful dashboard, deep integrations, and twelve approval layers will still fail if a manager cannot send a thank you in under a minute. Kwesi is blunt about where all that machinery is supposed to point.
"All of these HRIS integrations and dashboards and reports, it's all meant to power one thing, the actual recognition moment.
If we don't focus on making sure that is as frictionless and positive as possible, what was the point of all the other features?"
— Kwesi Thomas, Total Rewards Executive at Guusto
The takeaway for anyone evaluating a platform is to resist being seduced by the feature list. The question that predicts whether a program sustains has less to do with how much it can do and more to do with how little it asks of the person in the middle of a shift.
So where does this leave you? That depends on where you are standing today. Here is how the scalability principle plays out at three common starting points.
This is the most common situation we see, and it is rarely a software problem. It's usually that the program was launched as an event instead of run as a habit, which is the same mistake as the one big gesture, only stretched over time.
"For me, the launch wasn't the email we sent and the one meeting we had to kick it off. Spend the time figuring out the next three to six months.
Ask yourself when am I running contests? When am I coming back and reporting? When am I going to do a second push at another team meeting?
You are not going to have the adoption you want on day one. You're just not going to."
— Kwesi Thomas, Total Rewards Executive at Guusto
Sustainability has to be designed in from the start. The other quiet killer at this stage is under-powering the program, and Kwesi has a story that should make every HR leader wince.
"There was a really large company that completely under budgeted their program. They gave managers about $10 per store to recognize their employees.
$10 per store, once a month.
It was less effort for me to take $10 out of my pocket and hand it to them than to login and send it. Do I really want to take one employee a month and say here's $10, great job, after I've asked the whole team to kick butt for 30 days?"
— Kwesi Thomas, Total Rewards Executive at Guusto
When the math does not make sense to the person giving recognition, they opt out, and no feature set can rescue it. If your program has stalled, audit two things honestly: whether you funded it at a level that makes the effort worth it, and whether anyone owns adoption past launch day.
Gallup's finding that only 22% of employees feel adequately recognized often has less to do with frequency at the top and more to do with follow-through in the day to day (Gallup).
The conversations on our HR on the Frontline podcast go deep on exactly these tradeoffs, including the full episode with Joey Price referenced in this piece.
It’s candid, practical insights directly from and for the people who do this work for a living.
Listen to HR on the Frontline →
There is a moment in every growing company when recognition stops being something one thoughtful person can carry. Kwesi has watched admins who genuinely know their people, who remember that someone loves fishing and personalize the gift accordingly, hit the wall.
"That works at a certain scale and at a certain point you're going to hit a wall and realize that you can't keep up.
As we're growing, it doesn't sustain."
— Kwesi Thomas, Total Rewards Executive at Guusto
Scaling here means spreading recognition out so it no longer depends on a single heroic coordinator, which means putting the ability to recognize into the hands of managers and peers.
The data backs the instinct, because Gallup found that managers account for at least 70% of the variance in team engagement (Gallup, Managers Account for 70% of Variance in Employee Engagement). If recognition only ever flows from HR and the executive team, you are leaving the single biggest lever untouched. Decentralizing is also how you protect the rituals you already love.
Kwesi is emphatic that pizza parties, holiday events, and team outings should stay, with one upgrade: bring recognition from your everyday program into those moments and call people out by name, so the channels reinforce each other instead of competing.
"These things are not exclusive. If you're just trying to do one and not the other at a scalable rate, you're bound for failure."
— Kwesi Thomas, Total Rewards Executive at Guusto
This is where scalability is hardest and where the secret weapon matters most. Roughly 80% of the global workforce does not sit at a desk, around 2.7 billion people working in healthcare, manufacturing, retail, hospitality, and transportation (Emergence Capital, The State of Technology for Deskless Workers).
Most recognition software was built for the other 20% who are in front of a screen all day, and it shows the moment you try to stretch it across a hospital floor or a warehouse. A program that only scales for desk workers is, by definition, a one size fits all program wearing a different costume.
Two things tend to get missed. The first is that the person doing the recognizing on the frontline is frontline themselves.
"The leader in frontline that has to do the recognition is also a frontline employee themselves. They are also at the hospital floor or on the manufacturing floor.
You have to see that they need the ability to give the recognition in a way that's authentic to their workflow as well."
— Kwesi Thomas, Total Rewards Executive at Guusto
The second is the experience of receiving recognition, which is where Kwesi got honest about what most programs paper over.
"At the frontline, it's not aspirational.
I have to pay for gas on the way home. I have to go get dinner today.
It's a different world.
A senior financial analyst has a completely different lived experience than somebody working on a factory floor. We need to recognize and embrace the differences."
— Kwesi Thomas, Total Rewards Executive at Guusto
When recognition arrives in the wrong language, lands in an inbox the employee never checks, or comes as a reward they won't actually use, the moment dies on arrival, and that moment is the entire point of the program.
Scaling to the frontline means designing for how recognition is generated and how it is received: fast and authentic for a manager on their feet all day, and usable for the recipient in their language, on a channel they actually touch.
That question of which channel people actually touch is exactly where JD Dillon pushed our thinking when he recently joined HR on the Frontline. JD is a frontline learning and enablement expert and the author of The Frontline Enablement Playbook, and he has spent years studying how deskless teams really work.
His warning for anyone rolling out recognition is that the technology conversation almost always assumes a screen that a large share of the floor never sees.
As JD lays out, two people in the same grocery store can have completely different relationships with technology depending on what they do in it. A cashier stands at a point-of-sale screen all day, someone in the deli might share a tablet, and the person pulling carts from the parking lot may never see a screen during a shift.
Access points are everywhere once you look for them and a recognition strategy that ignores those realities will only reach the people it was built for.
The reason scalability is a secret weapon and not just an efficiency play is that it is what lets a program sustain, and sustaining is where the real return lives. Joey makes the business case in language a CFO will recognize, and his firm's research backs it: 55% of the HR leaders Jumpstart HR surveyed said improving financial and operational performance was their number one priority, and 61% were focused on managing costs and efficiency (source: Jumpstart HR research, shared on the HR on the Frontline podcast).
So watch the numbers that prove staying power. As recognition becomes consistent, look for movement in your employee net promoter score, because the through-line from "I like my boss" to "my boss finds things to like about me" is not a stretch.
In high-turnover environments like hospitality, retail, and frontline healthcare, track whether you are bending the turnover curve down, since that reduction shows up directly in lower hiring costs and a healthier promotion pipeline. In care settings, customer and patient sentiment can be a powerful proxy for whether recognition is actually reaching the people delivering the experience.
Those numbers carry weight because turnover is genuinely expensive. Gallup estimates that replacing a frontline worker costs around 40% of their salary, a technical employee around 80%, and a leader or manager around 200%, before you count the lost knowledge and the hit to morale (Gallup). A program that sustains for years compounds those savings, while a flashy program that dies in six months books the cost and never collects the return. Joey, drawing on Peter Drucker's old line that what gets measured gets managed, framed the technology's job as friction removal so the program keeps running regardless of who is in the seat.
The flashiest recognition programs aren't always still running in three years. The one that lasts is the one built to scale, which means it was designed around the real workday of the person giving recognition and the real life of the person receiving it, funded so the effort makes sense, stripped of friction that protects nothing, and run as a habit rather than launched as an event.
One size fits all feels like generosity and ambition, and they reliably collapse the moment you multiply them across a real, varied workforce.
Scalability is the unglamorous discipline underneath every recognition program that sustains. Or, in Kwesi's words, spend your time on how it's going to be used, how to design it to be used, how to strip out what you don't need, how to launch it, and how to drive adoption for the next three to six months. Get those five things right and the program grows with you instead of breaking under you.
Want help pressure-testing your own program before it hits the next stage of growth? Book a demo or start your free trial today.
— Skai Dalziel, Co-Founder & CEO @ Guusto