Three months into a promising project, the team hit a wall.
Not a technical wall. Not a budget wall. A meeting wall.
The project had everything going for it: clear goals, adequate resources, motivated people. But somewhere between the kickoff and the final deliverable, something went wrong.
The team held more meetings than ever. Weekly syncs became daily standups. Standups became ad-hoc calls. Every blocker seemed to require a meeting to "align."
By month three, the project was dead. Not canceled — just slowly strangled by the sheer volume of meetings that produced no decisions.
What Went Wrong
The team confused communication with coordination. They thought more meetings meant better alignment. It didn't.
Each meeting introduced new perspectives, new concerns, new scope. But it didn't actually move the project forward. It just created the appearance of progress.
The problem wasn't the number of meetings. It was that every meeting was a status update instead of a decision point.
The Rule That Would Have Saved It
Every meeting should end with a decision or an action.
Not a status report. Not a discussion. A decision. Who does what by when. That's it.
If a meeting can't produce either, cancel it.
What This Looks Like in Practice
Before scheduling a meeting, ask:
- What decision needs to be made?
- Who has the authority to make it?
- What information do they need?
If you can't answer all three, the meeting isn't ready.
During the meeting:
- State the decision upfront
- Get the relevant person to make it
- Capture the action and deadline
After the meeting:
- Send a one-line summary: "Decision: X. Owner: Y. Due: Z."
- If no decision was made, document why and when you'll revisit
The Inverse
If you're in a meeting and no decision happens, you should feel uncomfortable. That discomfort is the signal.
When the meeting ends without a decision, say: "So what's our next step, and who's responsible for it?"
If the answer is "let's discuss more next week," you've just identified the problem.
The Outcome
Projects don't die from too few meetings. They die from too many meetings that don't produce decisions.
The teams that ship fast have one thing in common: they treat meetings as a tool for making decisions, not discussing them.
Your next meeting — does it have a decision attached? If not, you already know what to do.
Top comments (0)