When to Meet and When a Message Would Do

The part overview made the case that a meeting is one of the most expensive things a group can do, and that most of them fail to earn their cost. This page hands you the single filter that prevents the most common waste of all: calling a meeting for something that never needed to be a meeting.

Here is the whole idea in one sentence. A meeting is a demand that several people stop what they are doing and be in the same conversation at the same moment. That demand is sometimes exactly right and sometimes pure waste — and you can usually tell which in about thirty seconds if you ask the right question. This page teaches that question, the distinction underneath it, and a short checklist you can run before you ever open the calendar.

Get this one filter working and it changes the texture of a whole week. The meetings you do hold become sharper, because the ones that shouldn’t exist never got scheduled to crowd them out. And the quiet work that actually moves things forward — the building, the thinking, the doing — gets the uninterrupted stretches it needs. This is the highest-leverage habit in the entire part, because it acts before any of the cost is paid.

The principle: a message is the default, a meeting must earn its existence

Start from what a meeting actually is, stripped of habit. It is synchronous communication: everyone present, everyone live, everyone’s time consumed at once. That synchronicity is the entire cost — and it is also the only thing a meeting offers that a message does not.

So the question is never “should we discuss this?” Of course you should. The question is: does discussing it require everyone live and synchronous, right now? Most of the time the honest answer is no. The information could be written once and read by each person when they have a moment. The approval could be a one-line reply. The update could be a short recorded clip.

This flips the usual instinct. Most people treat the meeting as the default — the natural way to “get everyone on the same page” — and reach for a message only when a meeting feels like too much. Turn that around. The message is the default. The meeting has to justify itself. A calendar invite should feel like a small claim you are making on other people’s lives, one you’d be a little embarrassed to make without a reason that only real-time contact can satisfy.

The reason this matters so much is that a message and a meeting fail in opposite, revealing ways. A message that should have been a meeting fails loudly — the thread goes in circles, tempers fray, someone finally says “can we just get on a call?” — and you fix it in minutes. A meeting that should have been a message fails silently — everyone shows up, sits politely through information they could have read in ninety seconds, and leaves with no idea the time was wasted, because the cost was invisible and shared. The loud failure self-corrects. The silent one repeats forever. That asymmetry is why the safe default is the message: when you guess wrong in that direction, the mistake announces itself and is cheap to reverse.

The evidence — the arithmetic of a meeting

Surveys of office work generally find that a large share of meetings are rated by attendees as unnecessary or unproductive, and that managers spend a strikingly large fraction of their week in them — often cited as roughly half. Treat the exact figures loosely; the pattern is robust. The underlying reason is structural, not a matter of bad luck: because a meeting’s cost is spread across everyone’s calendar and paid silently, nobody feels the bill, so meetings get scheduled far more freely than their true expense would ever justify. Making the message your default is the cheapest way to bring that bill back into view.

Synchronous work vs. asynchronous work

The filter becomes easy once you can sort work into two buckets. Some things genuinely need people live and together. Most things don’t. Learn the difference and half your calendar decisions make themselves.

Synchronous work — the kind a meeting is actually good at — has a common signature: it needs fast back-and-forth between people who can react to each other in the moment. Writing is too slow for it, or the human element matters too much to flatten into text.

• Debate. Several people hold different views and need to push on each other’s reasoning in real time, building on and challenging replies as they land. A written thread would take days and lose the thread.
• A decision under genuine disagreement. When people don’t yet agree and the choice matters, live discussion lets objections surface, get answered, and converge. (When people already agree, you don’t need the meeting — see below.)
• A sensitive conversation. Difficult feedback, a layoff, a conflict between two people, bad news. Tone, presence, and the ability to respond to someone’s reaction carry most of the meaning. These belong live, often one-to-one.
• Brainstorming with momentum. Early, generative thinking where one half-formed idea sparks the next. The energy of people riffing off each other in the moment produces things a solitary document rarely does.

Asynchronous work — the kind a message does better, not just cheaper — has the opposite signature: it is one-directional or slow-moving, and each person can absorb it on their own time.

