How to Run an Effective Meeting: A Leader's Playbook

MomUp Career Resources

This Meeting Could NOT Have Been an Email

Most professionals do not hate meetings. They hate meetings that waste their time.

They hate meetings without a clear purpose. Meetings dominated by updates that could have been shared in writing. Meetings where the same three people do all the talking. Meetings that end without a decision, an owner, or any idea of what happens next.

The problem is not just that people spend too much time in meetings. It is that too many meetings fail to produce enough value to justify the time they consume. Atlassian's research found meetings are ineffective 72 percent of the time, and 78 percent of workers say they attend so many meetings it is hard to get their actual work done.

The effect compounds fast. Microsoft's 2025 Work Trend Index found that heavily scheduled employees are interrupted every two minutes during core working hours by meetings, emails, and messages, and that 60 percent of their meetings are unscheduled or ad hoc.

A well-run meeting, though, can do what an email or Slack thread cannot: bring the right people together to make a decision, solve a complicated problem, surface disagreement, or do real work in real time. The goal is not to eliminate meetings. It is to be far more selective about when to hold them and far more disciplined about how to lead them.

First, decide whether you need a meeting

Before you send an invitation, ask: what needs to be different after this meeting? If you cannot answer that clearly, you are not ready to schedule it.

A meeting earns its place on the calendar when people need to interact in real time to make a consequential decision, solve an ambiguous problem, generate and evaluate ideas, resolve disagreement, coordinate interdependent work, discuss something sensitive, or build trust.

A meeting is usually unnecessary when the purpose is a routine status update, information that requires no discussion, a review of a document people have not read, straightforward feedback collection, announcements, or reporting metrics without acting on them.

Microsoft's research found only 35 percent of employees believed they would be missed in most of their meetings, and the top reason people considered a meeting worthwhile was simply receiving useful information. Many organizations are still using live meetings as information-delivery systems when written updates, recordings, or dashboards would work better.

The testDoes this work require conversation, collaboration, or a decision right now? If no, use an asynchronous format.

Define the outcome, not just the topic

"Marketing update" is a topic. "Decide which two campaigns get the remaining Q4 budget" is an outcome. "Discuss hiring" is a topic. "Agree on the final responsibilities, salary range, and interview panel for the new director role" is an outcome.

A useful invitation tells participants what they will accomplish, not just what they will discuss. Try completing this sentence: by the end of this meeting, we will have __________. Selected one of three vendors. Identified the cause of the implementation delay. Agreed on next quarter's three priorities. Assigned owners and deadlines for the launch.

A clear outcome helps people understand why they are attending, what preparation is required, and when the conversation is done.

Invite the people who need to contribute, not everyone who might be interested

Every additional attendee raises the cost of the meeting: more schedules to coordinate, more perspectives to manage, less airtime per person, and blurrier individual responsibility. Invite people who fall into at least one of four categories:

  1. Decision-makers: authority to approve or commit
  2. Contributors: knowledge or perspective that is necessary
  3. Implementers: will carry out the decision
  4. Facilitators: needed to guide the conversation or document the outcome

Everyone else gets the notes afterward. Do not invite someone merely for visibility. Visibility can be provided asynchronously. And make attendance expectations explicit: required for the decision, expected to give input, optional, or informed only. Giving people permission to decline irrelevant meetings is not rude. It is responsible leadership.

Create an agenda that requires action

A list of broad subjects is not an agenda. An effective agenda frames each item as a question to answer, a decision to make, or work to complete.

Instead of "sales update, hiring, website, other business," use: What caused the decline in qualified leads? Which candidate moves to the final interview? Which website revisions must be done before launch? What risks need escalation before Friday?

For every item, note the question or outcome, the person leading it, the time allocated, any pre-reading, and whether it needs discussion, input, or a decision. Harvard Business Review's guidance on agenda design recommends setting clear expectations, helping participants prepare, and allocating time by importance rather than treating every item equally.

Sample: 45-minute decision meeting

Purpose: Select the CRM platform the company will implement.

