How to Reduce Meetings Without Losing Information

Executives now spend nearly 23 hours a week in meetings, more than double what they did in the 1960s, and that pressure has spread across the entire organization.

Most teams already know they have too many meetings. The real problem is knowing which ones to cut without losing alignment.

The standard playbook handles the easy wins. Quick questions move to Slack, status updates to shared docs, and short explainers to recorded video. The calendar gets lighter, but only up to a point.

The real problem sits one layer deeper.

Recurring broadcast meetings, like all-hands, leadership updates, and training rollouts, take up the most time and are the hardest to replace. They’re structured one-way, but still consume hours of synchronous time across the entire organization.

Reducing meetings meaningfully means replacing those sessions with formats that deliver the same information without requiring everyone to be in the same place at the same time. That’s where approaches like internal podcasts start to fit into the stack.

Why Companies Have Too Many Meetings

Why are employees spending so much time in meetings, and how can companies reduce it?

The meeting load most teams complain about isn't the result of one bad habit; it builds up through structural patterns that compound quietly until the calendar is too full to ignore.

Three patterns show up consistently:

• Default-to-meet culture: When someone has a question, an update, or a decision to discuss, the reflex is to schedule a meeting rather than ask whether the conversation needs to be live. Each individual choice feels small, but multiplied across hundreds of employees making the same call every week, the cumulative cost shows up across the org.
• Recurring meetings rarely get audited: A standing meeting that made sense six months ago often outlives its purpose, but the calendar invite keeps it going long after the original reason has faded. Few organizations have a formal process for reviewing whether each recurring meeting still earns its slot.
• Broadcast meetings get treated like working meetings: Scheduling discipline that gets applied to decision meetings (smaller invite lists, agendas, action items) rarely gets applied to large information-cascade sessions, so they end up longer, broader, and more frequent than the content actually requires.

Together, these three patterns create the conditions for meeting time to grow without anyone deciding to do so.

8 Practical Strategies to Reduce Meetings

The strategies below work across team sizes and structures, and most of them can be adopted without rebuilding how an organization runs. The goal is to reduce the volume without losing the alignment that meetings are meant to provide in the first place.

1. Audit Recurring Meetings First

The biggest meeting-reduction wins almost always come from killing recurring meetings, not from declining individual invites.

A weekly meeting cancellation saves an hour for everyone on it, which adds up to hundreds of hours over a year.

A quarterly audit is the practical mechanism. Every recurring meeting on the calendar should justify itself or get cut.

Three useful tests: is the meeting producing decisions or just status? Are the same updates being repeated week to week? Would attendees notice if it disappeared?

Two reliable defaults sharpen the audit. Shorten anything currently scheduled for 60 minutes to 30 unless there's a specific reason it needs more. Cancel anything with chronically low attendance or unclear purpose.

The organizer can always reinstate a meeting if it turns out to be missed.

2. Require an Agenda Before Booking

Requiring an agenda as a precondition for sending the calendar invite forces the organizer to think through what the meeting is actually trying to accomplish before pulling other people into it.

The systemic version of this rule lives at the calendar level.

Most organizations can configure their calendar tool to require an agenda field on every meeting invite, turning the agenda from a nice-to-have to a built-in step.

A useful side effect: the agenda doubles as the meeting's written record. Anyone who couldn't attend can read the agenda and any notes added during the meeting, which often eliminates the follow-up sync that would otherwise get scheduled.

3. Default to Async for Updates and Status Reports

Status updates rarely need real-time discussion. The information flows in one direction, and the people receiving it rarely have questions urgent enough to justify a meeting on the calendar.

Several async alternatives cover the same ground.

A written end-of-week update from each team lead delivers the same information faster than a 30-minute standup. A shared task board shows progress at a glance without anyone needing to talk through it. Project trackers let everyone check the status on their own time.

Sync time becomes more valuable when it's reserved for the meetings that genuinely need it: decisions where stakeholders need to weigh in together, sensitive conversations that don't belong in writing, and brainstorming sessions where the group produces more than any individual could alone.

4. Replace Broadcast Meetings With Internal Podcasts

The all-hands, quarterly business review, and weekly leadership update are all structured one-way: a leader or small group speaks, and most attendees listen.

