You’re about to schedule a meeting.
Before you click “Send Invite,” stop. Ask yourself one question:
Does this actually need to be a meeting?
Because there’s a good chance it doesn’t. Studies show that over half of all meetings could be replaced with an email, a message, or a shared document. That’s not cynicism — that’s data.
The problem is that most of us default to meetings without thinking. Need to share something? Meeting. Need to decide something? Meeting. Not sure what you need? Meeting to figure it out.
But meetings are expensive. You’re asking multiple people to stop what they’re doing and give you their full attention at a specific time. That’s a big ask. It should require a good reason.
This article gives you a simple framework for deciding when a meeting is necessary — and when you should just send an email instead.
Why This Matters More Than You Think
Before we get to the framework, let’s acknowledge what’s at stake.
A one-hour meeting with six people doesn’t cost one hour. It costs six hours of collective productivity. Add in the context-switching before and after, the preparation time, and the calendar fragmentation, and the true cost is even higher.
Now multiply that across every unnecessary meeting in your organization. Every week. Every month. Every year.
The average professional spends 15% of their working life in meetings. For managers, it’s closer to 35-50%. And research consistently shows that at least half of that time is wasted on meetings that didn’t need to happen.
That’s not just an inconvenience. It’s an enormous drain on productivity, focus, and morale.
The good news? You can fix it. Not by eliminating all meetings — some meetings genuinely matter — but by getting better at recognizing which ones don’t.
The PAID Framework
Here’s a simple way to evaluate whether a meeting is necessary. Before scheduling, ask yourself four questions:
P — Is this Participatory?
A — Is there an Action to decide?
I — Is Immediacy required?
D — Is there potential for Disagreement?
If the answer to most of these is “no,” you probably don’t need a meeting.
Let’s break each one down.
P — Is This Participatory?
A meeting should involve active participation from most of the people in the room. If only one person is talking and everyone else is listening, that’s not a meeting — it’s a broadcast.
Ask yourself:
- Will multiple people need to contribute to this conversation?
- Is back-and-forth discussion required?
- Do I need input from the attendees, or am I just sharing information?
If participation is one-way, send an email instead.
Status updates, project announcements, FYI communications, policy changes, weekly reports — these are all broadcasts. They don’t require real-time attendance. Write them down and let people read at their convenience.
Examples:
| Scenario | Meeting? | Why |
|---|---|---|
| Sharing quarterly results with the team | No | One-way information; send a summary with key takeaways |
| Reviewing a document as a group | Maybe | Only if real-time discussion is needed; otherwise share async and collect comments |
| Brainstorming solutions to a problem | Yes | Requires active contribution from multiple people |
| Announcing a new hire | No | Send an email; nobody needs to “participate” in learning someone’s name |
A — Is There an Action to Decide?
Meetings are most valuable when there’s a decision to be made and the people in the room have the authority to make it.
If there’s no decision — if you’re just “aligning” or “syncing” or “touching base” — that’s a warning sign. Vague meeting purposes usually mean vague outcomes.
Ask yourself:
- What specific decision will we make in this meeting?
- Can I articulate the decision in one sentence?
- Do the attendees have the authority to make this decision?
If there’s no decision, send an email instead.
Or better yet, don’t send anything. Not every topic requires formal communication.
Examples:
| Scenario | Meeting? | Why |
|---|---|---|
| Deciding which vendor to choose | Yes | Clear decision required; stakeholders need to weigh in |
| Updating the team on project status | No | No decision to make; send a written update |
| “Syncing” on priorities | Maybe | Only if priorities are actively being debated; if already set, share in writing |
| Reviewing work and giving approval | Maybe | Depends on complexity; simple approvals can happen async |
A useful test: Complete this sentence before scheduling: “By the end of this meeting, we will have decided _______________.”
If you can’t complete that sentence, reconsider the meeting.
I — Is Immediacy Required?
Meetings happen in real-time. That’s what makes them expensive — everyone has to be available at the same moment.
Real-time communication makes sense when speed matters, when the topic is complex enough to require live back-and-forth, or when tone and nuance are important.
But many topics don’t require immediacy. They can wait. People can respond when it’s convenient. And the quality of the response often improves when people have time to think.
Ask yourself:
- Does this need to be resolved today?
- Would giving people time to think improve the outcome?
- Is real-time back-and-forth essential, or would async work?
If immediacy isn’t required, send an email instead.
Async communication isn’t just more convenient — it’s often better. People can read carefully, consider their response, and contribute more thoughtfully than they would in a live meeting where they’re put on the spot.
Examples:
| Scenario | Meeting? | Why |
|---|---|---|
| Crisis response requiring immediate coordination | Yes | Time-sensitive; real-time coordination essential |
| Gathering feedback on a proposal | No | Better done async so people can think before responding |
| Answering a quick question | No | Send a message; don’t schedule 30 minutes for a 30-second answer |
| Complex negotiation with external partners | Yes | Nuance and tone matter; real-time discussion is valuable |
D — Is There Potential for Disagreement?
Some topics are straightforward. Everyone’s aligned, the answer is obvious, and formalizing it is just a procedural step.
Other topics are contentious. People have different perspectives, competing priorities, or conflicting information. Resolving that conflict requires conversation — hearing each other out, asking clarifying questions, and working toward alignment.
Disagreement is one of the best reasons to have a meeting. Text-based communication is terrible for navigating conflict. Tone gets misread. Nuance gets lost. Small misunderstandings become big ones.
Ask yourself:
- Is this topic likely to generate debate?
- Are there conflicting perspectives that need to be heard?
- Would misunderstanding be costly?
If everyone already agrees, send an email instead.
Confirmation doesn’t require a meeting. If the decision is clear and uncontroversial, just document it and move on.
Examples:
| Scenario | Meeting? | Why |
|---|---|---|
| Choosing between two strategic directions | Yes | Likely disagreement; discussion needed |
| Confirming a date that works for everyone | No | Use a poll or async scheduling tool |
| Delivering difficult feedback | Yes | Tone matters; sensitive conversations deserve real-time attention |
| Sharing meeting notes and next steps | No | Just send the notes |
Putting It Together
Here’s the framework in action:
Should this be a meeting?
| Question | Yes = +1 | No = 0 |
|---|---|---|
| Is this participatory? (Multiple people actively contributing) | ||
| Is there an action to decide? (Clear decision to be made) | ||
| Is immediacy required? (Must happen in real-time) | ||
| Is there potential for disagreement? (Conflicting views to resolve) |
Scoring:
- 3-4: This should probably be a meeting
- 2: Consider whether a shorter meeting or async could work
- 0-1: This should probably be an email
When the Answer Is “Email” — What to Actually Send
Deciding not to meet is only half the battle. You still need to communicate effectively.
Here’s what makes async communication work as a meeting replacement:
- Be specific about what you need. Don’t just dump information — tell people what you want them to do with it. “Please review and reply with your approval by Thursday” is infinitely better than “FYI.”
- Structure for scanning. People skim emails. Use headers, bullet points, and bold text to make key information findable.
- Set a deadline. Without a meeting forcing a decision, async conversations can drift forever. Give people a clear timeline for responding.
- Make the decision default clear. “Unless I hear objections by Friday, we’ll proceed with Option A” prevents stalling.
- Offer a meeting as an option. “I don’t think this needs a meeting, but if anyone wants to discuss live, let me know and I’ll schedule something.” This respects both preferences.
When the Answer Is “Meeting” — Make It Worth It
If you’ve run through the framework and decided a meeting is genuinely necessary, great. Now make it count.
- Keep it short. Most 60-minute meetings can be 30. Most 30-minute meetings can be 15. Default to the shortest time that’s plausible.
- Limit the invite list. Every additional attendee increases the cost and decreases the chance of a productive conversation. Only invite people who need to participate — not people who might find it “useful to know.”
- Share the agenda in advance. People should know why they’re there before they walk in. “Discuss project status” isn’t an agenda — it’s a placeholder. “Decide whether to extend the launch deadline” is an agenda.
- End with clear outcomes. Before the meeting ends, state out loud: what did we decide, who is doing what, and by when? If you can’t answer those questions, the meeting isn’t over.
The Hardest Part: Changing the Default
The framework is simple. Using it consistently is hard.
Meetings are the default for a reason. They’re easy to schedule. They feel productive even when they’re not. And opting out — either as an organizer or an attendee — takes more courage than just going along.
But every meeting you don’t schedule is an hour you’ve given back to your team. Every meeting you replace with a well-crafted email is a signal that you respect other people’s time.
And when you do call a meeting, it will mean something. People will show up expecting it to matter — because your meetings always do.
That’s the reputation worth building.
What If You’re Not the Organizer?
Everything so far has been about deciding whether to schedule a meeting. But what if you’re on the receiving end?
You attend meetings you didn’t call. You sit through status updates that could have been emails. You watch the clock wondering why you’re there.
And you can’t exactly say that to the organizer.
Or can you?
Most meeting organizers have no idea how their meetings are perceived. Nobody tells them. Everyone just shows up, nods politely, and moves on.
That silence is why bad meetings persist.
If meeting organizers got honest feedback — real data on whether their meetings are valuable — they’d have a reason to change. The meetings that work would continue. The meetings that don’t would get fixed or disappear.
That’s exactly why we built Could Have Been an Email: a way for attendees to anonymously give feedback on any meeting they attend. No politics. No fear. Just honest data, shared equally with everyone in the room.
Because sometimes the best way to fix meeting culture isn’t a framework for the organizers — it’s a voice for the attendees.
