The Meeting That Should Have Been a Message
Nobody ever quit over one bad meeting. People quit over the two hundredth identical status meeting that could have been a message.
The three-part agenda
Decisions needed. Blockers. Wins and signals. If an item does not fit one of those three buckets, it moves to async — a message, a doc comment, a two-line update. And if the agenda is empty by the morning of the meeting, the meeting is cancelled, out loud, on time.
What each bucket is for
- Decisions needed — items that genuinely require the people in this room, framed as options with a recommendation
- Blockers — raised in one minute each, solved offline with only the people involved
- Wins and signals — two minutes that keep the team’s pulse honest and give quiet work a witness
Status updates are not a meeting. Reading a dashboard out loud to people who can read is a ritual, and rituals that waste ten people’s hour do not survive scrutiny — yours should not either.
Cancelling is a leadership signal
Cancelling a meeting you own is not a failure of leadership. It is one of the most visible signals of respect for your team’s time that you will ever send. The first time you write “nothing needs a decision this week — async updates only, enjoy the hour” you will get more goodwill than a month of pep talks.