They get scheduled as live calendar events because that's how they've always been delivered, not because synchronous attendance adds value.

Internal podcasts handle this content type cleanly.

Leadership records the message once, employees listen during commutes, walks, or focused work breaks, and the meeting that would have absorbed an hour of everyone's calendar disappears.

The information still lands, often more completely than it would in a live session where half the audience is multitasking.

Supporting Cast handles the distribution layer for this use case, specifically delivering private podcast content to the apps employees already have on their phones. Audience access ties to identity systems, so listener groups update as employees move between teams.

The result is a format that replaces broadcast meetings without asking employees to install anything new.

5. Use Recorded Video for Short Explainers

Quick visual explainers and one-off updates often get scheduled as meetings when they could be a 3-5 minute screen recording instead.

A walkthrough of a new tool, a project update with a shared screen, or an update from one team to another usually doesn't require everyone to be gathered at the same time. Recorded video tools make it easy to set up and consume.

Anyone receiving the recording can watch at 1.5x speed, skip to the part they need, and rewatch later if something matters. The 30-minute meeting that would have covered the same ground disappears from everyone's calendar.

For updates that don't need visual context, a written note or audio works just as well with less production time.

6. Establish Meeting-Free Blocks or Days

Meetings expand to fill the calendar unless something protects time for actual work. The fix is blocking that protection directly: a meeting-free morning, a no-meetings day, or a recurring window when calendars are closed by default.

Several companies have made this systemic. Some block Wednesday mornings, others designate one full day a week as meeting-free.

The specific configuration matters less than whether it's enforced at the calendar level. A policy that says "try to keep Wednesdays clear" gets ignored. A calendar setting that prevents meetings from being scheduled during those windows actually works.

7. Cut the Invite List

In many meetings, some attendees are invited as a courtesy, some out of habit, some because the organizer didn't want to leave anyone out. The result is rooms full of people whose attendance adds neither input nor value.

The fix is defaulting to the smallest viable invite list.

Anyone who genuinely needs to participate gets included; anyone who only needs the outcome gets sent the notes or recording afterward.

This single shift cuts the cost of every meeting because each unnecessary attendee multiplies the time tax across the org.

A useful test before sending the invite: would this meeting still produce its intended outcome if half the invitees were missing? If the answer is yes, the invite list is too large.

8. End Every Meeting With Action Items, Not Discussion

Meetings that end with "we'll figure it out" or "let's circle back next week" almost always spawn follow-up meetings. This pattern is one of the quietest drivers of meeting bloat.

The fix is to use the last five minutes of every meeting to produce three specific outputs: the action items generated, the owner of each, and the deadline. Without those three, the work doesn't move forward, and the meeting hasn't actually accomplished anything.

The practice changes what meetings produce. Instead of conversations that need to keep happening, meetings start producing decisions and assignments that move work forward independently.

Which Meetings to Cut First

The hardest part of reducing meetings is deciding which ones to actually cut.

A simple diagnostic makes the call easier: for each recurring meeting type on the calendar, ask whether it genuinely needs synchronous attendance to deliver its value.

The diagnostic is about matching the format to the goal, not eliminating meetings wholesale.

Most teams running through this exercise find that 30 to 50 percent of recurring meetings on their calendar fail the synchronous-attendance test.

The fastest path forward is to cut the clear "no" rows first, then revisit the "sometimes" rows quarterly to see whether the live sessions are still earning their slot.

Building a Meeting Culture That Stays Reduced

Cutting meetings once is easy. Sustaining the reduction is what separates teams that stay focused from those that drift back to a packed calendar within a quarter.

The teams that hold the line tend to share three traits: clear criteria for when a meeting is actually needed, an async stack that handles updates without defaulting to the calendar, and leadership that models the behavior instead of just encouraging it.

Most organizations already know how to cut small meetings. The real shift comes from replacing the broadcast ones that take up the most time.

That’s where internal podcasts change the equation.

Supporting Cast turns leadership updates, all-hands, and recurring briefings into a format employees can actually finish, without adding another meeting to the calendar. Delivered through the apps employees already use, with access tied to identity systems and visibility into engagement, it becomes a real replacement for broadcast meetings, not just another tool in the stack.

If your team is ready to move your highest-value communication out of the calendar and into a format people actually complete, schedule a demo and see how it fits.