A common inheritance in a large organisation: a list of 40-odd communities created between 2017 and 2021, most of them still technically alive inside Viva Engage, roughly six of them with any activity in the past quarter. Somebody has to decide which ones the internal communication team will actively support, which get archived, and what to tell the sponsor of each. Doing that well requires an honest view of which Yammer-era use cases genuinely transferred to Viva Engage, and which were quietly absorbed by Microsoft Teams while everyone was busy with the migration.
The test that separates a live use case from a dead one
There is a single question that sorts the list, and it is not about activity levels. Ask whether the exchange the community exists for can happen inside a bounded, permissioned group of people who already know each other. If it can, Teams does it better and has already taken it. If it cannot, because the value depends on someone you have never met and whose existence you were not aware of, then the enterprise social network is the only place it can happen and the use case is alive.
That is the whole distinction. Viva Engage is an open network product[1]. Its value comes from unbounded reach across the organisation. Teams is a bounded collaboration product, and its value comes from the boundary: a defined membership, a persistent channel, presence, files in one place. Where Yammer was used as a bounded space, it was being used against its grain, and Teams displaced it as soon as Teams was good enough. That happened around 2019 in most organisations, which is why the “which use cases work” question kept getting confusing answers afterwards.
What genuinely survived
Cross-site expertise exchange
The strongest surviving use case, and the one most often undersold to executives. A quality engineer at a plant in Lyon posts a question about a bonding failure. A quality engineer in Ohio has seen it, and answers within the day. Neither knew the other existed. In a 12,000-person manufacturer with 40 sites, this is the difference between solving a problem once and solving it forty times, and no bounded Teams channel can produce it because the person with the answer was never going to be in the channel.
Leadership presence that accepts a reply
A leadership post that permits public replies reads differently from an email that does not, and the difference is legible to the workforce. This survived because there is no other surface in Microsoft 365 where a country director can be visibly answerable to everyone at once. Whether leaders use it well varies enormously, but the affordance is genuinely unique and it is worth defending.
Communities of practice that outlive their sponsor
A project Team is dissolved when the project ends. A community of practice around, say, industrial safety or data governance keeps accumulating people and answers across reorganisations, and becomes a searchable record of how the organisation has solved things. This asset compounds and is almost always undervalued because nobody has ever put a number on it.
Frontline voice travelling upward
Feedback from people who are not on the org chart of anyone deciding anything. This survived, but conditionally: it only works if the frontline is actually present in the network, which in most organisations it is not. Our piece on engaging frontline workers on Viva Engage covers what has to be true for this to function.
What quietly died
Four use cases that appeared in every Yammer best-practice deck between 2016 and 2021 no longer belong in Viva Engage, and keeping them there costs you credibility.
Project coordination. Gone to Teams entirely. A project needs a bounded membership, threaded discussion tied to files, and meeting integration. Yammer never did these well and Viva Engage does not either. If you still have project groups in Engage, they are almost certainly dormant.
Team-level chatter and social groups. Also gone to Teams channels, and to a lesser extent to Teams chat. The social group that once ran the cycling club now runs in a Teams channel because that is where the people already are all day.
Document collaboration. Never really worked in Yammer, and correctly now lives in SharePoint document libraries and Teams. If you are trying to measure “collaboration” through Engage activity, you are measuring the wrong surface. This confusion sits alongside the broader problem covered in our piece on OneDrive, SharePoint and what the confusion does to your numbers.
The all-company culture group that was really a broadcast channel. This one is worth being direct about. A great many organisations ran an “All Company” Yammer group that was, functionally, a newsletter with a comments box that nobody was allowed to use critically. It survived into Viva Engage on paper, and it is usually the community with the highest membership and the lowest genuine engagement, which is why it flatters the monthly slide. If your largest community is your least conversational, it is a broadcast surface and should be reported as one, not counted as network health.
| Yammer-era use case | Status now | Where it actually lives | What to measure |
|---|---|---|---|
| Cross-site expertise exchange | Alive and the strongest case | Viva Engage communities | Answer rate, time to first answer, cross-boundary ratio |
| Leadership visibility with reply | Alive, unique to Engage | Viva Engage, leadership corner | Reply rate by leader, reach by population |
| Community of practice | Alive, compounds over years | Viva Engage communities | Returning contributors, question resolution |
| Frontline feedback upward | Alive but conditional | Viva Engage, mobile | Frontline participation rate, not headcount |
| Project coordination | Dead | Microsoft Teams | Do not report it as social network health |
| Team chatter and social clubs | Dead | Teams channels and chat | Nothing, archive the community |
| Document collaboration | Dead | SharePoint and Teams | Measure on SharePoint instead |
| All-company broadcast group | Alive but misclassified | Viva Engage, announcements | Report as broadcast reach, not engagement |
Measuring the survivors properly
The surviving use cases share a property: none of them is well described by post volume or membership count. All four are about whether a connection was made between people who would not otherwise have met, and that requires different measures.
- Answer rate. The share of questions that receive at least one substantive reply. A network where two thirds of questions go unanswered is not a network, and no membership figure will reveal that.
- Time to first answer. The measure that tells you whether the community is useful in the moment somebody needs it. A median of four hours is a working network. A median of six days is an archive.
- Cross-boundary ratio. The proportion of replies that come from a different site, function or country to the person who asked. This is the number that proves the lateral value, and it is the one executives find most persuasive, because it is the thing the org chart cannot do.
- Returning contributors. People who posted in more than one of the last three months. A community carried by four people is fragile regardless of its member count.
- Participation rate by population. Not “1,400 members” but “38 per cent of the commercial function and 4 per cent of manufacturing”. Gallup’s long-running workplace research has consistently found engagement gaps widest in frontline and deskless populations[2], and aggregate reporting hides exactly that.
None of these five is available from the native Viva Engage panels, and the reason is worth understanding rather than complaining about. It is covered in detail in our article on what Viva Engage changed about Yammer measurement, which deals with the continuity break the transition created.
The honest position on native analytics here
Viva Engage community insights are free, already switched on, and adequate for a community manager running one community. If you own a single community and want to know whether your posts are landing in it, use the native panel and buy nothing. The tenant-level Viva Engage activity report in the admin centre similarly does its job for adoption monitoring[3].
The gap appears when the question is organisational rather than per-community. Native insights hold no workforce attributes, so the cross-boundary ratio and the participation rate by population cannot be produced without joining to Entra ID or an HR file yourself. Teams often try to close that with a Power BI build on the Microsoft Graph reporting API. Be aware of three things before committing to it: the reporting API is not consistently reliable and produces days with missing data; customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period; and a dependable build therefore needs a robust ingestion process with scheduled reconciliation and a named owner. Budget for the pipeline rather than the dashboard. The limits of Viva Engage analytics are set out in more detail separately.
Tryane sits above this layer, reading Viva Engage alongside SharePoint, Teams and your newsletter platform, joining that activity to organisational structure through Entra ID or an HR file, and keeping unlimited history so the Yammer years and the Viva Engage years read as one trend. It is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, uses single sign-on through Azure AD or Entra ID, and deploys in a couple of hours with no agent to install. For the direct comparison, see Tryane against Viva Engage native analytics.
Frequently asked questions
Should we archive our dormant Yammer-era communities?
Usually yes, with one exception. Archive project groups and social clubs that have moved to Teams. Do not archive a community of practice simply because it is quiet, because its value is the searchable answer archive rather than current traffic. Check whether people are still finding it through search before deciding.
Is Yammer still a separate product?
No. Microsoft completed the transition to Viva Engage and retired the Yammer branding and standalone experience. Communities, posts and membership carried across. What did not carry across cleanly for most organisations was the reporting continuity teams had built around the old product.
How do we know if a community should be in Teams instead?
Apply the boundary test. If everyone who needs to be in the conversation can be listed in advance, it belongs in Teams. If the value depends on a reply from someone you could not have named, it belongs in Viva Engage. The comparison of Teams against Viva Engage works through the edge cases.
What is a realistic answer rate for a healthy community?
It varies by domain, so treat any single benchmark carefully. What matters more is the direction of travel in your own network and the spread between communities. A community of practice with a 70 per cent answer rate and a median first reply within a working day is functioning. One where most questions die unanswered needs an active moderator before it needs a measurement programme.
Can Tryane measure the cross-boundary ratio?
Yes, provided your organisational attributes are available through Entra ID or an HR file. That join is what makes it possible to say whether a reply came from a different site or function to the question, which is the measure that demonstrates lateral value. Without the join, no tool can produce it, including a custom Power BI build.
Sources
• Microsoft Learn, Viva Engage overview
• Microsoft Learn, Viva Engage activity report
• Gallup, State of the Global Workplace
• Gallagher, State of the Sector
Further reading
• How Yammer influenced your organisation, and what Viva Engage changed
• Creating relevant Viva Engage communities
• Measuring frontline worker communications
• The complete Viva Engage guide
• What an internal communication team needs from Microsoft 365 analytics
Tryane runs a 15-minute working session with Heads of Internal Communication, going through your inherited community list and showing which ones are genuinely connecting people on your own tenant. Book a slot with Jérémy to schedule yours.