Fewer Meetings Won’t Fix Your Calendar—but Smarter Ones Will

I remember a Tuesday in late winter, stuck in a conference room with twelve other people, watching someone click through a slide deck they’d clearly never opened before. The meeting was blocked for an hour. The call it was supposed to produce could have been settled in six paragraphs and a short email thread. Later, I ran the numbers: between salaries, prep time, and the mental cost of task-switching, that single hour burned somewhere north of $2,000. Nothing shifted that afternoon except my conviction that we’ve got a meeting problem—and the fix isn’t just fewer meetings. It’s better ones.

I’m Farah Adebayo, and I think a lot about how people actually work together. Not in that abstract, productivity-guru way, but in the messy, real-world sense where calendars are permanently double-booked and a “quick sync” grows into a 90-minute detour. Over the last few years, I’ve watched team after team treat meetings as the default way to collaborate. I’ve also watched those same teams burn out, not from the work itself, but from the work about the work. This piece is my attempt to lay out a research-informed, perceptive case for why we need to rethink the meeting from the ground up—and how to do that without losing the human connection that a good meeting can still deliver.

Group of professionals sitting around a table engaged in discussion

The Hidden Price of Too Many Gatherings

Back in 2022, researchers from the University of North Carolina and the University of Texas at Austin published a study in the Journal of Applied Psychology that put numbers to something many of us feel in our bones. They tracked over 600 employees across two organizations and found that time spent in meetings had crept up steadily since the 1990s. Middle managers now average nearly 35 hours a month in scheduled gatherings. More telling was the correlation: once you cross a certain line—roughly 20 hours a month for individual contributors—each extra hour of meetings comes with measurable dips in engagement and spikes in fatigue. It’s not just grumbling. It’s a real drain, both physiologically and psychologically.

A big part of the mechanism is what’s called attention residue. When you switch from a meeting back to focused work, your brain doesn’t snap neatly into place. Sophie Leroy, an organizational behavior scholar, coined the term to describe how thoughts about the last task hang around and trip up your performance on the next one. A 30-minute meeting followed by another 30-minute meeting isn’t two interruptions; it can shatter an entire afternoon. And yet, in too many organizations, the standard response to any snag is still “let’s get everyone in a room.”

Think about the pattern: a project stalls, so someone calls a status meeting. That meeting reveals two people haven’t read the brief, so another meeting gets scheduled to “align.” That alignment meeting then surfaces disagreements that demand a third meeting with a senior decision-maker. By the time the real work resumes, the team has spent more hours coordinating than doing. It’s not just inefficient—it’s demoralizing. People want to feel competent, and a calendar clogged with meetings that don’t produce visible progress eats away at that sense of competence.

Rethinking What Gathering Is Even For

When the problem is too many meetings, the itch is to swing hard the other way: cancel all recurring meetings, declare “meeting-free Fridays,” and hope the issue sorts itself out. In practice, that almost never works. The underlying need for coordination, feedback, and social connection doesn’t vanish. It just goes underground, popping up in ad-hoc Slack threads, hallway conversations, or—worse—passive-aggressive email chains that eat just as much time with less transparency.

What we need is a sharper definition of what a meeting is actually for. Drawing on work by organizational psychologist Adam Grant and others, I’ve come to see meetings as falling into three honest categories: decisions, creative problem-solving, and relational maintenance. Almost everything else—status updates, information sharing, document reviews—can be handled asynchronously. A status update doesn’t need a meeting; it needs a well-structured doc or a short recorded video people can watch on their own schedule. When you reserve synchronous time for the things that genuinely benefit from real-time human interaction, the meetings that remain become more purposeful.

Two colleagues in a modern office having a focused conversation by a whiteboard

This shift takes cultural change, not just a policy memo. Managers have to model the behavior: declining meeting invites that lack a clear agenda, asking “can this be an email?” without it sounding like a brush-off, and publicly recognizing someone who makes a thoughtful asynchronous contribution. It also means building the skill of writing clearly and concisely, because async communication only works when people can articulate context without leaning on the crutch of a live conversation.

The Agenda as a Small Act of Respect

