How to Start a Voluntary Employee Advocacy Programme

Employee advocacy works as a programme only if employees want to take part and the work serves a business purpose. Start with those two conditions before buying a platform or setting posting targets.

A useful first objective is narrow: help prospective customers understand how your team solves one problem. “Increase everyone's visibility” is too broad to tell you what support to provide or whether it helped.

Write the invitation before the content plan

Here is an example invitation for a fictional software consultancy:

We're testing a four-week writing group about project handovers. Participation is optional, and declining will not affect performance reviews. You can contribute an idea without posting from your account. We'll provide editing time during work hours. You approve anything published under your name and can leave the group at any point.

This makes the exchange concrete. The company gets access to expertise; participants get time and editorial help. A manager should not quietly turn the invitation into a quota.

Give the pilot one reader and one question

For the consultancy, the reader could be an operations manager taking over a software project. Their question: “What should I ask the outgoing team before they leave?”

Build the first topic list around that question:

• A developer explains which setup instructions a new teammate needs.
• A project manager describes how to record unresolved decisions.
• A support specialist explains where recurring customer issues should live.

These are possible contributions, not assignments based on job title. Ask each person which subject they can support from experience and are comfortable discussing publicly.

Run a four-week pilot with an actual decision point

Four weeks is a suggested learning window, not enough to promise revenue attribution. If there are few responses, examine whether the topics reached the intended audience before declaring the programme a failure.

Make review predictable

Agree which subjects need specialist review before drafting. Customer information, product claims and sensitive announcements need an appropriate owner. The compliance guide explains how to define those boundaries; the requirements depend on your organisation and context.

Keep factual corrections separate from style preferences. “This feature isn't available yet” is a necessary correction. “Our brand usually says delighted” is a suggestion the author can decline.

Decide whether the effort earned another cycle

Record editorial time, voluntary participation, relevant conversations and any attributable next steps. Ask contributors privately whether the support was useful and whether they felt pressured.

A pilot with modest reach but useful conversations may deserve another cycle. A high-impression programme that employees dislike needs redesign. Use the ROI worksheet to connect costs to outcomes without pretending every impression is a lead.

The next cycle should answer a specific unresolved question: a different reader problem, a lighter editing process, or a better route from a post to useful material. Expansion is a decision, not the default reward for finishing four weeks.