• Status. “Here’s where the project stands.” Nobody needs to react live; they need to know. Writing it down is faster to produce and far faster to consume than sitting through it read aloud.
• An FYI. A policy change, a new hire, a shifted date. Pure broadcast. A meeting to announce it wastes everyone but the speaker.
• A simple approval. “Can I proceed with X?” If the likely answer is yes and the details are clear, that is a one-line reply, not a thirty-minute slot.
• Document review. Comments on a draft. People read best alone, at their own pace, leaving remarks in the margin — not staring at a shared screen while one person scrolls.

Picture a small cafe owner rolling out a new menu. The decision about which dishes to add, where the staff genuinely disagree about what will sell and what the kitchen can handle at peak, is synchronous — get them in a room for twenty minutes and let them argue it out. But the final menu, once decided, is asynchronous: a printed sheet pinned by the pass and a quick message to the group chat does more than a meeting ever could, because each cook can study it on their own break and refer back mid-service. One topic, two phases, two different tools. The skill is telling the phases apart.

NEEDS EVERYONE LIVE?              A MESSAGE DOES IT BETTER?
────────────────────────         ────────────────────────
Debate                           Status update
Decision under disagreement      FYI / announcement
Sensitive conversation           Simple approval
Brainstorm with momentum         Document review
  → hold a meeting                 → write it down

The two lists aren’t a rigid law; they’re a starting sort. What actually decides the bucket is the reason underneath. A status becomes meeting-worthy the moment the status is alarming and people need to react and re-plan together — then it’s really a decision under disagreement wearing a status label. An approval becomes meeting-worthy if the “yes or no” hides a real judgment call several people must weigh in on. So don’t sort by the name of the activity; sort by whether, in this specific case, people need to respond to each other in real time. When they do, meet. When they only need to know or react on their own, write.

In practice — the update that shrank to a paragraph

A hospital ward ran a daily 30-minute “handover meeting” where each nurse read out the status of their patients while the rest listened. Most of it was routine and stable — information the next shift needed to have, not discuss. The ward switched to a shared written handover sheet each nurse filled in before shift-change, and kept a five-minute live huddle only for the genuinely tricky cases that needed a real conversation. The routine status went async; the judgment calls stayed synchronous. They reclaimed most of the half-hour and, because the sheet was written down, fewer details got lost in the retelling.

The test: could this be a doc, a thread, or a recorded update?

Here is the filter as a single, portable question you can ask about anything you’re tempted to schedule:

Could this be a document people read, a message thread they reply to, or a short recording they watch on their own time — instead of a live meeting?

If the honest answer is yes, don’t meet. Write the doc. Start the thread. Record the two-minute update. You will save everyone’s synchronous time and usually communicate better, because writing forces you to be clear in a way that talking rarely does.

Only when the answer is a genuine no — when the thing truly needs the live back-and-forth of synchronous work — has the meeting earned its place. Notice that this test also tells you the format: not everything that isn’t a meeting is an email. A decision-in-progress might be a threaded discussion; a status might be a dashboard; an announcement might be a recorded clip. “Not a meeting” is a menu, not a single fallback.

A useful sharpening of the test is to ask what the live minutes would actually be spent on. Picture the meeting happening. If most of it is one person talking while others listen — reading out a report, walking through slides, announcing a decision already made — that talking is broadcast, and broadcast is what writing and recording do better, because the audience controls the pace. The only minutes that truly need everyone synchronous are the ones where people respond to each other: a question that changes the next sentence, an objection that reshapes the plan, a reaction you need to see on someone’s face. If you imagine the meeting and can’t find those minutes, you’ve imagined a document being read aloud. Cancel it and send the document.

Case study — Amazon’s six-page memo (from the early 2000s)

Amazon famously banned slide presentations for many meetings and replaced them with a narrative memo — often around six pages — that the group reads in silence at the start of the meeting before any discussion. The lesson isn’t the page count; it’s the underlying principle. Writing a real argument down is harder than talking through slides, and that difficulty is the point: it exposes fuzzy thinking that a live presentation would have glossed over. Much of what we call a “meeting” is really an excuse to avoid the discipline of writing clearly. When the thinking is written first, the live time can be spent on what only live time is good for — genuine discussion — and a lot of would-be meetings turn out not to need the meeting at all.

