LoginSchedule demoLoginSchedule demoStruggling programs publish more when they should publish less. A hard cap, named owners, and one test: would an employee share this without feeling like they're doing corporate PR?
Participation is down. Shares are flat. Somebody in the quarterly review says the feed feels thin, and the team leaves with an action item to publish more.
I have watched this happen a lot, and it is almost always the wrong move. When a program stalls, adding content usually makes it worse. Not neutral. Worse.
Here is the number that should end the argument.
A global enterprise program with tens of thousands of members published well north of ten thousand posts in a single year. That is a real content operation with real budget and real people behind it.
Of everything they published, nearly two thirds earned fewer than ten shares, and roughly one in five never earned a single one.
About one in five pieces of published content was never shared by a single employee. Not underperforming. Untouched.
This was not a bad content team. It was a governance vacuum. Anyone could submit, submitters approved their own work, and most submitters never went back to check how their posts performed. There was no cap and no owner, so the feed became the place where anything that needed to go somewhere went.
Every large program drifts toward that. It is the default state, not an accident.
An employee opens the feed. It takes about 27 seconds for them to decide what this thing is. Either they think “industry news, company news, professional development, this is everything I need in one place,” or they think “there is a lot of marketing content here and not much that is relevant to me.”
That verdict is sticky. Get it wrong and you do not get a second 27 seconds a month later, because they have already learned that scrolling your feed is not worth the time.
So a piece with zero shares is not a zero. It is a small withdrawal from the credibility of everything you publish next. Publish ten thousand of them and you have not built a content library, you have trained tens of thousands of members to ignore you.
This is why the “just publish more” instinct fails. The problem was never supply. It was that the supply had made the good stuff unfindable.
Dead RSS feeds are the purest version of this. A group wired to an industry feed that nobody curates will happily push 20 articles a week forever. It looks like an active program in a dashboard. What it actually does is teach employees that the feed is a firehose of things no colleague chose, which is the fastest way to make a platform feel like a chore.
The turnaround in that program did not come from better headlines or a new content agency brief. It came from three decisions that any program can copy, at any size.
One: a hard cap. A hard monthly cap per category that cut publishing volume to a fraction of what it had been. Not a target, a maximum. Output fell sharply, and performance went up, not down.
The cap is the part people resist and the part that does the work. Most programs set a content minimum and stop there. A minimum keeps the feed alive. Only a maximum forces someone to choose, and choosing is the entire job.
Two: named owners with real editorial calendars. Every category gets one accountable human who owns the topic, owns the calendar, decides what makes the cap, and sees the performance data for their own category every month. “Anyone can submit” is not a content strategy, it is an inbox.
If nobody owns a group, the group should not exist. That single test will retire a third of the groups in most mature programs.
Three: one content test, applied to everything. Would an employee share this on their personal LinkedIn without feeling like they are doing corporate PR?
That question is doing more work than it looks like. It moves the decision from “is this on-message” to “does this cost the sharer something.” Because it does cost them something. They are spending their own professional credibility with their own network, and they will not spend it twice on something that made them look like a billboard.
Most advocacy content strategy is designed backwards, for the marketing calendar. Campaigns land, so content lands. The launch is in March, so March is heavy. The feed becomes a downstream artifact of somebody else’s plan.
The end user of that feed is not the marketing team. It is an employee deciding whether to spend social capital.
Design for them and the mix looks different. What holds up across programs is roughly:
That last number is the one that gets argued about. Ten percent feels low if you built the feed as a distribution channel. It feels obvious the moment you accept that a feed which is half promotional is not a feed anybody returns to.
A related pattern. In large programs, the categories that absorb the most publishing effort are routinely not the categories that produce the most sharing, and nobody notices because the reporting is measuring output. If your program has never compared what you publish most against what actually gets shared, that gap is probably sitting in your data right now.
Everything above was already true. AI made it urgent.
Producing content is now effectively free. Any team can generate a month of posts in an afternoon, and the constraint that used to enforce discipline, which was simply that writing things is hard, is gone.
So the bottleneck moved. It is no longer creation. It is attention, and attention did not get cheaper. Your employees still have the same 27 seconds and the same finite willingness to put their name on something.
Which means the scarce asset in 2026 is not content. It is the judgment to not publish. Editorial discipline used to be a nice-to-have that budget constraints handled for you. Now it is the only thing standing between your program and a feed nobody opens.
You do not need to redesign anything this week. Three moves, in order.
Then leave it alone long enough to learn something. The best programs I work with review their group structure quarterly and are ruthless about it, retiring what nobody shares and splitting what has outgrown its category.
Your launch setup was never supposed to be the final answer. But it also was not supposed to become a landfill.
Curious what your own bottom of the list looks like? Per-piece share counts sorted ascending is the fastest diagnostic in this post, and most programs have never run it. Book a demo and we will pull it with you.
See the platform that comms, marketing, and compliance teams use to run their advocacy program.