One of the most consistent findings in meeting research is that agendas improve outcomes. A 2019 meta-analysis by LeBlanc and Nosik reviewed decades of workplace studies and found that agendas were linked to higher perceived meeting effectiveness, faster decisions, and greater participant satisfaction. But the quality of the agenda matters a lot. A vague bullet list (“Discuss Q3 results”) is barely better than nothing. An effective agenda spells out the decision to be made, any background reading required, and the role of each person in the room. It turns a meeting from a passive information-receiving exercise into a focused, participatory event.

I’ve seen teams try out what I call “decision-first” agendas. Instead of warming up with context, they open with the exact question that needs answering: “Should we extend the pilot program to the European market by June 1?” Everything in the meeting then circles that question. If someone veers off into the weeds, the facilitator gently steers back: “That’s interesting, but does it help us answer the question on the table?” This discipline can feel stiff at first, but it respects everyone’s time and cognitive resources. Over time, it teaches the team to prepare more thoughtfully because they know the meeting won’t tolerate rambling.

Designing Around Human Attention

Meetings are, at bottom, a human attention economy. Every minute someone spends in a meeting is a minute they’re not spending on deep work, creative reflection, or even rest. And human attention isn’t bottomless. Cognitive psychologist John Sweller’s work on cognitive load theory reminds us that our working memory can only juggle a few pieces of information at a time. When a meeting is overloaded with slides, side conversations, and multi-threaded discussions, it overwhelms that capacity and leads to poor decisions.

One practical move is to shrink the size of meetings. Back in 2013, researchers at the University of Nebraska found that decision-making quality starts to slip noticeably once a meeting grows past seven participants. Beyond that number, social loafing kicks in—people assume someone else will carry the cognitive weight—and airtime gets dominated by a handful of voices. I’ve started nudging teams toward a “two-pizza rule” variant: if you can’t have a meaningful conversation with everyone in the room, you’ve got too many people. For larger gatherings, consider a “silent start” technique where everyone reads a shared document for the first ten minutes before discussion opens. This levels the information playing field and gives quieter voices a chance to form thoughts before the extroverts take the floor.

Person writing notes in a notebook during a calm, focused work session

Another principle borrowed from attention research is the value of breaks. The brain’s capacity for sustained focus fades after roughly 45 to 50 minutes, yet meetings are routinely scheduled for 60 or 90 minutes. The last 15 minutes of a long meeting are often where decisions get rubber-stamped without real scrutiny. A simple fix: schedule 45-minute meetings by default, or build in a five-minute silent reflection period before the final discussion. This isn’t about being rigid; it’s about working with the grain of how our brains actually function.

Relational Meetings and the Case for Showing Up

Not all meetings are about decisions or problems. Some are about people. In remote and hybrid setups, the water-cooler chats that used to build trust have largely disappeared. Replacing them with structured “team building” can feel forced, but ignoring the relational side altogether leads to transactional, brittle working relationships. Research on social cohesion in teams consistently shows that groups with higher interpersonal trust communicate more candidly, resolve conflicts faster, and report greater well-being.

The trick is to be intentional about these gatherings and to label them honestly. Don’t disguise a relational check-in as a status update. If the point is to reconnect, say so. A 30-minute virtual coffee where the only agenda is “how are you actually doing?” can be more valuable than a dozen forced-fun activities. I’ve watched teams adopt a practice of “walk-and-talk” calls, where both people agree to take the conversation outdoors and treat it as a break from screens. The physical movement seems to unlock a different kind of conversation—more reflective, less performative. It’s a reminder that meetings are, at bottom, human interactions, and they should feel human.

Building a Culture That Guards Deep Work

Cal Newport’s writing on deep work has gone mainstream, but its application to meeting culture is still underappreciated. Deep work demands long, uninterrupted blocks of concentration. A calendar shattered by 30-minute meetings scattered across the day makes deep work nearly impossible. The answer isn’t just individual time-blocking; it’s a collective agreement on protected periods. Some organizations have rolled out “no-meeting Wednesdays” or “maker mornings” (before noon) with measurable bumps in output and morale. But the specifics matter less than the principle: the organization has to collectively decide that certain hours are sacred for focused work and then enforce that norm.

This can feel countercultural when clients or partners expect instant replies. I’ve found that transparency helps. A simple note in an email signature—”I check messages at 10 a.m. and 3 p.m.; for urgent matters, call”—sets expectations without requiring real-time availability. When teams see that deep work is respected and protected, they start treating their own calendars with more care. They begin to ask, before scheduling anything, “Does this need to be a meeting, and does it need to happen now?”