Desired outcome: Choose one vendor and confirm the implementation owner.

Preparation: Review the vendor comparison and submit questions by Tuesday.

  • 0:00 to 0:05: Restate the decision criteria
  • 0:05 to 0:15: Clarify outstanding questions
  • 0:15 to 0:30: Discuss tradeoffs and risks
  • 0:30 to 0:38: Make the decision
  • 0:38 to 0:43: Assign implementation responsibilities
  • 0:43 to 0:45: Review decisions and next steps

Notice that most of the meeting is reserved for the work that requires people to be together. Information gathering happens beforehand.

Send pre-work people can actually complete

Pre-work is useful only when it is necessary, brief, easy to find, sent early enough to complete, and clearly connected to the outcome. Do not attach a 40-page deck the night before and call it preparation. Tell participants exactly what to do:

Say it like thisPlease review pages 2 through 5 and add your recommendation to the document by Wednesday at noon. Come prepared to discuss the two remaining risks.

If people repeatedly arrive unprepared, do not assume they are disengaged. Your preparation process may be unrealistic: too long, unclear deadline, or no visible reason why it matters.

Open by creating focus

Do not spend the first ten minutes waiting for stragglers or asking everyone what they want to cover. Begin on time and establish four things: why the meeting is happening, what outcome you need, what has already been decided, and how the conversation will work.

A strong openingWe are here to decide whether to delay the launch or reduce the initial scope. We have 40 minutes. I want to spend the first 15 clarifying the risks, the next 15 evaluating the two options, and the final 10 making the decision and assigning next steps. The launch budget is already fixed, so we are not reopening that question today.

That gives the group boundaries and keeps the meeting from drifting into adjacent issues it cannot resolve.

Facilitate the conversation instead of controlling it

The leader's job is not to talk the most. It is to help the group produce the best result: keep the conversation tied to the goal, invite useful disagreement, prevent a few people from dominating, clarify vague statements, separate facts from assumptions, name decisions as they happen, and move side issues elsewhere. Atlassian's research found dominant voices frequently make it hard for other attendees to contribute.

Use specific prompts rather than "does anyone have thoughts?"

  • "What risk are we underestimating?"
  • "What evidence would change your recommendation?"
  • "Jordan, you work most closely with this process. What are we missing?"
  • "I would like to hear from anyone who has not spoken yet."
  • "Before we decide, what is the strongest argument against this option?"
  • "Are we disagreeing about the facts, the priorities, or the proposed solution?"

Do not confuse silence with agreement. Junior employees, remote participants, and subject-matter experts may need a deliberate invitation into the conversation. For high-stakes questions, ask everyone to write down their view before open discussion begins. This keeps the first or most senior speaker from anchoring the whole conversation.

Manage time without cutting off the important work

A meeting that ends on time but fails its purpose is not efficient. Time management should protect the outcome, not just the clock. State how much time remains, close discussion when the question is answered, interrupt repetition, park unrelated issues, name it when the group lacks the information to decide, and end early when the work is done.

A useful interruptionI am hearing the same two arguments repeated. Before we continue, what new information would help us resolve this?

Schedule meetings for the time the work requires, not because your calendar defaults to 30 or 60 minutes. And end five or ten minutes before the hour when you can. Microsoft's brain research found back-to-back virtual meetings increase stress, while short breaks help people reset and engage.

Make the decision explicit

Many meetings feel productive in the moment but create little movement afterward. Everyone leaves with a slightly different idea of what was decided. Before moving to the next item, state the conclusion: "The decision is to proceed with Vendor B, pending legal approval of the data-processing terms." Then confirm who owns the next step, what they will deliver, by when, who else must be involved, and where the decision gets recorded.

Avoid "we should look into that," "someone will follow up," and "let's keep moving on this." Use concrete language: "Priya will send the revised agreement to Legal by 3 p.m. Thursday. Marcus will confirm the implementation timeline by Monday."

End with a two-minute recap

