What are examples of advocacy activities?

Common ones include resharing company announcements, writing first-person posts about projects and lessons, commenting in industry conversations, referring candidates, and speaking at events or on webinars. At the executive level, the highest-value activity is original posts: a leader explaining a decision, a tradeoff, or a point of view that only someone in their seat could write.

What are the disadvantages of advocacy programs?

Forced reshares read as corporate and get skipped. Participation decays once the novelty wears off, tone mistakes happen in public, and attribution is fuzzy because the results show up as inbound conversations rather than tracked clicks. Staff-wide rollouts also produce sameness: fifty people posting identical copy helps no one. Executive-first programs trade those problems for concentration risk, since a few voices carry most of the output.

What are the four main types of advocacy?

The classic framework lists self-advocacy, individual advocacy, peer advocacy, and systems advocacy. Employee advocacy in the marketing sense is closest to peer advocacy: people speaking up for an organization they belong to, to an audience that trusts them more than it trusts the organization itself.

When should a company expand from founder posts to executive advocacy?

When the founder's account is producing steady engagement and inbound conversations, and when specific leaders have distinct topics to own. Add one or two executives at a time, each with their own voice work and their own lane, and give each new account 6 to 8 weeks to ramp up before judging it.

Executive Advocacy: When the Leadership Team Posts Too

Q: What is employee advocacy?

Employee advocacy is employees sharing or creating content about their company on their own social accounts, usually LinkedIn. A formal employee advocacy program organizes that with curated content, posting guidelines, and often software that makes resharing easy. The executive version narrows it to a few leaders writing original posts in their own voice.

An employee advocacy program is a structured way to get your team sharing and creating content about your company on their own social accounts, usually LinkedIn. Companies build them because people follow people, and a company page reaches a fraction of what the personal accounts around it can reach.

I run content at Megaphone, where I review and write founder content every working day, and I've built my own accounts to 93k followers on X and 26k on LinkedIn. So I'm biased toward the people side of this. That bias comes with a position most advocacy guides skip: the staff-wide software rollout is the wrong first move for most B2B companies. Reputation starts with the founder, because that's where the reach is, and grows into the company from there. Co-founders and executives come second, the company page comes third. This article covers the standard program model, the data behind it, and the executive-first version I'd run instead.

What an employee advocacy program is

The standard program looks like this: marketing curates a library of approved content, employees get a tool with a share button and suggested copy, and a dashboard tracks who shared what. Some programs add leaderboards or small incentives. The pitch is reach: your company page has a ceiling, your employees collectively don't.

Which is fine as far as it goes. The failure mode shows up in the feed. Fifty people reshare the same product announcement with "Excited to share" on top, their networks scroll past, and six weeks later participation has dropped to the same three people. The program didn't fail because employees don't matter. It failed because resharing corporate copy was never the valuable part.

The benefits, measured

The underlying math holds up, and it comes from LinkedIn's own data. Their talent blog reports that a company's employees collectively have networks about 10x larger than the company's follower base, that people are 3x more likely to trust company information from an employee than from the CEO, and that employee reshares see roughly 2.1x the click-through rate of the original company post.

The stat I'd pay most attention to is quieter: only about 2% of employees share company content, yet that small group drives about 20% of the company's total social engagement. Concentration is already how this works. A handful of voices carry the result whether you plan for it or not. A program, done well, is how you choose who those voices are and give them something worth posting.

Benefits follow from there: a wider hiring funnel, warmer sales conversations, and a bench of credible names attached to the brand instead of one logo doing all the talking.

Where programs go wrong

The disadvantages are predictable. Reshared corporate copy reads as corporate, so networks learn to skip it. Participation decays after the launch push. Attribution is messy, because the best outcomes arrive as inbound conversations and warm replies rather than tracked clicks, and a dashboard built on clicks will undercount what's working. And a staff-wide rollout multiplies sameness: the same announcement in fifty feeds is one impression repeated, not fifty impressions earned.

The executive-first version trades those for a different risk: concentration. Two or three voices carry the output, so a leader leaving takes an audience with them. I'd still take that trade, since an audience attached to a person at least exists. The staff-wide alternative usually builds nothing durable at all.