Measuring What Actually Matters

If we’re serious about improving meetings, we need to measure their quality, not just their quantity. Most organizations track meeting hours as a cost metric, but that tells you nothing about whether the meetings were effective. A simple post-meeting pulse—two questions: “Did this meeting help us make progress?” and “Did you have the information you needed to participate?”—can surface patterns over time. One engineering team I observed used this data to kill a weekly “sync” that had been running for two years. The average usefulness rating was 2.1 out of 5. No one had thought to ask before.

Measurement also helps push back against the meeting-as-status-signal dynamic. In many workplaces, a crowded calendar gets worn like a badge of importance. When the organization starts valuing meeting effectiveness over meeting volume, that dynamic shifts. Being in fewer meetings becomes a sign of disciplined prioritization, not disengagement. It’s a cultural transformation that takes time, but it starts with leaders modeling the change and celebrating it openly.

Practical Steps You Can Start Tomorrow

Changing meeting culture doesn’t take a massive initiative. It can start with a handful of small, concrete experiments. Here are a few I’ve seen work across different types of teams:

  • Audit your recurring meetings. For one week, tag every meeting on your calendar as “decision,” “problem-solving,” “relational,” or “other.” At the end of the week, cancel or convert everything in the “other” bucket. Most status meetings land here.
  • Institute a “no agenda, no meeting” policy. If the organizer can’t spell out the purpose and desired outcome in three sentences, the meeting isn’t ready to be scheduled.
  • Experiment with async stand-ups. Use a shared document or a short video tool where each person posts their update by 10 a.m. Reserve synchronous time only for blockers that need real-time discussion.
  • Cut the default meeting length. Change your calendar settings so meetings default to 25 or 45 minutes instead of 30 or 60. The extra buffer between meetings lowers cognitive switching costs.
  • Designate a “meeting-free zone.” Pick one half-day per week where no internal meetings are allowed. Protect it collectively and watch what happens to the team’s output.

These steps aren’t draconian. They’re experiments in respecting human attention and time. The goal isn’t to wipe out meetings entirely—some of my most rewarding professional moments have happened in well-run, high-stakes collaborative sessions. The goal is to make meetings earned, not automatic.

The Long View

When I think about the future of work, I picture organizations where meetings are treated as precious, not plentiful. Where the default answer to “should we meet?” is “not unless we have to.” And where, when we do gather, we bring our full attention because we know it counts. This isn’t some utopian fantasy; it’s a design challenge. We’ve got the research. We’ve got the tools. What we need is the collective will to stop confusing activity with progress.

That $2,000 meeting I sat through last winter didn’t have to happen. The call could have been made faster and with less friction through a well-written document and a single round of comments. But the system was set up to reward meeting attendance, not meeting outcomes. Changing that system is doable, and it starts with each of us asking, before we click “schedule”: what is this actually for? And could we accomplish it better another way?

Frequently Asked Questions

How many meetings per week is too many?

Research suggests that for individual contributors, more than 10–12 hours of meetings per week starts to correlate with reduced engagement and increased fatigue. Still, the quality of those meetings matters as much as the quantity. A few well-run, purposeful meetings can be energizing; a dozen poorly structured ones will drain you. The real trick is to track not just hours but your own energy and output. If you feel like meetings are keeping you from your core work, it’s worth an audit.

What’s the single most effective change to improve meeting quality?

A clear, specific agenda distributed at least 24 hours in advance is the highest-impact change most teams can make. The agenda should state the meeting’s purpose, the decision to be made, any required pre-reading, and each person’s role. When attendees show up prepared, meetings stay focused, run shorter, and produce better outcomes. This one practice shifts the meeting from a passive information dump to an active working session.

Should we eliminate all recurring meetings?

Not necessarily. Some recurring meetings—like weekly one-on-ones or monthly strategy reviews—serve ongoing relational or strategic functions that benefit from a regular rhythm. The danger is when recurring meetings stick around out of habit rather than purpose. A good habit is to set an expiration date on every recurring meeting (say, every three months) and require a short review to renew it. That prevents calendar bloat while keeping the gatherings that genuinely add value.