What the Research Says About Meeting Length (And Why 60 Minutes Is Arbitrary)
The 60-minute meeting default is a calendar convention, not a research finding. Attention data, Parkinson's Law, and Amazon's operating model all point to the same conclusion — shorter defaults produce better outcomes at lower cost.
Quick answer: Research from Wharton Executive Education identifies 25 minutes as the optimal meeting length based on sustained attention data. Attention drops measurably after 30 minutes, and the 60-minute default is an artefact of calendar software conventions, not evidence about how long decisions take. Almost every meeting type — with the exception of creative workshops and deep planning sessions — is better served by a 25 or 50-minute default.
The one-hour meeting is the default unit of organisational time. It is what calendar software suggests, what invitees expect, and what most people fill — because Parkinson's Law ensures that any meeting scheduled for an hour will take an hour, regardless of how much the actual work requires.
This default is not grounded in research on attention, decision quality, or output. It is a convention inherited from hourly scheduling norms, and it has a measurable cost.
What the attention data shows
Researchers tracking real participant attention levels throughout meetings found a consistent pattern:
- 91% of participants are actively focused in the first 15 minutes
- 84% remain focused from 15 to 30 minutes
- Attention drops steeply beyond the 30-minute mark
This does not mean that useful work cannot happen after 30 minutes — it means that the marginal return per minute falls significantly as meeting length increases. A 60-minute slot does not purchase twice the output of a 30-minute slot. It often purchases roughly the same output at twice the cost.
Francesco Cirillo's Pomodoro research — which established 25 minutes as the optimal focused work interval before a deliberate break — aligns with these meeting attention findings. Wharton Executive Education cites 25 minutes as the optimal meeting length on similar grounds: it sits within the sustained attention window for most participants.
Parkinson's Law and the 60-minute trap
Parkinson's Law — "work expands to fill the time available" — applies to meetings with particular force because meetings have no natural stopping signal. A coding task ends when the code works. A writing task ends when the piece is complete. A meeting ends when the clock runs out.
The practical consequence: a meeting booked for 60 minutes will use 60 minutes. The same agenda booked for 30 minutes will use 30 minutes. The decision quality, in studies comparing matched meeting lengths on the same agenda, is not consistently different — but the cost is exactly half.
This is the core insight behind the 25-minute default: by setting a shorter slot, you apply Parkinson's Law in reverse. The constraint forces efficiency. Facilitators close discussions rather than open them. Attendees come prepared rather than using meeting time to catch up.
Amazon's operating model: the written memo
Jeff Bezos applied a structural solution to meeting length at Amazon that went further than timer discipline. Amazon meetings begin with a written narrative memo — a structured document presenting the context, options, recommendation, and anticipated questions — which all attendees read silently for the first 15 to 30 minutes of the meeting.
The memo approach does several things simultaneously. It forces the organiser to think through the problem before the meeting rather than during it. It equalises preparation across attendees. And it compresses the information-sharing phase — which consumes most of routine meeting time — into reading rather than presenting.
The result is that the live discussion phase is shorter, more focused, and more productive. A 60-minute meeting that would normally spend 40 minutes on status and 20 on discussion becomes a session with 20 minutes of silent reading and 25 minutes of focused debate.
The two-pizza rule and meeting size
Bezos also applied the two-pizza rule: if two pizzas would not feed the attendee group, the meeting was too large. In practice, this means five to eight people — the range at which research consistently shows the best balance of diverse input and coordination efficiency.
Meeting length and meeting size are coupled: larger groups require more coordination, more context-setting, and more time for each person to speak. A meeting with twelve attendees will almost always run longer than the same agenda with six, even when the decision does not require twelve perspectives. Each additional attendee adds communication overhead while adding diminishing returns to decision quality.
The standup as a format, not just a practice
Daily standups — the 15-minute team coordination meeting from Agile practice — represent the most widely deployed short-meeting format. A 2025 survey found that 87% of teams using Agile methods regularly use some form of daily standup.
The research on effectiveness is nuanced: standups are well-supported as relationship and coordination tools, with studies linking them to improved psychological safety and team performance. The persistent problem is drift — the same research found that standups average 22 minutes rather than the scheduled 15, and overrunning standups cost organisations an estimated $283 per employee per month in productivity lost to meetings that exceed their intended scope.
The standup is a proof of concept for short-format meetings, but it requires the same enforcement mechanisms — a clear agenda (three questions: what did I do yesterday, what am I doing today, what is blocking me), a timer, and a facilitator who cuts extended discussion and takes it offline.
Meeting-free days and length work together
Research published in MIT Sloan Management Review on the effect of meeting-free days found that the productivity benefits increase with the number of protected days:
- One meeting-free day per week: 35% productivity increase
- Two meeting-free days per week: 71% productivity increase
- Three meeting-free days per week: 73% productivity increase
The combination of shorter default meeting lengths and protected deep-work days addresses both dimensions of the meeting problem: reducing the cost per meeting and reducing the number of meetings that interrupt focused work.
What the right default actually looks like
Based on the research, here is a practical meeting length guide by type:
| Meeting type | Recommended length | Why |
|---|---|---|
| Daily standup | 15 min | Three-question format; take discussion offline |
| Weekly team sync | 25 min | Within sustained attention window |
| Decision review (small group) | 25–30 min | Focused agenda; prep distributed in advance |
| Cross-functional planning | 50 min | Allows five-minute transition before the hour |
| Creative brainstorm | 45–60 min | Generative sessions benefit from more time |
| Strategy or planning session | 90–120 min | Use breaks; treat as exception, not default |
The common thread: every meeting type should be shorter than its current default. The 60-minute default should be treated as the maximum, reserved for sessions where it is genuinely warranted, rather than the baseline applied to everything.
Applying time pressure without social friction
The most effective way to enforce shorter meetings is structural, not cultural. Changing the calendar default from 60 to 25 minutes creates organisation-wide pressure without requiring anyone to be the meeting police. Displaying a visible timer in the room — particularly one that also shows cost — creates an ambient enforcement mechanism that operates on Parkinson's Law directly.
MeetingTick shows elapsed time and rising cost on a shared screen. When the time remaining is visible to everyone in the room, discussions naturally close as the end approaches. The social pressure that normally extends meetings — the reluctance to cut someone off — is replaced by an environmental constraint that nobody personalises.
Set your next meeting for 25 minutes. Use MeetingTick on the shared screen. Send the agenda 24 hours in advance. The experiment takes one meeting to run.
Sources: Wharton / Bettermeets — optimal meeting length · World Economic Forum — the 25-minute meeting · MIT Sloan Management Review — meeting-free days · Inc. — Jeff Bezos two-pizza rule · Fast Company — how long should meetings last · ResearchGate — daily stand-up meetings research · Flowtrace — ideal meeting length · Inc. — meeting-free days 73% productivity