The meeting is scheduled for thirty minutes. It will run forty-seven.
You join two minutes early because someone told you a long time ago that this signals reliability. The host is already in the room. They are not talking. They are looking at their other screen. You exchange a small wave through video tiles.
People trickle in. The host says "let's give it a minute for everyone to join." This minute lasts seven minutes.
At minute eight, the host says "okay, why don't we get started." This is a lie. Nothing starts. The host says "before we dive in" and then spends four minutes recapping what was discussed at the previous meeting, which everyone attended, which nobody needed to relive. One person nods aggressively. They do this in every meeting. You are starting to suspect they are not actually paying attention but have developed nodding as a survival skill.
Someone shares a screen. It is a slide deck. The host reads the slide deck out loud. You can also read. So can everyone else in the room. This is happening anyway.
At minute twenty-one, an actual question is raised. The question deserves an answer. The answer is "we should circle back on that." The question is added to a parking lot. The parking lot has fifteen items in it. None of them have ever come back from the parking lot. The parking lot is where ideas go to die quietly.
At minute thirty-one, the host says "in the interest of time." This means the meeting will now run another fifteen minutes.
At minute forty-three, someone says "wait, what did we actually decide here." Nobody can remember. The host says they will send a recap. They will not send a recap. If they do, the recap will be a screenshot of the slide deck.
You leave the meeting. You have a meeting in three minutes. You have not had water in five hours.
What This Meeting Actually Was
It was a status update. Status updates are not meetings. They are documents.
The thing this meeting was trying to do, share information across a group of people who needed to know it, could have been accomplished by a written update that took the host eight minutes to write and the team three minutes to read. The total cost would have been the host's eight minutes plus three minutes times the number of attendees.
Instead, the meeting cost forty-seven minutes times the number of attendees, plus the context-switching cost of leaving whatever everyone was doing, plus the post-meeting recovery time which the productivity researchers say is about fifteen minutes.
For a team of eight, the meeting cost roughly six hours of working time to communicate something that would have taken about thirty minutes to communicate in writing.
This is not a productivity problem. This is a clarity problem dressed as a productivity problem.
Why It Keeps Happening
The recurring status meeting persists for three reasons. They are not the reasons people say out loud.
The host does not trust that people will read the written update. This is sometimes true and is also a solvable problem. If your team does not read the written updates, the answer is not to read the update to them out loud. The answer is to make the updates shorter, sharper, and tied to decisions they actually have to make.
The host is not entirely sure what the meeting is for. The meeting was put on the calendar at some point because the team needed to "stay aligned." Nobody has ever audited whether the meeting is still doing that, because canceling a recurring meeting feels like admitting it should not have existed in the first place. Which it should not have.
The host is anxious about visibility. The meeting is, for the host, a regular reminder to the team that the host exists and is in charge. The actual content of the meeting is secondary. This one is the hardest to say out loud because it is the most accurate.
What to Do Instead
The first move is to audit your own recurring meetings. Not the ones other people run. You can complain about those. The ones you run are the ones you can actually do something about. Pull up your calendar, look at every recurring invite with your name on it as the organizer, and ask yourself what decision each meeting is going to produce that could not be produced any other way. If you cannot answer the question, the meeting should not exist. Cancel it. Nobody will be mad. They will be relieved.
Replace the status update meeting with a written update. Send it on the same cadence as the meeting it is replacing, so the rhythm of the team does not break. Make it short enough that people will actually read it, which means under five minutes of reading time. The format that works is three paragraphs: what shipped, what is at risk, what you need from the team. Anything more belongs in a document people can read if they care. Anything less is not worth sending.
Use meetings for decisions and discussions. Not for information transfer. If the agenda for your meeting is some version of "I will tell you things," that is not a meeting. That is a presentation. Presentations can be recorded, written down, or scheduled for the people who actually need to hear them.
The meeting that has not produced a decision in three sessions is a habit, not a tool. Habits get audited. If the last three of these have come and gone with nothing actionable, the recurring invite is doing something other than what you scheduled it to do, and it is your job to figure out what.
Defend other people's time the way you would defend your own. The thing nobody will tell you, because they have to attend the meeting either way, is that when you send the calendar invite, you are spending hours of other people's working time. They will not push back on you. They will sit through it. They will give you the aggressive nod. That is why it is on you to be careful with the invite in the first place.
There is a specific version of this that applies if you are the high performer in the room. You are sitting through meetings where your ideas get reframed by someone else and credited to that person. You are also, probably, the one running a meeting somewhere on your calendar that another high performer is sitting through with the same complaint. The math runs both directions.
If your calendar is starting to feel like the problem and you are not sure where to begin, the IMPACT diagnostic will tell you. Ten minutes. tally.so/r/oboLXM