5 Reasons Your Meetings Are Unproductive (And How to Fix Each One)

Meetings go unproductive for five reasons: the meeting is trying to do too many jobs at once, the hour goes to status updates, the agenda gets rebuilt every week, nothing actually gets decided, and the goals never come up. Most leaders respond by shortening the meeting or tightening the agenda, which organizes the problem without solving it. The faster path is finding out which of the five is yours. Your team already knows, and you are the least likely person in the room to guess right.

The meeting starts eight minutes late because you're waiting on two people.

Someone shares an update that could have been an email. Someone else shares one you already heard on Tuesday. A real issue comes up around minute forty, everybody has an opinion, and you run out of time before anyone decides anything. So you agree to pick it up next week.

Next week you pick it up. Same conversation, same forty minutes in, same non-decision.

When I was leading a church, I ran a meeting like that for years. If you had asked me, I'd have told you the meeting was fine.

It wasn't fine. It was mostly a report, with people waiting their turn to say what they were working on. If I had rated that meeting one to five, I'd have said four. My team would have said two.

Steven Rogelberg has studied meetings for twenty years and found that leaders rate the meetings they run more favorably than the people sitting in them. The more you talk in a meeting, the better you think it went, and the person running the meeting talks the most.

So you walk out thinking it went okay. Your operations director walks out with a private list of what she could have done with that hour.

An unproductive meeting is one that changes nothing about the week that follows it.

Here are the five reasons meetings end up that way. Four of them are about how you spend the hour. The fifth is about whether the hour is pointed at anything.

1. The Meeting Is Trying to Do Too Many Jobs at Once

Your agenda has announcements, calendar coordination, somebody's project update, a problem that needs a decision, and a few minutes of team connection at the end because there's nowhere else for it.

Patrick Lencioni calls this meeting stew in Death by Meeting. Everything goes in one pot. Nobody can move from celebrating a win to arguing about the budget to brainstorming next spring inside sixty minutes. The room doesn't turn that fast.

Al Pittampalli calls the traditional meeting "a weapon of mass interruption" in Read This Before Our Next Meeting, and his argument is that most of them exist because nobody wanted to write anything down. His standard is narrow on purpose. A meeting is for working out conflict around a decision, or coordinating how a decision gets carried out. Everything else has a cheaper format.

The fix is to decide what this meeting is for and say it out loud. Ours is where we make decisions. Ours is where we solve problems. Pick one and tell people.

Then go down your agenda and ask what doesn't need everyone in the room. The calendar reconciliation could be a shared doc. The announcements could be an email. The project update could be three sentences somebody types Monday morning.

Somebody is reading this and thinking it sounds cold. The connection is not what I'd cut. Celebrating a win, asking how somebody is actually doing, that's the reason to be in a room together. What I'd cut is the twenty minutes of stuff everybody could have read on their own.

2. You Go Around the Table for Updates

You need to know what's happening so you ask everyone to go around the table. That means nine people sit through eight updates that don't affect them, waiting for a turn to talk.

Rogelberg found that only about half of meeting time is time well spent. In a weekly team meeting, the go-around is usually most of the other half.

Run the math on your own. If updates take forty minutes of your ninety, most of your meeting is spent on information people could have read.

The fix is to move status into written check-ins before the meeting. Everyone answers the same short set of questions: where their goals stand, what they finished, what they're focused on, what's blocking them. Two minutes to write, one minute to read. Then delete the go-around and start the live hour where the trouble is.

This is the change teams resist hardest and thank you for later.

Basecamp has run this way for years, and their employee handbook spells it out. The whole company answers two standing questions in writing. What did you work on today, answered at least twice a week, and what will you be working on this week, answered every Monday. Answers are grouped by team so you only see your own group's. Nobody sits in a room to hear any of it, and the written record is still there six months later when somebody needs to look something up.

Pittampalli goes further and says the informational meeting should be abolished outright. The trade he proposes is worth stealing: the leader cancels the update meeting, and in exchange everyone commits to actually reading what gets written. If people stop reading, the deal is off and the meeting comes back.

3. The Agenda Gets Rebuilt Every Week

Most weekly agendas get written the night before by whoever is most stressed. So the agenda reflects last week's anxiety instead of this quarter's priorities.

Rogelberg also found that simply having an agenda doesn't make a meeting better. It has to be built well, and it has to hold still long enough for people to learn it.

The fix is a block agenda. Same sections, same order, every week: wins, numbers, goals, issues, action items. The content changes weekly, and the shape never does.

People come prepared because they know what's coming. And anybody on your team can run the meeting when you're out.

4. Nothing Gets Decided

Discussion feels like progress. You can tell it isn't when the same item shows up on three consecutive agendas.

After that happens a few times, people stop expecting decisions. The meeting quietly becomes a place to talk about things, and everyone adjusts to it.

