The 30-Minute Meeting Is Dead. Here's What Replaces It.

Quick question: why are your meetings 30 minutes long?

Not "why do you have meetings?" That's a different essay. Why specifically 30 minutes? Was there a study? A pilot program? A deliberate analysis of how long it takes your team to accomplish different types of collaborative work?

Of course not. It's 30 minutes because that's the default in Zoom and Google Meet. Because that's what the calendar shows. Because that's what everyone else does. The 30-minute meeting is a convention without a justification — and it's wasting more time than any other workplace norm.

How we got here

When Microsoft built Outlook in the late 1990s, someone had to choose a default event duration. They picked 30 minutes. It could have been 20 or 45 or 17 — it was a UI decision, not a research finding. Google Calendar inherited the same default. A generation of workers absorbed it as natural law.

The 60-minute meeting has a similar origin: it maps cleanly to the clock and to academic class periods (themselves an artifact of 19th-century school design). Neither 30 nor 60 minutes has any basis in cognitive science, attention research, or organizational theory.

Yet these two durations account for approximately 80% of all scheduled meetings in modern organizations. We've let software defaults dictate the rhythm of collaborative work for three decades.

What research actually says

Attention research tells a different story. The human brain can sustain focused attention on a single topic for 10-18 minutes before it starts seeking novelty (John Medina, "Brain Rules"). After about 20 minutes, retention drops sharply unless the format changes (new speaker, activity shift, break).

This means a 30-minute meeting has approximately 10 minutes of diminishing returns built in — time where attendees are physically present but mentally elsewhere. A 60-minute meeting has 40 minutes of it. The longer the meeting, the lower the average quality of attention per minute.

Meanwhile, organizational behavior research (Perlow, "Sleeping with Your Smartphone") shows that the single biggest complaint knowledge workers have about meetings isn't their existence — it's their length. "This could have been shorter" is the universal post-meeting sentiment because it's almost always true.

Right-sized meetings

Instead of defaulting to 30 or 60 minutes, match the duration to the purpose:

• 10-minute standup — status updates, blockers, handoffs. If your standup takes longer than 10 minutes, you're solving problems in the wrong forum.
• 15-minute sync — two people aligning on a decision, reviewing a document, or coordinating a handoff. Most "quick calls" should be 15 minutes, not 30.
• 25-minute working session — collaborative problem-solving, design reviews, sprint planning scoped to a single topic. The 25-minute duration (not 30) builds in a 5-minute buffer before the next half-hour boundary, preventing the cascade of back-to-back meetings starting late.
• 50-minute workshop — deep collaborative work, brainstorming, retrospectives. The 50-minute duration (not 60) provides a 10-minute break before the next hour, which is essential for meetings that require sustained cognitive effort.

Notice the pattern: every suggested duration is shorter than the conventional default and includes buffer time. This isn't about being stingy with meeting time — it's about respecting attention as a finite resource.

The Parkinson problem

Parkinson's Law — "work expands to fill the time available" — applies perfectly to meetings. Schedule 30 minutes for a status update and you'll get 5 minutes of status followed by 25 minutes of meandering discussion. Schedule 10 minutes and you'll get 10 minutes of focused status. The content doesn't change; the filler does.

This is why the most effective meeting cultures use hard stops and shorter defaults. Amazon's "two-pizza team" rule limits attendees, but their 6-page memo format limits duration equally effectively — everyone reads silently for the first 20 minutes, then discusses for 40. No presentation theater, no "can you go back a slide," no filler.

What scheduling tools should do

If meeting duration is a design choice — and a consequential one — then scheduling tools should treat it as such instead of defaulting to 30 minutes and calling it done.

Smart scheduling should:

• Suggest durations based on meeting type — a 1-on-1 with a direct report defaults to 25 minutes, not 30. A standup defaults to 10, not 15.
• Nudge toward shorter — when someone creates a 60-minute meeting, prompt: "Would 50 minutes work? That leaves a buffer before the next hour."
• Track actual vs. scheduled duration — if meetings consistently end early, surface that data. "Your team meetings are scheduled for 30 minutes but average 18 minutes. Consider defaulting to 20."
• Build in buffers automatically — 25-minute meetings instead of 30, 50 instead of 60. The 5-10 minutes between meetings isn't wasted time — it's transition time that prevents the cognitive pileup of back-to-back calls.

The meeting culture crisis won't be solved by eliminating meetings. It'll be solved by right-sizing them. And that starts with killing the arbitrary defaults that have shaped our work lives for 30 years.

The 30-minute meeting was never designed. It was defaulted into existence. It's time to be intentional about how long we meet — because the compound effect of millions of meetings that are 10 minutes too long is an organizational tax that nobody voted for.