Why Meetings Exhaust Some People and Not Others

A ninety-minute block in your calendar with two thirty-minute meetings in it does not contain forty-five minutes of usable focused work. For some people it does, or close to it. For others it contains something more like fifteen minutes of fragmented time that is difficult to use for anything requiring sustained concentration.

The difference has nothing to do with introversion or how efficiently you transition between tasks. It comes from a functional characteristic of how attention works in a specific person, and it interacts with meeting load in ways that have real consequences for whether a job is sustainable.

Interruption recovery time

When you are pulled out of focused work, by a meeting, a message, any interruption, returning to full concentration requires rebuilding the mental context that was present before. For some people this takes two or three minutes. For others it takes twenty to thirty.

Someone who recovers quickly can move in and out of focused work without significant cost. Meetings punctuating the day are an inconvenience. The time between them is usable.

Someone who recovers slowly is not experiencing the same day. Every meeting has a recovery arc attached to it. A role with eight standing meetings per week, each separated by ninety minutes, produces a week where most focused work time is consumed not by the meetings themselves but by the recovery from them. The output may look similar from the outside. The cost is not.

Trying harder to refocus does not shorten the arc. The arc is what it is. Designing the workday around it, which is what long uninterrupted blocks accomplish, addresses it. Most work environments are not designed with this in mind.

People with long recovery arcs in high-meeting environments often develop workarounds. Arriving early to get focused work done before the meeting day starts. Staying late for the same reason. Front-loading demanding work into the narrow windows before the first meeting. These strategies work and they are not a sustainable solution. They move the cost from the workday into time that was supposed to be for recovery. The deficit still accumulates, just on a different schedule.

Meeting count is only part of the picture

Meeting load gets measured in hours per week, which is the right starting point and an incomplete picture.

A standing team sync where you receive updates and have nothing contested or at stake is a low-demand meeting. It costs time and not much else. A client negotiation, a difficult personnel conversation, a presentation to senior leadership where you are accountable for the outcome, a session where you are managing interpersonal tension, these are different. They require sustained attention, significant cognitive effort, often emotional labor, and they do not leave you in the same state they found you.

Two people with identical weekly meeting counts can have completely different experiences of their week depending on what those meetings required. When someone describes being depleted by meetings, the useful question is not how many but what they asked.

Communication volume runs in the background

Meetings are the visible form of organizational demand on attention. Communication volume is the ambient form.

A role where messages arrive throughout the day and rapid response is expected is a role where part of attention stays continuously allocated to monitoring incoming communication. Not the same as a meeting. Similar effect on the availability of focused work time.

Every message is a small interruption, or the anticipatory awareness of one. For someone with a long recovery arc, the combined effect of high meeting load and high communication volume is a workday where focused concentration is structurally difficult regardless of how the calendar is managed. For someone with a short recovery arc, the same conditions are more manageable. Much of the variation in experience between two people in the same role comes down to exactly this.

What postings leave out

Job postings describe meeting requirements with language like collaborative environment and strong cross-functional communication skills. These phrases tell you that meetings and communication exist. They tell you nothing about volume, composition, type, or what a high-demand week looks like.

The questions worth asking before accepting any role are how many standing meetings it carries in a typical week, what a high-demand week looks like and how often one occurs, what the expected response time on messages is, and whether there are norms around protected focus time or continuous availability is the standard.

An interviewer who answers these questions specifically, with actual numbers and real patterns, is describing a role that someone has thought carefully about. An interviewer who responds with collaborative and very communicative without specifics is describing a role where no one has tracked what it actually requires.

If the answer is vague, ask for a concrete one. What did last month look like? What did the most demanding month of the past year look like? The range between a typical week and a high-demand one tells you more than either number alone.

When the load drifts

A role that had six hours of meetings per week when you started may have twelve now. The drift is incremental and therefore invisible.

A standing sync gets added. A project kickoff that was supposed to be temporary stays on the calendar. A cross-functional initiative adds a weekly touchpoint. None of these individually seems significant. Together they consume a meaningful portion of the week, and because the change happened gradually no single meeting feels like the culprit.

If you have never counted the actual meeting hours your current role carries across standing commitments, recurring project touchpoints, and ad hoc requests, doing so once often produces a number larger than expected. That number is a concrete starting point for any conversation about whether the current structure is working, delivered as data rather than as a complaint.

Many organizations will respond to that framing. Some will not. When an organization cannot or will not address meeting load that is structurally untenable for the person doing the job, that is also information. A mismatch the organization is not going to address is a different situation from one that can be restructured.

