The Real Data on Remote Meeting Fatigue Across Time Zones

Ask remote workers to name their biggest struggle, and time zones don't win. Look at what's actually happening to meeting schedules instead, and time zones look like the dominant force reshaping the workday. Both of those things are true at once, from two different published data sources — and the gap between them is the more interesting finding.

What people say the problem is

Buffer's State of Remote Work survey asks remote employees directly what their single biggest struggle is. Time zones come in well behind the top complaints: 21%say their biggest struggle is staying home too often without a reason to leave, 15%cite loneliness, 11% say not being able to unplug — and working across time zones lands at just 14% naming it as their single biggest issue (19% mention it as a struggle at all, even if not the biggest one). By self-report, time zones are a real but mid-tier complaint, well behind the emotional and lifestyle costs of remote work generally.

What's actually happening to the calendar

Microsoft's 2025 Work Trend Index measured meeting patterns directly rather than asking people to self-diagnose the cause, and the picture looks different. 30% of all meetings now span multiple time zones — an 8 percentage point increase since 2021, meaning roughly a third of everyone's meeting load is now cross-zone by default rather than the exception. Meetings starting after 8pm are up 16% year-over-year, and chats sent outside the standard 9-to-5 window are up 15% year-over-year, averaging 58 messages per person landing before or after normal hours. Nearly 20% of employees who work weekends are checking email before noon on a Saturday or Sunday.

Why the two data sets disagree

The likely explanation isn't that one survey is wrong — it's that time zone cost doesn't arrive as a single, nameable event. Nobody experiences "a time zone problem"; they experience one 8pm call this week, one early message to answer before the school run next week, one weekend email check that felt normal in the moment. Each individual instance gets absorbed into a broader, vaguer feeling — chaos, fragmentation, not being able to unplug — rather than getting attributed back to its actual structural cause. This tracks with the rest of Microsoft's data: 48% of employees and 52% of leaders describe their work as chaotic and fragmented, and workers report being interrupted roughly every two minutes during core hours. Time zone spread isn't absent from that picture — it's diffused across it, uncredited.

This is the exact mechanism behind the scoring approach in the fair rotation formula: a single fringe-hour meeting doesn't feel like a crisis, so it never gets flagged as one — it's only when the cost is tallied explicitly, across weeks, that the pattern becomes visible. Self-report surveys ask people to name their biggest single struggle; they're not well suited to catching a cost that's spread thin across dozens of small, individually-forgettable instances.

Putting a number on the diffused cost

Take the 30%-of-meetings-cross-zones figure and run it through the meeting cost calculator framework: if a mid-size team runs, say, 15 meetings a week and roughly a third are now cross-zone, that's 4–5 meetings a week where at least one attendee is statistically likely to be in fringe or rest hours rather than working hours — using the working=0/fringe=1/rest=3 pain weighting from the rotation formula, that's a recurring, compounding cost that a per-meeting dollar figure alone doesn't capture, because it's paid in sleep and context-switching rather than payroll. The after-8pm-meetings-up-16% and after-hours-chats-up-15% figures are two independent signals pointing at the same underlying trend: as teams get more globally distributed, the workday isn't just getting longer on average — it's getting more asymmetric, with the cost landing disproportionately on whoever is in the "wrong" time zone for a given call.

What this means for how you read your own team's data

If you ask your own team what their biggest complaint is, don't be surprised if time zones don't top the list — Buffer's data suggests it usually won't, even on teams where it's structurally the biggest driver of after-hours work. The more reliable signal is the one Microsoft's report measured directly: look at what fraction of your team's meetings actually cross zones, and how many messages land outside core hours, rather than relying on people to correctly self-diagnose a cost that's designed to feel like background noise rather than a single named problem. Run your own team's actual meeting schedule against the SyncHours planner to see the working/fringe/rest breakdown directly, rather than waiting for it to show up as a complaint in an engagement survey.

Sources: Microsoft Work Trend Index Special Report, "Breaking Down the Infinite Workday," June 2025 (microsoft.com/worklab). Buffer, State of Remote Work 2023 (buffer.com/state-of-remote-work).