Half the meetings on your calendar exist because someone wanted confirmation that something was received.
Not a decision. Not a discussion. Just: "I want to make sure the team knows X."
That's a message. Not a meeting.
Why It Became a Meeting
At some point, sending a message felt insufficient. You wanted to see faces. You wanted to know people were paying attention. You wanted to ask if anyone had questions — and actually get responses in real time.
So you scheduled a meeting. Fifteen people joined. You read your update out loud. Someone asked a clarifying question. Someone else said "makes sense." Five minutes of actual discussion. The rest was you talking at people while they muted themselves.
The meeting accomplished the same thing a message would have. Except it took an hour of calendar instead of five minutes of reading.
The Replacement
Before scheduling a sync for an update, ask:
"What would make this meeting worth having?"
If the answer is "I just want to make sure people got it," send a message instead. Make it clear and specific. Name what you need from people. Set a deadline for feedback.
If people need to acknowledge receipt, ask for it in the message. "Reply by Friday if you have concerns." Done.
When It Actually Needs a Meeting
The update becomes a meeting when:
- People need to discuss and debate what you shared
- You need real-time input to adjust direction
- There are questions you can't answer without more context
That's a conversation. Schedule it with the people who need to have it — not everyone who needs to know the outcome.
The default for "I want people to know X" is message. Not meeting.
Top comments (0)