How to Run a Team Meeting Worth Attending

For about six months I ran a Monday team meeting that nobody wanted to be in. Including me.

Thirty minutes, no agenda, eight people. I would open by asking if anyone had updates. A few people would share things. Someone would raise a question that needed a longer conversation, we would run long, half the team would be disengaged because the conversation only mattered to two people, and we would end with no decisions made and nothing written down.

I thought the problem was the people. That I had a team that did not communicate well, did not prepare, did not take the meeting seriously.

I started noticing the pattern from a different angle when a new hire, three weeks in, asked me before a Monday meeting: "Is there an agenda I should know about?" I told her we kept it informal. She looked at me with an expression I am still thinking about. It was polite but extremely clear.

She was used to meetings with a point. I was running meetings with a habit.

Why most team meetings fail

The default team meeting is a status update dressed up as a coordination mechanism. The manager asks who has updates. People share what they remember. Someone raises a question. The question becomes a discussion. The discussion includes three people and excludes five. The meeting ends and nothing was decided.

Andy Grove wrote about this in High Output Management decades ago and it is still exactly right: a meeting without a defined output is a social event, not a work event. The issue is not that people are wasting time. The issue is that nobody defined what useful would look like.

Most managers run bad meetings because they do not know what they want out of the meeting before it starts. They expect the conversation to surface the value. It usually doesn't.

"If you could not describe the single most important thing that needs to happen in this meeting before it starts, you are not ready to run it."

The fix is not a longer agenda or a more formal format. It is getting clear on what each meeting is actually for.

The three types of team meetings (and why mixing them breaks everything)

This is the frame that changed how I thought about it.

Team meetings serve one of three functions: information sharing, decision making, or relationship building. Most bad meetings fail because they are trying to do all three at once and doing none of them well.

Information sharing is one-directional. Someone has information the team needs. The goal is clarity and efficiency. These meetings should be short, async-friendly, and honest about whether they need to be meetings at all. A lot of information sharing is better as a written update that gets read before the meeting.

Decision making requires a defined problem, the right people in the room, and a clear owner. If you cannot name who makes the call before the meeting starts, you are not ready to have the meeting. Decision meetings often go long because the decision has not been scoped. You end up relitigating context instead of making the call.

Relationship building is slower and harder to justify but real. Team offsite conversations, retrospectives, check-ins that are genuinely about how people are doing. These do not need an agenda. They need time and intention.

The best managers I know keep these separate. Status updates go to a written doc the team reads before the meeting. Decisions get their own focused block. Relationship conversations get protected time that is not contaminated by task overhead.

Common mistake: Trying to accomplish all three in the same thirty-minute recurring slot because it is already on the calendar.

A structure that actually works

For weekly team meetings, I landed on a format that I have iterated on across a few teams. It is not original, but it is consistent, and consistency is what makes a meeting feel like a ritual instead of a waste of time.

Five minutes: wins and blockers only. Not full updates. Each person gets one sentence on what is going well and one sentence on where they are stuck. No elaboration unless someone asks. This forces people to be useful instead of exhaustive.

Fifteen minutes: one focused topic. One thing the whole team needs to think about together. Decided in advance, distributed before the meeting. Not a discussion that surfaces in the first five minutes and hijacks the rest of the time. The manager picks the topic and is responsible for coming in with a clear question or decision that needs resolution.

Five minutes: decisions and next steps. What got decided in this meeting. Who is doing what. What happens before next week. This gets written down in real time, not reconstructed from memory later.

That is it. Twenty-five minutes. Maybe thirty if something genuinely needs more time. The structure is designed so that anything that does not fit into these buckets goes somewhere else, usually an async channel or a smaller meeting with the right people.

Try this week: Before your next team meeting, write down one sentence: "The most important thing I need this team to leave with today is ___." If you cannot complete that sentence, postpone the meeting. You are not ready. Send an update instead.

The pre-meeting doc nobody writes

The other thing that changed my meetings was sending a short document before each one. Not a full deck. Not a list of talking points. Just this:

• What we are discussing today and why
• What I am hoping we decide or align on
• Any context people need before the meeting starts

It takes me five minutes to write. It takes each team member two minutes to read. It eliminates about half the time we used to spend getting everyone oriented.

A colleague of mine who manages a larger team than I ever have told me she has been doing this for years: "Once I started the pre-read habit, my meetings got twenty percent shorter immediately. People show up already knowing the context. We skip all the setup."

Her other rule: if someone cannot answer a basic question about the agenda because they did not read the pre-read, the meeting pauses for ninety seconds while they read it. She does this once per person, once. It stops happening after that.

What to Do When Meetings Keep Drifting

Even with a structure, meetings drift. Someone raises something off-topic. A thread opens that is interesting but not relevant to the thirty people in the room. Someone starts monologuing.

The manager's job is to catch the drift before it becomes the meeting.

"Let's put that in the parking lot and come back to it after we finish this." That phrase saves twenty minutes. Most managers are afraid to use it because it feels rude. It is not rude. It is what good facilitation looks like. The people whose tangent you interrupted will appreciate being redirected once they realize the meeting actually ended on time.

"Your job in the room is not to be liked. It is to make the meeting worth the time of everyone in it."

The hardest version of this is when the drifting thing is important and people can see that you are aware of it. The answer is: name it. "This is real and we're going to give it time. But I don't want to shortchange it by trying to resolve it in the last five minutes of this meeting. Can we book thirty minutes this week?" Then do it.

The Quiet Cost of a Bad Meeting Culture

This is the thing I underestimated for a long time.

Every bad meeting teaches your team something: that their time is not valued, that showing up prepared doesn't matter because the meeting is going to wander anyway, and that participation is optional because real decisions get made elsewhere.

It is hard to reverse that once it is set. Teams calibrate to the environment. If the environment is unstructured, they stop preparing. If they stop preparing, the meetings get worse. It compounds.

Claire Hughes Johnson writes in Scaling People about meeting hygiene as a form of organizational trust. When meetings are run well, people show up with their thinking done. When meetings are run badly, people learn to protect their real attention for other contexts. The signal travels fast.

I have been in organizations where the team meeting was the one thing everyone actually came to prepared and engaged. And I have been in organizations where team meetings were where you checked your phone and waited for it to be over. The difference was almost always the manager's intentionality about the format.

It is not hard to fix. It just has to be a priority.

Cadence helps me keep the thread from meeting to meeting, specifically the next steps and decisions that otherwise disappear into memory. The worst version of a good meeting is one where something important gets decided, nobody writes it down, and by Thursday no one can agree on what actually happened. Having a consistent place to put that changes what your team trusts about whether decisions stick.

Run every team meeting with a real agenda.

Cadence now includes team meeting agendas alongside 1:1s and task tracking, so every meeting has a purpose, notes, and follow-through. 14-day free trial.