The traps: why we meet when we shouldn’t

If a message is so often better, why do we reach for meetings anyway? Because meetings quietly serve needs that have nothing to do with communication — and naming those needs is how you stop falling for them.

• Meeting to feel busy. A calendar full of meetings feels like work and looks like importance. But a booked calendar is not the same as progress; often it’s the enemy of it, because the meetings crowd out the focused time where the actual work gets done.
• Meeting to share responsibility. Calling everyone into a room so “we all decided together” can be a way to make sure no single person is on the hook if it goes wrong. Real alignment is worth a meeting; using a meeting to blur accountability is not, and it usually produces a decision nobody actually owns.
• Meeting to avoid writing something down. This is the big one. Writing is effortful — it forces you to know what you actually think. A meeting lets you stay vague, “talk it through,” and leave without ever committing to a clear statement. That comfort is exactly why the meeting felt easier, and exactly why it was the wrong choice.
• Meeting because someone might feel left out. Meetings get bloated with attendees invited for reassurance, not contribution. Inviting someone to be polite feels kind, but it quietly taxes their time and dilutes the room. A better kindness is a clear written summary sent afterward: people stay informed without having to sit through a conversation they had no stake in.

A quick way to catch yourself: for each trap, there’s a truthful sentence you’d be reluctant to say out loud. “I’m booking this so my day feels productive.” “I want cover if this goes wrong.” “I haven’t figured out what I think, so I’ll wing it live.” “I’m inviting them so they don’t feel excluded.” If the real reason, said plainly, sounds like one of those, you’ve found a message pretending to be a meeting.

The common trap — the recurring meeting nobody dares to cancel

The most expensive meetings are rarely the one-off ones; they’re the standing meetings that made sense once and now run on pure inertia. A weekly sync gets created for a real reason, the reason fades, and the meeting continues — because canceling it feels like a bigger decision than attending it. Nobody feels the accumulating cost, so nobody acts. Audit your recurring meetings the way you’d audit a subscription: for each one, ask whether it would genuinely need to be created today if it didn’t already exist. Many wouldn’t. The next page makes that cost concrete enough to act on.

The honest cost of going async

None of this means writing is free. A message shifts cost rather than erasing it, and pretending otherwise is how teams overcorrect from too many meetings into a swamp of endless threads. It’s worth naming the trade so you choose it with open eyes.

• Writing loads the sender, meeting loads everyone. A clear document takes the author real effort up front — but it’s paid once, by one person, and saves each reader time forever after. A meeting is the reverse: cheap for the organizer to call, expensive for everyone who attends. As a rule, prefer the option that concentrates cost on the person best placed to do the thinking, and spares the many.
• Async is slower per round-trip. A live disagreement can resolve in ten minutes; the same disagreement in a thread might take two days of replies. When something needs many quick rounds and it’s genuinely contested, that slowness is the tell that you’ve crossed into synchronous territory. The threshold isn’t “is there any back-and-forth” — it’s “does the back-and-forth need to be fast.”
• Some things carry badly in text. Tone, empathy, and nuance are easy to lose in writing, and a misread sentence can do real damage. This is why sensitive conversations belong live even when they could technically be “handled” over message. The medium isn’t just about speed; it’s about whether the human element survives the trip.

So the goal isn’t “never meet.” It’s to spend synchronous time only where it’s the right tool — fast contested rounds, human moments, live generation — and let everything else settle into writing where it’s cheaper and clearer. A team that gets this balance right meets rarely and communicates constantly.

The evidence — why writing tends to sharpen thinking

Studies of writing and learning generally find that composing an idea in prose forces a kind of processing that talking doesn’t demand: you have to sequence the argument, close the gaps, and commit to specifics, with no tone of voice or hand-waving to paper over the cracks. Hold the specific claims loosely, but the direction is well supported — the act of writing surfaces confusion that a conversation lets you glide past. This is the quiet bonus of a message-first default: it’s not only cheaper on everyone’s calendar, it tends to produce clearer thinking as a side effect.

