Rethinking Meeting Necessity

Welcome to Making Meeting Preparation Count! Throughout this course, you'll develop essential skills to turn meetings from time-wasters into powerful tools for team collaboration and decision-making. This isn't about adding more process or bureaucracy—it's about using proven strategies to ensure every meeting you lead or attend has a clear purpose, delivers real value, and respects everyone's time.

Research shows that managers spend a significant portion of their workweek in meetings, and many report that a large percentage of these gatherings are unproductive. This course will change that reality for you and your team. You'll discover how to determine when meetings are truly necessary, craft agendas that drive meaningful discussions, optimize meeting duration for maximum impact, and ensure the right people—and only the right people—are in the room.

In this lesson, you'll explore practical frameworks from the HBR Guide to Making Every Meeting Matter, featuring insights from leading experts like Elizabeth Grace Saunders and Al Pittampalli. By mastering these skills, you'll confidently navigate the common meeting challenges that plague most organizations: endless status updates that could have been emails, overcrowded rooms where decisions stall, and vague agendas that waste everyone's time. More importantly, you'll model meeting excellence that elevates your entire team's performance and gives them back precious hours for actual work.

The phrase "Let's schedule a meeting" has become the universal default response to most business issues. However, scheduling a meeting isn't always the best answer. Here is a systematic decision tree approach to evaluate whether gathering people together is truly necessary.

The evaluation begins with a fundamental question: Have I thought through this situation? If you haven't gained clarity about what you're doing on a project, scheduling a meeting to give yourself the feeling of progress is an inefficient use of everyone's time. Instead of rushing to gather people, invest time in strategic thinking first. This means evaluating the project scope, understanding its current status, identifying potential milestones, and laying out your action plan. Only after this essential preparation should you consider whether a meeting makes sense.

Once you've done your thinking, the next question becomes Do I need outside input to make progress? Sometimes the path forward is clear, and you know exactly what needs to be done—you simply need to execute. In these cases, updating your to-do list and taking action is far more productive than scheduling a meeting. However, if you genuinely require outside input to answer critical questions or get feedback before moving forward, then you should continue evaluating whether a meeting is appropriate.

The third critical question asks Does moving forward require a real-time conversation? Many situations that seem to need meetings actually don't require synchronous communication at all. For instance, if you need feedback on written plans or documents, email can be far more efficient than gathering everyone in a room. Your colleagues can review materials at their own pace, provide thoughtful written responses, and avoid the awkwardness of reading documents while others watch during an in-person meeting. When you don't have clarity about your project but schedule a meeting anyway, "unless the meeting's intent is to structure the project, scheduling a meeting is probably an inefficient use of your time—and your colleagues'." This decision-making framework radically reduces unnecessary meetings while ensuring the meetings you do schedule have clear purpose and genuine value.

Once you've determined that a real-time conversation is necessary, consider whether it truly requires face-to-face interaction. This evaluation has become even more critical in our hybrid work environment where bringing people together physically requires significant time, effort, and often considerable expense.

The key insight here is that two-way conversations don't automatically mean needing to see the person. An asynchronous chat can help you resolve questions in minutes that might otherwise require scheduling an hour-long meeting. For more in-depth conversations, a phone call or video conference frequently works just as well as meeting in person. These alternatives offer practical advantages beyond mere convenience. They save transition time by eliminating walks to and from meeting rooms, and they allow you to continue working productively if someone runs late, rather than sitting idle in a conference room waiting for stragglers to arrive.

Let's see how this evaluation plays out in practice:

• Jessica: Hey Victoria, I think we need to get everyone together in the conference room this afternoon to discuss the Q3 budget revisions.
• Victoria: Before we schedule an in-person meeting, do you think we could handle this over a video call or even through email? What exactly do we need from the group?
• Jessica: I need input on where we can cut costs, but I suppose people could review my analysis and send their feedback online.
• Victoria: Exactly. If there are conflicting views or we need a real-time discussion, we could set up a short video call with just the key decision-makers. That way, we save everyone the trip and still get what we need.

To make the right choice, consider your goals: Are you brainstorming where body language matters, building relationships needing personal interaction, or simply exchanging information that could be done through other channels? Many managers default to in-person meetings out of habit, missing opportunities to save time. If face-to-face interaction is genuinely required, ensure it is worthwhile by preparing thoroughly and respecting everyone's time, as in-person meetings disrupt focused work and require mental transition time.

Meeting problems stem partly from linguistic confusion. We call everything a "meeting," whether it involves two people or two hundred, and whether we're making decisions or just sharing updates. This vague terminology makes it difficult to set appropriate expectations, prepare effectively, or even understand what we're being invited to attend. By using more precise language, you can dramatically improve your team's meeting culture and efficiency.

Consider breaking down the term "meeting" into more specific categories:

• Conversations: Meetings with just two people are actually conversations. Unlike formal meetings that require agendas and documented outcomes, one-on-one discussions can remain casual and flexible. They aren't "weapons of mass interruption"—those larger gatherings that derail productivity.

• Group Work Sessions: When people gather to execute work together, such as programmers collaborating on code or writers crafting content, these are group work sessions, not meetings. Group work sessions require tools for collaboration and an environment that supports deep focus without interruption, since it's difficult to make real progress on tasks while also trying to hold a meeting.

• Brainstorms: If the primary goal is generating ideas, call it a brainstorm, not a brainstorming meeting. Brainstorms need different preparation, such as warm-up exercises and an atmosphere that encourages creativity without judgment.

There are also some common problematic patterns:

• Convenience Meetings: These save time for one person by wasting everyone else's, like when information could have been shared via email.

• Formality Meetings: These occur out of tradition rather than need, treating the meeting as a given and then searching for topics to justify its existence.

By using precise language to define these gatherings, you can question their value and potentially eliminate unnecessary meetings, transforming meeting culture and reclaiming productive time.

Now that you've learned these foundational frameworks for evaluating meeting necessity and types, you'll have the opportunity to apply them in realistic scenarios. In the upcoming tasks, you'll practice using the decision tree to assess actual meeting requests, evaluate whether face-to-face interaction is truly needed, and implement precise meeting terminology to improve team communication and efficiency.