DEV Community

Kinetic Goods
Kinetic Goods

Posted on

The Meeting That Should Have Been Two Meetings

You put two unrelated topics in the same meeting. The meeting runs long. Neither topic gets the attention it needs. Everyone leaves frustrated.

This is the meeting that should have been two meetings.

When This Happens

The project review that turns into a design debate

Half the meeting is reviewing progress. The other half is arguing about a design decision. These need different people and different time allocations.

The status update that turns into a planning session

You're updating on progress. Then someone says "while we're all here, let's talk about next quarter." Now you have two meetings in one.

The all-hands that tries to cover everything

Company updates, team updates, Q&A, strategic discussion. This is really three or four meetings pretending to be one.

Why It Happens

Calendar efficiency theater

We want to seem efficient. "Kill two birds with one stone." But calendar efficiency and meeting effectiveness are different things.

Fear of scheduling

Scheduling feels like admitting you can't handle it in the time you have. So you cram multiple topics into one meeting to avoid the discomfort of booking another slot.

The meeting that grew

A meeting for one topic gets a second topic added. Then a third. Nobody ever removes topics.

How to Fix It

When it happens in the meeting

"I think this deserves its own meeting. Let's finish discussing X today and schedule Y for another time."

This is uncomfortable. Do it anyway.

When you're the organizer

Audit your recurring meetings. If two topics have different audiences, different purposes, or different decision-makers, they should be different meetings.

Set the agenda

Every meeting should have ONE purpose. Not "project review and planning." Either "project review" OR "planning."

The Real Rule

If the agenda has an "and," it's probably two meetings.

The meeting that tries to cover two topics usually covers both poorly.


Split it. Schedule two meetings. Your team will thank you.

Top comments (0)