All guides · Meetings

How to run an effective team meeting (a guide for new managers)

An effective team meeting has one purpose you can say in a sentence, an agenda sent the day before, a hard stop, and ends with every decision and task written down with a name and a date. Keep updates out of it (they go in writing) and spend the time on what needs the whole team: decisions, problems, and plans that touch more than one person. For most teams that's one 30 to 45 minute meeting a week.

This guide is for first-time managers who now own a weekly meeting, maybe one they used to sit in. Below: how to decide if you need the meeting at all, a timed 30-minute agenda, what to say to open and close, how to handle the talker, the silent ones and the tangent, a notes format, how to run your first meeting as the new manager, and how to tell if your meetings are working.

Do you need this meeting at all?

Before you book a recurring hour for six people, check what it's for. A meeting is the most expensive way to share information: a 45-minute meeting with eight people uses six hours of the team's week. It's worth it when the work needs people to talk, not just to know.

Patrick Lencioni makes the same split in Death by Meeting: a weekly tactical meeting for this week's work, and separate, rarer strategic meetings for the big questions. Mixing them is a common reason a meeting feels long and lands nothing: you start on next week's rota and end up debating the team's direction with 4 minutes left.

Give the meeting one purpose

Write it at the top of the agenda in one line. Some examples that work:

• "Agree this week's priorities and clear anything blocking them."
• "Decide what we cut from the March release."
• "Share what we learned from last week's customer calls and pick one thing to change."

If you can't write the line, you probably don't need the meeting this week. Cancel it and say why: "Nothing needs the whole group this week, so I'm giving you the 45 minutes back. Updates in the doc by Thursday, please." People remember a manager who gives time back.

A 30-minute weekly team meeting agenda

This shape works for a team of 3 to 10. Times are a guide; the order matters more than the minutes.

For a 45-minute meeting, give the extra 15 minutes to the topics, not to updates. For a 60-minute meeting, ask whether you need it: an hour every week is a big share of a small team's time, and most weekly meetings that run an hour are 30 minutes of decisions and 30 of status.

Write topics as questions

"Hiring" is a topic. "Do we hire a contractor for Q1 or wait for the full-time role?" is a question, and it tells everyone what the 10 minutes is for and when it's done. If a topic has no question, it's an update: put it in the written notes.

Let the team add to the agenda

Keep a shared doc. Anyone can add a topic until noon the day before. You send the final agenda that afternoon with anything people should read first. The meeting stops being "the manager's meeting" and becomes the place where people bring problems, which is what you want.

Before the meeting: 15 minutes of prep

1. Check last week's action list. Ask anyone with an overdue item privately first, so nobody is caught out in front of the team.
2. Pick the two or three topics. More than three and the last one gets 2 minutes and a bad decision.
3. Send the agenda the day before with the purpose line, the topics as questions, who leads each, and any pre-read. Keep pre-reads to a page; if it's longer, people won't read it.
4. Decide how each decision gets made. Is it yours after hearing everyone? The team's by agreement? One person's, with input? Say it at the start of the topic. Many meetings drag because people think they're voting when the manager is deciding, or the other way round.
5. Name a note-taker and a timekeeper. Rotate both weekly. It's hard to lead a discussion and watch the clock at once.

How to start a team meeting: what to say

The first 60 seconds set the tone. Start on time even if someone is missing; waiting teaches everyone that 5 minutes late is on time. Then say three things: why we're here, what we'll cover, when we stop.

"Morning, everyone. We've got 30 minutes, finishing at 10:30. The goal today is to agree the order for the three client launches. We'll do wins, a quick look at last week's actions, then two topics: the launch order, which Maya will lead, and whether we move the Friday deploy. Sam's taking notes, Priya's on time."

If the team is new or you're new, add a short round: "Before we start, one line each: what's the one thing on your plate this week you'd most like to go well?" It takes 3 minutes for 8 people, gets every voice in the room early, and people who've spoken once speak again more easily.

