Why Frontline Rewards Programs Die In The First Ninety Days

A rewards program either takes hold in the first month or it does not take hold at all. There is no slow burn. If the activation curve is flat at week four, it will still be flat at month twelve, and the renewal conversation will be about why nobody used it.

Here is what actually goes wrong.

1. It Was Built Around An Email Address Most Staff Do Not Have

This is the single biggest cause and it happens before launch day. The platform is provisioned against the HRIS, the HRIS holds work email addresses, and in a retail or hospitality workforce a large share of those fields are blank, shared, or point at a store-level inbox that four people log into.

Invitations go out. Somewhere between a third and half of them land nowhere. Nobody notices for a fortnight because the dashboard reports invitations sent, not invitations received.

The fix is unglamorous: invite by mobile number, and treat any staff record without a reachable contact method as a rollout task rather than a data-quality footnote.

2. The App Was Empty On Day One

Someone logs in for the first time, sees a balance of zero points and a catalogue they cannot afford anything in, and closes it. They will not open it again on the strength of a reminder email.

Whatever else the program does, there has to be something of value available before a single point has been earned. Everyday discounts do this job — groceries, fuel, phone plans — because they cost the employer nothing and they work on the first visit.

The first login is the only one you are guaranteed. Everything after it has to be earned by what happened during it.

3. Managers Were Never Given A Reason To Use It

Peer recognition is the engine of most programs, but it does not start itself. In every rollout that worked, a small group of managers sent the first hundred recognitions in the first fortnight, and everyone else copied them.

In every rollout that did not, managers were told about the platform in a launch email and then left alone with it. Recognition volume in week one is the leading indicator, and it is visible on day three — long before activation numbers tell you anything.

4. Nobody Owned It After Launch

Programs are usually implemented by whoever ran the procurement, and that person moves on to the next project the week after go-live. Three months later the budget has not been topped up, two sites have never been onboarded, and the leavers file has not been synced since launch.

Ownership does not have to be a full role. It has to be a named person with an hour a month and access to the reporting.

What Actually Predicts Success

Across the rollouts we have run, the programs that were still healthy at twelve months shared four things, and none of them cost money:

• Staff could sign in without a work email address.
• Something was redeemable before any points were earned.
• Managers were briefed separately from staff, with a target for week one.
• One named person looked at the numbers monthly.

The catalogue mattered too, but it mattered fourth. A merely adequate catalogue with those four things in place beats an excellent catalogue without them, every time.

What To Do In Week Two If It Is Going Badly

Do not send a reminder email. It will not work and it burns the one channel you have left. Instead:

1. Pull the undelivered invitation list and fix the contact data by hand. It is usually under an hour of work and it is the highest-return hour of the rollout.
2. Ask three managers to send ten recognitions each this week. Not a policy, a favour.
3. Turn on everyday discounts if they are not already on, and say so in one sentence on the roster board rather than in an email.

If activation is still under a third at week four after all of that, the problem is not the program. It is worth finding out what it actually is before spending another quarter's budget on points.