Which KPIs to Follow on Yammer, and Which Ones to Retire in Viva Engage

By Nicolas Saliba · 8 min read

The KPI list on most Viva Engage reporting slides was written for Yammer, and it shows. Number of communities. Number of members. Posts, replies, reactions. Monthly active users. That was a reasonable list in 2018, when the honest question was whether anyone would use the enterprise social network at all. It is a poor list in 2026, when the question from the CCO is whether the network reaches the parts of the organisation that need reaching. Every metric on the inherited list answers the first question. None of them answer the second.

Yammer no longer exists as a product. Microsoft completed the transition to Viva Engage and retired the Yammer branding and the standalone experience^[1]. What did not get retired was the measurement habit that grew around it. This is about which of those indicators to drop, which genuinely still earn their place, and what to put in the gap.

What the Yammer-era KPI lists were actually measuring

Start by being fair about how the list came to exist. It was not laziness. The Yammer analytics surface exposed activity counts, so activity counts were what teams reported, because activity counts were what existed. Every KPI list is shaped by what the tooling happens to expose, and Yammer exposed volume.

The problem is that volume and reach move together early on and then decouple. In the first eighteen months of a network, rising post volume genuinely does mean more people are joining in. After that, volume can rise while distinct participants fall, because a small group of enthusiasts gets more prolific. A community with 1,400 members and 90 monthly posters reads identically whether those 90 sit in one head-office marketing team or spread across 22 countries. One of those networks connects the organisation. The other is a very active club.

Activity was a proxy for adoption, and adoption was the 2018 question

In 2018 most internal communication teams were still arguing for permission to run a social network at all, and activity was the right evidence in that argument: it showed the thing was not dead. That argument was won years ago. The question has moved on and the KPI list has not moved with it.

The indicators worth retiring

Four of them, and the reason each one misleads rather than simply being uninformative.

Total member count. Membership in Viva Engage is close to free to acquire. Communities get auto-joined during onboarding, added through Microsoft 365 group membership, or joined once and forgotten. A rising member count usually reflects headcount growth or a governance decision, not communication performance. It is the number most likely to be quoted in a board pack and least likely to mean anything.

Total posts, replies and reactions. A supply metric dressed as a demand metric. Post volume mostly tells you how busy the communications team and the community managers were, which is worth watching operationally and nothing more. Our note on why optimising internal communication usually means publishing less covers what happens when a team optimises for it.

Tenant-level monthly active users. The Microsoft 365 admin centre publishes a Viva Engage activity report with active user counts across the tenant^[2]. It is a legitimate operational number for an IT owner tracking licence usage. As a communication KPI it aggregates away exactly the variance you need: a stable tenant-wide figure can hide a collapse in one country and a surge in another.

Top-poster leaderboards. These were popular in Yammer-era reporting and they actively distort behaviour. A leaderboard rewards frequency, and frequency in an internal social network is not obviously a good thing. If you keep one, keep it as a community-management working tool, not as an executive KPI.

What a Viva Engage KPI has to prove

A useful test: can a senior stakeholder ask one follow-up question that the KPI cannot survive? “How many members” dies to “how many of them are in operations”. “How many posts” dies to “did the safety message reach the plants”. A KPI that survives the follow-up question has three properties. It has a denominator that is a defined population rather than the whole tenant. It is attached to a segment you can name. And it can be compared with the same measure a year earlier.

Retired indicator	Why it misleads	What to measure instead
Community members	Membership is acquired passively through group provisioning and onboarding.	Participation rate against a defined population: viewers or contributors as a share of the headcount the community is meant to serve.
Total posts and replies	Measures production by the team, not consumption by the audience.	Distinct participants per period, and the ratio of contributors to viewers.
Tenant-wide monthly active users	Averages over countries, functions and contract types, hiding the variance.	Active share by function, site, country and language, tracked as a spread rather than a mean.
Top posters	Rewards frequency and concentrates the network around a small group.	Breadth of contribution: how many distinct people posted or replied at least once.
Reactions per post	Sensitive to community size and to how the post was seeded.	Answer rate and time to first substantive reply on question-type posts.

That last row is the one teams overlook. In a large organisation, a meaningful share of enterprise social network value comes from questions getting answered by someone the asker has never met. A quality engineer at a plant in Lyon posts a process question, a quality engineer in Ohio answers it within the day, and the organisation solved a problem once instead of forty times. Time to first substantive reply is measurable, it is defensible, and it is about outcomes rather than volume.

