Somewhere in your team’s shared drive there is a board with forty post ideas on it. It was produced in a good workshop about eighteen months ago. Roughly six of them were used. The community feed currently shows two posts from the last month, both of them intranet articles relayed with the sentence “worth a read”, and the community manager who ran the workshop has since moved to the employer brand team.
This is the normal state of affairs, and it is worth being clear about the diagnosis. No enterprise social network has ever failed because the people running it ran out of ideas. They fail because nothing recurs. A good idea is used once. A format with a slot, an owner and a rhythm is used forty times, and the fortieth is better than the first because the audience knows it is coming. The unit of editorial work in Viva Engage is the format, not the post.
Why idea lists do not survive a quarter
An idea list has three structural weaknesses. It has no owner, so it belongs to whoever remembers it. It has no cadence, so it competes with urgent work every single week and loses. And it has no retirement rule, so when an idea stops working nobody notices, because nobody was tracking it as a thing that could stop working.
Formats fix all three. A format is a named, repeating thing with a person’s name against it, a place in the calendar, and a stated purpose you can test it against. When the quarter gets busy, a format survives because skipping it is a visible decision rather than an invisible omission.
There is a craft argument here too. Repetition is what makes a channel legible. People learn that Tuesday is the question thread and Thursday is the field story, and they start arriving with expectations. Novelty every week does the opposite: it makes the channel unpredictable, and unpredictable channels get checked less often. Microsoft’s own campaign feature exists precisely to group repeated activity around a theme rather than to help you invent one-offs[1].
Six formats that hold up over years
These are not the only possible formats. They are the ones that keep working in large organisations, and the point of the table is the last two columns rather than the first.
| Format | The job it does | Cadence | Owner | Retire it when |
|---|---|---|---|---|
| The open question | Surfaces what the centre does not know. The engine of the whole channel. | Weekly, same day. | Community manager. | Answers come from the same five people three weeks running. |
| Field story | Makes one site or team legible to the rest of the organisation. | Fortnightly. | Rotating, sourced from a site contact. | You are chasing contributors rather than turning them away. |
| Decision explainer | Explains why, after something changed. Requires a leader in the thread. | Event-driven, roughly monthly. | Executive, supported by the team. | Never. If there is nothing to explain, skip it rather than fill it. |
| Ask the expert | Puts a named specialist in front of the organisation for a fixed window. | Monthly, one community at a time. | The expert, briefed by the team. | Questions fall below roughly a dozen per session twice running. |
| Problem solved | Publishes the answer to something that was asked and resolved, so it is findable. | Fortnightly. | Community manager. | It stops generating follow-up questions. |
| Recognition with a specific detail | Makes contribution visible past its own team boundary. | Weekly. | Managers, nudged by the team. | It becomes a rota. Recognition on a rota reads as an obligation. |
Note what is not on that list: the relayed intranet article with no comment attached. Relaying is fine, and Viva Engage is a good traffic driver for the intranet, but a relay is not a format because there is no question in it. If you relay, relay with a question that only your audience can answer, and then be present when they answer it.
The mix, and why the ratio matters
A workable starting split is roughly half of published items asking something, a third telling a specific story about a specific place, and the remainder relaying or explaining. Teams usually discover they are running the inverse, with the great majority relaying and almost nothing asking. That single correction changes reply rates faster than any amount of new ideas, because a feed of statements has nothing for a reader to do.
Gallup’s workplace research keeps returning to the same finding: people are engaged where they believe their opinion counts and where they are recognised for specific work rather than in general[2]. The asking formats and the recognition-with-a-detail format are the ones that map onto that. The relay formats do not, which is why an estate built entirely from relays feels busy and produces nothing.
Writing the post itself
Three habits separate posts that get answered from posts that do not, and none of them is about tone of voice.
End with a question only your audience can answer. “What do you think?” is not that question. “Which of these three checks would you drop if you had ten minutes less on the line?” is. The specificity is what makes a reply feel low risk, because the responder knows what a useful answer looks like.
Name someone. Not a department, a person, and preferably a person who has agreed to be named. Posts naming a real individual are answered far more often than posts about a team, because a named person creates an obvious first responder.
Be present for 48 hours. A post nobody returns to teaches the audience that replying is pointless. If the person who published cannot be in the thread for two days, the post should move to a week when they can. This is also why timing matters more than it looks, and why our note on identifying the best time to post on Viva Engage is worth reading before you fix your slots against shift patterns.
Retiring a format is the discipline nobody has
Every format decays. The open question that generated thirty replies in March generates four in November because the interesting version of it has been asked. Teams keep publishing anyway, because stopping feels like failure, and the dead format sits in the calendar consuming the slot a live one could have used.
Put the retirement rule in the table at the moment you create the format, which is the only time you will be honest about it. Then review the whole set quarterly with the community managers who run them. Communities and formats decay for related reasons, and the portfolio question sits in our article on the community lifecycle, including when to close one. If your community managers do not currently have that conversation with each other, the piece on working with community managers is the place to start.
Measure the programme, not the post
Post-level metrics are the wrong altitude for editorial decisions. A single post can do well for reasons that will never repeat. What you want to know is whether a format is working, which means comparing the same format against itself over months.
Three programme-level measures are enough. Reply rate by format, tracked as a trend rather than a number. Distinct contributors by format, which catches the case where reply volume holds up because the same handful of people are propping it up. And reach by population, because a format that works beautifully in head office and never touches the plants is not the format you thought it was. Gallagher’s State of the Sector research has repeatedly found measurement to be the capability internal communicators name as their biggest gap[3], and format-level reporting is where most teams first notice the tooling does not reach.
The honest position on native analytics here
Viva Engage analytics report activity within a community and will show you how an individual post performed[4]. For a community manager running one community and wanting to know whether last Tuesday landed, that is free, already switched on, and enough. Do not buy anything for that job.
What it will not do is group posts into a format and trend them, join responders to function, site or contract type, or compare the Viva Engage version of a campaign against the intranet and newsletter versions running alongside. Teams often try to close that with a Power BI build on the Microsoft Graph reporting API. It can be made to work, but 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 needs a robust ingestion process, scheduled reconciliation and a named pipeline owner. Budget for the pipeline rather than the dashboard, and read our honest guide to SharePoint analytics in Power BI before you commit a quarter to it.
Tryane is the layer that does the grouping and the joining. It reads Viva Engage alongside SharePoint, Teams and your newsletter platform, joins the activity to your organisational structure through Entra ID or an HR file, and keeps history across product transitions, so a format you started in the Yammer years still trends as one line. It 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 Azure AD or Entra ID single sign-on, and installs no agent. For how the attributes should be structured first, see audience segmentation for internal communications.
Frequently asked questions
How many posts a week should a community publish?
Fewer than most calendars assume. Two well-attended posts with the author present in the thread beat six that nobody returns to. Publishing volume is the easiest number to move and the least connected to whether the channel is doing its job.
Should we relay every intranet article into Viva Engage?
No. Relay the ones that have a genuine question attached, and let the rest live on the intranet where they are findable. Blanket relaying trains the audience that the feed is a duplicate of somewhere they have already been, which is the fastest way to lose them. The channel-by-channel logic is in our guide to what Viva Engage is actually for.
What do we do when a format runs out of material?
Retire it and say so publicly. A short post explaining that a format is ending and why costs nothing and preserves the credibility of the ones that remain. Silently stopping teaches people the channel is unreliable.
Do polls count as a format?
They can, but they decay faster than any other format because the effort to answer is so low that the signal is weak. Use them to open a conversation you then follow up in the thread, not as the conversation itself.
Does Tryane replace Viva Engage analytics?
No. Viva Engage continues to record what it records. Tryane sits above it, grouping activity into formats and campaigns, joining responders to your organisational structure, and reading Viva Engage alongside SharePoint, Teams and newsletters so cross-channel and segmented questions become answerable.
Sources
• Microsoft Learn, Viva Engage campaigns
• Microsoft Learn, Viva Engage analytics
• Gallup, how engaged employees behave differently
• Gallagher, State of the Sector
Further reading
• Viva Engage in 2026, what it is actually for
• Getting executives genuinely active in Viva Engage
• Which Yammer use cases survived into Viva Engage
• Creating communities people actually join
• Measuring an internal newsletter beyond the open rate
Tryane runs a 15-minute working session with Heads of Internal Communication, looking at which of your recurring formats are still generating replies and which are quietly running on empty. Book a slot with Jérémy.