During the meeting: keep it moving

When someone talks too much

Interrupt kindly and with a reason: "That's useful, and I want to get the others in before we run out of time. Jordan, what's your view?" If it happens every week, raise it in their 1:1, not in front of everyone: "You've got a lot to add in the team meeting, and I've noticed the quieter people tend to fold when the room is full. Could you hold your view until two others have gone?"

When people stay silent

Silence doesn't mean agreement. Ask by name, with warning: "I'd like to hear from everyone on this. Sam, then Ali, then Kim." Or give a minute for everyone to write their view first, then go round. The writing minute helps people who think before they speak, and stops the first speaker setting everyone else's answer.

If one person never speaks, ask them before the meeting: "I'd love your view on the launch order on Thursday; you know the client side better than anyone." People speak more when they've been told their view is wanted.

When the talk goes off topic

Keep a "parking lot": a list at the bottom of the notes. "Good point, and it's not today's question. I'm putting it in the parking lot and we'll pick a time for it at the end." Then actually pick a time at the end, or the parking lot becomes where ideas go to die and people stop trusting it.

When two people disagree

Disagreement about the work is the point of the meeting. Your job is to keep it about the work. Restate both views fairly in one line each, ask what each would need to see to change their mind, and if it's still split, say who decides and when: "I've heard both. I'll decide by tomorrow noon and tell you why." If it turns personal or heated, stop that topic and take it to two separate conversations; our guide to difficult conversations with employees covers conflict between two people.

When a decision is made and not everyone agrees, say so plainly. Amazon calls it "disagree and commit" (Jeff Bezos, 2016 letter to shareholders): people can disagree in the room, and once it's decided, everyone works to make it succeed. Saying it out loud makes it acceptable to have disagreed.

When you're running out of time

At the 5-minutes-left mark, stop the topic wherever it is. "We're at 25. Let's leave this here: Maya and Ali, can you take 20 minutes after this and bring a proposal to Thursday's doc?" Protecting the close matters more than finishing the topic, because the close is where the meeting turns into work.

How to end a team meeting

Read the actions aloud: who, what, by when. Every action needs one name, not "the team" or "we." Then end on time, even if you finish early. Ending early is fine; ending late is not.

"Before we go: we've decided the launch order is Brightline, then Halo, then Merit. Actions: Maya tells the clients by Wednesday, Ali updates the plan by Thursday, I'll talk to finance about the Friday deploy by tomorrow. Parking lot: the on-call rota, I'll find 20 minutes for it next week. Thanks, everyone, see you at 10:30 next week."

What to write down: a notes format

Notes are for the person who wasn't there and for you in three weeks. Keep them short and post them within the hour.

Leave out who said what. A list of decisions and actions is enough, and people speak more freely when they aren't being quoted.

Your first team meeting as a new manager

Your first meeting is less about the work and more about how you'll lead. The team is watching to see what changes. Keep it short and say four things:

1. What you've noticed and what you'll keep. "I've been on this team for three years, and the way we help each other out on deadline weeks is something I don't want to lose."
2. What you don't know yet. "I'll be doing a 1:1 with each of you over the next two weeks, mostly to listen. I'm not changing anything big before then."
3. How this meeting will work. The agenda doc, the stop time, the actions list. "Let's try this for six weeks and then you tell me what to change."
4. How to reach you. "If something's blocking you, don't wait for Tuesday. Message me."

If you used to be their peer, name it once and move on: "This is a bit odd for all of us. I'm still the same person; my job now is to clear the way for you." More on that in our first time manager tips.

Not sure what kind of meeting-runner you'll be: the one who decides fast, the one who wants everyone to agree, the one who avoids the tense topic? The free leadership style quiz takes about 2 minutes and names your style, with the conversations it tends to put off.

Remote and hybrid team meetings

