DEV Community

Sannan Malik
Sannan Malik

Posted on

Meeting Fatigue Is Real. Here's What's Actually Causing It (and How AI Helps)

Meeting fatigue isn't about video. Researchers who initially attributed the exhaustion of remote work to video calls — "Zoom fatigue," as it was widely labeled — have since found a more complicated picture. The camera isn't the main culprit. The structure of the meetings, or the lack of it, is.

What actually causes meeting fatigue

Context switching. Most knowledge workers move between meetings with no buffer. The cognitive cost of shifting from a technical review to a client call to a strategy discussion, back-to-back, accumulates in a way that a single long meeting doesn't.

Low signal, high noise. Meetings where attendees don't know why they're there, decisions never get made, or topics drift without resolution aren't just a waste of time — they're actively draining. The brain works hard tracking a conversation that goes nowhere.

The burden of being "on." Video adds a specific layer: the awareness of being seen, managing your own image (the self-view problem), and the social obligation to appear engaged even when the content doesn't require it.

Post-meeting overhead. The meeting ends, but the work doesn't. Someone needs to write the notes, send the follow-up, debrief stakeholders who weren't there, and track the action items that came out of it. That invisible overhead falls unevenly across teams.

What makes it worse on distributed and global teams

Remote and hybrid teams have amplified every one of these factors. More meetings happen because fewer decisions are made in passing. Async coordination gaps get patched with synchronous calls. And for global teams with language differences, the cognitive load of following a meeting in a second language sits on top of everything else.

Non-native speakers in a meeting aren't just listening — they're translating, processing and responding simultaneously. The fatigue that creates is different in kind from what native speakers experience, and it rarely shows up in satisfaction surveys because it's rarely named.

Where AI actually helps — and where it doesn't

AI isn't a cultural fix. If your meetings are poorly structured, have unclear ownership, or exist because your organization hasn't learned to communicate asynchronously, adding an AI summary tool will give you a more organized record of a bad meeting.

That said, there are specific fatigue vectors where AI genuinely reduces load:

Note-taking anxiety. Many people attend meetings half-listening, half-documenting, fully not doing either well. When notes are generated automatically, attention can go fully on the conversation. That's not a small thing.

The "what was decided" loop. The cycle of following up, re-checking, and re-litigating decisions because there's no reliable written record is exhausting. AI-generated recaps with structured decisions and action items break that loop.

Translation overhead. For non-native speakers, per-participant live translation — the kind where each person reads in their own language, not a shared second language for the room — reduces cognitive load in a way that a monolingual transcript doesn't. Tools like MeetOye build this into every call, so it's consistent rather than something the host has to configure per meeting.

Post-meeting documentation. Automatically emailed recaps replace the half-hour one person spends reconstructing the meeting from memory afterward. That half-hour, multiplied by meeting frequency and team size, is real recovered time.

What HR teams should actually measure

Meeting fatigue doesn't show up cleanly in engagement scores. If you want to actually understand it:

  • Meeting load per person: total hours in meetings per week, not just count
  • Meeting-to-outcome ratio: how many meetings produce a clear decision or action vs. status updates and discussions with no output
  • Post-meeting time cost: who is doing the recap, debrief and follow-up work, and how long it takes
  • Participant role distribution: are most attendees active or passive? High passive-attendee rates signal a list problem (too many people invited) or a structure problem (no clear reason to be there)

The goal isn't to eliminate meetings. It's to make the time in them worth the cognitive cost — and to reduce the invisible overhead that happens after them.


Author bio:
The MeetOye Team writes about people operations and the future of work. MeetOye (meetoye.com) is an AI-native video meeting platform that automatically transcribes, translates per participant, and emails a recap with decisions and action items when every call ends.

Top comments (0)