62
Open your company’s last advocacy report. Chances are it counts shares. How many employees clicked the button, how many times, how many impressions followed.
Now open LinkedIn and scroll. Which posts from colleagues do you actually remember? Probably not the reshared company announcement with no comment. Probably the one where a recruiter said, in her own words, why she spent a Saturday at a student hackathon.
That gap is the whole subject of this article.
The short answer: resharing company content is a form of amplification, and it has value, but it is not what most people mean by employee advocacy. Advocacy is an employee saying something, in their voice, that their network believes because they said it. A reshare carries the company’s words. A native post carries the person’s. LinkedIn practitioners also widely report that the feed gives bare reshares less reach than original posts, which makes the gap bigger than it looks.
Resharing means passing along something someone else wrote. Advocacy means putting your own name behind a view or an experience.
Both can help. If the company posts a role you know a friend would love, forwarding it is useful. But forwarding is a different act from advocating. Nobody reads a bare reshare and thinks, “Wow, she really loves working there.” They think, “The company posted something and she hit the button.”
Candidates make that distinction fast. They are not looking for the sixth copy of the same announcement. They are looking for a person to believe.
Probably, and it’s worth being precise about what we do and don’t know.
LinkedIn has not, to our knowledge, published a rule saying reshares are penalized. What exists is a steady stream of reports from social teams and consultants that a straight repost gets noticeably less distribution than a post written from scratch, and that a repost with real commentary does better than one without. Several of those write-ups sell tools, and the ones we reviewed don’t show their data. So treat this as a strong pattern, not a law.
The part that doesn’t depend on the algorithm is simpler. If forty employees reshare the same company post, their connections see the same post forty times, in forty feeds, with the same words. The first one lands. By the third, people scroll past. Feeds reward the unfamiliar, and a reshare is by definition familiar.
You don’t need to settle the algorithm debate to change your approach. You need to ask what you want a colleague’s network to see.
Ask for native posts, and make resharing the fallback.
The words are the company’s, and the effort for the employee is a single click. Their network sees a brand message with a colleague’s name attached. Reported reach on LinkedIn is lower, and the risk is repetition: the same post, in many feeds, until people scroll past. It’s best for open roles, urgent news and events.
The words are the employee’s, and it takes a few minutes. Their network sees a colleague’s real experience. Reported reach is higher, and the risk is that a post drifts off-brand or off-message. It’s best for stories, opinions and moments.
Notice the trade. Resharing is easy and low-risk, which is why programs default to it. Native posting is harder and riskier, which is why it works. The job of an advocacy program is to shrink the “harder and riskier” part until employees do it anyway.
Rarely because they don’t want to. Usually it’s one of four things.
They don’t know what to say. A blank box is intimidating, especially for someone who isn’t in marketing. They worry about saying the wrong thing, since nobody told them what’s okay. They don’t have a moment worth posting, or don’t realize they do. And they have no time, so anything above a one-click task loses to the actual job.
Notice that none of these is about motivation, and none gets fixed by a leaderboard alone, a reminder email, or a request from the CEO. They get fixed by giving people something to start from and clear permission to change it.
Think of it as handing over material, not scripts.
Give them moments, not messages. “Post about our Q4 launch” produces a reshare. “Tell your network about the project you’re proudest of this quarter” produces a post. Prompts that point to a person’s own experience get more distinctive results.
Offer a starting draft they’re encouraged to rewrite. A suggested caption is a fine place to begin as long as it’s clearly a draft. The strongest posts keep one line of the draft and replace the rest with something only that person would say. This is where AI caption help earns its place: it removes the blank page, and the employee supplies the detail. (We covered the line between AI help and human voice last week.)
Make the real stuff easy to capture. A short story told in the employee’s words, with no film crew or app to learn, is far more likely to get posted than a polished asset nobody feels ownership of.
Show them it worked. People repeat what they see being appreciated. Recognition, whether a shout-out or a leaderboard, works best when it celebrates the quality of a post, not only the volume.
Most policies are written to prevent harm and read like it. Employees open them once, learn what they can’t do, and conclude it’s safer to post nothing.
An advocate-friendly policy reverses the order. Lead with what employees are encouraged to do. Say plainly that they can talk about their own work and experience in their own words. Then cover the guardrails, which usually come down to a few things: don’t share confidential information, don’t speak for the company on legal, financial or crisis matters, be honest about your relationship with the company, and ask when unsure. Name one person or channel for questions, and make the answer fast.
Keep it to a page. If you want people to follow it, they have to be able to remember it. (Have your legal team review the final version. This is general guidance, not legal advice.)
Counting reshares tells you the button got clicked. It doesn’t tell you whether anyone cared.
Better questions: How many employees posted natively, not just shared? Which posts brought candidates to your jobs? Did the people who engaged look like the people you want to hire? Did awareness lead to visits, and visits to applications?
This is where the numbers can get big. A Cliquify customer with 51,000 employees, tracked three years of employee-shared stories: more than 9,500 stories shared, 348,000 organic visits to open jobs, over 15 million LinkedIn impressions, and an estimated $1.87 million in ad spend avoided. Employee recommendation also rose from 75% to 78%, the highest the company had recorded. Those results came from employees telling stories, at scale, over time. Not from a single clever campaign, and not from reshares alone.
Keep resharing. Use it for what it’s good at: open roles, event reminders, news people need to see. Then stop counting it as the whole program.
The programs that work treat advocacy as a content problem as much as a participation problem. They give employees a reason to post, a starting point, a clear boundary, and a reason to believe it mattered. At Cliquify, that’s how we think about employee advocacy: suggested content and CLEOai captions to get past the blank page, People Stories to capture real experiences without a production crew, and leaderboards to recognize the people doing it. The goal is a program people want to use, not another task on a list.
If you want a quick audit, pull your last month of advocacy activity and sort it into two piles: reshares and native posts. The ratio will tell you more than the impressions do.
Want to see what the blank-page fix looks like in practice? See CLEOai in action and book a Cliquify demo.We’ll show you how suggested captions, People Stories and leaderboards work together to get employees posting in their own words.
Read More
