Meeting design, when the calendar is a symptom, not the problem

Good morning. At some point this week you will sit in a meeting that didn't need to happen, or didn't need to be as long as it was, or covered things that could have been handled in a two-line message. This is not an unusual experience. Many leaders would name their meeting load as one of their biggest productivity frustrations.

But the problem is rarely the meetings themselves. It's that most of them have accumulated, without thoughtful design, without review, and, often, without anyone finding real value in them. Yet, many leaders haven't realised that the way their team's time is structured is a choice they've already made, and one they can easily make again.

Leaders probably already know there's inefficiency in this part of the work system. They know the Thursday all-hands runs too long. They know the weekly check-in has become a status update nobody particularly needs. They know the weekly site-visit arrives with no one prepared. They already know. And yet the meetings stay as-is in the schedule. Not because they're working or people feel they're invaluable, but because cancelling one feels like a signal that the thing it covers, or the people in it, doesn't matter, and nobody wants to send that message.

So the calendar keeps filling. And the work fits around it.

You might recognise some of these:

None of these are unusual. They're simply what happens when a team's meeting rhythm has grown organically, rather than been strategically designed to serve actual needs.

Steven Rogelberg, an organisational psychologist who has studied workplace meetings more extensively than almost anyone, finds that meeting overload is one of the leading contributors to employee fatigue and disengagement, and that quality matters as much as quantity. More meetings don't produce better coordination. Better meetings do.

One thing his research surfaces consistently: leaders tend to underestimate the cost of meetings to the people in them.

From a management perspective, an hour-long meeting is a unit of work. For someone doing concentrated, complex work, a developer, a writer, an analyst, a designer, an hour-long meeting in the middle of the afternoon doesn't cost an hour. It often costs the rest of the afternoon. The meeting itself takes sixty minutes. The recovery, getting back into the thinking that was interrupted, takes considerably longer. When that happens across a week, the accumulated cost is significant, and it rarely shows up anywhere obvious.

Between a meeting that makes a decision and one that shares information that could have been an email or another type of asynchronous update. Between a weekly check-in that keeps the team coordinated and an hour-long status update where most people are waiting for the five minutes relevant to them. Between synchronous collaboration where the room genuinely needs to think together, and synchronous attendance where the thinking could have happened another way.

When those distinctions aren't made, the meeting becomes a catch-all. And the calendar fills accordingly.

The case for better meeting design is often made in terms of time saved. That's real, but the more important case is about what good collaboration actually requires.

Teams don't collaborate well by default. Collaboration, done well, not just done, is cognitively demanding. It requires trust, psychological safety, and conditions that most workplaces don't deliberately create. Anita Woolley's research on collective intelligence links to Amy Edmondson's work on psychological safety, and found that the teams who consistently outperform aren't the ones with the highest average individual intelligence. They're the ones where more people contribute, where listening is as active as speaking, and where social sensitivity, genuine attention to what others are bringing, is high.

Meetings, designed well, are one of the primary places that quality of collaboration can happen. Not because getting in a room together is inherently generative, but because some work genuinely requires real-time thinking together: listening to and building on each other's ideas, surfacing disagreement safely, working through complexity that a document or a message can't resolve. The question is not whether to meet. It's whether the time you're spending together creates the conditions for that kind of thinking and discussion, or whether it's just coordination wearing collaboration's name.

That distinction is important because when meetings aren't designed for real collaboration, they don't just waste time, they also make good collaboration harder to come by. The signal gets lost in the noise of everything else the calendar is prioritising.

Purpose. Every meeting should have a single clear purpose that couldn't be better served by a different format. Information sharing is often better as a written update people can read when it works for them. Decisions need the right people present and a clear process for reaching them. Problem-solving requires real time and cognitive space, not a slot at the end of a packed agenda. If you can't name the purpose and desired outcome in one sentence before you schedule it, it's worth pausing to rethink.

Attendance. More people in the room rarely means better decisions. It usually means more time consumed and less clarity produced. The question for every meeting: who genuinely needs to be here, and who would be better served by a summary afterwards? Being removed from a meeting you don't need to attend is not a demotion. It's someone treating your time as worth protecting.

Rhythm. Your team's recurring meeting pattern, what runs weekly, fortnightly, monthly, is a structural decision that shapes how everyone experiences their work. A poorly designed rhythm creates constant context-switching and the feeling of perpetual motion without progress. A well-designed one creates space for both coordination and concentrated work. It's worth asking, at least once a year: if we were designing this from scratch, would we make the same choices?

Workflow. A meeting is rarely the whole picture. The most effective synchronous, collaborative time is built on what happens before it and what happens after, both of which are asynchronous.

Before the meeting: a clear purpose shared in advance, so no one arrives cold. Context, data or information that participants can absorb on their own time, so the session isn't spent getting everyone to the same starting point. A question or decision framed specifically enough that people can actually think about it before walking in. This is not extra overhead, it's what makes the synchronous time worth having.

After the meeting: decisions documented clearly, so they don't resurface as questions two weeks later. Actions assigned with owners and timelines, not left as a loose conversation thread. A short written summary the people who weren't in the room can actually use. This is where the value of the meeting compounds or evaporates, and it almost always happens asynchronously.

When a meeting is designed this way, as the synchronous node in an asynchronous workflow, with preparation before and follow-through after, the time together becomes more focused, more useful, and genuinely easier to justify. The goal is not fewer meetings. It's meetings that are worth the time they take from everything else.

This is where most leaders get stuck. They can see the problem but aren't sure how to move it without making it awkward.

When cancelling a recurring meeting: "I'm going to stop scheduling this one. I think we can do this differently, here are my ideas [insert recommendations and reasoning]. If you think there's something the meeting was doing that I've missed, please tell me."

When redesigning one: "I want to change how we run this. Here's what I'm thinking, [new format, shorter length, different attendees]. Let's try it for a month and see if it's working better."

When removing someone from a meeting they don't need to attend: "I'm going to take you off this one. You'll get a summary of anything that needs your attention. I'd rather give you the time back."

The framing that matters in all three: you're making a deliberate choice, not making a judgement about what anyone's contributed.

When did it last produce something, a decision, a change, a shared understanding that couldn't have happened another way? If the honest answer is "I'm not sure," that's worth knowing.

Meeting design is not a productivity hack. It's a signal about what you think your team's time and attention are worth.