Ask a remote worker why they're exhausted and workload usually isn't the first answer. It's the scheduling: a string of back-to-back video calls with no walk between rooms, a 7am call for one time zone that's a 10pm call for another, and the constant low-grade tax of figuring out whose morning it actually is. Burnout research increasingly backs this up. It isn't just how much people work — it's how fragmented and coordination-heavy that work has become.
What burnout research actually measures
The World Health Organization's ICD-11, published in 2019, defines burnout specifically as an occupational phenomenon resulting from chronic workplace stress that has not been successfully managed. That's a deliberate framing — not a medical diagnosis, but a response to how work is structured. It matters here because it means burnout isn't purely a personal-resilience problem. It's a structural one, and scheduling is part of that structure.
The meeting-time evidence
The Microsoft 2024 Work Trend Index found that knowledge workers spend an average of 57 per cent of their working time in meetings, email and chat, leaving a shrinking window for focused work. Gallup's 2024 State of the Global Workplace found that employee stress remains near record highs even as engagement scores improve, with schedule unpredictability and after-hours contact among the most commonly cited stressors in remote and hybrid roles.
Context-switching is the hidden cost
Research on task-switching published in the Journal of Applied Psychology has repeatedly found that shifting attention between unrelated tasks carries a measurable cognitive cost: a lag before full performance resumes on the new task, paid again every time a calendar forces a jump from deep work into a call and back again. A remote calendar full of meetings scattered across a global team multiplies this switching cost, because those meetings rarely cluster into a single block. They arrive at whatever hour happens to suit the other time zone.
Slack's own workforce data points the same way
Slack's 2023 Workforce Index found that employees who described their schedules as fragmented reported lower productivity and higher stress than those with consolidated blocks of focus time, even when total hours worked were similar. The problem wasn't the hours. It was the shape of the day.
Why distributed teams feel this more than office teams
An office-based team's meetings are bounded by a shared working day. A distributed team's aren't. Someone is always taking the early call or the late one, and the timezone miss that comes from a scheduling error compounds the problem rather than resolving it — a missed or mistimed meeting doesn't just disappear, it gets rescheduled into whatever gap is left, further fragmenting an already broken day. A look at what timezone confusion actually costs remote teams put the direct cost of a single missed call at £150 to £300 in lost professional time, before counting the rescheduling itself as another fragment stacked on top.
The version of this that never shows up in an engagement survey
Most burnout surveys ask about workload, autonomy and recognition. Almost none ask "how many times this week did you do timezone maths in your head before replying to a message." That's exactly why the scheduling layer of burnout stays invisible in the data that leadership actually reviews — it isn't absent, it's just uncategorised, folded into generic "meeting fatigue" answers that don't point back to a fixable cause.
Is remote work burnout really about meetings?
Not entirely, but meetings and the scheduling overhead around them are a large and measurable share of it. None of the research above says workload doesn't matter — it says that how work is distributed across the day, and how much of that distribution sits outside any one person's control, does real damage on its own. Two people working the same total hours can have very different stress outcomes depending on whether their meetings are clustered or scattered across the day.
Can better scheduling actually reduce burnout?
It won't fix every driver of burnout, but it removes one of the few that's genuinely solvable with better tools rather than a change in workload or headcount. Scheduling a meeting across time zones without a back-and-forth of proposed times nobody has checked against their own calendar removes a specific, recurring source of both wasted time and the low-grade stress of getting it wrong in front of a client or colleague.
What's the single most effective fix?
Removing the manual timezone conversion step entirely. A meaningful share of scheduling fragmentation comes from people doing time-zone maths by hand in the middle of a chat conversation, getting it wrong, and then losing the rescheduling time on top of the original meeting. A tool that shows everyone their own local time automatically, in the conversation where the scheduling is already happening, removes that step rather than asking people to do it more carefully.
Wenya is a scheduling keyboard built for WhatsApp, iMessage and Telegram. It shows each person in the conversation their own local time automatically, cutting out the manual conversion that fragments so many remote calendars. Try it at wenyawanna.ai