Pittampalli's test for a real meeting is that it ends with a written action plan naming three things: what the team committed to, who owns each piece, and when it's due. Most standing meetings produce none of the three.

The fix is to commit to solving one real problem, using IDS. That comes from EOS, the operating system Gino Wickman lays out in Traction. Three steps.

1. Identify. Name the actual problem, not the symptom. "Our response times are slipping" is a symptom. The problem might be that two people left in the spring and nobody rebalanced the work. This is the step everybody skips and where teams lose the most time.
2. Discuss. Everyone says their piece once. Whoever is running the meeting cuts off repetition and tangents, which is uncomfortable for about two weeks and then becomes normal.
3. Solve. End with a decision, a name, and a date. The issue comes off the list. If it doesn't come off, you discussed it, and it's back next week.

One solved problem a week is fifty a year. Five half-discussions solve nothing and everyone leaves tired.

You don't have to adopt all of EOS to use this part of it. We wrote about which pieces of the system are worth borrowing and which ones really do need an implementer in EOS without the consultant.

5. Your Goals Never Come Up

This is the big one, and it's the easiest to miss, because nothing about it feels wrong in the moment.

FranklinCovey's xQ research surveyed 26,500 workers across more than 150 companies and found that only 15% could name their organization's top three goals. That looks like a communication problem. Usually it's a calendar problem. The goals don't come up in the one meeting where the whole team is in the room, so they don't come up anywhere. Then in October you wonder why nothing moved.

The fix is to put your three clear goals at the top of the agenda with one name on each. Not the group. One person. Each owner takes about two minutes: what's moving, what's stuck, how they're doing. Only the stuck ones get discussion.

If your goals are vague, this part of the meeting stays vague with them. A goal written From X to Y by When and Why gives the owner something specific to report against, which is what keeps the two minutes from turning into a story.

There's a motivational reason this works, beyond alignment. Teresa Amabile and Steven Kramer studied roughly 12,000 workday diaries and found the biggest driver of a good day at work is making progress on meaningful work. It beat recognition and it beat incentives. When 669 managers were asked what motivates their people, only 5% put progress first.

A meeting that opens by showing what moved lets people see their own progress. One that opens with announcements doesn't.

Running All Five in One Place

Everything above works with a shared document, a recurring calendar block, and somebody willing to keep it up. Some teams run it that way for years and it works fine.

What breaks is the upkeep. Somebody has to build the agenda, chase the written check-ins, keep the action items, and carry the unfinished issues into next week. That's the job that slips around week four, and once it slips you're back to the round-robin.

That's the part Alignify handles:

• A block agenda that keeps the same shape every week, with a timer on each block
• Written check-ins that come in before the meeting and land in one place
• Your three goals at the top, each with an owner and a status
• An issues list anyone can add to, carried forward until it's decided
• Action items with a name and a date, and a rating when the meeting ends

Which One Is Yours?

You don't have to guess. Before your next meeting, send your team one question and ask for a written answer.

What is the one thing we do in this meeting that you would cancel?

Then read the answers without defending anything.

That's uncomfortable, and it's faster and more accurate than anything I can tell you from here. Your team has been answering that question with their body language for months. You might as well collect it in writing.

Your team gives you that hour every week whether it's good or not. The question is what they get back for it.

Common Questions About Unproductive Meetings

How Long Should a Weekly Team Meeting Be?

Shorter than you think. Work expands to fill whatever you block, so ninety minutes becomes ninety minutes of talking. Start at sixty for a full team meeting, or thirty if your team is under six people and status is already written down. Put a clock on each section so an overrun is a decision you make out loud instead of an accident.

Should We Just Cancel Our Weekly Meeting?

Rarely. Cancel the parts that are pure information transfer and keep the parts that need everyone in a room: decisions, priorities, and the conversations that only happen live. A team with no standing meeting usually replaces it with a dozen ad hoc ones, which costs you more attention, not less.

How Do I Change the Meeting Without It Feeling Like a Crackdown?

Tell your team you're taking something off their plate, and then actually take it off. Deleting the round-robin is the easiest first move because it gives time back to everyone in the room. Introduce one change at a time and ask for feedback after three weeks.

What If One Person Dominates the Discussion?

The standing agenda and a clock on each section handle most of it without a confrontation. IDS handles the rest. When everyone says their piece once, the person who talks for forty minutes gets one turn, and the two who never talk get asked directly.

Free Live Training: Why Staff Meetings Stink (And How to Fix Yours)

Wednesday, September 9. I'm teaching the whole framework live: all five of these reasons, a standing agenda you can run without building it from scratch each week, and how to work a real issue to a decision in the room.

It runs about forty minutes plus questions, it costs nothing, and you'll leave with something you can use in next week's meeting.

Save your spot for the September 9 training →

Can't make it live? Register anyway and we'll send you the replay. If you'd rather see the software side first, watch the demo.