The test, in one question
Before booking anything, answer this: do these people need to respond to each other, or do they just need to respond to me?
If the answer is the second one, you are transferring information, and a document does it better. People read at their own pace, refer back to it, and do not have to be simultaneously available in five different calendars.
If the answer is the first, you probably need the meeting, because written back-and-forth is slow for genuine discussion and terrible for disagreement.
Second question, if the first is unclear
What decision will exist at the end of this meeting that does not exist now? If you cannot answer, you are planning a broadcast. Write it.
When to meet, when to write
| Purpose | Meet or write | Why |
|---|---|---|
| Sharing a decision already made | Write | Nobody needs to respond, they need to know |
| Making a decision with trade-offs | Meet | People need to react to each other's reasoning |
| Status and progress updates | Write | Reference-able, and readable at speed |
| Anything with disagreement in it | Meet | Written disagreement escalates |
| Giving critical feedback | Meet | Tone does not survive text |
| Brainstorming options | Both | Write first, then meet to choose |
| A complex explanation | Write, then meet | Reading first makes the meeting shorter |
| Anything emotionally loaded | Meet | Always |
| Onboarding someone to context | Write, then meet | The document is what they re-read later |
Two rows deserve emphasis. Anything with disagreement in it should be a meeting, because written disagreement hardens: people compose positions rather than think, and tone is consistently read as more hostile than intended.
And complex explanations work best written first. Sending the document beforehand and meeting only to handle the questions typically turns a sixty minute meeting into a twenty minute one.
How to write the thing that replaces the meeting
A written update that actually replaces a meeting needs more structure than a message thrown into a channel. Four parts:
State the point in the first two lines
What this is about and what, if anything, is needed from the reader. People decide whether to keep reading in about five seconds.
Burying the ask at the bottom is the most common reason a written update fails to replace a meeting: nobody reaches it.
First two lines carry itSeparate what is decided from what is open
Two headings. Decided items need no response. Open items are where you want input.
Mixing them means people either respond to everything or nothing, and both outcomes waste the exercise.
Two headings, alwaysName who needs to do what, by when
By name. "Someone should look at this" is reliably nobody.
This is the part a meeting does naturally through eye contact, and the part writing loses unless you are deliberate about it.
Names and datesSet a response deadline
"If I do not hear back by Thursday, I will proceed with option B." Without this, a written decision can sit indefinitely, which is what people mean when they say async is slower.
A default action plus a deadline is what makes written decision-making faster than meeting.
Default action plus a date
Cancelling meetings without causing offence
The obstacle is almost never a rational one. It is that cancelling implies a judgement about whoever set it up.
Three approaches that avoid that:
Attach it to a trial. "Let us try replacing this with a written update for a month and see if we miss it." Nobody has to defend the meeting, and reinstating it costs nothing.
Cut the invite list rather than the meeting. Often the meeting is fine and only three of the nine people need to be there. Telling six people the meeting is now optional for them is easier than cancelling, and recovers most of the time.
Decline individually, and say why. "I do not think I add much here, could you send me the notes?" Done openly once, it gives everyone else permission.
The version that works better than either
For most recurring meetings, the best structure is neither pure meeting nor pure document.
Written update circulated in advance, then a short live session for questions and decisions only. The reading happens on people's own time, the meeting handles the parts that genuinely need people in a room, and it is usually half the length.
The rule that makes it work: if nobody has questions on the document, the live session is cancelled that week. Which happens more often than people expect, and each time it does, that is an hour back for everyone.
Frequently asked questions
- How do I know if something needs a meeting?
- Ask what decision will be made and who has to react to whom. If the answer is that people need to respond to each other, meet. If the answer is that everyone needs to know something, write it. Information transfer is the single largest category of unnecessary meetings.
- Is it rude to decline a meeting?
- Not if you decline clearly and ask for the notes. It becomes normal quickly once one or two people do it openly. Most unnecessary attendance persists because declining feels impolite, not because anyone believes the attendance is useful.
- What about meetings for team connection rather than work?
- Those are legitimate, and the mistake is disguising them as work meetings. A social meeting with a fake agenda satisfies nobody. Name it for what it is, keep it optional, and it will work far better.
- Should status updates ever be meetings?
- Rarely. Status is information, and information transfers better in writing where people can read it at their own pace and refer back to it. The exception is when the status itself needs interpretation or triggers immediate decisions.
- How do I convince my team to have fewer meetings?
- Do not campaign. Cancel one recurring meeting you own, replace it with a written update, and let people notice that nothing was lost. Demonstrating it once works better than arguing for it repeatedly.