The business case said internal email would fall by a third. Eighteen months on, email volume is flat, the collaboration platform has 4,000 registered users and roughly 300 people who post in a given week, and the internal communication team produces a monthly report with one more tab on it than before. Nobody would call the project a failure. Nobody can say what it improved either.
That pattern is common enough to take seriously, and it is not caused by a bad platform choice. A collaboration platform does not improve internal communication by existing. It improves internal communication when a small number of conditions hold, and it adds a channel to your measurement burden when they do not. This article is about those conditions, and about how to tell early which situation you are in.
What a collaboration platform actually changes
Start with the mechanism, because benefit claims usually skip it. A collaboration platform changes the direction and the marginal cost of a message. Microsoft Teams channels, Viva Engage communities and a SharePoint communication site with comments enabled all do something email does not: they make the audience visible to itself[1]. A reply is public. A question asked once gets answered once and read by two hundred people who never thought to ask it.
That is a genuine benefit with a genuine precondition. Enough of the right people have to be in the same place at the same time for a public reply to be worth more than a private one. Below that threshold you have built a slower email. Above it the economics invert, and the same drafting effort serves a much wider audience.
What it does not change, whatever the business case said: the number of messages your organisation produces, which is set by how many people may publish rather than by where they publish. It does not decide what is important. And it does not reach a person who is not looking. A frontline worker who checks a shared screen twice a shift is no more reachable in Teams than in Outlook if nothing in the working day sends them there.
Condition one: an audience model that predates the launch
The best predictor of whether a collaboration platform improves anything is whether the internal communication team can name its audiences before launch day, in the same terms the HR system uses. Function, entity, country, site, language, contract type, manager or not, desk or no desk.
Without that model, the only segment you have is the whole tenant. Every launch metric becomes a tenant-wide average, and no one can answer the first question a sceptical executive asks, which is whether the population the platform was bought for is using it. With the model, the same launch produces a diagnosis: adoption at 61 per cent in the commercial function, 9 per cent in operations, and a reason to look at what operations does at 6am. Our note on audience segmentation for internal communications sets out how to build that model before you need it.
The awkward part is that the model is easiest to build before launch and hardest to retrofit. Once the reporting habit has formed around tenant totals, adding segmentation means restating numbers someone has already shown a board.
Condition two: something genuinely moves off the old channel
Collaboration platforms produce benefits by substitution, not addition. If the weekly operations update now appears in a Teams channel and still goes out as an all-staff email, nothing has been reduced. You have doubled the production cost and split the readership, so both numbers look worse than the single channel did.
Substitution has to be decided, named and enforced. That means picking a category of message and moving it wholesale: policy updates, shift-level operational news, or the leadership question-and-answer thread. Then removing the old route for that category rather than leaving it open for whoever complains. Half-substitution is the most expensive outcome available, and it is the default when nobody owns the decision.
Gallagher’s State of the Sector research has repeatedly found channel proliferation and measurement to be the two problems internal communicators name most often[2]. The two are related. Every channel added without a channel retired increases both the production load and the difficulty of showing that anything reached anyone.
Condition three: the new channel joins one measurement estate on day one
The third condition is the one internal communication teams control least and pay for most. A collaboration platform arrives with its own analytics, which report on itself. Viva Engage community insights describe the community. SharePoint site analytics describe the site[3]. Neither describes the message, which is the unit your stakeholders care about, and no native panel adds the two together.
If the new channel enters your reporting as a separate tab, cross-channel reach becomes impossible to state, so you stop stating it. Comparisons between channels turn into comparisons between metrics never defined the same way. And the total audience of a campaign quietly becomes whichever channel reported the largest number. Working out how to measure across channels before the platform lands is far cheaper than reconstructing it later.
| The benefit as written in the business case | What has to be true for it to appear | The number that shows it |
|---|---|---|
| Less internal email | A named category of message left email entirely | Volume of that category on the old channel, at zero |
| Faster answers to operational questions | The people who answer are present and expected to answer in public | Median time to first useful reply, by community |
| Better reach to the frontline | Something in the shift routine points at the platform | Participation rate among the no-desk population, not tenant total |
| More two-way communication | Leaders reply in the thread rather than by direct message | Share of leadership posts with a leader reply below them |
| One place for company news | The publishing right was narrowed, not widened | Number of distinct publishers per week, falling |
When you should not add a platform at all
The honest case against is stronger than most vendors admit. If your organisation runs one intranet, one newsletter and one set of team meetings, and the internal communication team is three people, adding a collaboration platform will probably make things worse for a year. The native tooling you have is free, already switched on, and sufficient for a single channel with a single audience.
The case for a platform strengthens as three things grow: the number of distinct populations you must reach, the geographic and linguistic distance between them, and the share of your workforce without a desk. A 900-person single-site company rarely clears that bar. A 14,000-person group with 60 sites in nine countries usually does, for a specific reason: at that size, missing lateral communication paths show up as the same problem being solved independently in six places.
The first 90 days, and what to actually watch
Launch reporting is where most collaboration platform programmes lose their argument. Registered users is the least informative number available and the one most often presented, because it is large and rises on its own. Three measures are worth more than any adoption curve.
- Participation rate by population. Not 4,000 users, but 61 per cent of the commercial function and 9 per cent of operations. The second version tells you where to work.
- Substitution evidence. Volume on the channel that was supposed to shrink. If it has not moved, the benefit has not started.
- Reply depth on the messages that matter. A leadership post with 900 views and no replies is a broadcast in a different font. The internal communication KPIs that survive executive scrutiny are almost always about depth and coverage rather than volume.
None of these are available from a single native dashboard, which is the practical reason this gets skipped. Teams reporting and Viva Engage insights each cover their own product. If you are measuring a Teams rollout specifically, our guide to measuring internal communications on Microsoft Teams covers what the native reports do and do not include.
Where a measurement layer fits
This is the layer Tryane occupies. It reads SharePoint, Viva Engage, Teams and your newsletter platform together, joins that activity to organisational structure through Entra ID or an HR file, and keeps history across product transitions so that a platform launched in 2024 and a channel retired in 2026 read as one trend. 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 through single sign-on with Azure AD or Entra ID, and installs no agent.
Teams often try to build this themselves in Power BI against the Microsoft Graph reporting API[4]. It can be made to work, and some organisations run it well. Be clear-eyed about what it costs. 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 difficult 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, so budget for the pipeline rather than the dashboard. Our piece on SharePoint analytics in Power BI covers the failure modes in detail.
Frequently asked questions
Is a collaboration platform worth it for an organisation under 1,000 people?
Usually not as a communication investment. Below roughly 1,000 people on a single site, the lateral paths a platform creates already exist informally. The calculation changes when populations are separated by geography, language or shift pattern, because that is when the same problem starts being solved several times over.
How long before the benefits show up in the numbers?
Substitution evidence appears within one quarter or not at all. If the channel that was supposed to shrink has not moved in 90 days, the programme has added a channel rather than replaced one, and waiting rarely fixes it. Participation and reply depth take two to three quarters to settle, because they depend on managers changing habits rather than on a rollout.
Can we measure the platform with the native analytics it ships with?
For questions inside the product, yes. Native insights tell you whether a community is active and whether a site is visited, which is often enough for the person running that community. They will not give you participation by function or country, they will not add the platform to your other channels, and their retained history is finite.
What is the single most misleading launch metric?
Registered users. It rises without anyone doing anything, it counts people who were provisioned rather than people who came, and it invites a comparison with headcount that flatters the programme. Participation rate within a named population is worth far more in a budget conversation. Our guide to building a defensible reach figure for SharePoint communications works through the same problem on the intranet side.
Does Tryane replace the native analytics in Microsoft 365?
No. SharePoint, Viva Engage and Teams keep recording what they record. Tryane sits above them, reads them together, and joins the result to your organisational structure so you can answer cross-channel and segmented questions no single native panel can. You keep the Microsoft 365 investment and add the layer for what native was never built to do.
Sources
• Microsoft Learn, Overview of teams and channels in Microsoft Teams
• Microsoft Learn, Microsoft 365 reports, SharePoint site usage
• Microsoft Learn, Graph reportRoot getSharePointSiteUsageDetail
• Gallagher, State of the Sector
Further reading
• Measuring cross-channel internal communications
• Audience segmentation for internal communications
• Building an internal communications measurement strategy
• Measuring frontline worker communications
• The limits of Viva Engage native analytics
Tryane runs a 15-minute working session with Heads of Internal Communication, mapping the channels you run against the populations you need to reach. Book a slot with Jérémy.