A restructuring announcement goes out at 09:00 on a Tuesday. In the office, it is processed by 11:00: people read it, then they read each other’s faces, then someone says the thing everyone was thinking and the room settles. The team that comes in on Thursdays hears about it on Wednesday afternoon, second hand, from someone who was in the room. By the time the official message reaches them it is confirming a rumour rather than delivering news, and their manager is answering questions with information she has had for a day and a half.
Nothing failed in the channel. The email sent, the intranet published, the Teams post went up. What failed was sequencing, and it failed because hybrid work quietly removed something internal communications had relied on for decades without ever naming it: the shared information moment.
What the shared moment was actually doing
Before hybrid, most organisations had at least one reliable synchronising event. The Monday morning briefing, the shift handover, the screen in the canteen, the ten minutes after the all-hands when everyone walked back to their desks together. Those moments were never mainly about distribution. Email already handled distribution. They were doing three other jobs.
They created a common reference point. Everyone knew that everyone else knew, which is the precondition for a conversation about a change rather than a series of private reactions to it. They provided a correction mechanism, because a badly worded sentence got a raised eyebrow within thirty seconds and could be fixed before it hardened into a story. And they signalled importance through their own format: the fact that this was said in the room, at that time, told people how seriously to take it.
Hybrid did not remove those moments entirely. It made them partial. Half the audience is in the room, half is on a call with cameras off, and a third group is on shift and will catch up later. Gallup’s tracking of hybrid work has consistently found that the practical experience of hybrid varies enormously by role and by team, not by policy[1]. That variation is exactly what breaks a single shared moment.
The window replaced the moment
Messages now land over days, not minutes
The honest description of what happens now is that a message lands across a window. For an office population that window might be four hours. For a field engineering team it might be four days, because the message competes with a job list and a van. In a manufacturer with shift patterns, a Friday afternoon publication reaches the Monday morning shift on Monday, whatever the send time says.
This matters because most internal communications reporting still describes reach as though it were a single event. A message with 82 per cent reach after two weeks looks identical to a message with 82 per cent reach after one day, and the two are entirely different pieces of work. The shape of the curve is the information.
The manager cascade became load-bearing
When there is no shared moment, the manager conversation stops being a nice reinforcement and becomes the actual mechanism by which most people find out what a change means for them. That is a significant increase in the load placed on line managers, and most organisations increased it without saying so, without giving managers the message earlier, and without measuring whether the cascade happened.
The practical fix is unglamorous: brief managers on a genuine lead time, give them a version they can say out loud rather than forward, and measure whether their teams read the material at a different rate from the site average. That last number, read rate by team against the site baseline, is the single most useful hybrid-era diagnostic we see, because it locates the break precisely.
Asynchronous does not mean whenever
The most common mistake is treating asynchronous as a licence to publish and hope. Asynchronous communication needs more structure than synchronous, not less: an explicit order of who hears first, a stated window in which everyone should have it, and a named point at which you check the tail. Without that, the sequence defaults to proximity, and proximity now correlates with being in the office, which is precisely the inequity hybrid was supposed to avoid.
How to sequence when there is no shared moment
Sequencing is a deliberate decision about order and spacing, made before publication. The table below is the pattern we see working in organisations of 5,000 people and above.
| Message type | Who should hear first | Acceptable window to full reach | What breaks if you get it wrong |
|---|---|---|---|
| Restructuring or role change | Directly affected teams, via their manager, before anything is published | Same day, all populations | People learn about their own job from a rumour, and trust in the channel does not recover for a year |
| Safety or compliance instruction | The operational population it applies to | 24 to 48 hours, measured against that population only | An audit finding, and a genuine risk that has nothing to do with communications |
| Strategy or results | Managers 24 hours ahead, then everyone simultaneously | Five working days | Managers are asked questions they cannot answer, which trains them to disengage |
| Culture, recognition, community | No sequencing required | Two weeks, and the tail does not matter | Very little. Do not spend sequencing effort here |
The last row is the one teams forget. Sequencing is expensive in attention and coordination. Spend it on the two or three message types where the order genuinely changes the outcome, and let everything else find its own pace.
What this does to measurement
Three measures follow directly from the loss of the shared moment, and none of them is a total.
- Time to reach a threshold. How many hours or days to get to 80 per cent of the addressable population, tracked per message type. This is the number that tells you whether your sequencing worked, and it is comparable across messages in a way that raw reach is not.
- The composition of the tail. Who is still unreached on day five, expressed by function, site or contract type rather than as a count. A tail made of people who were on leave is fine. A tail made entirely of one country or one shift pattern is a structural problem you can fix.
- Cascade evidence. Read rate by team compared with the site average, which tells you where the manager conversation happened and where it did not.
The mechanics of building these across distributed teams are covered in our piece on measuring hybrid work internal communications across distributed teams. The prerequisite for all three is a clean definition of the addressable population, which is a segmentation problem before it is an analytics problem, and our guide to audience segmentation for internal communications covers how to structure the attributes.
The honest position on native reporting
Microsoft 365 gives you a lot of this for free at the single-channel level. Teams reporting will tell you activity in a channel, and SharePoint site analytics will tell you views on a news post[2]. For a team that publishes in one place and wants to know whether last week’s post was read, that is genuinely sufficient and nothing else is needed.
Where it stops is exactly where the hybrid questions start. A time-to-reach curve needs the same person recognised across the intranet, Teams, Viva Engage and the newsletter, otherwise you are measuring four separate curves and adding them. Tail composition needs workforce attributes, which native reporting does not hold. And a comparison against last year’s restructuring needs history that outlives the native retention window. Gallagher’s State of the Sector research keeps finding measurement to be the capability internal communicators rate lowest in themselves[3], and this is a large part of why.
Some teams build the join in Power BI on the Microsoft Graph reporting API[4]. That works when it is resourced properly. The reporting API is not consistently reliable and produces days with missing data, which is particularly damaging for a time-to-reach curve because a missing day distorts the shape rather than just the total. 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, with an owner. Budget for the pipeline, not the dashboard.
Where Tryane fits
Tryane reads SharePoint, Viva Engage, Teams and your newsletter platform as one estate, joins the activity to your organisational structure through Entra ID or an HR file, and keeps history across product transitions. That is what makes a time-to-reach curve, a tail composition and a cascade comparison producible rather than approximated. If your hybrid population includes people who are not at a desk at all, our note on measuring communications that reach frontline workers covers the specifics, and measuring cross-channel internal communications explains why the same person reading in three places must be counted once.
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
Does hybrid work make internal communication harder, or just different?
Different in a way that is genuinely harder for one specific class of message. Routine information is arguably easier now, because people read on their own schedule and the channels are better than they were. Anything where the order of finding out matters, restructuring above all, is much harder, because the shared moment that used to enforce simultaneity no longer exists.
What is a reasonable time to reach 80 per cent in a hybrid organisation?
It depends on the population, which is why the number is only useful against your own baseline. A desk-based population should reach 80 per cent within one working day on a message that matters. A shift-based or field population is usually three to five days, and holding it to the office standard produces a target nobody can hit and a report nobody trusts.
Should we still run an all-hands if half the audience is remote?
Yes, but stop treating it as the moment everyone finds out. Treat it as one event inside a sequence, brief managers before it, and publish a version that reads well for the people who will watch the recording on Thursday. The all-hands is now a signal of importance rather than a distribution mechanism.
How do we know whether managers actually cascaded a message?
Compare read rates by team against the site average over the days following the manager briefing. Teams whose read rate rises noticeably above baseline almost always had the conversation. Teams that track the baseline exactly usually did not. It is an inference rather than proof, but it is a reliable one and it points you at the right dozen conversations.
Can Microsoft 365 native reporting produce a time-to-reach curve?
Per channel, roughly. Across channels, no, because there is no shared identity of a reader across SharePoint, Teams, Viva Engage and your newsletter tool in the native reports, and no join to workforce attributes to define the denominator. You need a layer that recognises the same person across surfaces and holds the organisational structure alongside.
Sources
• Gallup, hybrid work indicator
• Microsoft Learn, Teams analytics and reporting reference
• Gallagher, State of the Sector
• Microsoft Learn, Microsoft Graph reporting API
Further reading
• Measuring hybrid work internal communications across distributed teams
• Measuring cross-channel internal communications
• Measuring internal communications on Microsoft Teams
• Measuring communications that reach frontline workers
• Internal communication KPIs for 2026
Tryane runs a 15-minute call with Heads of Internal Communication, plotting the time-to-reach curve of your last significant announcement and showing who was still in the tail on day five. Book 15 minutes with Jérémy.