How-To Guide

How to Run Fewer Meetings and Get More Done

Q: How many meetings per week is too many?

If meetings consume more than 40% of your working hours, you're spending more time talking about work than doing it. For most professionals, 8-12 hours of meetings per week is the productive ceiling. Above that, the quality of both your meeting contributions and your independent work degrades.

Q: How do I cancel recurring meetings without offending people?

Frame it as an upgrade: "I want to make sure our time together is high-value. Let's try async updates for the next two weeks and see if we miss anything. If we do, we'll reinstate the meeting." Most people are relieved. They didn't want the meeting either.

Q: What if my company culture requires lots of meetings?

Start with your own calendar. You can't change culture overnight, but you can decline optional meetings, suggest async alternatives for your own team, and demonstrate that fewer meetings = better output. Culture changes when people see results.

Q: How do I decline a meeting without being seen as "not a team player"?

Provide value in the decline: "I can't make this one, but here's my input on X and Y. Let me know what's decided." You're contributing without attending. That's more useful than sitting in a meeting checking your phone.

Q: Should I batch all my meetings on certain days?

Yes, if you can. "Meeting days" and "maker days" is one of the most effective calendar strategies. Tuesdays and Thursdays for meetings, Monday/Wednesday/Friday for focused work. The key is consistency. Your team learns when you're available and stops scheduling randomly.

Q: How does alfred_ help reduce meeting load?

alfred_ surfaces information that eliminates the need for meetings. When your Daily Brief includes client updates, email context, and task status, you don't need a "sync" to stay informed. It also prepares pre-meeting briefs so the meetings you do keep are shorter and more focused.

You spent 23 hours in meetings this week. You have 17 hours of actual work to do. The math doesn't work. And neither do you, at this rate.

The Meeting Audit: What Actually Needs a Meeting?

Status updates

4-6 hrs/week — false — Async Slack/email update. 3 bullets: done, doing, blocked.

Brainstorming sessions

2-3 hrs/week — true — Keep, but only with < 5 people and a clear problem statement.

"Quick syncs"

3-5 hrs/week — false — 90% of these are a question that takes 2 Slack messages to answer.

Client check-ins

3-4 hrs/week — true — Keep, but biweekly instead of weekly for stable projects.

All-hands / team meetings

1-2 hrs/week — true — Keep, but only if there's new information. Cancel when there isn't.

Meetings about meetings

1-2 hrs/week — false — "Pre-alignment" meetings shouldn't exist. Write the doc, share it, meet only if there's disagreement.

"Can I pick your brain?"

1-3 hrs/week — false — Office hours. Block 30 min on Thursdays. Batch all the brain-picking.

The "Does This Need a Meeting?" Decision Tree

Does this require a real-time decision between 2+ people?

Meeting is justified. — Go to next question.

Could this be handled in a 3-paragraph email or Slack thread?

Write it. Don't meet. — Go to next question.

Is this a status update with no decisions needed?

Async update. No meeting. — Go to next question.

Are there more than 6 people invited?

Cut the list. Nobody makes decisions in a group of 8. — Go to next question.

Does everyone need to be there for the full time?

Proceed. Keep it tight. — Split into two shorter meetings or let people drop after their segment.

What to Use Instead of a Meeting

Weekly status meeting

Monday morning async update — Each person posts 3 bullets to a shared channel: (1) What I shipped last week, (2) What I'm focused on this week, (3) Where I'm blocked. Read time: 2 min. Meeting time saved: 30-60 min.

"Let's discuss this" meeting

Decision doc + async comments — Write a 1-page doc with: Context, Options (2-3), Recommendation, Risks. Share it. Give 24 hours for comments. If no disagreement, proceed. If disagreement, now you have a focused 15-min meeting instead of a 60-min exploration.

Recurring "check-in"

Trigger-based meeting — Instead of meeting every Tuesday "just in case," meet only when there's a specific agenda item. The calendar invite stays, but the default is "cancel unless someone adds an agenda 24 hours before."

"Quick sync" request

Structured Slack thread — When someone says "can we hop on a call?", reply: "Happy to, what's the question? Sometimes I can answer faster here." 70% of the time, they type it out and you're done in 2 messages.

5 Rules for the Meetings You Keep

No agenda, no meeting

If the organizer can't articulate what decisions need to be made, the meeting isn't ready to happen. An agenda doesn't need to be formal, "We need to decide X and Y" is enough.

Default to 25 minutes

Parkinson's law: work expands to fill the time. A 30-minute meeting will take 30 minutes. A 25-minute meeting forces focus, and gives you 5 minutes to breathe before the next one.

End with actions, not vibes

The last 2 minutes of every meeting: "Who is doing what by when?" If you can't answer that, the meeting failed. Write it down. Send it immediately after.

Recurring meetings need a renewal date

Every recurring meeting should have a "review by" date, 6 weeks max. If it hasn't earned its slot by then, cancel it. It can always be restarted.

Spectators become readers

If someone is in the meeting "just to stay informed," they should read the notes instead. Observers inflate meeting size, reduce candor, and pay full attention cost for zero participation value.

Try alfred_

What If You Didn

alfred_ gives you visibility without the meeting. Your Daily Brief surfaces email context, client updates, calendar conflicts, and pending tasks so you walk into your day already informed.

Try alfred_ Free

Frequently Asked Questions

How many meetings per week is too many?

If meetings consume more than 40% of your working hours, you're spending more time talking about work than doing it. For most professionals, 8-12 hours of meetings per week is the productive ceiling. Above that, the quality of both your meeting contributions and your independent work degrades.

How do I cancel recurring meetings without offending people?

Frame it as an upgrade: "I want to make sure our time together is high-value. Let's try async updates for the next two weeks and see if we miss anything. If we do, we'll reinstate the meeting." Most people are relieved. They didn't want the meeting either.

What if my company culture requires lots of meetings?

Start with your own calendar. You can't change culture overnight, but you can decline optional meetings, suggest async alternatives for your own team, and demonstrate that fewer meetings = better output. Culture changes when people see results.

How do I decline a meeting without being seen as "not a team player"?

Provide value in the decline: "I can't make this one, but here's my input on X and Y. Let me know what's decided." You're contributing without attending. That's more useful than sitting in a meeting checking your phone.

Should I batch all my meetings on certain days?

Yes, if you can. "Meeting days" and "maker days" is one of the most effective calendar strategies. Tuesdays and Thursdays for meetings, Monday/Wednesday/Friday for focused work. The key is consistency. Your team learns when you're available and stops scheduling randomly.

How does alfred_ help reduce meeting load?

alfred_ surfaces information that eliminates the need for meetings. When your Daily Brief includes client updates, email context, and task status, you don't need a "sync" to stay informed. It also prepares pre-meeting briefs so the meetings you do keep are shorter and more focused.