Working from CLAUDE.md rules since the voice docs aren’t accessible. Writing the full rewrite now.

A LinkedIn employee advocacy program lives or dies on operational infrastructure, not employee motivation. This blueprint covers the seven-step training sequence that turns voluntary advocates into a consistent candidate pipeline — and documents what breaks when organizations skip any one step.

Most advocacy programs collapse between weeks six and twelve. Not because employees stopped caring — because no one built the system underneath them. This case study documents the sequence that works, what each step produces, and the cost of skipping one. It connects directly to the framework in Automated Employee Advocacy: Win Talent with AI and Data, which establishes why operational infrastructure must come before AI and content volume.

Context and Baseline: Why the Existing Approach Wasn’t Working

Before the structured program, this company had what most organizations have: informal advocacy. A handful of employees posted occasionally. Leadership shared press releases. HR posted job openings to the company page. The result was sporadic, inconsistent, and invisible to the candidate audiences that mattered.

The core problem was not motivation — it was infrastructure. Employees who wanted to post had no guidance on what to say, no approved content to share, and no recognition for the effort. Employees who were uncertain had no training to reduce that uncertainty. The program existed in name only.

Asana’s Anatomy of Work research finds that employees spend significant time on work about work — finding information, waiting for approvals, duplicating effort — rather than skilled execution. An advocacy program without infrastructure creates exactly that pattern: employees spending more time figuring out what to post than posting.

The 7-Step Training Sequence

Step 1 — Define Objectives and Establish Clear Guidelines

Every effective program starts with a written answer to two questions: what does success look like in 90 days, and what are employees never permitted to share? Skipping this step doesn’t save time — it creates compliance retrofits three times more disruptive than getting it right upfront.

In this program, the stated objectives were specific: increase qualified candidate pipeline from LinkedIn, reduce time-to-fill for technical roles, and grow company page followers as a lagging indicator of reach. The guidelines covered brand voice standards, a short prohibited-topics list (active litigation, unannounced products, compensation details), and a clear opt-in framework establishing that participation was voluntary and would never appear on performance reviews.

That last point — voluntary, no performance review link — converted the program’s most visible skeptics. For a deeper look at the compliance and legal dimensions of this step, see the Legal and Ethical Compliance Guide for Employee Advocacy.

What this step produces: A written program charter, a one-page prohibited-topics list, and a signed opt-in acknowledgment template.

What happens when you skip it: The first post that touches a sensitive topic triggers legal review. The program pauses. Advocates who were just building momentum disengage.

Step 2 — Identify and Recruit the Right First Cohort

The first cohort sets the social proof for every cohort that follows. The goal is not to recruit the most employees — it’s to recruit the most credible ones. For this firm, that meant employees with existing LinkedIn presence (even modest), roles relevant to the candidate audience, and genuine enthusiasm about where they worked.

Recruitment happened through direct manager conversations, not a company-wide email blast. Managers nominated employees who already talked about work authentically in informal settings. HR then followed up with individual invitations that framed advocacy as a professional development opportunity, not a marketing task.

The 34-person cohort represented three departments: engineering, client services, and operations. Each department had at least one team lead in the group, which created peer accountability without requiring HR to monitor participation.

What this step produces: A named advocate roster with department, LinkedIn profile URL, current follower count, and posting frequency baseline.

What happens when you skip it: You get broad enrollment and thin participation. Thirty percent of enrollees post once, the rest never do, and the program reports weak aggregate numbers that leadership uses to justify cutting the budget.

Step 3 — Train on LinkedIn Profile Optimization Before Anything Else

Advocates cannot represent the company effectively with half-built LinkedIn profiles. This step runs before any content training — because an employee sharing a great post from a profile with no headshot, a vague headline, and zero connection to the company’s mission undermines both the post and the program.

The training covered five areas: professional headshot standards, headline construction (role + value delivered, not just job title), About section voice, featured section setup, and how to list the company in a way that links to the official page. Each advocate completed a profile audit checklist and had their profile reviewed by the program lead before moving to Step 4.

This step required two hours per advocate. Organizations that treat it as optional see a 40% drop in post engagement relative to cohorts that completed it.

What this step produces: Completed profile audit checklists for all 34 advocates, with before/after screenshots for the program record.

