LoginSchedule demoLoginSchedule demoThe real failure mode is a good launch followed by a silent quarter, and the early-warning signals show up four to eight weeks before anyone names the problem.
Launch days are almost always good.
The executive posts. The announcement lands in Slack. Activation climbs faster than anyone expected, somebody screenshots the leaderboard, and the program owner sends a note to their VP that afternoon saying this is going better than we planned.
I have been in a lot of those weeks, and I have learned not to read much into them. A good launch tells you the announcement worked. It tells you nothing about whether the program will exist in six months.
What kills employee advocacy is not a bad launch. It is a good launch followed by a silent quarter. Nobody makes a decision to stop. There is no meeting where the program is canceled. It simply gets quieter, and then it is month three, and someone asks why the numbers look flat, and the honest answer is that they have looked flat for a while and nobody was looking.
The decline is not invisible. It is legible in the data four to eight weeks before anyone says the word “problem” out loud.
The numbers below are invented, but the shape is exactly what this looks like in practice.
A 400-seat program launches. In month one, 280 people activate and 150 of them share at least once. Month two: 138 people share. Month three: 119. Nobody raises a flag, because the number everyone reports on is activation, and activation is still sitting at 70 percent, which looks perfectly healthy on a slide.
Meanwhile the number that was actually moving is shares per active user, and it went 2.4, then 1.9, then 1.5. The roster held steady while the behavior underneath it drained out. By the time the sponsor notices the program has “gone quiet,” it went quiet two months ago.
Activation is a launch metric. It is the wrong thing to be watching in month three, and it is the number most likely to be reassuring you while the program dies.
Five indicators, all of them visible to a program owner without any special reporting.
Activation stalls below target past day 90. Not slow, stalled. A curve that is still climbing at day 90 is fine. A curve that flattened at day 45 and has not moved since is telling you the people who were going to opt in have opted in, and the rest need a different reason.
Share rate per active user falls for two consecutive review cycles. This is the one I would keep if I could only keep one. People still logging in but sharing less means the platform is fine and the content is not. They looked, and there was nothing worth putting their name on.
The same few names dominate the leaderboard every period. Concentration reads as success right up until it doesn’t. If your top five advocates are producing most of your reach, you do not have a program, you have five enthusiastic people, and your program’s survival is now tied to whether any of them change jobs.
Admin and sponsor attention drifts. The softest signal and the most predictive one. When the executive who launched the thing stops posting, employees read it correctly and immediately. When the program owner stops being the person who brings it up, it stops being a program and becomes a tool nobody was assigned.
Inbound questions go quiet. Nobody asking how to connect their account, nobody asking whether they can share a competitor’s article, nobody complaining about the notification volume. Silence is not stability. It means people have stopped thinking about it.
Any one of these has an innocent explanation. A quiet month happens. A sponsor gets busy. So here is the rule I use:
When two signals trip, act. Do not wait for a third.
Two at once is not a coincidence, it is a trend with a few weeks of head start on you. And the practical reason to move early has nothing to do with elegance: a re-engagement push at 20 percent decline is a completely different job than one at 80 percent. At 20 percent you are reminding people of a habit they still half have. At 80 percent you are relaunching, and you are relaunching with less credibility than you had the first time.
Almost every program plans one calendar and needs two.
The first calendar is campaigns. A launch. A hiring push. A conference. An earnings announcement. A product release. These are easy to plan because they announce themselves. They arrive with a date, an owner, a budget, and usually a leaderboard. Everybody is good at this calendar.
The second calendar is the baseline. Weekly content in every group. Exactly one post flagged as high priority, because two dilutes the signal and five means nothing is important. A monthly pull of everyone who activated and has never shared, followed by a personal message rather than a bulk email. A quarterly health review with somebody who controls budget.
The Greeks had two words for time. Kronos for the clock that just keeps running, kairos for the moment worth acting on. Every program plans its kairos moments and almost none of them plan their kronos.
The baseline calendar has no urgency built into it. Nothing on it is due. Nobody gets thanked for it. Every item can be skipped this week without any visible consequence this week. And it is the only thing keeping a program alive between the moments that everybody does plan.
Here is the tell. If a program looks alive during campaigns and dead in between, that is not a campaign problem. The campaigns are working. There is simply nothing underneath them.
Every program has a plan for day one. Launch checklists are the most reliably completed document in this entire category of work. Executive post, announcement email, Slack message, monitor for login issues.
Almost nobody has a plan for day three.
Day three is when announcement energy is spent. The people who were going to log in on impulse already have. The rest of your company has moved on to whatever they were doing before your email arrived. And nothing about day three feels urgent, which is exactly why it gets skipped.
The seven days after launch are where the habit forms or doesn’t, and they are the only seven days your program will ever have this much organizational attention available to spend. Most programs spend them congratulating themselves.
What that week should contain is not complicated. Somebody decided in advance that non-activators get a nudge midweek, that content gets refreshed before it goes stale rather than after, that the first handful of people who shared get named publicly, that the sponsor sees real numbers by Friday. The specific list matters less than the fact that it was written down before launch day, when there was still time to think, instead of improvised on a Wednesday when everyone is tired.
The discipline scales. The first week’s rhythm becomes the monthly rhythm becomes the quarterly review. Programs that survive year one are the ones where that rhythm became automatic before anyone had to be reminded of it.
When two signals trip, the instinct is to plan a relaunch. Resist it. A relaunch tells everyone the first one failed, and it spends credibility you will want later.
Fix the supply first. Nothing new to share is the single most common cause of a quiet program, and it is also the cheapest thing on this list to fix. Then go directly at the people who activated and never shared, individually, because a personal message from a human converts at a rate no automated nudge will match. Then get the sponsor visible again, in whatever forum your company actually watches.
None of that is clever. It is just the baseline calendar, run deliberately, a quarter later than it should have started.
The programs still running in year three are not the ones that launched best. They are the ones that were boring on purpose.
Not sure which quarter you are in? The signals are already sitting in your own data, and catching them at 20 percent is a very different job than catching them at 80. Book a demo and we will show you where they surface.
See the platform that comms, marketing, and compliance teams use to run their advocacy program.