Reserve the final minutes to review decisions made, open issues, action items, owners, deadlines, and whether another meeting is needed. Ask participants to correct the recap in real time:

A good closeWe selected Vendor B. Priya owns the contract review by Thursday. Marcus owns the implementation plan by Monday. The data-migration question stays open and will be resolved in the project document, not another meeting. Is anything inaccurate or missing?

Then end. Do not undermine a disciplined meeting by introducing a major new issue in the final minute.

Send a short, useful follow-up

Notes are not a transcript. Most people need a concise record of what was decided, why, what remains open, who is doing what, and when it is due.

Sample follow-up

Decision: We will move forward with Vendor B because it meets the security requirements and can be implemented before the October deadline.

Action items:

  • Priya: Send contract to Legal by Thursday, September 10
  • Marcus: Confirm implementation timeline by Monday, September 14
  • Elena: Notify Vendor A that we are closing the evaluation by Friday

Open question: The project team will resolve the historical data-migration process in the implementation document by September 18.

Next meeting: None currently required.

Share the recap the same day if possible. AI-generated summaries can help, but they are not substitutes for judgment: a transcript may capture what people said without identifying what the group agreed to. Recording can also change how candidly people participate. Consider consent, confidentiality, and company policy before recording sensitive discussions.

Audit recurring meetings regularly

Recurring meetings are the most likely to outlive their purpose. Once a month or quarter, ask: Does this meeting still serve a defined purpose? What has it accomplished recently? Does it need the same attendees or frequency? Could items move to a written update? What would happen if we canceled it for a month?

Do not keep a weekly meeting because it is already on the calendar. That is not a reason. It is inertia. Try alternating live discussion with written updates, separating decision meetings from status updates, or running a four-week experiment without the meeting and measuring the effect.

The effective meeting standard

A meeting should not exist merely because people are available to attend it. It should exist because bringing those people together is the best way to accomplish a specific piece of work. Before you send the next invitation, make sure you can answer: Why does this require a meeting? What must be accomplished? Who genuinely needs to participate? What should happen beforehand? Who can make the decision? How will actions be captured?

A productive meeting does not need to feel dazzling. It needs to create clarity, movement, and accountability. If it does not, it probably should have been an email.

Meeting planning worksheet

Use this before scheduling or leading an important meeting. Print it or copy it into a doc.

Part 1: Should this be a meeting?

What am I trying to accomplish?

Does this require real-time conversation, collaboration, or a decision?

  • Yes
  • No
  • Unsure

Could the same result come from one of these instead?

  • Email
  • Shared document
  • Project-management update
  • Recorded presentation
  • Dashboard or report
  • One-to-one conversation
  • No, a meeting is the best format

What would happen if this meeting did not occur?

Part 2: Define the outcome

By the end of this meeting, we will have:

Meeting type:

  • Decision
  • Problem-solving
  • Planning
  • Brainstorming
  • Feedback
  • Coordination
  • Relationship-building

What is outside the scope of this meeting?

Part 3: Identify the right participants

ParticipantWhy is this person needed?Role

Role options: decision-maker, contributor, implementer, facilitator

Who could receive the notes instead of attending?

Part 4: Prepare the agenda

TimeQuestion, decision, or activityLeaderDesired result

What must participants review or complete beforehand?

Who has final decision authority?

Part 5: Plan for participation

Whose perspective is most important to hear?

Who may need to be invited into the discussion more deliberately?

Questions I will use to improve the conversation:

How will I prevent one or two people from dominating?

Part 6: Capture the outcome

Decisions made:

Action items:

ActionOwnerDeadlineDependencies

Open questions:

Does another meeting need to be scheduled? Why?

Part 7: Evaluate the meeting

Did we accomplish the stated outcome?

  • Yes
  • Partially
  • No

Were the right people present?

  • Yes
  • No

Did everyone who needed to contribute have the opportunity?

  • Yes
  • No

Were decisions and next steps clear?

  • Yes
  • No

Could any part have been handled asynchronously?

What will I change before leading the next meeting?