• If one person is remote, everyone joins on their own screen. Otherwise the room talks to itself and the remote people become an audience.
• Cameras on for the opening round, optional after, unless the team agrees otherwise. Say what you expect rather than leaving people to guess.
• Use the chat for the quiet round. "Type your answer, don't send until I say go." Then everyone posts at once and nobody copies the first answer.
• Keep it shorter. Attention drops faster on video. If 30 minutes works in a room, try 25 online.
• Rotate the time if the team spans time zones, so the same people aren't always on at 7 a.m.

Other team meetings and how they differ

A new manager rarely needs all of these. Start with a weekly meeting and weekly 1:1s; add others only when a real need shows up.

How to tell if your meetings are working

Every six weeks or so, ask. Three questions in an anonymous form, or the last 3 minutes of a meeting:

• "On a scale of 1 to 5, was this meeting worth your time?"
• "What's one thing we should stop doing in it?"
• "What's one thing we should start?"

Watch for signs too: people arriving late, cameras off and typing, the same topic coming back every week, actions not getting done, or the real decisions happening in a side chat after the meeting. Each tells you something. Repeat topics mean decisions aren't being made or written down. Side-chat decisions mean the meeting is too big or not safe to disagree in.

Steven Rogelberg's research on meetings, collected in The Surprising Science of Meetings, found that how people feel about their meetings is tied to how they feel about their job overall. Bad meetings aren't a small thing to your team, even if nobody complains.

Mistakes new managers make in team meetings

• Turning it into a round of status updates. Ten people taking 3 minutes each is half an hour of people waiting for their turn.
• Talking most of the time. If you speak for more than about a third of the meeting, it's a briefing. Ask more than you tell.
• Raising one person's performance in front of the group. Even mildly. That conversation belongs in private.
• Deciding after the meeting without saying so. If you'll decide later, say when, then tell everyone what you decided and why.
• Letting it run over. Running 10 minutes late every week tells people their next meeting matters less than yours.
• Never cancelling. A meeting that happens because it's Tuesday, not because there's something to decide, trains people to tune out.
• No follow-through on actions. If nobody checks last week's list, people stop doing the items on it.

Questions about team meetings

How long should a team meeting be?

For a weekly team meeting, 30 to 45 minutes is enough for most teams of up to 10 people. A daily stand-up should be 15 minutes or less. If you often run over, cut the agenda to two topics before you add time.

How often should a team meet?

Once a week suits most teams, with day-to-day updates in writing. Teams with fast-moving daily work (support, operations, software sprints) often add a short daily stand-up. Fewer than every two weeks and decisions start piling up or happening in side chats.

What should a team meeting agenda include?

The purpose in one line, the stop time, last week's actions, two or three topics written as questions with who leads each, and time at the end for decisions and actions. Send it the day before.

Who should run the team meeting?

You own it, but you don't have to lead every part. Let the person who raised a topic lead it, and rotate note-taking and timekeeping. Some teams rotate the whole facilitator role weekly once the format is settled.

Should I cancel a team meeting if there's nothing to discuss?

Yes. Tell the team the day before, ask for written updates instead, and give the time back. Cancelling now and then, for a reason, makes the meetings you do hold count for more.

What if my team won't speak up in meetings?

Ask people by name with a bit of warning, give a silent minute to write before talking, and thank the first person who disagrees with you, out loud. If it persists, ask in 1:1s what makes the meeting hard to speak in; the answer is often about one person, or about how you react to bad news.

Next: take the free leadership style quiz to see how your style shows up when you run a room, or browse all our guides for new managers.

Sources

• Patrick Lencioni, Death by Meeting: A Leadership Fable About Solving the Most Painful Problem in Business, Jossey-Bass, 2004.
• Steven G. Rogelberg, The Surprising Science of Meetings: How You Can Lead Your Team to Peak Performance, Oxford University Press, 2019.
• Jeff Bezos, 2016 Letter to Shareholders ("disagree and commit"), Amazon: https://www.aboutamazon.com/news/company-news/2016-letter-to-shareholders
• Andrew S. Grove, High Output Management, Random House, 1983 (chapter on meetings).