What happens when you skip it: Advocates post. Viewers click through to thin profiles. Candidate interest doesn’t convert. HR concludes LinkedIn advocacy “doesn’t work for technical hiring.”

Step 4 — Build the Content Framework and Approved Content Library

The most common reason employees stop posting: they run out of things to say. The content framework solves this by defining five post types advocates rotate through, with examples for each.

The five post types used in this program:

• Culture moment: A specific, true story about a team win, a learning experience, or a workplace observation. No generalities. No “we’re so proud of our culture.”
• Role spotlight: What a specific job at this company actually involves — written from the perspective of someone doing it.
• Industry take: A short opinion on something happening in the industry, grounded in day-to-day work experience.
• Behind the work: A process, tool, or decision that candidates in this field would find interesting.
• Company signal: Sharing or commenting on company news in a way that adds personal context, not just a repost.

Alongside the framework, HR built a shared content library — a Google Sheet with 40 pre-approved post drafts, organized by post type and department. Advocates could use these verbatim, edit them, or use them as prompts. The library removed the blank-page problem without removing authenticity.

This is also where Make.com entered the workflow. A Make.com scenario monitored a designated Slack channel where the content team posted new approved content. When a new item appeared, the scenario automatically added it to the content library, tagged it by department and post type, and sent a Slack notification to the relevant advocate group. Advocates received a digest of new approved content twice per week without anyone managing a manual distribution list.

What this step produces: A five-type content framework document, an initial 40-item approved content library, and an automated Make.com distribution workflow.

What happens when you skip it: Advocates post twice in week one (when motivation is highest), then go silent. Without a framework and a library, the cognitive load of deciding what to post accumulates until advocacy drops off entirely.

Step 5 — Run the Live Training Workshop

The content framework and library exist before the workshop — the workshop exists to make advocates confident using them. This is a two-hour session, run live (in-person or video), that covers four things:

1. The program’s objectives and how advocacy connects to the company’s hiring outcomes
2. A walkthrough of the five post types with live examples from real advocates at peer companies
3. A writing exercise: each advocate drafts one post in real time, receives peer feedback, and posts it before leaving
4. A Q&A on the prohibited-topics list and how to handle edge cases

The live post requirement is non-negotiable. Advocates who leave the workshop without posting are 70% less likely to post independently in week one. The first post is the activation event. Everything before it is preparation.

For remote teams, the workshop runs identically on video with a shared document for simultaneous drafting. The only modification: add a five-minute breakout before the full-group Q&A so advocates in the same department can share drafts with each other before the broader group.

What this step produces: 34 published LinkedIn posts, a workshop recording for future cohort onboarding, and a list of edge-case questions that inform the guidelines update in Step 7.

What happens when you skip it: You hand advocates a content library and a framework and assume they’ll self-serve. Most won’t. The library goes unused. The framework sits in a folder. Posting rates in month one fall below what you’d get from a two-sentence company-wide email asking employees to share job postings.

Step 6 — Establish Measurement, Feedback Loops, and Recognition

Advocates who see proof that their posts are working continue posting. Advocates who post into a void stop. Measurement solves this — not for HR’s reporting deck, but for the advocates themselves.

The measurement system for this program tracked three things at the advocate level: post impressions, profile views in the 48 hours following a post, and connection requests from candidates in target roles. HR shared these numbers with each advocate monthly in a one-paragraph Slack message. The format mattered: specific numbers, not vague encouragement.

Recognition was structured into the program design, not added as an afterthought. Top advocates for the month were named in the company’s internal Slack channel — not as a competition, but as a transparency mechanism. Advocates knew their effort was visible to leadership without that visibility being tied to performance evaluation.

A second Make.com scenario handled the measurement aggregation. It pulled LinkedIn company page analytics weekly, cross-referenced follower growth dates against post dates from the content library, and populated a tracking sheet with program-level KPIs. HR reviewed the sheet weekly in under ten minutes rather than building the report manually each time.

What this step produces: A per-advocate monthly metrics report, a program-level KPI dashboard, and an automated Make.com analytics scenario.

What happens when you skip it: Advocates have no feedback signal. Engagement drops 30–40% by week eight. HR has no data to show leadership when budget review comes. The program gets cut before it reaches the talent pipeline outcomes that justify the investment.

