In 2021, researchers named it "Zoom fatigue" and published papers about why video calls were more exhausting than in-person meetings. The explanation that got the most attention was the mirror effect — seeing your own face constantly creates self-monitoring anxiety. Other explanations involved the cognitive load of processing non-verbal cues through a compressed digital medium.
All of that is real. But most teams have misdiagnosed the actual cause of the fatigue, which means they've implemented the wrong fixes.
It's not the screen. It's the performance.
When you're on a video call, you're not just participating in a meeting. You're performing attentiveness. You're watching your face to make sure it looks engaged. You're managing your background. You're thinking about whether you should have turned off your camera or whether that would look rude. You're monitoring the audio lag and waiting for the right moment to speak so you don't interrupt someone who's already started talking on a two-second delay.
None of this happens in an in-person meeting because none of it needs to. Physical presence is self-evident. You don't have to perform being there when you're clearly there. Video calls require you to demonstrate presence constantly, and that demonstration is tiring in a way that the meeting content itself usually isn't.
Teams that've gone to four or five video calls a day have essentially asked their people to perform continuous attentiveness for four to five hours. That's not sustainable regardless of how interesting the meetings are.
What async-first teams do differently
The answer isn't better video call hygiene, though that helps at the margins. The real difference in async-first teams is that video calls are rare and intentional. When they happen, people want to be there because it serves a specific purpose that couldn't be served asynchronously. The calls are short because the information has already been shared and the agenda is tight. There's no performance anxiety because the call is actually valuable and everyone knows it.
The ratio matters. A team that has one genuinely necessary video call per day and handles everything else async is in a fundamentally different situation than a team that has five video calls, four of which could have been an async update. The fatigue isn't linear — it compounds. One unnecessary call doesn't just waste thirty minutes, it taxes the attention reserve needed for the next three hours.
The async video difference
This is where async video as a format is specifically valuable, separate from just "not having a call." When you record an async video update, you record it once, when you're ready, without the pressure of a live audience. You can retake it if you misspoke. You can be conversational and direct because you're not managing anyone else's reactions in real time.
The person watching it has the same advantage: they watch when they have the capacity for it. They can pause and come back. They don't have to perform attentiveness for an audience. They can watch it at 1.5x speed if they're short on time. They get the context without any of the presence tax.
This is not a minor quality-of-life improvement. Teams that use async video consistently report meaningfully lower fatigue levels, not because they're staring at a screen less, but because they're performing presence less. The cognitive load of synchronized collaboration is higher than people realize until they remove it.
What companies keep getting wrong
The most common "fix" for screen fatigue is shorter meetings and camera-optional policies. Both help, but neither addresses the structural issue. Shorter meetings reduce the symptom. Camera-optional policies reduce one specific source of the performance pressure. But if the fundamental model is still "we coordinate primarily by having everyone available at the same time," the fatigue will continue in a slightly more manageable form.
The second common mistake is assuming that fewer scheduled meetings means less screen time overall. Often it doesn't, because unscheduled calls — "can we jump on a quick call?" — fill the gap. Quick calls are often worse than scheduled ones because they're unplanned, they interrupt focused work, and they end without a written record of what was decided. Teams that ban recurring meetings but still have a culture of quick calls are not async-first. They're just async-flavored.
The working day shape change
One pattern that emerges in genuinely async-first teams: the shape of the working day changes. Instead of a series of calls with blocks of "between meetings" time, the day becomes mostly deep work with a few focused synchronous interactions. People have long stretches of time for concentrated work. They check their async channels at a few points during the day and respond when there's something to respond to. The texture of a good day feels different.
Most people who've worked this way for a few months say it's the first time in years they've been consistently tired at the end of a day in a good way — tired from thinking hard and getting things done, not tired from eight hours of attention management.
That's not a small thing.