Why the founder goes first

Reach on X and LinkedIn concentrates in people with a clear lane. From what I see in my own analytics and across our client base, the algo favors accounts that talk about one specific thing well, consistently, over months. My account is the example I know best: I've posted about marketing for years, and the algorithm now knows me as a marketer. When I post about the NBA or my family instead, impressions drop and the next few posts are dampened. Maybe I'm just uninteresting on those topics, but the pattern has held long enough that I plan around it.

A company page is the opposite of a clear lane. It posts product news, hiring, culture, and events to an audience that followed it out of politeness. The founder's account is where a focused point of view and existing relationships already overlap, which makes it the cheapest place to start compounding.

I saw the people-first version of this early. I was the first CMO at Copy.ai, and we grew from $0 to $2.5M ARR in under a year. At Megaphone the team's combined accounts hold over 200,000 social followers, built name by name rather than through any company page. The order matters: get the founder's account working, then expand.

Executive advocacy is the second stage, done on purpose

Executive advocacy means a small number of leaders, usually two or three to start, each writing real posts in their own voice about the part of the business they own. The CTO writes about build decisions. The head of sales writes about what decision makers are asking this quarter. Nobody reshares a press release.

This differs from a staff-wide rollout in three ways:

It's opt-in and selective. You pick leaders who face customers, candidates, or investors, and who have something to say. Twenty reluctant participants produce less than two committed ones.
The voice is extracted, not assigned. Before anyone drafts, you pull each leader's real stories and opinions out through interviews and voice notes. At Megaphone every voice gets its own audience map and voice guide, because the CTO writing in the founder's voice reads as fake to everyone who knows either of them.
Each leader gets a lane. Topics are divided so the executives extend the founder's coverage instead of echoing it.

The company page comes last, once there are personal accounts worth pointing it at.

A good primer on the standard model

If you're new to the category, Sprout Social has a short explainer called "What is Employee Advocacy & How Can it Boost Your Social Strategy?" that lays out the conventional program model clearly: the content library, the sharing workflow, the measurement. Watch it for the baseline, then weigh that model against the executive-first sequence in this article. The mechanics they describe work best after a few leadership accounts are already earning attention on their own.

How to launch the executive-first version

Here's the game plan I'd run:

Get the founder's account working first. Posting is binary: off while you build the system, on at the full schedule when it's ready. A soft launch teaches the algorithm nothing and teaches the founder to quit.
Pick two or three leaders. Selection beats scale. Choose the ones with distinct expertise and real exposure to the people who decide your company's future.
Do the voice work before the content work. Interviews, voice notes, old emails, recorded customer calls. Generic content comes from zero inputs, so the fix is inputs.
Assign lanes. Each leader owns a content pillar the founder doesn't cover. Overlap wastes the second voice.
Set a weekly publishing plan sized to each person's calendar, and hold it. A sustainable rhythm beats an ambitious one that dies in month two.
Expect a ramp up. I always anticipate 6 to 8 weeks on a new or dormant account before we see much movement. Judge the program at week twelve, not week three.
Review monthly, and weight the right signals. My rough model, and it is rough: a like is worth maybe 0.5, while a share, a comment, or a resulting follow runs 4x or 5x that. Optimize for posts people send to a colleague.

When you're ready, and when you're not

You're not ready if the founder's account is still flat, if no one owns the program as a weekly operating job, or if your leaders expect software to write for them. You're ready when founder posts generate steady engagement and inbound conversations, when executives start asking to post rather than being asked, and when candidates mention specific posts in interviews.

One question worth asking before you expand: which leader could publish something this week that the founder couldn't? If the answer is obvious, that's your first executive. If nobody comes to mind, keep building the founder layer.

If you want a read on where your feed sits before adding more voices, take the feed diagnostic quiz. It takes a few minutes and tells you what to fix first.

Employee advocacy earns its reputation when it stops meaning everyone resharing everything and starts meaning the right few people saying something worth reading. Build it in that order and the company page, the software, and the wider team all have something real to stand behind.