Launch a LinkedIn employee advocacy pilot

Turn an idea into a four-week test: choose a business question, prepare verifiable topics, agree on participation rules, and make a decision about what comes next. Adapt the kit to your team; no one is required to publish.

See the four-week plan Open the contributor brief

A team sharing ideas around a table during a working meeting.

A four-week pilot

Move through the steps in order, but fit the pace to your team. The pilot should not become an individual posting quota. A week spent listening and adjusting still counts, even if nobody publishes.

Week 1: frame the test
Pick one question buyers or candidates actually ask. Define who should find the answer useful, name an owner and a backup, and invite volunteers from the relevant roles. List the facts, figures, and customer details that need a check before publication.
Check before moving on: Can you explain in one sentence what the team wants to learn and for whom?
At the end of the week: A one-page plan covering the goal, volunteers, responsibilities, and publication boundaries.
Week 2: prepare verifiable topics
Collect questions you have actually heard, current product facts, approved examples, and experiences volunteers can discuss. For each idea, record a source, the person who can verify it, and anything that remains uncertain. Offer angles, never a required script.
Check before moving on: Can another person verify each important claim from the source you listed?
At the end of the week: Three short briefs with a possible personal angle, supporting evidence, and a fact-check owner.
Week 3: try the workflow
Share the prompts and let each volunteer adapt them, decline, or start from a personal idea. Make it easy to request a fact check without requiring approval for every opinion. Note where people hesitate, lose time, or need more source material.
Check before moving on: Do contributors control their own wording and know whom to ask for a factual review?
At the end of the week: A review of the useful steps, blockers, and drafts that volunteers chose not to publish.
Week 4: review and decide
Review the same signals across the full period and ask volunteers what they would keep or change. Do not let one widely viewed post define the pilot. Choose one testable improvement and decide whether to continue, adjust, or pause.
Check before moving on: Does the decision account for participant feedback, available evidence, and the time required?
At the end of the week: A documented decision, an owner, and the next question to test.

Frame the pilot before inviting the team

Complete this one-page outline with the program owner and interested volunteers. It keeps the business objective, the topics people want to discuss, and the signals worth tracking distinct.

Keep the scope proportionate: no individual posting quotas, private-message collection, or business claim without an explicit source and method.

Question the pilot should answer: [one business question]
Audience to help: [people who should find the posts useful]
Volunteer group: [roles involved and how to take part]
Owner and backup: [who coordinates and answers questions]
Period and available time: [dates, realistic rhythm, no publishing obligation]
Three possible topics: [questions, not scripts]
Sources and reviewers: [current source + person who can verify facts]
Information to exclude: [customer data, figures, or claims not approved for sharing]
Participation rules: [adapt, pass, leave, request a fact check]
Signals to collect: [participation, voluntary feedback, reported conversations, method]
Decision at the end: [continue, adjust, or pause based on what?]

Four rules that protect trust

Employee advocacy is professional participation, not a relay for slogans. Put these rules in writing before you invite the team.

Participation is voluntary

People can join, pass, or leave the pilot without explaining why. Do not set individual quotas or compare employees with one another.

The author owns the voice

A contributor can rewrite the idea, add their point of view, or publish nothing. A brief provides context; it does not dictate a post.

Claims need a source

Name the source and the person responsible for checking figures, customer references, and product claims. Remove anything the team cannot confirm.

Accounts stay personal

Never ask for a password or post from an employee’s profile on their behalf. Keep signal collection limited, explained, and voluntary.

Ask the appropriate internal owners to review privacy, image rights, disclosure, and working-time rules. This template does not replace your HR or legal policies.

Three starting briefs by role

These are working prompts, not customer stories or Orsana results. Replace each one with a question people actually hear, the contributor’s experience, and a source they are allowed to use.

Marketing: make a claim verifiable

Question to address: What should a team understand before evaluating an employee advocacy program?
Possible angle: Clarify one selection criterion, such as voluntary participation, author control, or source quality, then explain how the team applies it.
Check before publishing: A current public document or an approved internal rule. A campaign objective is not an observed result.

Sales: start from a recurring objection

Question to address: Which criteria should a buyer compare before choosing employee advocacy software?
Possible angle: Explain one criterion and its trade-off from questions heard in the role, without turning the post into a product pitch.
Check before publishing: Document how the criterion is defined and remove details that could identify a prospect or customer.

Customer success: explain an adoption step

Question to address: What makes a brief genuinely useful to a contributor?
Possible angle: Describe the context someone needs to choose an angle, request a fact check, or pass on a topic.
Check before publishing: Use a method or experience the author can explain. Anonymize customer examples and check permission.

A brief to complete for each topic

Copy the outline for one idea. If you cannot name the source or the author’s real experience, keep the idea in draft.

