Programme Reviews
Part of Employee advocacy
Measuring advocacy without ranking staff by follower counts
Review employee advocacy through useful audience responses and editorial learning while respecting private member analytics and separate Page results.
Measure employee advocacy against the reader question each contribution was meant to answer. Keep company Page figures separate from personal post figures. Ask before using an employee's private analytics, and review what the programme helped explain. Follower totals do not show whether an individual contribution was useful.
Pros and Cons of Using Follower Counts to Measure Advocacy
- ProsSimple to measure; visible indicator of reach
- ConsDoes not reflect relevance, accuracy or impact of message; can lead to ranking bias and reduced morale
Set the review question first
Record the intended reader, the subject and the response that would help you assess it. When a willing engineer explains a maintenance decision, a relevant follow-up question may be more informative than general reactions. If an employee helps share a confirmed service update, check whether responses reveal confusion about who is affected or where to ask for details.
These purposes need separate editorial judgements. Before comparing contributions, record the topic, publishing identity, date, observation period and any paid distribution.
Use platform numbers within their limits
LinkedIn provides post analytics for your content. If an employee chooses to share analytics, do not require account access or screenshots.
LinkedIn provides content analytics for a Page. Page and member figures describe different publishing identities, so adding their impressions does not produce a verified count of distinct people reached.
LinkedIn's My Company and Employee Advocacy tabs are no longer available.
Platform Analytics: Company Page vs. Individual Post Metrics
- Source of DataLinkedIn Page analytics
- What It MeasuresImpressions and engagement for company content
- LimitationDoes not include personal network reach; separate from individual post metrics
- Source of DataIndividual employee post analytics
- What It MeasuresReach and engagement of personal posts shared by employees
- LimitationPrivate data; requires consent before review; not representative of audience reach beyond personal networks
Keep a programme record that respects people
A simple review sheet can record the reader question, contribution, company fact used, useful follow-up and correction needed. Let the author decide whether to add available personal analytics. One thoughtful comment is one response, not evidence of a market-wide view.
| What to review | Useful observation | Limit |
|---|---|---|
| Information quality | Were company claims current and qualified? | An accurate post may receive little visible response. |
| Audience response | Did a relevant reader ask a specific question? | Replies come only from people who chose to respond. |
| Editorial learning | What explanation or fact card needs revision? | Later activity alone cannot show that a revision caused a change. |
| Employee experience | Did contributors find the request workable? | Ask them; posting frequency cannot answer this. |
Decide what to change
Look across contributions serving a similar question before drawing a pattern. If readers ask for a missing condition, improve the fact card.
If attention is broad but relevant questions are scarce, consider a more specific subject. If the process takes employees' time without giving them a contribution they value, reduce the request or use the Page.
Report only what the evidence shows, such as specific questions that led to a clearer explanation. Claims about sales impact, comprehension or unique reach need separate evidence. The review should guide what the programme does next without turning individual networks into a ranking.
