You have inherited a community with 3,200 members. The Viva Engage insights panel says posts are up twelve per cent on last month and that 214 people were active. Your sponsor, who is a divisional director and has about ninety seconds of attention for this, asks whether the community is working. Post volume cannot answer that. Neither can membership, which mostly records a decision somebody made in 2019 to add everyone in a department. The uncomfortable part is that a community can be busy, growing and completely failing at the thing it was set up to do, and the standard panel will show all green.
This piece is about what to put on a community manager’s dashboard instead. It assumes you are working in Viva Engage today, and that the Yammer years are history you still have to account for.
What happened to the Yammer manager dashboard
Yammer group insights became Viva Engage community insights, and the transition was less of a straight swap than the naming suggests[1]. The communities, posts and membership carried across. The reporting continuity that community managers had built up, usually in spreadsheets maintained by one person, largely did not. If you want the longer version of what that transition did to organisational measurement, we covered it in what Yammer changed and what Viva Engage altered, and the product-level differences are set out in the difference between Viva Engage and Yammer.
The practical consequence for a community manager is that the panel you now have is honest about the community and silent about the organisation. It reports what happened inside the community walls. Your sponsor’s question is almost always about something outside them.
The three questions a community dashboard has to answer
Every genuinely useful community dashboard we have seen answers these three, in this order. Most dashboards answer none of them.
1. Is it reaching the people it exists for?
A community set up for 900 field engineers is doing well if 300 field engineers read it. It is doing badly if it has 3,200 members and 214 active people who turn out to be head-office staff who joined out of curiosity. Membership is a vanity denominator. The intended population is the real one, and it is the number you have to establish yourself, because the platform does not know who your field engineers are.
2. Is participation broadening or concentrating?
Take the share of posts and replies produced by your top ten contributors. In a healthy community that number falls over time. In most communities it rises, because the same handful of enthusiasts carry it and everyone else becomes an audience. A community where 80 per cent of content comes from ten people is a newsletter with a comment box, which is a legitimate thing to run but should not be reported as a community.
3. Are questions getting answered?
This is the one nobody measures and the one that decides whether people come back. Count questions asked, questions with at least one substantive reply, and median time to that reply. A community where half the questions go unanswered for a week trains people to stop asking. That is a measurable, fixable problem, and it is invisible in a post-volume chart.
A nine-tile layout you can build this week
Three columns matching the three questions. The fourth column below is the honest bit: what you can get from the native panel and what needs work.
| Tile | Measure | Native Viva Engage? |
|---|---|---|
| Reach of intended population | Distinct readers as a share of the named target group | No, needs an attribute join |
| Reach trend | Same measure over 12 months | No, retention window is finite |
| New joiners who then read | Share of new members active within 30 days | Partly, needs manual work |
| Top-ten concentration | Share of posts and replies from the ten most active contributors | Partly, from the active-members list |
| Distinct contributors | People who posted or replied at least once | Yes |
| First-time contributors | People contributing for the first time this period | Partly, needs manual work |
| Questions asked | Threads tagged or identified as questions | No, needs a convention |
| Answer rate | Share of questions with a substantive reply | No |
| Median time to first reply | Hours, not days, is the target | No |
Four of the nine come straight from native tooling or from the Viva Engage activity report in the Microsoft 365 admin centre[2]. The question tiles need a convention rather than a tool: agree that questions carry a specific hashtag, and the counting becomes trivial. The reach tiles are the ones that need data the platform does not hold.
If you are building the wider communications dashboard rather than a single community view, our guide to building an internal communications dashboard covers the executive layer, and the note on the best time to post on Viva Engage is useful once you know who you are trying to reach.
What native insights will and will not give you
The native panel is free, already switched on, and genuinely the right tool for a community manager running one community. If your question is whether your posts are landing inside your community, use it and buy nothing. We mean that: a large share of the community managers we talk to are well served by what Microsoft already gives them.
It stops in three specific places. It does not join to workforce attributes, so the reach question above is not answerable natively, because Viva Engage does not know which of your members are field engineers in Normandy. Its retained window is finite, so a twelve-month or multi-year trend across the Yammer transition is not available. And it reports one community at a time, so if the same message also went out on the SharePoint intranet and in the newsletter, you have three unrelated numbers. The detail is in our note on the limits of Viva Engage analytics.
The usual next move is a Power BI build over the Microsoft Graph reporting API[3]. Know three things before you commit. 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, which is a hard thing to explain in front of an executive audience. And a dependable build needs a robust ingestion process with scheduled reconciliation against the native figures and a named owner, so budget for the pipeline rather than for the dashboard.
Three habits that matter more than the dashboard
The dashboard is downstream of these. Get them right and a mediocre dashboard still works.
- Name the population in writing. One line at the top of the community charter: this community exists for these people. It fixes your denominator, it settles arguments about scope, and it takes five minutes.
- Publish the concentration number. Put the top-ten share on the monthly report even when it is embarrassing. It is the measure that most reliably predicts whether a community survives a change of manager.
- Work the unanswered questions weekly. Fifteen minutes finding threads with no substantive reply and routing them to someone who can answer. This does more for participation than any campaign, and Gallup’s workplace research is consistent that responsiveness, not volume of communication, is what people register[4].
Where the reach tiles need data the platform does not hold, that 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 so participation by function, site, country or contract type becomes reportable, and keeps unlimited history across the Yammer and Viva Engage years so a multi-year trend reads as one line. Tryane is SOC 2 Type 2 certified and GDPR compliant by design, hosts in the EU by default with US data residency on request, deploys in a couple of hours over single sign-on with Azure AD or Entra ID, and installs no agent. The side-by-side is in Tryane compared with Viva Engage native analytics.
Frequently asked questions
Does the Yammer dashboard still exist?
No. Yammer group insights became Viva Engage community insights when Microsoft completed the transition, and the Yammer branding and standalone experience were retired. Communities, posts and membership carried across. Reporting continuity generally did not, which is why multi-year comparisons spanning the change are hard to produce from native tooling alone.
What should a community manager report monthly?
Three things, in this order: reach against the population the community exists for, the share of content coming from the top ten contributors, and the answer rate on questions. Distinct contributors is a useful fourth. Membership and post volume can appear, but not at the top, because neither responds to anything you actually control.
How do I measure whether frontline staff are participating?
Not from the native panel, which does not hold workforce attributes such as function, site or contract type. You need to combine Viva Engage activity with your organisational structure, either by exporting and joining the data yourself or with a dedicated analytics layer. Our note on engaging frontline workers on Viva Engage covers the practical side.
Is a high top-ten concentration always bad?
No. A community of practice with genuine experts will always concentrate, and that is the point of it. What matters is the direction of travel and whether it matches the community’s purpose. A general employee community that is concentrating year on year is drifting into broadcast, and it is better to notice that than to report a rising post count and call it growth.
Does Tryane replace Viva Engage community insights?
No. Viva Engage keeps recording what it records. Tryane sits above it, reading Viva Engage alongside SharePoint, Teams and newsletters and joining the activity to your organisational structure, so you can answer segmented and cross-channel questions no single native panel can. Community managers often keep using the native panel for day-to-day work.
Sources
• Microsoft Learn, Viva Engage overview
• Microsoft Learn, Viva Engage activity report
• Microsoft Learn, Microsoft Graph reporting API
• Gallup, State of the Global Workplace
Further reading
• Boosting Viva Engage performance with community managers
• The limits of Viva Engage analytics
• What Yammer changed, and what Viva Engage altered
• Tryane compared with Viva Engage native analytics
• How to build an internal communications dashboard
Tryane runs a 15-minute working session with community managers and Heads of Internal Communication, taking one of your Viva Engage communities and rebuilding its reach and concentration figures against the population it was set up for. Book a slot with Jérémy.