Audience question: [specific situation]
Why it matters: [what the reader needs to decide or understand]
Contributor angle: [real experience or point of view]
Main idea: [answer in one sentence]
Verifiable source: [link or approved public document]
Fact to review: [claim, figure, or customer example, if needed]
Limit: [what we do not know or cannot claim]
Open question: [invite a response without forcing a sales meeting]

To make the prompt concrete, start from a real situation: “We hesitated between [option A] and [option B] because [constraint]. This is the criterion that shaped our decision: [verifiable detail].” Replace every bracket with a real, publishable fact; otherwise, do not present it as lived experience.

An invitation to adapt and send internally

Add the program owner, dates, and realistic time commitment before sending. Explain how to decline or leave the pilot.

Hi [name],

We are running a four-week test to help volunteers share their expertise on LinkedIn in their own words. The goal is to answer useful questions for [audience], not to repost corporate copy or hit a posting quota.

You can adapt every prompt, suggest your own topic, pass, or leave at any time. We will share available sources and name someone you can ask to check factual claims. Plan for about [realistic time] per week; we will adjust the process based on your feedback.

If you would like to take part, reply to [owner] by [date] with a question you would be comfortable discussing. There is no obligation to publish.

Check facts without writing posts for people

Decide in advance which claims need review and who checks them. Otherwise, review can slow every topic down or turn contributors into spokespeople reading from a script.

01The contributor chooses the idea, angle, and wording they want to use.
02The reviewer checks only the sensitive claims, figures, product details, and customer information identified in the brief.
03The author decides whether to publish, edit, or withdraw the draft after feedback. A review is not an obligation to publish.

Have the appropriate HR, legal, and security owners adapt privacy, disclosure, image-rights, and working-time guidance. This template does not replace internal policies.

A weekly scorecard

Track how the program works and whether useful signals appear, not individual employee performance. Keep definitions and time windows consistent.

Signal	What to record	What it does not tell you
Voluntary participation	Count people who chose to contribute against the invited volunteer group.	Do not compare employees or use the whole company as the denominator.
Participant feedback	Each week, note what felt clear, difficult, useful, or too time-consuming.	A small number of responses calls for a conversation, not a ranking.
Topic workflow	Count prompts prepared, sourced, adapted, reviewed where needed, and published.	An unpublished draft can reveal a topic to improve; it is not an individual failure.
Useful conversations	Record relevant replies and inquiries that volunteers choose to report.	A view or reaction does not prove purchase intent or an opportunity.
Business outcome	Connect an opportunity to the program only with a CRM source, time window, and stated method.	Separate direct attribution, self-reported influence, and coincidence.

Use analytics available in native tools or signals volunteers choose to share. Do not ask for passwords or try to collect private messages.

At the end of week four, choose what happens next

A sound decision may be to continue small, change one step, or stop. Base it on volunteer feedback, source quality, and signals you actually observed.

Continue

Volunteers want to carry on, topics have verifiable sources, and the time commitment is workable. Keep the scope small before expanding.

Adjust

There is interest, but a specific step blocks progress: missing sources, slow review, or topics that sound too corporate. Change that step and test it in the next cycle.

Pause

People do not want to continue, evidence cannot be shared, or the effort does not fit the available time. Stop and document what would need to change before restarting.

References used to shape this kit

LinkedIn: measuring an employee advocacy program
LinkedIn Business guide published in 2016. It separates content engagement, employee activation, and business outcomes. This kit uses those measurement categories, not the guide’s promotional figures or any claim that they are current benchmarks.
LinkedIn: setting program goals
LinkedIn Business guide published in 2016. It recommends starting with program goals and the people involved. Product-specific details may have changed; consult current platform resources for current rules.
LinkedIn: authentic content and conversations
LinkedIn’s March 2026 publication describes artificial commenting and coordinated sharing as inauthentic engagement signals. This kit therefore recommends sincere feedback, never organized reaction exchanges.
LinkedIn Professional Community Policies
The policies require accurate, authentic content and prohibit using another person’s account. Contributors keep control of their profiles and their decision to publish.
CNIL: monitoring employees’ work activity
CNIL says monitoring must be justified, proportionate, and brought to employees’ attention. Ask the appropriate internal owners to review any measurement or data collection for the pilot.

See how Orsana works with your team

Choose a time to explore how your team's LinkedIn presence can create useful conversations and business opportunities.

Your current LinkedIn approach
Ideas your team can make their own
A practical next step

Book a demo

The Motion booking form is displayed in English.

FAQ

How many employees should join the first pilot?

Choose a small group of willing contributors from the roles relevant to one clear audience question. The right size is the group your coordinator can support and learn from, not a fixed percentage of the company.

Do participants have to publish during the four weeks?

No. The four-week structure is a learning cycle, not a posting quota. Participants can adapt an idea, pass on a topic or leave the pilot; the team can still learn where its process needs work.

What should the team measure during the pilot?

Track voluntary participation, participant feedback, how topics move from source to draft, and relevant conversations people choose to report. Treat views as distribution data, not proof of intent or revenue.