The short version
To build an employee advocacy program, pick one owner, recruit five to ten volunteers who already post now and then, and give them raw material worth talking about every week or two — the result, the decision, the story — rather than finished posts. Let each person write their own version on their own LinkedIn profile. Run that pilot for about ten weeks, measure how many different people are still posting in month three, and only then decide whether to expand.
That is the whole method. The rest of this page is the detail: a week-by-week 90-day plan, the roles, how to choose the pilot group, what the material should look like, a program plan template you can copy, and the signals that tell you it is time to grow. If you are earlier than that and still deciding whether to do this at all, start with what employee advocacy is and why it works.
Why most employee advocacy programs stall
Almost every failed program follows the same arc. There is a launch: an all-hands mention, a channel, a tool, a burst of posts in week one. Then participation halves, then halves again, and by week six the same three enthusiasts are carrying it. Somebody reports the launch-week impressions, nobody reports the decay, and the program is quietly retired at the next budget review.
The cause is rarely effort. It is design. Programs that stall tend to share three choices: they launch to everyone at once, they hand out finished copy to be reposted word for word, and they measure total volume instead of how many people keep participating. Each choice makes the launch look better and the program worse. We go through the failure modes in more detail in why employee advocacy programs fail; the plan below is built to avoid all three.
Roles: who does what
An employee advocate program needs fewer people than you would think, but every role has to be named. Unnamed responsibilities are the ones that slip in week four.
| Role | Who | What they do | Time |
|---|---|---|---|
| Program owner | One person in marketing, comms or employer branding | Collects material, runs the cadence, answers questions, reports the numbers monthly | Two to four hours a week |
| Team leads | A manager or senior person in each participating team | Spots material in their team, posts themselves, nudges without pressuring | An hour a fortnight |
| Participants | The volunteers | Write and publish their own version of the material, when it is relevant to them | Fifteen to thirty minutes per post |
| Reviewer | Someone from comms, legal or compliance, as needed | Checks posts that touch numbers, customers or regulated topics before they go out | On request |
Two notes. First, the program owner does not have to be senior, but they need access: to the product roadmap, to customer wins, to hiring plans. A program owner who hears about the launch on the same day as everyone else cannot prepare material for it. Second, the reviewer is optional for most posts. If every post needs sign-off, people stop writing. Decide in advance which topics need a second pair of eyes — usually anything with financial figures, a named customer, or a regulated claim — and leave the rest alone.
Selecting the pilot group
The pilot group decides whether the program survives, so it is worth choosing deliberately rather than sending an open invitation to the whole company.
Who to invite
- People who already post. Search LinkedIn for colleagues who have written anything about their work in the last six months. They have already decided it is worth their credibility.
- A mix of functions. One salesperson, one engineer, one recruiter, someone in customer success, a team lead. Different roles reach different networks and have different stories.
- At least one senior person. A founder, director or head of department who posts signals that it is allowed. They do not need to post often; they need to post.
- Five to ten people. Fewer than five and one holiday breaks the pilot. More than ten and the owner spends the pilot chasing instead of learning.
Who not to start with
People who are told to take part by their manager, people whose profiles are empty and who have never wanted to post, and anyone whose role makes posting risky before you have guidelines in place. None of these are permanent exclusions. They are people you invite once the pilot has produced examples they can learn from.
How to ask
Ask individually, not with a company-wide announcement. Explain what you are asking for (one post every week or two, in their own words, when the material is relevant to them), what you are not asking for (resharing finished copy, posting on a quota), and that they can stop at any time. Voluntary means voluntary: advocacy tied to performance reviews stops being advocacy.
The 90-day employee advocacy program plan
Ninety days is long enough to see whether people keep posting after the novelty wears off and short enough that you get a decision before the next planning cycle. The weeks below are a starting point, not a contract; move them if your launch calendar demands it.
| Weeks | Phase | What happens | Done when |
|---|---|---|---|
| 0–2 | Setup | Name the owner and reviewer. Write one-page guidelines. Choose and personally invite the pilot group. Collect the first four to six pieces of material. Agree on the three numbers you will report. | Guidelines approved, five to ten people said yes, first month of material ready |
| 3–6 | Pilot | One ask a week or every two weeks. Each participant writes their own version. The owner checks in individually after each round: what was easy, what was awkward, what got a reaction. Swap material that nobody wanted to post for material people asked for. | Every participant has posted at least once; you know which material types work |
| 7–12 | Expand or decide | Keep the cadence. Measure breadth and retention. If the pilot is healthy, invite a second group, ideally recruited by the first one. If it is not, fix the cause before adding anyone. Write a one-page review for leadership at week twelve. | A written expand, adjust or stop decision with the numbers behind it |
Weeks 0–2: setup
Most of the setup work is unglamorous. Write the guidelines first — one page, plain language, covering what people may share, how to disclose that they work for the company, what stays confidential and who to ask when unsure. Our employee advocacy guidelines template is a starting point you can copy. Then build the first month of material, so the pilot does not stall in week four while the owner scrambles for something to share.
Weeks 3–6: pilot
The pilot is where you learn, so the owner's main job is listening. After each round, ask two or three participants what they thought. You will hear things a dashboard cannot tell you: the material was too salesy, the deadline was too tight, they did not know whether they were allowed to mention the customer. Fix those things fast. A pilot that adapts in week four is far more likely to be alive in week twelve.
Weeks 7–12: expand or decide
By week seven you have real numbers. The decision is not whether the program "worked" in the abstract; it is whether enough of the pilot group is still posting without being chased. The expansion criteria below make that concrete.
The material: raw ingredients, not finished posts
This is the single most important design decision in building employee advocacy, and the one most programs get wrong. If you hand people a finished post to reshare, you get the same sentence on twelve profiles on the same afternoon. Readers notice, discount it, and the people who posted have spent their credibility for nothing.
Instead, give people the ingredients and let them cook. A good piece of material contains:
- The fact. What happened — the launch, the result, the hire, the decision.
- The specifics. The number, the customer quote you have permission to use, the thing that went wrong first.
- The why. Why it matters, and to whom.
- A link, if there is one. The blog post, the job ad, the case study.
- A few angles. Suggestions for how different roles might talk about it: the engineer's angle, the salesperson's, the recruiter's.
- What not to say. Anything confidential or not yet public.
A draft post can be included as a starting point, as long as everyone understands it is meant to be rewritten. The getting-started post explains the reasoning in more detail: how to start employee advocacy without annoying your team. For what the finished posts end up looking like, see twenty employee advocacy examples.
Where material comes from
The owner cannot invent material; they have to find it. Reliable sources: product releases and the reasoning behind them, customer results with permission to name the customer, open roles and the teams hiring for them, events and talks, internal retrospectives that can be made public, and opinions from leaders on things happening in your industry. A standing fifteen-minute slot with each team lead every fortnight will surface more than a request form ever will.
Cadence: how often to ask
One good ask every week or two. Not daily. A daily stream of material trains people to ignore it, and it pushes them toward resharing without thinking, which is the behaviour you are trying to avoid. Each participant should feel free to skip anything that is not relevant to them; across a month, most people posting two or three times is a healthy rhythm.
Plan the material a month ahead so the cadence does not depend on the owner having a good week. A simple calendar that lists what is coming, which teams it is for and when it should go out does the job. We cover the mechanics in building an employee advocacy content calendar, and how often individuals should post on LinkedIn in general in our LinkedIn posting frequency guide.
Launching without a launch
Resist the big launch. An all-hands announcement creates expectations the pilot cannot meet yet, and it pulls in people who join because they were told to. The better launch is quiet: the pilot group posts for a few weeks, the posts are good, colleagues notice, and some of them ask how to take part. That is your second cohort, and they arrive already wanting to do it.
What you do need in the first week is a short kickoff with the pilot group: half an hour, covering the guidelines, how material will reach them, how to write their own version, and who to ask when they are unsure. Show two or three good examples from other companies or from people already posting internally. Then let them start.
Employee advocacy program plan template
Copy this into a document and fill it in before week zero. If you cannot answer a line, that is the thing to fix before the pilot starts.
Employee advocacy program plan — [company], [quarter]
- Goal. The one outcome this program is for in the next 90 days (for example: more qualified applicants for engineering roles, or more first conversations in one market).
- Program owner. Name, and hours a week committed.
- Reviewer. Name, and the topics that need review before posting.
- Pilot group. Five to ten names, their roles, and why each was chosen.
- Guidelines. Link to the one-page policy; date approved.
- Material sources. Which teams and meetings the owner will draw material from.
- Cadence. How often material goes out, on which day, and how far ahead it is planned.
- Channel. Where material reaches participants (a tool, a shared document, a channel).
- Metrics. The three numbers reported monthly: active advocates, breadth, one outcome metric.
- Check-ins. When the owner talks to participants individually.
- Expansion criteria. What has to be true at week twelve to invite a second group.
- Stop criteria. What would make you pause or redesign the program.
Employee advocacy best practices
The practices below are the ones that consistently separate programs that last from launch-week spikes. None of them is novel. All of them are routinely skipped.
- Keep it voluntary. Mandatory participation produces low-effort posts and quiet resentment.
- Let people write their own words. Every post should sound like the person who published it.
- Lead from the top, lightly. A leader who posts occasionally, in their own voice, does more than any memo. See executive advocacy on LinkedIn.
- Make it easy to say no. Material is an offer, not an assignment. People who skip a round should feel no pressure.
- Share what came back. Tell participants when a post led to an applicant, a customer conversation or an invitation. Outcomes motivate more than impressions.
- Measure breadth and retention before volume. How many different people posted, and how many are still posting in month three. More in employee advocacy metrics.
- Publish guidelines before you need them. People hold back when they are unsure what is allowed. A clear page removes that hesitation.
- Protect the material pipeline. A program with nothing to share dies faster than one with no tool.
- Pick one network first. For most B2B companies, LinkedIn. Spreading across every network dilutes the effort.
- Review the program, not just the posts. Once a quarter, ask what is working and what people want more of.
For how well-known companies applied these practices at scale, see successful employee advocacy programs.
When to expand the program
Expand when the pilot is healthy, not when the calendar says so. These are thresholds we suggest, not industry benchmarks; adjust them to your size, but write yours down before the pilot starts so you are not tempted to move them later.
- Retention. Most of the pilot group (say, two-thirds or more) posted at least once in weeks 9–12 without being individually chased.
- Breadth. Posts came from most of the people invited, not from one or two enthusiasts carrying the numbers.
- Material. The owner has a reliable pipeline and is not inventing things to share.
- Demand. Colleagues outside the pilot have asked to join.
- At least one outcome. An applicant, a conversation, a customer who mentioned a post — something beyond reach.
If retention is low, do not expand. Find out why: usually the material was not interesting, the asks were too frequent, or people were unsure what they were allowed to say. Fix that with the existing group, then reassess. Adding people to a program that is losing its pilot only makes the decline larger.
When you do expand, grow by teams rather than by announcement. Invite the next function or office, recruit through the people already posting, and give each new group its own material where it makes sense. Sales and recruiting rarely want the same things to talk about.
Running the program in software
A pilot can run on a shared document and a calendar reminder. Software becomes worth it when you have more than one team, need to know who actually posted, and want results per person rather than by anecdote.
In Blabigo, the program maps onto a few objects. Your pilot group becomes an advocacy team. Each round of material becomes a campaign, holding posts that act as raw material, assigned to one or more teams; members find it under My campaigns, edit the copy in their own voice and publish from their own LinkedIn account. Posts that touch sensitive topics can be sent to a reviewer — a colleague or an external reviewer by email — whose approval is advisory and does not block publishing. Shares, impressions, clicks and engagement roll up per campaign, per team and per person, which is exactly the breadth and retention view the expansion criteria above need. Blabigo is LinkedIn only. If you are comparing tools, our comparison of employee advocacy software covers the alternatives honestly, and you can run a pilot campaign in the free trial before deciding.