How to Run a Meeting People Don't Hate

Most meetings are bad. Not occasionally bad. Not bad when they run long or when someone goes off topic. Structurally, fundamentally bad. The average professional spends 31 hours per month in unproductive meetings, according to a frequently cited Atlassian study. That’s nearly four full workdays per month spent in rooms (or Zoom calls) that don’t produce decisions, don’t advance projects, and don’t justify the collective salary cost of everyone sitting there.

The reason is almost always the same. Nobody is clearly in charge. Someone schedules a block, invites too many people, opens with “so, what are we talking about today,” and spends the next 45 minutes watching a conversation wander between three topics while half the room checks email behind their laptop screens. The meeting ends with a vague sense of alignment and no concrete next steps. The same topics reappear in the next meeting because nothing was actually decided in this one.

Milos Eric, entrepreneur and Forbes Human Resources Council member, reframes the problem in terms that cut through the dysfunction: “Think of it not as just running a meeting. The goal is to host an event that makes people think it was worth their time.”

Decide What the Meeting Is For Before You Invite Anyone

If you can’t articulate the desired outcome of the meeting in one sentence, don’t schedule it. This is the filter that eliminates the majority of unnecessary meetings. “Decide whether to launch feature X this quarter” is a meeting. “Align on Q2 priorities” is a meeting. “Discuss the project” is not a meeting. It’s a conversation that will become a meeting only if someone defines what the conversation is supposed to produce.

Three types of meetings serve distinct purposes, and confusing them is how most meetings fail. Decision meetings exist to make a choice between options. Alignment meetings exist to get everyone on the same page about direction. Information-sharing meetings exist to disseminate updates. Each type requires a different format, a different attendee list, and a different duration. Combining all three into one hour-long block guarantees that none of them gets done well.

Invite Fewer People Than Feels Polite

Every additional attendee adds drag. More people means more perspectives to reconcile, more tangents to manage, more schedule constraints to navigate, and more collective salary wasted when the meeting could have been an email.

Amazon’s two-pizza rule (if you can’t feed the meeting with two pizzas, there are too many people) has been endlessly cited for a reason: it works. Include only the people essential to the outcome. Everyone else can read the summary. This feels rude until you realize that most people would rather receive a two-paragraph email than sit through a 30-minute meeting they didn’t need to attend. You’re not excluding them. You’re respecting their time.

Set the Agenda and Send It in Advance

Outline the topics. Allocate rough time blocks. Send the agenda before the meeting, ideally the day before. This accomplishes three things simultaneously. It forces you to think through the structure before you walk into the room. It forces attendees to prepare (if they read it). And it gives everyone permission to move the conversation along when a topic runs past its allocated time, because the agenda provides a shared reference point for what’s supposed to happen when.

An agenda-less meeting is a conversation with a calendar invite. It feels productive because people are talking, but talking without structure produces discussion, not decisions. The agenda is the structure. Skip it and you’re hoping the conversation organically arrives at something useful. Hope is not a strategy.

Start on Time, End Early

Starting late signals that punctuality doesn’t matter. Every minute you wait for stragglers tells the people who arrived on time that their respect for the schedule is less important than the convenience of the people who didn’t share it. Start at the scheduled time. Every time. Without exception. The stragglers will adjust their behavior when they realize they’re missing context, not when you send a passive-aggressive Slack message about punctuality.

Ending early signals that their time matters to you. If you scheduled 30 minutes and you’ve covered everything in 23, give them seven minutes back. Don’t fill the remaining time with filler. Don’t open the floor for “anything else.” End the meeting, send the summary, and let people return to the work the meeting was supposed to support.

Control the Pace Without Dominating

The meeting runner’s job is to guide, not to lecture. Surface viewpoints from quieter attendees. Redirect when the conversation drifts. Summarize key points periodically so everyone tracks the same thread. Interrupt gently but decisively when someone is taking the discussion off course. Park off-topic items in a “parking lot” for later follow-up rather than allowing them to hijack the current discussion.

The balance is between facilitation and domination. A meeting runner who talks for 80% of the time isn’t running a meeting. They’re giving a presentation that they incorrectly formatted as a collaborative discussion. A meeting runner who says almost nothing except “let’s move to the next topic” and “here’s what I heard” is facilitating effectively.

Close With Decisions and Next Steps

Recap what was decided. Name who owns each action item. Set deadlines for follow-ups. If a meeting ends without clear next steps, the meeting didn’t accomplish anything. It just felt like it did. The feeling dissipates within an hour. The lack of next steps persists until the topic surfaces again in the next meeting, where it will receive the same treatment.

Send the summary within 30 minutes of the meeting ending. Written summaries create accountability in a way that verbal recaps don’t, because a written record can be referenced when someone claims they weren’t aware of a decision or a deadline.

When Not to Hold a Meeting

If the goal is sharing information that doesn’t require discussion, send an email. If the goal is collecting feedback, use a shared document with comment permissions. If the goal is a simple status update, use a messaging channel. Meetings exist for decisions and alignment. Everything else is a meeting that shouldn’t exist, consuming hours that could be spent on the work the meeting was supposed to advance.