Should Your Meeting Be an Email? Find Out Using AI

Your calendar has a recurring meeting nobody remembers the reason for anymore. It keeps happening because canceling it costs more political capital than just showing up quietly, and sometimes it's simply cultural: you've gotten so used to that meeting existing that you assume it must be useful.

Every meeting exists to solve one of two problems: a decision that changes direction depending on who speaks up in the moment, or an update that doesn't change anything whether it's read right now or two hours from now. Only the first problem requires everyone in the same place at the same time. The second one has always been an email, or whatever official channel your team already uses, like Slack, Microsoft Teams, or even a WhatsApp group chat.

Why AI sees the meeting web you can only see from inside it

You know the purpose of each of your own meetings, one at a time. What you rarely do is lay all of them side by side and ask whether two of them are, without anyone noticing, solving the same problem. AI scans the whole list at once and spots the overlap on the first pass, because it isn't stuck living each meeting separately from the others.

The test doesn't depend on notes or a meeting history, just on what you already know off the top of your head: what's usually discussed in each meeting, and whether that discussion changes direction depending on who's in the room live, or just confirms something that was already decided.

The prompt that cross-checks urgency and overlap for you

Asking AI "which meetings have less value" gives it no real criteria to apply. It needs two concrete tests: urgency of response, and overlap with the rest of the calendar.

I'm going to describe my team's recurring meetings: name, frequency, participants, and what's usually discussed or decided in each one. Based on that, I want you to:
1. For each meeting, assess whether the topic usually requires a real-time response or decision (something that could change 
direction depending on live debate), or whether it could wait for an asynchronous reply without real cost to the team.
2. Cross-reference the meetings against each other and flag if any of them fully or partially cover the same ground as another.
3. For low-urgency or redundant meetings, suggest the equivalent async format and the ideal update frequency.

Meetings: [list each one with frequency, participants, and what's usually discussed or decided in it]

Run this on a team with a typical tech routine, and the output looks something like this:

Weekly status sync (30 min, Monday, 8 people): low urgency, it's a progress update that doesn't change direction based on live debate. Partially overlaps with the biweekly planning meeting.
Suggestion: move to an async update in the team channel.
Biweekly prioritization meeting (60 min, 5 people): high urgency, an item's priority shifts depending on who argues for it in the room. Doesn't overlap with any other routine. Keep the meeting format.

Why this test works

The test works because it doesn't ask you to already know which meeting is weak, it only asks for what you already know without effort: what's usually discussed in each one. It's the AI that cross-references urgency and overlap across all of them at once, something nobody stops to do by laying out the whole calendar together.

Most executive teams can reclaim 30 to 40% of the time spent in meetings without losing real collaboration. The hard part was never spotting that, it was having the conversation about pulling a meeting off someone's calendar. Coming from a cross-check across the whole agenda, that conversation gets less personal.

Next time your calendar fills up again, the question isn't whether the meeting was productive yesterday. It's whether it genuinely needs a real-time response, or whether another meeting on your calendar is already covering the same ground.