Burnout in Distributed Teams

Burnout is not a remote-work phenomenon. Remote work changes the conditions under which it develops and, more importantly, removes the signals that would have caught it earlier.

Why it stays hidden longer

In an office, someone in trouble is visible. They look exhausted, they stop joining conversations, colleagues notice and mention it.

Remotely there is a rectangle on a call and completed work. A person can deteriorate substantially while output holds, because the first thing that goes is not productivity — it is everything outside work. By the time output drops, the situation is well advanced.

Managers routinely report being surprised. That surprise is structural, not negligence.

The conditions remote work creates

No boundary. The commute served a function: a physical transition marking the end of the day. Without it, work bleeds until the person decides to stop, which under pressure means later.

Always reachable. The laptop is in the next room. Checking messages in the evening is easy, feels harmless, and prevents the day ending.

Isolation. Difficulty that would have been shared over lunch is carried alone.

No visible workload. Colleagues cannot see the queue, so requests keep arriving. The person absorbing them looks fine because absorbing is invisible.

Meeting density. Back-to-back calls with no gaps are more depleting than the office equivalent, and calendars fill more easily when there is no travel between rooms.

What to watch for

None of these is proof. Each is a reason to ask.

Activity late at night, consistently. Occasionally is normal; every night for a month is not.

Holiday not taken, or taken while still working.

Withdrawal from anything optional. The first thing to be dropped is contact that is not required.

Camera off after months of camera on.

Shorter, flatter written communication. People under strain write less and warmly less.

Work that is technically complete and lacking care.

Someone who never says no. Frequently the person closest to trouble.

What managers should do

Ask directly and then be quiet. "How are you actually doing?" followed by a pause long enough to be uncomfortable. Asked in passing and moved past, it produces "fine".

Look at their calendar and workload yourself. Do not rely on them to report overload; the people most overloaded are the least likely to raise it.

Remove something concretely. Sympathy without a reduction in work is not help. Take something off them, name what it is, and tell whoever else needs to know.

Model boundaries visibly. A manager who messages at 11pm has set the norm regardless of what they say. Scheduled sending costs nothing and removes most of the implicit pressure.

Protect time, not just hours. Someone with a calendar of consecutive calls has no working time, whatever their contracted hours say.

Make holiday real. Cover arranged, handover done, and a visible expectation that they are not reachable.

Where the obligation sits

Beyond the human case, several jurisdictions treat psychosocial risk as within health and safety duties, and some have specific requirements about workload, rest and out-of-hours contact.

Framing this as an obligation rather than a wellbeing initiative tends to change how it is resourced, which is a practical argument for doing so.

What does not help

Wellbeing apps and resilience training offered to someone whose workload is the problem. It communicates that the difficulty is their capacity to cope rather than the volume of work, and people read that accurately.

If the cause is workload, the response is workload. Everything else is decoration.