A decision checklist before you send the invite

Run this before any calendar invite. If you can’t clear the first gate, you don’t have a meeting — you have a message.

BEFORE YOU SCHEDULE A MEETING, ASK:

1. Does this need real-time back-and-forth?
   (debate · decision under disagreement · sensitive talk · live brainstorm)
   → NO  → write a doc, thread, or recording. Stop here.
   → YES → continue.

2. Could a document, thread, or recording do it just as well?
   → YES → do that instead. Stop here.
   → NO  → continue.

3. Am I really reaching for a meeting to feel busy,
   spread the blame, or avoid writing it down?
   → YES → name it, then write it down instead.
   → NO  → continue.

4. Do I know who must be live for this, and why each one?
   → NO  → figure that out first; don't invite "everyone" by default.
   → YES → NOW you may schedule — with an agenda and a clear purpose.

Gate 4 hands you off to the rest of this part. A meeting that clears these gates has earned its existence — and now deserves to be run well: the right people, a real agenda and pre-read, and a clear way to decide and follow up. Earning the meeting is step one; not wasting it is everything after.

A small caution about the checklist itself: it’s a filter, not a bureaucracy. You don’t need to write out four answers on paper before every conversation — the point is to run it in your head often enough that skipping the pointless meeting becomes reflex. Used well, it should take seconds and mostly end at gate 1 or 2, sparing you the meeting entirely. The checklist has done its job when you rarely need to consult it, because a message-first instinct has become your default.

How it connects

This filter is the gatekeeper for the whole part. Once a meeting passes it, The Real Cost of a Meeting shows you the true bill you’re choosing to pay, and Types of Meetings helps you pick the right shape for the job. The preference for writing over talking echoes a theme that runs through the whole book — clear communication as the backbone of reliable outcomes — and it pairs naturally with the async habits in the rituals that earn their keep.

Try this

This week, catch one meeting before you schedule it — one you’d normally book on reflex — and run it through the checklist above. If it fails gate 1 or 2, don’t hold it: write the doc, post the thread, or record the update instead, and send that to the people who’d have attended. Then notice two things: how long the written version actually took to produce, and whether anyone missed the meeting. Separately, look at your recurring meetings and pick the one you’d least confidently re-create from scratch today — that’s your first candidate to cancel or shrink.

Reflect

1. Look at your calendar for the past week. Which meetings needed everyone live and synchronous — and which were really status, FYI, approval, or review that a message could have carried?
2. When you last called a meeting, what was the honest reason? Was it real-time back-and-forth — or was it partly to feel busy, share responsibility, or avoid writing something down?
3. Which of your recurring meetings would you not create today if it didn’t already exist? What keeps it on the calendar?
4. Where in your work does writing feel harder than talking — and is that difficulty a sign the writing is exactly what’s needed?
5. If your default flipped from “book a meeting” to “write a message,” what would change about how your week feels and how much focused time you’d get back?

Show reflections

1. Most people find the synchronous-worthy meetings are a minority. The value is in seeing, concretely, how much live time went to things that were one-directional — status, announcements, approvals — and could have been read on someone’s own schedule.
2. This is meant to catch the hidden motives honestly. If the reason was genuine debate or a hard conversation, the meeting was earned. If it was busyness, blame-spreading, or avoidance of writing, that’s the trap firing — and naming it is what disarms it next time.
3. The recurring-meeting audit almost always turns up one or two that survive on inertia alone. What keeps them is usually that canceling feels like a decision and attending doesn’t — so the fix is to make the default reversal explicit: prove it should exist, or drop it.
4. A strong answer notices that the resistance to writing is often a signal, not an obstacle. If putting it in words is hard, it’s usually because the thinking isn’t clear yet — and a meeting would have let that fuzziness slide. Writing is where clarity gets forced.
5. The point is to feel the compounding effect: fewer meetings means more uninterrupted time for the actual work, clearer written records people can refer back to, and decisions that have an owner. The trade-off is that writing takes upfront effort — but that effort usually buys back far more than it costs.