The Best Digital Workplace Is the One People Actually Use

By Nicolas Saliba · 8 min read

Three vendor demos in a fortnight, and the feature grids come out looking almost identical. Personalised homepage, targeted news, mobile app, enterprise search, deep Microsoft 365 integration, an analytics dashboard. Every one of them ticks every box. And yet you already know, because you have lived through at least one intranet launch, that two organisations can buy exactly the same product and end up somewhere completely different. In one, the intranet becomes the place people check before they ask a colleague. In the other, it becomes a link in an email signature that nobody follows. The feature grid did not predict that, and it will not predict it this time.

What does predict it is behaviour, and behaviour is measurable before you commit to anything. This piece sets out the four pieces of evidence that separate an intranet people use from one they do not, how to gather each on the intranet you already run, and what to ask a vendor to demonstrate rather than assert.

Why feature grids do not predict adoption

A feature grid measures capability. Adoption is a function of habit, and habit forms around a very small number of things that reliably work. If search returns the travel policy on the first attempt, people come back. If it returns four versions of the travel policy from three different sites and one of them is from 2019, they stop coming back, and no amount of personalisation on the homepage will recover them.

That is why the capability question and the adoption question come apart. Almost every serious platform can do targeted publishing. Very few organisations have the audience attributes clean enough to target with, the editorial discipline to keep the homepage short, and the governance to retire dead content. The platform is rarely the constraint. The operating model usually is, which is the subject of our practical guide to digital workplace components and ownership.

There is one honest exception, and it is worth stating before the rest of the argument. A feature grid is exactly the right instrument for the things that are binary and non-negotiable: accessibility conformance, data residency, supported languages, retention and legal hold, single sign-on, and whatever your regulator requires. Score those on a grid, eliminate anything that fails, and then stop using the grid. It has done its job.

The four pieces of evidence that actually separate them

1. Return rate, not reach

Reach tells you how many people arrived. Return rate tells you whether arriving was worth it. The number to look at is the share of the addressable population that visited in at least three separate weeks of the last eight, not the share that visited once. A launch campaign, a mandatory compliance module or a payslip link will all produce a reach spike. Only usefulness produces a return.

You can approximate this today. Microsoft 365 admin centre site usage reports give unique visitor counts per site over a rolling window^[1]. What they do not give you is the same person tracked across the intranet, Viva Engage and Teams, which is why cross-channel return rate needs a layer above the native reports.

2. Search that ends in an answer

The single most diagnostic number on an intranet is the proportion of searches that end without a click. In most estates it sits far higher than anyone expects, and it is the clearest signal that the information architecture, not the platform, is the problem. Microsoft publishes guidance on managing the search schema and refiners precisely because default search on a large tenant degrades as sites multiply^[2].

Pull your top 200 internal search queries and read them. Not the aggregate, the actual strings. You will find the same five questions asked in nine different phrasings, which tells you what the homepage should say and what needs a redirect rather than a new page.

3. Depth past the homepage

A homepage view is close to worthless as evidence, because a browser start page produces one every morning whether or not anyone reads it. What matters is the second click. Track the proportion of sessions that reach a content page, and the proportion that reach it from somewhere other than a push notification or an email link. An intranet whose traffic collapses the moment the newsletter stops sending is not an intranet, it is a landing page for the newsletter.

4. Coverage of the populations with no desk

This is the piece that separates a genuinely good digital workplace from a good head-office digital workplace. Gallup’s workplace research has consistently found engagement lowest and most volatile in frontline and deskless populations^[3]. If your intranet reports 71 per cent monthly reach and that figure is 88 per cent in corporate functions and 22 per cent in operations, the aggregate is actively misleading you. Our note on measuring communications that reach frontline workers goes through how to build that split without an HRIS project.

What to ask a vendor to show you

Turn each claim into a demonstration. If a vendor cannot show it on a real tenant, treat the claim as unproven rather than false.

