Most Meeting Problems Aren't Logistical. They're Cultural

There's a particular kind of exhaustion that sets in around Wednesday afternoon when you look at your calendar and realize you've spent much of the week in meetings and somehow have less clarity than when the week started.

This is when people start talking about needing fewer meetings, better agendas, and stricter time limits. And those things can help. But in my experience working with teams, the problem usually runs deeper.

What most teams are missing isn't a meeting template. It's a shared set of agreements about when gathering as a team is worth it, who actually needs to be there, and what it means to show up well when you do.

Without those agreements, the same patterns usually repeat: meetings that run long not because people are inefficient, but because there's no shared norm around pacing. Conversations that drift into minor agenda points because nobody has the standing to redirect, and minor points that you thought you’d sail past, take up most of the energy and space. Calendars that fill up because scheduling a call feels easier than building a system that would make the call unnecessary.

These aren't calendar problems. They are cultural problems.

Two Questions Worth Asking Before You Schedule Anything

Priya Parker, in The Art of Gathering, makes the case that most gatherings fail before they begin because the host never got clear on why the gathering should exist at all. A topic isn't a purpose. "Q3 budget review" is a topic. A purpose is the reason people need to be in the same room, and what they should leave with that they didn't have before.

She's equally clear on who needs to be there. Most leaders default to inviting everyone who might be affected or might feel left out. Parker pushes back on this. Over-inclusion is often conflict avoidance masked as generosity. Not being in the room doesn't mean not being valued. It might just mean this particular conversation isn't the right use of your time.

Cal Newport adds a different perspective. He argues in Deep Work and A World Without Email that organizations underestimate the actual cost of meetings. It's not just the hour on the calendar. It's the mental wind-up before, the fragmentation of the day around it, the recovery time after. His question before any meeting: Is this worth an hour of five people's deep thinking? Not "does this have some value?" The bar should be whether the benefit justifies the real cost.

Together, these become a useful two-part filter before anything gets scheduled:

• Does this meeting have a real purpose (and have we clearly defined it), and have I been honest about who actually needs to be there?

• Does it require real-time conversation, or am I defaulting to a meeting because it's easier than building something better?

Most meetings that feel necessary can't cleanly answer both.

Once You've Decided to Meet, You Still Have to Design It

Deciding a meeting should happen is only half the work. The other half is designing how the

conversation will actually function, and most teams skip this completely.

For many organizations, open discussion is the norm, but often isn't actually democratic. In practice, it usually means the most vocal or senior person shapes the outcome while others disengage or defer. The meeting felt collaborative (especially to the most vocal or senior people), but often, the thinking didn't take advantage of the best ideas in the room.

Small structural shifts change this. Having people write silently before discussing, using timeboxed responses to distribute airtime, and making priorities visible through dot voting or post-its. When people know exactly how they're expected to engage, they engage more. Structure liberates participation rather than restricting it. 

It also helps to separate the role of facilitator from participant. Someone should be running the meeting rather than simply being in it. The facilitator's job is to protect the process, not contribute content. That difference, usually left implicit, is worth making explicit, because it’s really hard to do both.

The Case for Structure and "No-Meeting Day."

Your calendar is a reflection of your values, just as your budget is. What gets scheduled, how often, and with whom says something real about what your organization actually prioritizes, whether or not that matches what you say you prioritize. If your calendar is full of reactive, unplanned meetings, that's worth paying attention to. And if the people you lead need a lot of unplanned access to you, it's worth exploring from a place of genuine curiosity about what your team needs that they aren't getting another way. One practical response is to build in office hours: a dedicated window when people know they can bring questions, problems, or decisions that need your input. It protects both your focus and their access.

Protecting time on the calendar is how that intention becomes real. What organizations that have tried no-meeting days consistently find isn't just that people feel less busy. It's that they think more clearly and produce better work. And it's diagnostic. When you watch what rushes in to fill the protected time anyway, you learn something about your culture: what people feel they can't communicate any other way, and what decisions people don't feel empowered to make on their own.

Some organizations take it further. No-meeting weeks, particularly when a team is deep in a project and needs time to focus, can create the kind of uninterrupted time that a single protected morning can't.

One organization I work with structures its professional development time on a fixed monthly cadence: the first Monday for DiSC and culture and communication work, the third for learning and sharing practices around AI. Everyone can plan around it. The time has a purpose, and people know how to show up for it. That predictability turns what could feel like another thing on the calendar into something people actually look forward to.

A no-meeting day, a no-meeting week, a protected Monday morning: the specific structure matters less than the intention behind it. If your calendar reflects your values, it should have room in it for thinking, not just talking.

Different Meetings Need Different Designs

One of the most useful things Patrick Lencioni argues in Death by Meeting is that organizations fail partly because they run every type of meeting through the same format. A standup works best when it's short and consistent. A working session needs facilitation and a small group. A decision meeting needs clear options and a visible decision rule, not more discussion. A brainstorm needs divergent space before evaluation. A meeting meant to build culture and connection needs food and room to actually focus on each other. And a status update, more often than not, doesn't need to be a meeting at all.

The Feedback Loop Most Teams Are Missing

Most teams don't have a shared language for feedback or talking about meeting behavior. Without one, the same patterns repeat because there's no low-stakes way to name what's happening.

The goal isn't policing. It's enough shared vocabulary that someone can say, without it feeling like a critique, "that felt more like a discussion than a decision," and have everyone know what that means. Real change in meeting culture rarely comes from reading about it. It tends to come from practicing new structures together and from the team building shared agreements, rather than a leader announcing new policies.

Questions Worth Sitting With

What unspoken rules currently govern your meetings, and does your whole team agree on them?

If every meeting you scheduled this week had to pass the Parker-Newport test, how many would

survive?

What would make it safe for anyone on your team to give honest feedback when a meeting didn't work?

Better meetings don't start with a better agenda (although it doesn’t hurt). They start with a shared belief that everyone's attention is worth protecting, and a culture deliberate enough to hold that belief.

Have questions, thoughts, or want to dive deeper? Reach out! hello@eddyline-coaching.com