The honest position on Viva Engage native insights

Viva Engage community insights are free, already switched on, and genuinely sufficient if you own one community and want to know how your own posts are landing inside it. A community manager running a single community does not need anything else, and buying a measurement layer for that job would be an overreaction. If you are setting up that view, the sibling piece on what a Viva Engage community dashboard should contain lays out a tile-by-tile layout, and how to read the native insights panel covers where each number comes from.

The limits show up when the question turns organisational. Native insights do not join to workforce attributes, so function, grade, site, country and contract type are not available as filters without exporting and joining the data yourself. The retained reporting window is finite, which makes any multi-year narrative awkward, and a Yammer-to-Viva Engage comparison particularly so. And Viva Engage data sits apart from your SharePoint intranet numbers and your newsletter numbers, so unique cross-channel reach stays out of reach. The limits of Viva Engage native analytics are set out in detail separately.

Many teams try to close the gap with a Power BI build against the Microsoft Graph reporting API. That can work, and some organisations run it well, but it is more demanding than the first sprint suggests. The reporting API is not consistently reliable and produces days with missing data^[3]. Customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period, which is a bad conversation to have in front of an executive audience. A dependable build needs a robust ingestion process, scheduled reconciliation against the native figures and a named owner. Budget for the pipeline, not the dashboard.

A KPI set that holds up in a budget review

Five indicators, and each one has a denominator.

Participation rate by population. Not “1,400 members” but “38 per cent of the commercial function, 4 per cent of manufacturing”. The second version tells you where to act next quarter.
Reach of the specific message against its intended segment. A safety update written for plant operators is measured against plant operators, never against the tenant.
Breadth of contribution. Distinct people who posted or replied at least once in the period, expressed as a share of the population, so it cannot be inflated by five enthusiasts.
Answer rate and time to first substantive reply. The clearest available evidence that the network is doing work rather than existing.
Unique cross-channel reach. Some of your audience will never open Viva Engage. They get the message from the SharePoint intranet, a manager cascade or a printed board. Counting the social channel alone systematically undercounts the hardest people to reach, a point developed in measuring cross-channel internal communications.

Gallagher’s State of the Sector research has repeatedly found measurement to be the capability internal communicators name first when asked where they are weakest^[4]. The cause is structural rather than personal: native tooling reports activity inside a product, not participation across a workforce. Gallup’s workplace research points the same way, consistently finding engagement lowest in frontline and deskless populations^[5], exactly the populations an aggregate count hides.

This is the layer Tryane occupies. It reads Viva Engage alongside SharePoint, Teams and your newsletter platform, joins that activity to your organisational structure through Entra ID or an HR file, and keeps history across product transitions so the Yammer years and the Viva Engage years read as one trend. Practical detail: SOC 2 Type 2 certified, GDPR compliant by design, EU hosting by default with US data residency on request, deploys in a couple of hours over single sign-on, no agent to install. Structure the attributes first: audience segmentation for internal communications covers how.

Frequently asked questions

Are Yammer KPIs still relevant now that the product is Viva Engage?

The channel carried over, so continuity of measurement is worth protecting. The specific indicators mostly did not deserve to carry over. Keep anything with a defined denominator, such as participation as a share of a named population. Retire raw counts of members, posts and reactions from executive reporting, and keep them only as operational working numbers.

What is the single best Viva Engage KPI if I can only report one?

Participation rate against the population the community was created to serve. It has a denominator, it segments, it is comparable year on year, and it survives the obvious follow-up. Everything else is a supporting number.

Can native Viva Engage insights show frontline participation?

Not directly. Community insights report activity within a community and do not join to workforce attributes such as site, function or contract type. Answering a frontline question means combining Viva Engage activity with your organisational structure, either by exporting and joining the data yourself or by using a dedicated layer that performs the join.

How far back can we compare, given the Yammer transition?

Native reporting retains a finite window, so comparisons starting before the migration are usually not available from native tooling. If your narrative needs to begin in the Yammer years, that history had to be held independently. It is the gap teams discover the first time an executive asks for a five-year view.

Does Tryane replace Viva Engage analytics?

No. Viva Engage continues to record what it records. Tryane sits above it, reading Viva Engage alongside SharePoint, Teams and newsletters and joining all of it to your organisational structure, so you can answer segmented and cross-channel questions that no single native panel can. You keep the Microsoft 365 investment and add the measurement layer for what native does not do. The comparison with Viva Engage native analytics sets out where each fits.