How to Run a Timed Meeting That Ends on Time

A meeting with a 60-minute slot and five agenda items has an implicit plan that nobody has written down. Make it explicit: give each item a number of minutes and put the numbers on the agenda that goes out beforehand. The act of assigning minutes forces the organiser to decide what the meeting is for; items that get two minutes are updates, items that get twenty are decisions.

A workable default for a 60-minute meeting:

Block	Minutes	Purpose
Open	3	State the goal and the decisions needed. No round of updates.
Item 1 (the important one)	20	Discussion and decision while attention is highest.
Item 2	15
Item 3	10
Actions and owners	7	Read back who does what by when.
Buffer	5	Absorbs the inevitable overrun without pushing the end time.

The meeting timer takes exactly this kind of list, names each segment and moves through them with a chime at each boundary, so the plan becomes a clock rather than a good intention.

A timer that only the chair can see does half the job. When everyone can see the remaining time, people self-regulate: they shorten their point, they stop repeating, and they raise the "we are out of time on this" flag themselves. Share the timer on the meeting screen or, in a room, put it on a laptop facing the table. Online, the timer's tab can be shared briefly at each transition rather than for the whole call.

A visible clock also depersonalises the interruption. "The timer says we have two minutes" is easier to say and to hear than "you have been talking for too long". The chair's job becomes reporting the clock, not policing people.

A single alarm at the end is too late; by then the overrun has happened. Use two warnings per segment: one at roughly the halfway point ("we are halfway and still on the first option") and one with a couple of minutes left ("two minutes; what is the decision?"). The second warning should be a question, because it converts the remaining time into a push towards an outcome rather than a countdown to being cut off. The meeting timer sounds both automatically; in a presentation or a single-topic discussion the presentation timer gives the same amber and red signals.

Overruns are usually one of three things, and each has a script:

• The topic is bigger than the slot. "This needs more than we have. Let us take the two people who care most and book thirty minutes tomorrow; for now, is there anything that blocks the other items?" Park it, name the owner, move on.
• The decision is being avoided. "We have heard the options. Unless there is new information, I am going to propose we go with B and revisit in a month." Silence is consent; someone will speak if they genuinely object.
• One person is repeating. "I think we have your point, and it is noted. Let me get a view from anyone who has not spoken." Redirecting to others is kinder than stopping the speaker directly.

For discussions where equal speaking time matters, such as a review panel or a structured debate, give each side a clock of its own; the debate timer does exactly that.

Daily stand-up, 15 minutes. Each person answers three questions in under a minute. Use a per-person timer of 60–90 seconds and stand up; sitting doubles the length.

Decision meeting, 25 minutes. Send a one-page brief in advance; spend the first five minutes reading it in silence; twenty minutes deciding. Amazon-style silent reading beats slide presentations for getting everyone to the same starting point.

Retrospective, 45 minutes. 5 to set the scene, 15 to collect points, 15 to discuss the top three, 10 for actions. Timebox the collection phase hard or it eats everything.

Across time zones, pick the slot with the world clock before you send the invite, and remember that "9 a.m. our time" moves for the other side twice a year; our time zones guide explains why. For a launch or deadline that everyone is working towards, a shared countdown on the team screen does more for urgency than another status meeting.