The autonomy dimension

Meeting load does not operate in isolation. It interacts closely with how much of your time is yours to direct versus reactive to what comes in from others.

A high-meeting role with significant schedule control is a different experience from a high-meeting role where the meetings are largely imposed and the time between them is also filled by reactive demand. Both may have the same count. Only one allows the person to structure remaining focused time deliberately.

For someone who functions well when they can organize their own work and protect the conditions they need, the loss of schedule control that comes with high externally-imposed demand is a separate cost layered on top of the meeting load itself. When evaluating any role, the parallel question to meeting count is how much control the person has over the time that is not in meetings, and whether the organization has any norms around protecting that time.

Making sense of the pattern

Most people assess their meeting situation by how it feels. Feeling is real information and it is hard to analyze systematically. The correlation between specific meeting patterns and specific capacity outcomes stays vague without something concrete to look at.

Tracking meeting hours week over week alongside a simple capacity rating changes that. After several weeks, patterns emerge that feeling alone does not surface. Heavy meeting weeks show up clearly in the data. Weeks that included several emotionally demanding meetings show a different recovery pattern from weeks with the same count of informational ones. Back-to-back demanding weeks show accumulation before it becomes a visible problem.

The Capacity Tracking Tool is built for exactly this kind of tracking. If you want a broader picture of your resilience across the different demands in your life, not just work, the Resilience Reserves Radar maps where your reserves sit and where they are being drawn down. Six to eight weeks of data typically makes clear whether meeting load is driving the cost, which is actionable, or whether it is not the primary driver, which redirects attention to what actually is.

For people who have been in high-meeting environments long enough to normalize them, the exercise of counting the actual hours often produces a number that is both larger than expected and illuminating about why certain kinds of energy do not seem to be available anymore. The load is visible on the calendar, but it is rarely added up.

If what the data reveals suggests a structural mismatch between your meeting load and how you function, the question of whether that is addressable within the current role or requires something different is a specific analysis. Coaching built around the Career Fit framework is useful for working through that, particularly when you have concrete data rather than a general sense that something is off.

The manager dimension

Meeting load interacts with management style in ways that are worth understanding separately.

Some managers run their relationships with direct reports primarily through meetings. Regular one-on-ones, frequent check-ins, standing touchpoints to stay aligned. For someone who recovers quickly and finds this kind of contact energizing, this management style is a feature. For someone with a long recovery arc who works best with a clear brief and then long periods of independent execution, the same management style adds meaningful cost to the week on top of whatever organizational meeting load exists.

This is not a statement about which management style is better. Both exist for real reasons and suit different people. The point is that when evaluating a role, asking specifically about the manager's style, how often they typically check in, what their expectation of communication frequency is, what a productive working week looks like from their perspective, surfaces something that organizational meeting load numbers alone do not capture.

A role with ten hours of standing meetings per week and a hands-off manager who rarely adds to that count is a different experience from the same ten hours with a manager who adds daily check-ins and expects high communication frequency. Both candidates would see the same meeting count in the job description. The actual experience of the week is meaningfully different.

There is also an asymmetry worth knowing about. Roles rarely lose meeting load over time. They accumulate it. A role at eight hours of meetings per week when you join is more likely to be at twelve in two years than at six. Meetings get added, rarely removed, and each addition comes with a rationale that makes sense in isolation. The person in the role adapts incrementally and often does not register the cumulative change until they stop to count the actual hours.

Checking the count periodically, and comparing it to what the role carried when you started, is a simple practice that keeps the picture accurate. The number changing is not automatically a problem. The number changing without the person noticing is.

For people who have been in high-meeting roles for a long time, the normalization runs deep. It is not just that they have stopped noticing the count. They have often reorganized their expectations of what a workday should feel like around the constraints the meeting load imposes. The sense that focused work happens in stolen moments, that real thinking requires arriving early or staying late, that the hours between meetings are too short to use for anything demanding, all of this can feel like the natural condition of the work rather than the product of a specific structural arrangement.

Stepping back far enough to count the hours, and to ask whether that count is compatible with how you actually function, is not always comfortable. But it is more useful than continuing to adapt to conditions that may not need to be accepted.

Meeting load is one of the most measurable dimensions of a job and one of the most reliably misrepresented in hiring. Treating it as a real evaluation criterion, before accepting a role and throughout the time you are in one, changes how you make career decisions.

If this resonates, this is the work I do: helping neurodivergent adults identify what in their environment is generating the friction, and change it.