How to ask if a meeting could be an email instead

Do not ask the question. Send the thing the meeting was booked to produce, then say the slot is still there if they want it. Someone who already has the answer in their inbox will cancel the meeting themselves, and they get to be the one who did it.

The joke has been told too many times for the sincere version to survive. Say "could this be an email?" and a lot of people hear "I think your meeting is a waste of my afternoon."

Which is often what it means. That is the part worth being honest about before you send anything.

Why the plain question lands badly

The question asks the organizer to defend a decision they have already made, usually in front of everyone they invited.

Someone looked at a calendar, found a gap that worked for five people, and spent a bit of their own credibility booking it. Your question puts that on trial.

It also gives them nowhere good to stand. If they say yes, they wasted everyone's time. If they say no, they sound defensive about their own invite. Most people pick no.

And the real subject leaks through. The organizer hears that your half hour is worth more than the half hour they spent arranging it, which is a claim you did not intend to make and cannot take back.

Do the meeting in writing before it happens

The move that works is to deliver the meeting's output early and let the reason for meeting quietly disappear.

If the meeting is a status check, the status goes in the message. If it is a decision, you send the options with your recommendation and the date you need an answer by. A review turns into a document that arrives with your comments already in it.

This is more work than typing one sentence about calendars. That is why it reads as help instead of complaint.

The cancel decision stays with the person who booked the slot, and that is the whole trick. You are removing the reason rather than arguing about it.

Half an hour of writing to save half an hour of meeting sounds like a bad trade. It is not, because the writing survives the week, gets read by the two people who missed the call, and settles the question again the next time it comes up.

The message, and the words that do the work

A message that turns a meeting into a thread has four parts and fits on a phone screen.

• Say what you think the meeting is for, in one line, so they can correct you.
• Put the actual content in the message instead of promising to send it later.
• Name the one thing you need back, and when you need it.
• Leave the slot standing and let them decide what to do with it.

Here is roughly what I send. "I think Thursday is about whether the onboarding change ships before the audit. My read is below, with the two options and the one I would pick. If a reply works, I will drop the slot. If you would rather talk it through, I will be there with this open."

The last two sentences are the polite part. "If a reply works" is an exit that costs the other person nothing, and "I will be there" proves you were not fishing for a free afternoon.

Notice what is missing. No line about how many meetings you have this week. Your calendar is a complaint with a spreadsheet attached, and it persuades nobody.

When the meeting should stay a meeting

Some conversations get worse in writing, and forcing those into a thread costs more time than the meeting ever would.

• People disagree, and the disagreement is not really about the facts.
• Someone is about to hear news they will not like.
• You have never worked with them and have no read on how they take things.
• The idea is half formed and needs somebody to interrupt you mid sentence.
• Several people need to react to each other rather than to you.

I have watched a contested call turn into a four day thread that ended in a meeting anyway, with everyone crosser than when it started. Written disagreement is a skill, and it has a shape that works, but the shape takes longer than talking when feelings are already in the room.

Recurring status meetings are the opposite case. They are the easiest thing in the world to replace with a written update people actually read, which is why they are the ones worth spending this move on.

Asking someone senior to you

Upward, you ask once, in terms of what they get, and then you let it go.

Frame it around their outcome rather than your time. "You would have the decision by tomorrow morning instead of Thursday" gives a senior person a reason to say yes that has nothing to do with being nice to you.

Send it as a direct message, never in the group thread. In public it reads as a challenge to the person who called the meeting, and they will defend the meeting to defend themselves.

One attempt. If they keep the slot, show up and be the most useful person in it, because you have already written the material and everyone else is reading theirs off the screen.

This is the message where tone carries most of the weight, and my first drafts of it are always a few degrees colder than I mean. Taking the Warm rewrite in Unvent is usually where I find that out, because the offer suddenly reads like an offer again.

The recurring meeting version

For a standing meeting, do not raise the format at all. Propose a trial with an end date.

"Can we try the written version for the next two and see if anything breaks?" is easy to say yes to because it is easy to reverse. Nobody is being asked to admit their meeting was pointless, only to run an experiment that they can end whenever they like.

Then you have to actually send the written version, on time, both times. I have lost this argument by winning it: I got the trial, then got busy in week two, and the meeting was back on the calendar by the end of the month. Organizers are right to be suspicious of us.

If the trial goes well, say nothing and keep writing. Someone deletes the recurring invite a few weeks later and never mentions it.

The uncomfortable half of this

A lot of meetings that could be emails exist because somebody's emails were bad.

People book time to decode messages. A vague update has a calendar invite waiting behind it, and so does an ask with no date on it. The invite finds you eventually.

I have booked those meetings myself, more than once, because reading the thread again felt slower than asking the person out loud. That is not a meetings problem.

So the fastest route to a quieter calendar runs through your own outbox. Put the decision you need in the first line and leave nothing in the message that somebody would have to ask you about. I still get this wrong on the days I am typing fast, and I can usually name the meeting it cost me.