Half My Meetings This Week Could Have Been an Email
I counted my meetings last week: 14. Status updates with clients who just wanted to know things were on track. 'Quick syncs' that lasted 45 minutes. Kick-off calls for projects that hadn't started yet. At least half could have been a 2-paragraph email. That's 7+ hours, almost a full workday, gone to meetings that didn't need to exist.
Why do most meetings not need to exist?
- 98% of meetings are status updates, information sharing, simple decisions, or coordination, none of which require synchronous conversation.
- Meetings persist because 'schedule a meeting' is the path of least resistance, not because real-time conversation is the best format.
- For freelancers and consultants billing $200–$500/hour, unnecessary meetings cost $104K–$390K in lost annual capacity.
- The fix: default to async communication and only schedule meetings when synchronous conversation genuinely improves the outcome.
Meetings create real value for complex problem-solving, negotiation, high-stakes decisions, and relationship building. Everything else should be async.
The Meeting Tax
Lost to unnecessary meetings per week
Annual cost at $200-$500/hour billing rate
The Problem: Meetings Are the Default for Everything
In most organizations, "let's schedule a meeting" is the default response to any question, decision, or coordination need.
The result: calendars filled with 30-minute and 1-hour blocks for conversations that could have been a 2-minute Slack message, a 5-paragraph email, or a shared document.
Here's what gets turned into meetings unnecessarily:
- • Status updates ("What's the progress on X?")
- • Information sharing ("Here's what happened this week")
- • Simple decisions ("Should we do A or B?")
- • Coordination ("When can everyone meet next?")
- • Quick questions ("Can you clarify this?")
- • FYI announcements ("Just wanted to let everyone know...")
None of these require synchronous conversation. But because "schedule a meeting" is the path of least resistance, they consume 10-15 hours per week, time that could go toward client work, deals, or deep thinking. The result is a culture that rewards activity over actual output.
What Most Meetings Actually Are
When you audit what happens in meetings, most fall into one of five categories, and four of them don't require synchronous conversation:
1. Status Updates (70% of Meetings)
What it is:
People take turns sharing what they've been working on, blockers they've hit, and what's next.
Why it's a meeting:
Because everyone's calendar was open at the same time, and "let's sync" felt easier than writing updates.
What it should be:
A shared document, Slack thread, or email where everyone posts their update asynchronously. If there are questions, address them in comments or a quick call.
2. Information Sharing (15% of Meetings)
What it is:
One person presents information to a group: new process, product update, policy change, project plan.
Why it's a meeting:
"It's easier to explain in person" or "we want to make sure everyone hears it at the same time."
What it should be:
A written memo, recorded video, or shared document. If questions arise, answer them async or schedule a short Q&A for those who need it.
3. Simple Decisions (10% of Meetings)
What it is:
A binary or straightforward choice: "Should we do A or B?" "Do we approve this budget?"
Why it's a meeting:
"We need everyone's input" or "let's discuss the options."
What it should be:
A written proposal with options, trade-offs, and a recommendation. People vote or comment async. If there's strong disagreement, then schedule a short call to resolve it.
4. Coordination (3% of Meetings)
What it is:
Aligning on timelines, dependencies, or who's doing what: "When can you deliver X?" "Who's handling Y?"
Why it's a meeting:
"Let's get everyone in a room to figure this out."
What it should be:
A shared project tracker or task list where people update their status. If there's a blocker, resolve it in a quick 15-minute call with only the people involved.
5. Real Collaboration (2% of Meetings)
What it is:
Live problem-solving, brainstorming, complex negotiation, or creative work that benefits from real-time conversation.
Why it's a meeting:
Because synchronous conversation genuinely adds value. You need back-and-forth, nuance, and rapid iteration.
What it should be:
A meeting. This is the only category that actually benefits from real-time conversation.
98% of meetings are not real collaboration. They're status updates, information sharing, simple decisions, or coordination, all of which can happen asynchronously.
When Meetings Actually Create Value
Meetings are valuable when synchronous conversation genuinely creates better outcomes than async communication. Here are the only scenarios where that's true:
1. Complex Problem-Solving
When a problem requires rapid iteration, multiple perspectives, and real-time debate, a meeting accelerates resolution. Example: diagnosing why a product launch failed and deciding what to do next.
2. Negotiation and Persuasion
When you need to read tone, respond to objections, or build rapport, synchronous conversation is more effective than written communication. Example: closing a deal, resolving a conflict, or pitching a new client.
3. High-Stakes Decisions
When a decision has significant consequences and requires nuanced judgment, a meeting ensures everyone understands trade-offs and alignment. Example: deciding whether to pivot strategy, hire a key executive, or shut down a product line.
4. Creative Collaboration
When you're brainstorming, whiteboarding, or designing something together, real-time conversation generates ideas faster than async threads. Example: product design session, campaign brainstorm, strategic planning workshop.
5. Relationship Building
When trust, culture, or human connection matters, face-to-face (or video) conversation builds rapport in ways that text cannot. Example: onboarding new team members, client relationship check-ins, team morale conversations.
Try alfred_
See what this looks like in practice
alfred_ applies these principles automatically — triaging your inbox, drafting replies, extracting tasks, and delivering a Daily Brief every morning. Theory becomes system. $24.99/month. 30-day free trial.
Try alfred_ freeWhat to Do Instead of Meetings
For the 98% of meetings that don't require synchronous conversation, here's what should replace them:
Replace Status Update Meetings With Written Updates
How it works:
- • Everyone posts a weekly update in a shared doc or Slack thread
- • Format: What shipped this week, what's next, blockers (if any)
- • People read and comment asynchronously
- • If a blocker needs discussion, schedule a 15-minute call with only the people involved
Time saved:
1-hour weekly meeting replaced with 10 minutes of writing. Entire team saves 50 minutes each.
Replace Information Sharing Meetings With Memos
How it works:
- • Write a clear, well-structured memo explaining the information
- • Share it with the team and set a deadline for feedback/questions
- • Answer questions in comments or a follow-up thread
- • If complex questions arise, offer optional office hours for Q&A
Time saved:
30-minute presentation meeting replaced with 15 minutes of reading. People absorb information at their own pace.
Replace Decision Meetings With Proposals
How it works:
- • Write a proposal: context, options, trade-offs, recommendation
- • Share with stakeholders and ask for feedback by a specific date
- • If everyone agrees, move forward. If there's disagreement, schedule a short call to resolve it
Time saved:
45-minute decision meeting replaced with 10-20 minutes of async review. Only schedule a call if consensus isn't reached.
Replace Coordination Meetings With Shared Trackers
How it works:
- • Use a shared project tracker (Asana, Notion, Linear, etc.) where everyone updates their tasks
- • Dependencies and deadlines are visible to the whole team
- • If someone's blocked, they flag it and relevant people resolve it async or in a quick call
Time saved:
30-minute coordination meeting replaced with 5 minutes of tracker updates. Real-time visibility eliminates the need for check-ins.
The pattern: default to async. Only escalate to synchronous conversation when async isn't working.
How to Eliminate Unnecessary Meetings From Your Calendar
Even if you understand that most meetings shouldn't exist, getting them off your calendar requires specific tactics:
Tactic 1: Decline Meeting Requests That Should Be Async
Response template:
"Thanks for the invite. Can we handle this asynchronously? Please share a doc/proposal/update and I'll review and comment. If we still need to meet after that, I'm happy to schedule a quick call."
This pushes the organizer to think about whether the meeting is truly necessary. Most of the time, they'll realize it's not.
Tactic 2: Require Agendas for All Meeting Requests
Response template:
"Can you send an agenda so I can prepare? Specifically: what's the goal of this meeting, what decision needs to be made, and what do you need from me?"
If the organizer can't articulate a clear agenda, the meeting doesn't have a purpose. Decline it.
Tactic 3: Leave Recurring Meetings That No Longer Add Value
How to do it:
"I'm stepping away from this recurring meeting to focus on [client work / strategic priorities]. If something urgent comes up that needs my input, feel free to ping me async or schedule a one-off call."
Recurring meetings ossify over time. They keep happening even when they've stopped adding value. Audit them quarterly and leave the ones that don't serve you. For the meetings that do remain, learn how high-performers prepare for meetings automatically so they're actually worth attending.
Tactic 4: Propose Shorter Meetings
Response template:
"I'm happy to discuss this, but can we do 15 minutes instead of 30? I think we can cover it quickly if we stay focused."
Most meetings expand to fill the time scheduled. A 15-minute meeting forces focus and eliminates filler conversation.
Tactic 5: Batch Meetings Into Specific Days
Instead of accepting meetings any day of the week, limit them to specific days (e.g., Tuesday and Thursday afternoons). This protects the rest of your calendar for deep work and prevents fragmentation. For more on structuring your calendar around real work, see our guide on consultant calendar strategy.
How alfred_ Helps You Manage Meeting Overhead
Saying no to unnecessary meetings takes time and mental energy: drafting a polished decline, proposing an async alternative, or following up afterward. alfred_ handles the surrounding communication so you can act faster.
- Meeting request triage: alfred_ surfaces and categorizes meeting request emails so you see them in context, not buried in your inbox.
- Draft decline replies: alfred_ drafts polished responses, declining, proposing async updates, or requesting an agenda, for your review and one-tap send.
- Pre-meeting context: For meetings you do accept, alfred_ prepares a brief from related emails so you walk in prepared and the meeting stays focused.
- Follow-up tracking: Action items from meetings get extracted from email threads and added to your task list so nothing falls through.
- Daily Brief: Every morning, alfred_ shows your meeting load alongside the emails that need decisions, so you start the day with context, not chaos.
The friction of managing meetings lives in the surrounding communication. alfred_ handles that layer so your decisions about meetings are fast and your calendar stays intentional.
Summary: Most Meetings Are Expensive Coordination Theater
Most meetings are status updates, information sharing, simple decisions, or coordination, none of which require synchronous conversation. They happen because "schedule a meeting" is the path of least resistance, not because meetings are the best way to accomplish the goal.
The cost: 10-15 hours per week and $50K-$200K in lost annual capacity for professionals billing $200-$500/hour. This is part of the broader time that knowledge workers lose to coordination overhead.
Meetings create value when they enable complex problem-solving, negotiation, high-stakes decisions, creative collaboration, or relationship building. Everything else should be async.
Default to async. Only schedule meetings when synchronous conversation genuinely improves the outcome.
Try alfred_
Stop Letting Meetings Eat Your Calendar
alfred_ triages meeting requests, drafts decline replies, and preps you for the meetings that actually matter, so your calendar works for you, not against you.
Get Your AI AssistantFrequently Asked Questions
Why do most meetings not need to exist?
Research shows that roughly 98% of meetings are not real collaboration. They are status updates, information sharing, simple decisions, or coordination, all of which can be handled asynchronously through written updates, shared documents, or brief messages. Meetings persist because scheduling a call is the path of least resistance, not because synchronous conversation is the best format for the work.
How many hours per week are wasted on unnecessary meetings?
Professionals typically lose 10-15 hours per week to meetings that could have been handled asynchronously. For consultants and freelancers billing $200-$500 per hour, that translates to $104,000-$390,000 in lost annual capacity. The cost includes not just the meeting time itself but also preparation, context switching, and recovery time between back-to-back calls.
How do I politely decline a meeting that should be an email?
Use a simple response template: 'Thanks for the invite. Can we handle this asynchronously? Please share a doc or update and I will review and comment. If we still need to meet after that, I am happy to schedule a quick call.' This pushes the organizer to evaluate whether the meeting is truly necessary. Most of the time, they will realize it is not.
When should a meeting actually happen instead of an email?
Meetings create genuine value in five scenarios: complex problem-solving requiring rapid iteration, negotiation or persuasion where tone and rapport matter, high-stakes decisions with significant consequences, creative collaboration like brainstorming or design sessions, and relationship building where human connection is the goal. If the outcome could be achieved by reading a document, it should not be a meeting.
How do I reduce meeting overload as a freelancer or consultant?
Apply five tactics: decline meeting requests that should be async, require agendas for all meetings before accepting, leave recurring meetings that no longer add value, propose 15-minute meetings instead of 30- or 60-minute defaults, and batch all meetings into specific days to protect the rest of your calendar for deep work. These changes can reclaim 10 or more hours per week.
What should replace status update meetings?
Replace status update meetings with written async updates. Everyone posts a weekly update in a shared document or Slack thread covering what shipped, what is next, and any blockers. People read and comment on their own schedule. If a blocker needs real discussion, schedule a focused 15-minute call with only the relevant people. This replaces a 1-hour meeting with 10 minutes of writing per person.
Can AI help reduce unnecessary meetings?
AI assistants like alfred_ can automate meeting management by identifying requests that could be handled asynchronously, enforcing agenda requirements, suggesting shorter durations, batching meetings into specific time blocks, and drafting async responses as alternatives to scheduling calls. This removes the manual effort of filtering meeting requests while still protecting your calendar for high-value work.