Ask five people in the same organisation what the digital workplace is and you will get five answers: the intranet, Microsoft 365, the mobile app, “everything that is not email”, or a programme name from a transformation that finished two years ago. That confusion is not a semantic problem. It is the reason nobody can say who is accountable when the homepage carries a news item that contradicts an HR policy, or when a site with 400 documents has had no owner since a reorganisation.
A digital workplace fails on ownership far more often than it fails on technology. This guide sets out the components of a Microsoft 365 digital workplace, who should own each one, the four governance decisions that determine whether it holds together, and where the measurement problem starts. It is the practical companion to why your cross-channel digital workplace totals do not add up, which deals with what happens when you try to measure all of this as one thing.
What the digital workplace actually consists of
A useful definition is narrow: the digital workplace is the set of surfaces through which the organisation communicates with itself and through which people find what they need to do their job. In a Microsoft 365 estate that is a short and specific list.
- The SharePoint intranet. Home site, news, hub-linked departmental and country sites. This is the publishing surface and the system of record for anything with a policy attached. Microsoft’s planning guidance treats the home site and hub architecture as the structural decision everything else rests on[1].
- Viva Connections. The dashboard and the mobile and Teams entry point, which is how anyone without a corporate laptop reaches the intranet at all[2].
- Viva Engage. Communities and the leadership corner. Conversation rather than publication, which is why it needs different owners and different rules.
- Microsoft Teams. Team and channel posts. In most organisations this is where operational communication actually happens, whatever the intranet strategy says.
- The newsletter. Whether that is a dedicated platform or Microsoft 365 native email. It remains the only channel that reaches people who do not visit anything.
- Search. Not a channel, but the thing that decides whether the other five are usable.
Notice what is not on the list: the HR system, the expenses tool, the ticketing system. They are part of the digital employee experience and they matter, but folding them into the digital workplace makes the scope unownable. Keep the definition to the communication and findability surfaces, and the ownership question becomes answerable.
Who should own what
The single most common failure we see is a digital workplace where IT owns the platform, internal communications owns the content, and nobody owns the experience. Every unresolved question falls into the gap between them.
| Surface | Platform owner | Editorial owner | Decides what appears | Retires it |
|---|---|---|---|---|
| Home site and organisational news | IT or M365 team | Internal communications | Internal communications, with a published editorial policy | Internal communications, on a fixed cycle |
| Departmental and country sites | IT or M365 team | Named local owner in each function | Local owner within a template | Governance board, on evidence of inactivity |
| Viva Connections dashboard | IT or M365 team | Internal communications | Joint decision, since cards compete for the same small space | Quarterly review |
| Viva Engage communities | IT or M365 team | Community manager per community | Community manager | Governance board, using group lifecycle policy |
| Teams channels for comms | IT or M365 team | Team owner | Team owner | Group expiration policy |
| Newsletter | Whoever holds the tool | Internal communications | Internal communications | Not applicable |
| Search relevance | IT or M365 team | Nobody, usually | Should be a joint quarterly review | Not applicable |
The last row is the one that quietly ruins digital workplaces. Search is the surface with no natural owner: IT considers it configured, communications considers it technical, and it degrades steadily as sites multiply. Assign it to someone, review the top queries quarterly, and manage the search schema deliberately[3].
The four governance decisions that actually matter
1. Who can create a site or a community
Open creation produces sprawl, restricted creation produces shadow channels in Teams. The workable middle is self-service creation inside a template, with mandatory ownership metadata and an expiry date attached at creation. Microsoft 365 group lifecycle policies can enforce the renewal step so that abandonment becomes visible rather than permanent[4].
2. What gets to be organisational news
Every function believes its announcement is organisational. If everything is boosted to the home site, the home site stops being read and targeting becomes meaningless. Write a one-page editorial policy that states the three or four categories that qualify, publish it, and refuse politely on the record when something does not meet it. This is the least technical and highest impact decision in the whole guide.
3. Retirement, and who is allowed to do it
Nothing degrades an intranet faster than content that is technically still true and practically obsolete. Retirement needs a named owner, a fixed cycle and a default: content with no owner and no views in twelve months goes to an archive unless someone claims it. Announce the rule, apply it, and expect exactly two complaints in the first year.
4. Where a given message belongs
Publish a channel matrix that says which channel each message type uses, and stick to it for a year before revisiting. Not because the matrix will be perfect, but because inconsistency is what teaches people to ignore all channels equally. If a safety instruction can arrive by intranet, Teams, email or a poster depending on who wrote it, nobody develops a habit.
The measurement problem this creates
Distributed ownership is the right answer for running a digital workplace and the wrong answer for measuring one. Each owner sees their own surface. SharePoint site analytics reports on the site. Viva Engage community insights report on the community. Teams reporting reports on the team. Nobody sees the person who read the same story in three places, and every attempt to total those figures overstates reach, which is the subject of our piece on measuring cross-channel internal communications.
Native reporting deserves a fair description here. The Microsoft 365 admin centre reports are free, already on, and entirely sufficient for a site owner asking whether last week’s page was read. They are not designed to answer organisational questions, because they hold no workforce attributes, retain a finite window and report per surface. That is a scope decision by Microsoft, not a defect.
Many teams try to assemble the cross-surface view in Power BI on the Microsoft Graph reporting API. It is a legitimate route with a real bill attached. 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. A dependable build needs a robust ingestion process and scheduled reconciliation against the native figures, with a named owner. Budget for the pipeline rather than the dashboard. Our honest guide to SharePoint analytics in Power BI covers the failure modes in detail.
Where Tryane fits
Tryane sits above the surfaces rather than replacing any of them. It reads SharePoint, Viva Engage, Teams and your newsletter tool together, joins the activity to your organisational structure through Entra ID or an HR file, and keeps history across product transitions so a rebrand or a migration does not restart your trend. In governance terms, that gives the board the two things it cannot otherwise get: an evidence-based dead-site list, and a single reach figure that does not double-count. If you are choosing or reviewing a platform, judging a digital workplace on evidence rather than features covers what to ask for, and the KPIs that show intranet success covers the reporting.
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.
Frequently asked questions
What is a digital workplace, precisely?
Used narrowly, it is the set of surfaces through which an organisation communicates with itself and through which people find what they need: the SharePoint intranet, Viva Connections, Viva Engage, Teams, the newsletter and search. Broader definitions that include every business application are common but make the scope unownable, which is the practical reason to keep it narrow.
Who should own the digital workplace?
Ownership should be split by surface and by layer, with IT owning platforms and internal communications owning the organisational editorial layer, but there must be one named accountable owner for the experience as a whole. In most organisations that sits with internal communications, with a governance board that includes IT, HR and two business representatives.
How often should digital workplace governance meet?
Quarterly for the board, with a standing agenda: sites to retire, dashboard cards to change, search queries with no good result, and any channel matrix exceptions granted since the last meeting. Monthly is too often and creates busywork. Annually is not often enough to stop sprawl.
Do we need a separate intranet if we already use Teams heavily?
Usually yes, because they do different jobs. Teams is where operational conversation happens and it is poor at persistence: a policy posted in a channel is unfindable in six weeks. The intranet is the system of record for anything with a policy attached. The mistake is treating them as competing rather than sequential, with Teams driving attention and the intranet holding the durable version.
Can we measure the whole digital workplace with native Microsoft 365 tools?
Per surface, yes, and quite well. As a whole, no, because there is no shared identity of a reader across surfaces in the native reports and no join to workforce attributes. Adding the figures together produces an inflated reach number that will not survive a question from anyone who understands the data.
Sources
• Microsoft Learn, planning an intranet in SharePoint
• Microsoft Learn, Viva Connections overview
• Microsoft Learn, manage the search schema in SharePoint
• Microsoft Learn, Microsoft 365 group lifecycle policy
Further reading
• Why your cross-channel digital workplace totals do not add up
• Judging a digital workplace on evidence rather than features
• Viva Connections analytics and intranet adoption
• Which intranet metrics matter to communications
• Measuring the impact of a SharePoint intranet redesign
Tryane runs a 15-minute call with Heads of Internal Communication, going through the ownership table against your own estate and showing which surfaces currently have no named owner. Book 15 minutes with Jérémy.