Video Call Fatigue Isn't About Video: What the Research Actually Shows

"Zoom fatigue" gets treated as a single, vague phenomenon — video calls are tiring, full stop — but the research that actually studied it found something more specific and more fixable: the fatigue isn't caused by video as a medium, it's caused by a handful of identifiable mechanics that video conferencing tools happen to default to. That distinction matters, because it means the fix isn't "have fewer video calls," it's "fix the specific things video calls do that in-person conversation and audio calls don't."

What the research actually identified

Stanford's Virtual Human Interaction Lab, led by Jeremy Bailenson, published a 2021 framework identifying four specific mechanisms behind video call fatigue, not video generally:

• Excessive close-up eye contact. In-person conversation involves natural gaze breaks — glancing away, around the room, at notes. A video grid puts every participant's face at a close, fixed distance with sustained mutual gaze the whole call, which the brain processes as a much more intense social signal than it's used to sustaining continuously.
• Constant self-view. Seeing your own live video feed for the entire meeting is roughly equivalent to being followed around by a mirror all day — a cognitive load that doesn't exist in any in-person conversation and that most video tools default to leaving on.
• Reduced mobility. In-person meetings and phone calls allow pacing, stretching, and general movement; video calls implicitly demand staying framed in the camera, which removes a normal physical outlet for restlessness.
• Higher cognitive load from nonverbal signaling. Gestures, nods, and expressions have to be exaggerated to register clearly on camera, and read carefully by everyone else — both directions cost more effort than the equivalent signal does in person.

Why this framing changes the fix

If the diagnosis were "video itself is tiring," the fix would be fewer video calls — which conflicts directly with the value video actually provides for the synchronous, high-ambiguity conversations described in the async-first decision framework. Since the real mechanisms are specific and mostly tool-configuration problems, the fix is cheaper and doesn't require giving up video's actual benefits for the meetings that need it.

Concrete fixes mapped to each mechanism

Camera-on norms vary by culture, and that's a separate axis

Camera-on expectations aren't just a personal-preference question — they track cultural norms around the same high-context/low-context spectrum covered in high-context vs low-context communication. In some high-context cultures, camera-off can read as disengaged or even disrespectful; in others, constant camera-on for internal working sessions is seen as unnecessary formality. A team spanning both norms benefits from an explicit, stated policy — "cameras optional for internal working sessions, expected for external and all-hands calls" — rather than leaving each person to guess what an unstated default signals about their engagement.

A default policy worth adopting

1. Hide self-view by default across the team's video tool, not as an individual opt-in setting.
2. Default to speaker view, not full gallery, for calls over 5–6 participants.
3. Explicitly allow audio-only for one-on-ones and status calls that don't need a shared screen.
4. Build a buffer between back-to-back meetings — even a short one — rather than scheduling calls edge to edge.
5. State the camera-on expectation explicitly per meeting type, rather than leaving it as an unstated cultural default that different teammates read differently.