Why Video Calls Are More Draining Than In-Person Meetings
Remote workers frequently report that video calls leave them more mentally depleted than in-person meetings of comparable length and intensity. This observation was largely anecdotal until 2021, when Jeremy Bailenson of Stanford University's Virtual Human Interaction Lab published a formal analysis of what he termed "Zoom fatigue" — documenting four distinct mechanisms by which video calls impose unusual cognitive and physiological demands that face-to-face interaction does not.
The first mechanism is continuous eye contact at close range. In normal social interaction, eye contact is intermittent — you look at the speaker, look away to think, break contact naturally and unconsciously throughout the conversation. Video calls eliminate this. Participants maintain eye contact with a large face in a small frame for the entire duration of the meeting, at distances closer than normal social interaction, which triggers a continuous mild threat-evaluation response that is absent in typical conversation.
The second is the demand to monitor your own video image. In a video call, you can see yourself speaking in real time — something that does not happen in face-to-face meetings. Research on self-focused attention shows that this creates a low-level, continuous self-monitoring load that is cognitively expensive and often anxiety-producing. You are managing your presentation while simultaneously trying to participate substantively.
The third is reduced mobility. Physical movement is deeply integrated with thinking — people pace, gesture, turn away, lean in, adjust posture continuously during in-person discussions. Video call norms constrain all of this to a small frame, reducing the physical-cognitive integration that usually supports sustained attention.
The fourth is the cognitive effort of interpreting reduced nonverbal signals. In a video meeting, you are receiving a flattened, compressed version of another person's communication — no peripheral body language, lower audio fidelity, occasional lag, frozen expressions from buffering. Your brain fills in these gaps continuously, which requires more active inference than in-person communication where nonverbal signals are rich and automatic.
Together, these mechanisms mean that a one-hour video meeting depletes cognitive resources more than a one-hour in-person meeting would. The recovery time after a video call is correspondingly longer — and most remote workers do not take it.
What the Brain Is Carrying After a Call Ends
When a video call ends and you click "Leave," the meeting is over as a calendar event. Cognitively, it is not over at all.
The brain is carrying several different types of open loops simultaneously. There are the decisions that were made during the call — some of which were clear, some of which were ambiguous, some of which were implied rather than stated. There are the actions that were assigned — to you explicitly, to you implicitly, and to others who may or may not actually follow through. There are the things said that sparked related thoughts but could not be pursued in the moment. There are the tensions or unresolved questions that the meeting did not fully address. And there is the emotional residue of the social interaction itself — whether the call felt easy or strained, whether something was said that requires a response, whether you said something you wish you had said differently.
When this cognitive load is carried directly into the next task, it functions exactly like the "attention residue" that Sophie Leroy's research documented when switching between tasks: part of the brain's processing remains on the meeting rather than transferring fully to the new task. This produces the characteristic post-meeting work state that remote workers describe as feeling busy but unable to focus — the work is happening, technically, but not at full cognitive capacity.
The Jump-to-Next-Task Mistake
The default remote work pattern is to close the meeting and immediately open whatever is next: email, a document, a task board, Slack. This feels efficient. There is no transition in a remote setting — no hallway walk, no physical movement from one room to another — so the expectation is that work resumes immediately.
What actually happens is that the post-call cognitive load stays active in the background while the nominal next task starts. The work that follows a meeting without a recovery period is slower, produces less output per hour, and creates more errors than work done after a proper processing gap. The time "saved" by jumping directly to the next task is an illusion — it is repaid in lower quality and greater effort for the next two hours.
A ten-to-fifteen minute recovery block is not wasted time. It is a maintenance investment in the cognitive capacity needed for everything that follows.
The Ten-Minute Capture: What to Write and in What Order
The recovery block has a specific sequence. Do not improvise it in the moment — the sequence is the tool.
The first two minutes are for decisions. Write every decision that was made in the meeting, even ones that seemed obvious. Decision memory degrades quickly, especially when subsequent tasks carry their own information. Specific format: a complete sentence stating the decision. "The project deadline moved to the 15th" is useful. "Deadline thing" is not. "Client prefers option A over option B for the homepage layout" is useful. "Design preference" is not. The specificity matters because vague notes do not resolve ambiguity when you return to them in three days.
The next three minutes are for actions. Write every action that belongs to you — using verbs. "Send the updated brief to Maria by Thursday." "Schedule the follow-up with the technical team for next week." "Review the proposal draft and send comments by Friday." Add a date or timeframe where one was mentioned or implied. If an action was implied rather than stated explicitly, write it anyway — implied responsibilities are the most common source of professional missed expectations.
The next two minutes are for anything open that the meeting raised but did not resolve. A question worth thinking about. A concern worth flagging. An idea the meeting sparked that deserves its own slot in your work. These go in a separate "follow-up thoughts" section — not your action list, because they are not tasks yet. They are seeds of potentially useful thinking that will evaporate if not noted.
The final three minutes are for assigning everything to its place. Actions go into whatever task system you use, with dates. Decisions go into the relevant project or client file. Follow-up thoughts go into an ideas file or the relevant document they belong to. The capture note itself can then be deleted or archived — its contents have been placed where they can actually be found and acted on.
Decisions vs. Actions: The Distinction That Prevents Confusion Later
The distinction between decisions and actions sounds obvious but is consistently collapsed in practice, and collapsing it creates specific problems.
A decision is a settled outcome of the meeting: "We are proceeding with the second approach." "The timeline extends by two weeks." "Budget for this is confirmed at X." Decisions require recording but do not require work from you — they are context you need to maintain.
An action is a specific next step requiring someone to do something: "Sarah will send the contract to the client by Tuesday." "I need to revise the scope section." Actions require scheduling and follow-through.
When decisions and actions are mixed together in the same notes, you return to them and cannot immediately tell what requires your attention versus what is just context. This ambiguity creates cognitive overhead every time you review the notes. Separating them in the capture eliminates that overhead permanently — your action items are clean and immediately processable, your decisions are reference material, and you do not waste time re-interpreting your own notes.
A third category worth noting separately is open questions: things the meeting raised without resolving. "Legal team needs to confirm the IP clause." "We are not sure yet whether the Q3 target is realistic." These belong in neither the decision nor the action section — they are outstanding uncertainties that someone owns, or no one owns, and they need to be followed up differently from tasks you personally own. Writing them separately prevents them from being forgotten when they dissolve into the general meeting notes.
The Physical Break: What Actually Helps (and What Keeps You in the Same State)
After the capture, a physical break is the second component of the recovery block. The word "break" understates what this is for: it is specifically for reducing the physiological activation that video calls produce.
Eye contact, self-monitoring, and constrained mobility all produce mild activation responses that do not end the moment the meeting ends. A transition activity that involves physical movement and does not require social attention or screen use is what actually starts to resolve this activation. Standing up, walking around the home or building for a few minutes, looking out a window at a distance (which relaxes the eye muscles that have been in close focus for the entire call), and drinking water are all genuinely useful.
What does not help: opening social media, checking email, scrolling anything. These maintain the attentional pattern of the meeting — rapid information processing, social input, response evaluation — without any of the physical reset. You arrive at the next task equally activated and additionally loaded with whatever the inbox contained. It feels like a break because you stopped the explicit meeting-related work. It is not a break in any functional sense.
A five-minute walk is more restorative than fifteen minutes of scrolling. This is not an opinion — it is what the physiology of activation and recovery predicts, and what experience reliably confirms.
Returning to Work: One Task, Not the List
When you return from the physical break, do not look at your full task list. Looking at a full task list after a draining meeting activates the same decision-making overhead that precedes any work session — what should I do first, is this more important than that, am I spending my time on the right thing. That overhead is the last thing a cognitively depleted post-meeting brain handles well.
Instead, decide on the one task before taking the physical break, while your short-term memory of the meeting's outputs is still fresh and you can choose the most relevant next step clearly. When you return, that task is already chosen. You sit down and start it. The decision is not made again.
The task should be specific enough to start immediately: not "work on the proposal" but "write the scope section of the proposal based on what was agreed in today's call." The connection to the meeting's outcomes provides natural momentum — you have immediate context for the work, the meeting just provided it, and the first ten minutes of the task are often the most productive because the relevant information is still active.
The Multi-Meeting Day: How to Protect Remaining Deep Work Time
For remote workers with heavy meeting schedules, the recovery block raises a scheduling concern: if there are four meetings in a day and each one requires a fifteen-minute recovery block, where does the deep work go?
The answer is that it does not go in the gaps between meetings — those gaps are, at best, fifteen minutes of recovery time and at worst nothing at all. Deep work after a draining meeting, without a recovery block, is low-quality work that creates the illusion of productivity without producing proportional results.
The practical scheduling principle is to cluster meetings rather than distribute them across the day. Two hours of consecutive meetings followed by a single twenty-minute recovery block costs less total deep work time than two meetings separated by two hours, each of which degrades the deep work time that surrounds it. Back-to-back meetings feel worse in the moment — you lose the intermission where you could check things and decompress — but they protect larger, uninterrupted blocks of time for the work that requires sustained cognitive attention.
When clustering is possible, protect one block in the day — ideally morning, before meetings begin — that has no meetings, no calls, and no interruptions. That block should receive the most cognitively demanding work of the day. Everything else, including the meetings and the recovery blocks and the follow-up actions, fits around it rather than displacing it. The recovery block is what makes this possible by preventing the meeting's cognitive overhead from bleeding into work that happens hours later.