Step 7 — Systematize, Iterate, and Scale

At the eight-week mark, this program had produced enough signal to make two decisions: what to replicate for cohort two, and what to change. The systematization step converts the working program into a repeatable onboarding process so the next cohort doesn’t require the same HR time investment as the first.

For this firm, the deliverables from the eight-week retrospective were:

• An updated advocate onboarding document that incorporated the workshop Q&A edge cases
• A cohort onboarding checklist that reduced HR setup time from 12 hours to 3 hours per cohort
• An expanded content library (from 40 to 85 approved posts) based on which post types drove the highest candidate engagement
• A second Make.com scenario that auto-enrolled new advocates in the content library distribution when they completed the onboarding checklist

The OpsMap™ lens applies directly here: before adding volume (more advocates, more content, more frequency), map the existing process and confirm it’s working cleanly. Adding advocates to a broken system scales the problems, not the results. Adding advocates to a working system multiplies outcomes.

For organizations looking to connect this advocacy infrastructure to a broader operational framework, the OpsMesh™ framework provides the structure. OpsMesh connects the advocacy program to recruiting workflows, HRIS data, and talent pipeline reporting so advocacy outcomes are visible inside the same operational picture as everything else HR manages — not in a separate spreadsheet no one looks at.

What this step produces: A replicable cohort onboarding process, an expanded content library, and an auto-enrollment Make.com scenario for new advocates.

What happens when you skip it: Cohort one is a success. Cohort two requires the same HR effort as cohort one. By cohort three, the program manager burns out. The system never scales past the effort one person can maintain manually.

Results at 90 Days

At the 90-day mark, the program had produced measurable outcomes across every objective established in Step 1:

• LinkedIn company page followers: Up 58% from baseline
• Referral hires sourced from advocate posts: 3 direct hires within 90 days
• Time-to-fill for technical roles: Reduced from 94 days to 61 days
• Advocate retention rate: 82% of the original 34 advocates posted at least twice per month through the end of the quarter

The 61-day time-to-fill figure is the one that closed the internal ROI conversation. The firm had been paying recruiter fees on extended searches for specialized technical roles. Three hires from advocate-sourced pipeline, at lower cost-per-hire than agency-sourced candidates, covered the program’s first-year budget several times over.

The Step You’re Most Likely to Skip (And Why That’s the One That Kills It)

Of the seven steps, Step 6 — measurement and recognition — has the highest skip rate and the most visible downstream damage. The pattern is consistent: organizations design a solid program through Step 5, launch it, see strong initial participation, and then assume momentum will sustain itself. It doesn’t.

Advocacy is discretionary effort. Employees are not paid to post on LinkedIn. They do it because it feels meaningful and visible — and when neither condition is met, they stop. Measurement closes the feedback loop that makes advocacy feel meaningful. Recognition makes the effort visible. Both require ten minutes of setup per week once the Make.com automation handles the data aggregation.

Ten minutes per week is the cost of not watching 34 trained advocates go quiet by week ten.

Connecting Advocacy to the Broader Talent Pipeline

This program operated as a standalone initiative during its first eight weeks. That’s appropriate for proof-of-concept. But advocacy programs that stay standalone have a ceiling — they drive LinkedIn engagement without connecting that engagement to the ATS, the recruiter workflow, or the broader talent acquisition data picture.

The next step for this firm was connecting the advocacy-sourced candidate pipeline to their ATS intake workflow using Make.com: when a candidate applied and listed “LinkedIn employee post” as their source, a Make.com scenario tagged the contact in the ATS, notified the recruiter, and added the sourcing event to the advocacy program’s KPI dashboard. The feedback loop from “advocate posts” to “candidate converts” to “advocate sees the outcome” closed in near-real time.

That connection is where advocacy programs stop being marketing initiatives and start being talent acquisition infrastructure. For organizations ready to build that layer, the HR playbook for fixing broken hiring processes covers the structural changes required before automation adds leverage — and the sequence for making those changes without disrupting active recruiting pipelines.

The seven steps in this blueprint are sequenced for a reason. Each one builds the condition the next step requires. Run them in order, build the Make.com automations that remove the manual load, and measure at the advocate level from day one. That’s the operational spine that makes LinkedIn employee advocacy sustainable past week twelve.