The recurring meeting that should have been a system

Look at any organization’s standing weekly meetings and you will find at least one that exists because a system doesn’t. It was created during a genuinely difficult stretch, it helped, and then it stayed — long after the difficulty passed and long after anyone remembered why it started.

These are expensive. Not dramatically, which is exactly the problem. Eight people, forty-five minutes, every week, is roughly three hundred hours a year. Nobody has ever proposed a three-hundred-hour project without a business case, and yet the meeting renews itself indefinitely on nothing but inertia and the awkwardness of being the person who suggests cancelling it.

How to tell the difference

Not every recurring meeting is waste. Some genuinely need to exist: the ones where people make decisions together, work through ambiguity, or build the trust that makes hard conversations possible later. Those are cheap at twice the price.

The suspect ones have a specific shape. Watch for these:

• Most of the time is status reporting. People saying what they did, to people who could have read it. If the meeting could be replaced by a document with no loss, it is a document wearing a calendar invite.
• The same issue comes up more than three times. A recurring topic is not a discussion item. It is an unresolved system problem that the meeting is absorbing instead of fixing — and absorbing it is what allows it to stay unfixed.
• Attendance is defensive. People come because being absent means decisions get made without them, not because they contribute. That is a signal about how information flows, and it will not improve by adding another meeting.
• Nobody can say what a good outcome is. Ask what would make this week’s meeting a success. Silence is an answer.

A meeting that keeps handling the same problem isn’t solving it. It’s storing it.

What we actually did

One weekly meeting on our schedule existed to catch scheduling conflicts across disciplines — two providers assigned to the same room, a family booked with the wrong clinician, that kind of thing. Real problems, worth catching. It ran for years.

When we finally traced it, three things turned out to be true. Most conflicts came from one specific gap between how two systems handled recurring appointments. Nearly all of them were visible in the data on the day they were created, not on the day of the meeting. And the meeting was catching them an average of four days after they became a problem for somebody.

So the fix was not a better meeting. It was a daily report that flagged the conflicts automatically, and a small change to how one of those recurring appointments was entered. Both took a couple of weeks of unglamorous work.

The meeting went from forty-five minutes weekly to fifteen minutes biweekly, and the remaining fifteen minutes got spent on the genuinely ambiguous cases that need human judgment — which is what those people were good at, and what the status reporting had been crowding out.

If you want to try this

1. Pick one meeting. Not all of them. Nothing derails this faster than turning it into a calendar audit.
2. Log what actually comes up for a month. Every item, one line. Do not analyze yet.
3. Sort the log into three piles: information that could have been written down, recurring issues with a common cause, and genuine judgment calls.
4. Handle the first pile with a document, the second with a fix, and keep the meeting for the third. The third pile is almost always smaller than the calendar suggests.
5. Tell people why. Cancelling a meeting without explanation reads as a decision made about them. Explaining what replaced it reads as respect for their time — and gets you the next four meetings volunteered.

Most organizations have three or four of these. Finding them takes a month of paying attention. Fixing one usually buys back more time than any tool you could purchase this year.