The feature claim	What it actually means in practice	The evidence that would prove it
Personalised homepage	Content varies by audience attribute	Show two named users in different functions seeing genuinely different pages, and show where the attribute came from
Powerful enterprise search	People find the answer on the first attempt	The no-click search rate on a live tenant, and the top 50 queries with their success rate
Mobile app for frontline	People without a corporate laptop use it weekly	Weekly active share for the deskless population specifically, not tenant-wide
Built-in analytics	You can answer questions from your leadership	Answer this live: which sites did the manufacturing population read last month, in which countries
Integrates with Microsoft 365	One record of a person across channels	A single report combining SharePoint, Viva Engage and Teams activity for one segment

The fourth row is where most demonstrations stall. Publishing tools are good at publishing and report on their own surface. Combining surfaces is a different problem, and one we cover in why cross-channel digital workplace totals do not add up, because the same person reading the same story in three places is counted three times unless the view definitions are normalised first.

The honest case for staying where you are

For a large number of organisations the right answer is not a new platform at all. SharePoint with Viva Connections is already licensed, already governed by your existing tenant policies, and Microsoft’s own portal health and launch guidance is a genuinely good playbook for building an intranet that performs^[4]. If your problem is that the homepage is stale and nobody owns retirement, buying a different platform will reproduce the same intranet with a new logo in eighteen months.

Native analytics is similarly worth defending. Site usage reports are free, already switched on, and completely sufficient if you own one site and want to know whether last week’s page was read. The gap opens when the question becomes organisational: participation rate by function, country or contract type, one story followed across the intranet, Viva Engage and the newsletter, and a trend that survives a tenant migration or a rebrand. Native reporting holds a finite window and does not join to workforce attributes, so those three questions stay out of reach.

Teams often try to close that with a custom Power BI build on the Microsoft Graph reporting API^[5]. It can be made to work. Be clear-eyed about what it takes. 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 and scheduled reconciliation against the native figures, with a named owner. Budget for the pipeline, not the dashboard.

Where Tryane fits

Tryane sits above the platform rather than replacing it. It reads SharePoint, Viva Engage, Teams and your newsletter tool together, joins that activity to your organisational structure through Entra ID or an HR file, and keeps history across product transitions so a redesign or a migration does not reset your trend line. That is what makes return rate by population, cross-channel reach and the frontline split answerable rather than estimated. If you are about to change platforms, our piece on measuring the impact of a SharePoint redesign covers what to capture before the old intranet goes dark, and the KPIs that show intranet success covers what to put on the slide afterwards.

On the practical side: 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 with single sign-on through Azure AD or Entra ID, and installs no agent on any device.

Frequently asked questions

Which digital workplace platform is the best one?

There is no defensible answer to that question in the abstract, and any ranking that claims one is selling something. The platforms on a typical shortlist have converged on capability. What varies is whether your organisation has clean audience attributes, editorial discipline and a content retirement process. Score the binary requirements on a grid, then choose on evidence of use rather than breadth of features.

How do I measure intranet adoption before I decide to replace it?

Start with four numbers on your current estate: the share of the addressable population that visited in at least three of the last eight weeks, the no-click search rate, the share of sessions that reach a second page, and the reach split between corporate and frontline populations. If those four are healthy, your problem is content, not platform.

Is SharePoint good enough for a modern intranet?

For most Microsoft 365 organisations, yes, provided the governance exists. SharePoint with Viva Connections covers targeted news, a mobile surface and integration with the tools people already have open. Microsoft’s portal health guidance is a serious operational playbook. The constraint is usually ownership and retirement, not the product.

Why does my intranet reach look good but engagement look poor?

Almost always because reach is inflated by a browser start page or a push notification, while engagement measures what happened after arrival. Separate arrivals driven by a push from arrivals driven by intent, and look at the second click rather than the first. The gap between those two numbers is the honest measure of whether the intranet is useful.

Does Tryane replace SharePoint or Viva Connections analytics?

No. Both continue to record what they record. Tryane reads them alongside Viva Engage, Teams and your newsletter platform, joins the result to your organisational structure, and holds history across migrations. You keep the Microsoft 365 investment and add the layer that answers segmented and cross-channel questions.