The 7 Most Ridiculous and Bad Meeting Invites People Send.
Meta Title: The 7 Most Ridiculous Meeting Invitations People Actually Send | Conductor
Meta Description: From the pre-meeting meeting to the Friday 4 pm quick sync, these unnecessary meetings are costing companies $37 billion a year.
If you think your day is starting on a bad note, think about someone who has received an invite to three unnecessary meetings on a Friday Morning. One meeting to recap the week's meetings, another to prepare for the Monday Meeting, and the last is an emergency meeting from the CEO about a delayed delivery.
Somewhere right now, someone is sending a meeting invite. A title has been typed, attendees have been selected, and a time has been chosen. What’s left is to hit send.
And the receiver? Almost as soon as they stare at the screen, they realise they have been handed a problem they’d rather not deal with, but cannot refuse anyway.
The meeting invite is one of the most powerful tools in today’s workplace. It has the power to summon ten people in a room regardless of time, reason, or validation. It simply requires a sender with calendar access and the guts to use it
And while some use this power responsibly, some unfortunately don’t.
This is a hilarious yet learned guide to dealing with the seven most ridiculous meeting invitations you’ll come across, sent by founders, executives, managers, and the new intern who hasn't learned to use the calendar properly.
They are absurd but real. And if you have been in the workforce for more than eighteen months, you have almost certainly attended at least three of them.
Type 1: The Pre-Meeting to Plan the Real Meeting
Title: "Quick sync before Wednesday's call."
This is the unnecessary meeting that exists for the sole purpose of discussing an upcoming meeting.
Not to prepare materials. Not to resolve a specific confusion before the room fills. To discuss, in real time, with almost the same people who will be there on Wednesday, the meeting that is happening on Wednesday.
It is usually an internal meeting to prepare for an external meeting, knowing well enough that this same conversation could have been a document, written in 30 minutes, distributed and read in 15 minutes by concerned parties.
The organisation has now spent 90 minutes of collective time on one conversation twice.
That same conversation could have been a document. Written in thirty minutes. Distributed and read in fifteen. By the exact people who will be on the Wednesday call.
But a document requires someone to sit down and write it. The pre-meeting only requires someone to open the calendar, and so they use the easy way out.
Type 2: The Four-Hour Status Update Nobody Asked For
Subject line: "Q3 Quarterly Team Update and Alignment Session — Mandatory."
Four hours.
Two hundred and forty minutes. Enough time to watch two full films. Enough time to fly from Lagos to Nairobi. Enough time, if used differently, to actually produce the work the meeting is about.
This meeting invitation arrives with genuinely good intentions: information, alignment, and team connection.
The problem is not the intention. Intention is never enough to justify a meeting. The problem is the format. By hour one, the room is tired, by hour two, nodding has begun, by hour three, cameras are off, and at least three attendees are quietly eating lunch.
The four-hour status update does not produce alignment. It produces the particular exhaustion of people who spent four hours in a room together and left knowing less about what they are supposed to do next than when they arrived.
In short, the four-hour status update does not produce alignment; it is a kind of team bonding that no employee wants but has to attend.
Type 3: The 9 pm Emergency That Isn't
This one arrives with the urgency of a crisis and the content of a Tuesday.
The meeting invitation lands after working hours. Subject line: "Urgent — tonight." Agenda, when there is one: "Just wanted to get everyone on the same page before the morning call."
The morning call is at 9 am. There are twelve hours between now and then.
The question that prompted a 9 pm emergency could have been a message. Could have been answered by email.
Could have waited 11 hours with no consequence to anything, because really, what does the CTO, about to sleep, want to do for a client whose shipping was delayed?
So, the 9 pm emergency meeting is not usually an emergency but anxiety with calendar access, the meeting equivalent of sending a five-alarm notification for a question that, written down, takes two sentences.
Type 4: The Recap of Last Week's Recap
This meeting invitation is to discuss what happened in the previous meeting.
The original meeting had action items.
The follow-up checked on those action items and found that most had not been completed because the people responsible for completing them were in meetings.
The follow-up to the follow-up is checking on the check-in of the action items from the meeting before, which were supposed to be completed in the time between meetings, that was never actually available because it was full of meetings.
Nobody asks why the action items were not completed. Nobody suggests fewer meetings as a way to create the time needed to complete them.
Another meeting is scheduled instead.
The recap of a recap is the organisational equivalent of discussing why you haven't gone to the gym instead of actually going. It takes the shape of accountability. It produces none
It is not the solution to the problem. It is the problem, rescheduled.
The 20-Person Email Chain Turned Zoom Call
Subject line reads "RE: RE: RE: RE: Thoughts on this? Let's just hop on a call."
The email chain had thirty-four replies.
It originally had six people, which grew to ten and then fifteen colleagues who had ‘’context’’ with a 50-page PDF that no one opened.
At reply thirty-two, someone typed five words that changed everything.
"Let's just hop on a call."
And so, fifteen people, some of whom had not replied to the email, several of whom had been CC’ed, and at least two with different time zones and found the meeting time technically possible but personally unreasonable, joined a Zoom call to discuss the email chain.
The 20-person email-to-Zoom meeting does not resolve the email chain; instead, it creates a verbal version of it. No decision was made. The PDF remains unopened. The thirty-four replies now have a meeting summary attached to them.
Type 6: The Brainstorm Run by an Idea Dictator
The meeting invitation says all ideas are welcome.
The meeting begins with the idea dictator sharing their idea. Not as a starting point. As context, someone suggests a different direction. The idea dictator nods thoughtfully and says "interesting" in a tone that communicates the opposite. Then circles back to the original idea.
Someone else offers a modification. The idea dictator writes it on the whiteboard and draws an arrow connecting it to the original idea. It is not a modification of the original idea. It is a different idea entirely, and the arrow does not change this.
By the end of the session, the original idea had been affirmed by a room of people who technically participated and effectively didn't.
This is not a brainstorm; it is a meeting invitation to witness a decision already made, with a whiteboard and good lighting to make the process feel collaborative.
All ideas were welcome; only one would ever be chosen.
Type 7: The Friday 4 pm Quick Sync That Isn't
TGIF!
4 pm precisely. The week is almost complete. The weekend is closer than the hair on your skin, but then,
The meeting invitation arrives.
"Quick sync."
The word quick does a lot of work in that subject line. It implies brevity. It implies a shared understanding that everyone involved would prefer to be doing something else. It implies that whoever sent this is aware of the time and day and is asking for something small.
The sync begins at 4:10 pm because someone was finishing a call.
At 4:25 pm, a topic is introduced that was not in the subject line.
At 4:45pm, a decision is required, but nobody was prepared for a decision. It was a quick sync.
At 5:03 pm, someone says "I know we're running over" and then does not end the call.
At 5:22 pm, the meeting ends with three action items, no documented owners, and the quiet certainty that everyone present will spend at least part of the weekend thinking about it whether they want to or not.
The Friday 4 pm quick sync is not quick. It is a meeting that borrows from the weekend with a smile — and a promise both parties know, from experience, is not going to hold.
Stop Bad Meetings Invites even before They Reach Your Calendar
The good news: none of these meetings is mandatory.
They feel mandatory; they arrive with the formal weight of a calendar invite and the social pressure of a room that expects your name in the attendee list. But someone chose to send them. Someone else chose to accept.
The pre-meeting to plan the meeting dies when the organiser is asked, before acceptance, to send the agenda for the meeting is intended to be planned.
The four-hour status update dies when leadership decides written updates are distributed before the meeting, and the room is reserved for decisions, not briefings.
The 9 pm emergency dies when the organisation enforces a simple rule: non-critical communication does not travel after 7 pm.
The recap of the recap dies when action items are documented with named owners, visible deadlines, and the follow-up is a message rather than a meeting invitation.
The 20-person Zoom call dies when the person who typed "let's just hop on a call" is asked: which three people actually need to be on it, and what decision should it produce?
The Friday 4 pm quick sync dies when the person receiving it asks, before accepting, whether this could be an email. If the answer is yes, and it usually is, the reply is a message that addresses the topic, names the next steps, and costs fourteen minutes instead of ninety.
These are not rebellions. They are simply the questions the calendar, left to its own logic, will never ask on your behalf.
They sound Funny Until You Calculate What They Cost
The seven meeting invitations in this piece are absurd.
According to Doddle, $37 billion is the annual cost of American businesses, but according to an Atlassian study, these meetings are part of 50% of unproductive meetings that waste funds every year.
Forbes, citing a study from the Harvard Business Review, stated that 71% of senior managers consider their meetings unproductive and inefficient. And yet the pre-meeting to plan the meeting is on someone's calendar right now. Wednesday. Eight attendees. No agenda.
The reason these unnecessary meetings are funny is that everyone in the organisation recognises them immediately.
The reason they persist is that recognising something is not the same as acting on it.
So as long as the meeting invitation is accepted instead of questioned, the seven specimens in this list will continue to reproduce undisturbed, unaudited, and entirely convinced of their own importance.
Your calendar does not know the difference between a meeting that moves the company forward and a meeting that moves the meeting.
But you do.
The question is whether you will act on that knowledge before the next Friday, 4 pm quick sync arrives, and whether the emoji in the subject line will be enough to make you forget what you know.
@
