Internal Communication Tools: Choose a Stack, Do Not Rank Tools

By Nicolas Saliba · 8 min read

An internal communication team of four in a 9,000-person group already runs a SharePoint intranet, Viva Engage, an all-company Teams channel, a newsletter platform, digital signage in three plants and an annual survey tool. A vendor demo lands promising to unify the lot. The instinct in the room is to add, because adding is visible and consolidating is not.

Before adding anything, one question is worth an hour: which job in the current stack is genuinely unowned, and is a tool the answer or is an owner the answer? Most internal communication functions do not have a tool shortage. They have more channels than they have people to run them, and every channel is quietly generating a number that nobody can reconcile with any other number.

Why ranked tool lists do not help

A ranking compares products on features. Your problem is not feature coverage, it is fit with a channel model you have already partly built, inside a Microsoft 365 tenant you are not going to abandon, for a workforce with populations that differ enormously in how they can be reached.

The second reason is that the licence is rarely the real cost. Each additional surface brings an audience model that does not match the others, a retention window set by someone else, a login that a proportion of your workforce will never use, and a reporting seam. Three years later the seam is the expensive part. Gallagher’s State of the Sector research repeatedly finds measurement to be the capability internal communicators name as their biggest gap^[1], and a stack assembled tool by tool is one of the reasons.

The jobs a stack has to cover

Rather than counting tools, count jobs. Five of them, and a tool can cover more than one.

Job	Typical Microsoft 365 answer	What breaks when nobody owns it
A durable place things live	SharePoint communication sites and news^[2]	Policy questions get answered by rumour because nothing is findable
A place where replies are expected	Viva Engage communities, or a designated Teams channel^[3]	Leadership broadcasts and never learns what landed badly
A push that reaches people who do not come looking	Newsletter platform or Microsoft 365 email	Only the already-engaged see anything
Reach without a desk or a corporate device	Manager cascade, shared devices, signage, printed board	Whole populations are structurally invisible
Listening and feedback	Survey or pulse tool, plus comment analysis	The function measures its own output and calls it impact

Measurement is not a sixth channel. It runs across all five, which is precisely why it fails when treated as a feature of whichever tool was bought most recently.

The job most often unowned

In manufacturing, retail, healthcare and logistics it is almost always the fourth row. Populations without a corporate email address, working shifts, sharing a terminal, reading in a second language. They are not disengaged, they are structurally out of reach of the channel model, and no dashboard shows this because the denominator used is the tenant rather than the headcount. Our note on measuring frontline worker communications works through what can actually be counted for those populations.

Six questions before you add anything

These are worth putting in writing and answering honestly, because a vendor cannot answer most of them for you.

What job is unowned, and is a tool the answer? Frequently the gap is a person or a cadence, not a product. A newsletter nobody has time to write does not become a better newsletter on a better platform.

Who publishes, how often, and what happens when they leave? Every surface needs a named owner and a realistic cadence. A channel that goes quiet for two months is worse than one that never existed, because it teaches people not to look.

What audience model does it use? If it maintains its own list of recipients that nobody reconciles with the directory, you have created a second version of the organisation. Attributes should come from Entra ID or an HR extract^[4] so that percentages across tools share a base. The structure to aim for is set out in audience segmentation for internal communications.

What does it retain, and can you export it? Ask for the retention window and the export format before signing, not during a migration. This is the question teams regret skipping.

Does it create a second source of truth? Two places holding the same announcement produce two versions, and the one people quote back is whichever their manager posted.

What is the exit? Every tool is eventually replaced. What happens to three years of history when it is, and does your year-on-year comparison survive?

The measurement seam

Here is the arithmetic that makes a stack expensive. With five channels you have five reporting surfaces, five audience bases and five retention windows. The intranet reports views, the newsletter reports opens, Viva Engage reports active members, Teams reports tenant activity, and signage reports nothing at all. None of these numbers can be added, and the same person appearing in three of them looks like three people.

The consequence is a monthly report built from five screenshots, which survives exactly until a senior stakeholder asks what proportion of the workforce saw the restructuring announcement. Answering that requires counting people rather than events, against a workforce denominator rather than a platform base. The method is set out in measuring cross-channel internal communications, and what to put on the slide is covered in dashboards for internal communications.

The honest position on Microsoft native

For a team measuring one surface, native reporting is free, already switched on and sufficient^[5]. SharePoint site analytics answers site questions, Viva Engage community insights answer community questions, and if that is the whole of your remit you do not need to buy anything.

Teams with a wider remit often try Power BI on the Microsoft Graph reporting API. That route can work, but the reporting API is not consistently reliable and produces days with missing data^[6], and customers have observed KPI values in Power BI that do not reconcile with the native SharePoint reports for the same period. A dependable build needs a robust ingestion process and scheduled reconciliation against native figures, so budget for the pipeline rather than the dashboard. The failure modes are in SharePoint analytics in Power BI.

Tryane occupies the measurement job across the stack rather than adding a channel to it. It reads SharePoint, Viva Engage, designated Teams channels and newsletter platforms together, joins that activity to organisational structure through Entra ID or an HR file, and holds history across product transitions. 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 through single sign-on, and installs no agent. If you are evaluating that category specifically, the criteria are in how to choose an internal communications analytics tool, which goes into scoring and vendor questions in more depth than this article does.

When to consolidate instead

Three signals that the right move is subtraction. A channel with no named owner and no cadence should be closed rather than relaunched. Two channels serving the same audience with the same content should become one, with the other redirecting. And a tool whose only remaining use is one annual campaign is a licence you are paying to keep a habit alive.

Consolidation is unglamorous and it is usually the highest-return move available to an IC function in its second or third year of maturity. Where your function sits on that curve is worth checking against the internal communications maturity model before the next budget cycle.

Frequently asked questions

How many channels should an internal communication function run?

Fewer than most run. A useful test is whether each channel has a named owner, a stated cadence and a population it exists to reach that no other channel reaches better. Channels that fail all three are usually kept out of habit. The number itself matters less than whether the set covers the five jobs without overlapping.

Do we need a dedicated internal communication platform on top of Microsoft 365?

Often not. Most organisations on Microsoft 365 already own a publishing surface, a conversation surface and a push channel. The genuine gaps tend to be reaching people without a desk, and measurement across the whole set. Buy against those gaps rather than against a feature comparison.

What about AI writing and summarisation tools?

They help with production, which is rarely the binding constraint. If the team is short of time, they are worth trialling for drafting and translation. They do not address whether the message reached the intended population, and they should support the judgement of an experienced communicator rather than replace it.

How do we justify an analytics layer when the channels are already paid for?

Frame it as the cost of the seam rather than as another channel. The concrete version is the question you cannot currently answer: what proportion of a named population saw a specific announcement, on any channel, compared with last quarter. Put a number on how long it currently takes to assemble the monthly report by hand, and the case usually makes itself.

Should signage and print count as channels we measure?

They should count as channels you plan, and be reported honestly as estimated rather than measured. A screen in a canteen has real reach and no telemetry worth trusting. Marking it explicitly as an estimate is more credible than either ignoring it or quietly folding a guess into a total.