15, 30, or 60 Minutes? A Meeting Duration Guide
Choose a default length based on the decision, participants, preparation, and energy the meeting requires.
Choose a default length based on the decision, participants, preparation, and energy the meeting requires.
Duration follows the work of the meeting
Start by identifying who owns the decision and which availability is authoritative. Empty calendar space is not automatically bookable capacity: working hours, notice, buffers, preparation, travel, and daily limits all shape the honest set of choices.
Why most meetings are an hour
Calendar apps default to 60 minutes. That is the only reason. The work of a meeting rarely needs an hour, and a meeting fills whatever time it is given.
Match the length to the job
| Length | Use it for | Not for |
|---|---|---|
| 15 minutes | A status check, a yes-or-no, a quick handoff | Anything with more than one open question |
| 30 minutes | One focused conversation and one decision | Workshops or several stakeholders |
| 45 minutes | Discovery with a new client, a review with prep | Routine syncs that could be 30 |
| 60 minutes | Workshops, complex discovery, several decisions | Recurring team meetings |
End early on purpose
Set 25 and 50 minute slots instead of 30 and 60. The five or ten minutes back give people time to write notes and walk to the next thing. Meetings that start late usually start late because the last one ran to the boundary.
Signs the length is wrong
- Meetings end well early: shorten the event type.
- Meetings always run over: lengthen it, or split the agenda into two meetings.
- People multitask: the meeting is too long for the decision it makes.
How to apply this guidance
Use one real meeting type, complete these actions in sequence, and record what changed.
Use 15 minutes for narrow alignment with no exploration.
Use 30 minutes for a focused conversation and one decision.
Reserve 60 minutes for workshops, complex discovery, or several decisions.
Test the core scheduling flow
Create a booking page or group poll, then complete it in a separate browser session.
Measure meetings ending materially early or running over
The primary signal for this guide is meetings ending materially early or running over. Pair it with time to confirmation, completion, reschedule rate, attendance, organizer intervention, and the intended meeting outcome. Segment results by meeting type and participant context so one high-volume workflow does not hide another's failure.
Questions about meeting duration guide
How long should a meeting be?
As long as the decision needs and no longer. Fifteen minutes for a status check, thirty for a working discussion, sixty only when several people must contribute substantively.
Why are meetings scheduled for an hour by default?
Because calendar software defaults to it, not because the work requires it. Changing the default to twenty-five or fifty minutes recovers real time with no other change.
Should meetings have gaps between them?
Yes. Ending at :25 and :50 gives everyone time to write notes and move. Consecutive meetings guarantee late starts that compound through the day.
