Photo by Chris Montgomery on Unsplash
Stanford Research Explains and Helps Prevent Zoom Fatigue
Zoom fatigue. We all know it’s a real thing—it’s exhausting to spend more than an hour or so in a videoconference, and for many people working and attending school from home, those video sessions can go for six or more hours per day. Jeremy Bailenson of the Stanford Virtual Human Interaction Lab has now identified four reasons why video chats are so tiring, and he offers suggestions for avoiding their worst effects. In short:
- Close-up eye contact is intense. You’d never be so close to someone’s face in real life, so try using gallery view and reducing the size of the window. Talking postage stamps are less likely to make you feel like someone is up in your face.
- Looking at yourself is stressful. Staring at yourself in a mirror—and worrying if you look OK—for hours per day would cause insanity, and yet that’s what we do in many videoconferencing platforms. Once you’ve verified that you’re properly framed and have brushed your hair for the day, hide your preview or switch to a view that doesn’t include it.
- Sitting still is hard. When meeting in person or talking on the phone, we move around, even if it’s just adjusting position in a chair. Keeping yourself framed in a video window dramatically reduces your mobility, so try turning off your video at times or positioning your camera such that you can fidget or pace as you would in person.
- Video chats have a high cognitive load. Videoconferencing encourages all sorts of odd behaviors that require some level of active thought. For instance, keeping yourself framed in the video chat, using a thumbs-up to indicate silent approval, and trying to interpret everyone else’s reactions all require cognitive processing that doesn’t come naturally. The solution is to give yourself an audio-only break, both sending and receiving, so you can let your brain rest.
Read the full article for more details, plus an encouragement to participate in a study of the new Zoom Exhaustion & Fatigue Scale, which aims to measure how much fatigue people experience in the workplace from videoconferencing. The results from the study could help videoconferencing companies change their apps to make them less exhausting.
If it is permitted by your organization, consider not using video.
Where I work, we’ve been using Microsoft Teams for remote meetings for several years. We rarely turn on video. Most calls are audio only, with the presenter sharing his screen or a PowerPoint presentation. This allows us to focus on the content and not on personal appearances.
Of course, this may not always be permitted (e.g. a classroom environment), in which case, the tips presented in the article sounds like a great idea.
I’m really looking forward to trying the tips from Stanford, though I’m lucky in that I don’t have to have that many video calls. That said, I think video is way overused. It’s obviously powerful and necessary in a lot of cases, but on many calls, particularly when the number of people is relatively low, the stream of primary importance is audio. Whenever I’m having an audio-only call, I pace, do mindless things like folding laundry or weeding the garden, or just watch the birds visiting the birdfeeder. All of which help me focus more on what’s being said.
Bandwidth limits video on NASA Teams calls (NASA has banned, barred and disabled Zoom like many US federal agencies). Often attendees are asked to turn off video on Teams. On big calls with over 100 attendees, agency IT asks us to turn off agency VPN, saying that constrains bandwidth even more. This is a dire directive: normally we cannot log in to NASA servers without using VPN, and we must restart VPN if a connection exceeds 24 hours.
In light of this research, it may have been a good thing for bandwidth issues to decrease use of video in NASA Teams meetings.@ace Adam I’d be interested in your findings on using these tips from the Stanford research. Please keep communicating … as you’ve done so well for over 30 years.
P.S.
Welcome back, sponsor Rogue Amoeba. While I’m not an audio person, their tech has always been top capability and quality … a rare combo. Also I’ve always loved that their founder’s title is “CEO and Lackey”.
EDIT: In fairness, I should say that bandwidth is a limiter for NASA because of all the people working from home with their variable quality internet connections. But I still think NASA’s servers bear responsibility as well – if an internet user can stream Netflix, shouldn’t that be enough to stream Teams or Zoom? The question is real: I would welcome responses.
I love it when I hear that some MS product is being pushed for “security reasons”.
At my wife’s work they like to act super paranoid about security (large medical device company handling lots of patient data → HIPPA). But half the company is using some ancient version of IE on the oldest Windows release they can still get updates for.
Back in the olden days when I worked for GM/Opel we did a lot of phone conferences. Nobody ever asked about “phone conference fatigue”. There were only 2 rules:
Sounds like the skills my father tried to teach us to survive ‘polite’ company. Be able to:
Yawn with your mouth shut
Sleep with your eyes open
Avoiding video calls is the one good thing about having a really slow connection. Gee, I’d like to, but it’s simply not possible…
It’s not quite comparable, since Teams or Zoom will require upstream bandwidth as well, whereas Netflix only needs downstream, and that’s usually a much larger pipe. I also don’t know how Teams would be provisioned for an organisation like NASA—would it be large enough to have an on-premises Teams server, or is it all really Microsoft’s cloud?
Of course, there’s an argument to made that NASA should be thinking hard about low-bandwidth communications given the distance to places like Mars. :-)
NASA comprises Headquarters at Washington DC and 10 major field centers. Each field center, including Marshall Space Flight Center where I work, has its own infrastructure for Teams and many other server-based applications. This is so each center and headquarters is self-sufficient for “within center” major Teams meetings or other cloud-based and server-based functions. All infrastructure from field centers is rolled up to administrative oversight at NASA Headquarters itself.
Disclaimer: I am a major technology geek going back decades learning from Adam and Tonya Engst: therefore I understand a lot of issues. However I certainly do not speak for NASA in any official sense; I’m just sharing what I perceive based on what I’ve learned from capable IT people.
On low bandwidth applications, just look up what the communications capabilities were with the Apollo missions! I’ll bet you it was something like three baud.
Even today, the deep space network used by NASA among others operates on S band and Ka band frequencies. The transmission capability remains at analog modems, especially because signal quality decays as the square of distance between communications transceivers! I do not have numbers, but anyone who looks it up will laugh at them. This excludes satellite TV and internet because you’re not operating at interplanetary distances.
And remember that the power budget for a transceiver is even more stringent then communications. Top engineers at Goddard and JPL make good salaries for any given satellite or probe to balance power vs communications. Many such operate(d) with power a fraction of that of a standard lightbulb. Remember that in space, you’re physically limited in the small power sources you can bring with you.
Microsoft’s Office365 business services (which Teams is a part of) may be hosted by Microsoft’s cloud servers, or they may be hosted by the customer’s corporate data center. I’ve worked at companies that chose to host their own instances of Microsoft’s servers (Exchange, SharePoint, etc.) and at companies that chose to use Microsoft’s cloud servers.
As a user, you shouldn’t notice a difference, because the Microsoft cloud URLs redirect to your corporate servers when you login using a corporate user ID, but this is of course, only theory. Server and network availability and capacity is never identical and they vary throughout the day.
I hope nobody is trying to conference in from Mars.
The bandwidth may or may not be an issue, but the latency will kill you. Round-trip times between 8 and 48 minutes, depending on how the Earth and Mars orbits align.
Microsoft has now done some research into what happens in your brain when doing too much videoconferencing. Hint: you get stressed out.