A meetup rarely falls apart because of one big delay. It slips a minute at a time: the opening starts five minutes late, the first speaker takes three extra, questions run long. By the last talk the room is watching the clock and the last speaker is left with half their slot.
Why the schedule slips
People almost always underestimate how long their own work will take. Psychologists call it the planning fallacy. In the classic study by Buehler, Griffin and Ross, students expected to finish their theses in 34 days on average; it took them 55.5, and only about 30% finished by their own estimate [1]. A speaker who says “I need exactly 20 minutes” errs in the same direction. It is not bad faith: they picture the outline of the talk, not how their past talks actually went.
A late start costs more than it seems, too. Allen, Lehmann-Willenbrock and Rogelberg tested it experimentally by starting meetings 5 or 10 minutes late. Participants in those meetings rated both satisfaction and effectiveness lower, and produced fewer ideas of lower quality [2].
What helps
- Buffer in the plan, not hope. Build slack into the agenda — say, 5 minutes per hour — and make it a stage of its own instead of spreading it across the talks. Slack hidden inside talks gets eaten by the first speakers.
- Breaks are stages too. In a Microsoft study, people in four back-to-back half-hour meetings showed stress building up on EEG from one meeting to the next. With ten-minute breaks between meetings it did not accumulate [3]. A break is time for the room to recover attention, not a reserve for overruns.
- Let the speaker see the time. A host is reluctant to interrupt someone on stage, and a speaker can hardly watch a clock while talking. Toastmasters clubs have a dedicated role for this — the timer. The timer confirms each speech's length beforehand, shows signals, and turns on red when the allotted time is up [4]. How to agree on timing with a speaker is covered in the guide on talk length.
- Mark progress instead of keeping it in your head. When the host marks the start and end of every stage, you can see how far behind you are right now — and the call to shorten Q&A gets made after the second talk, not the last one.
- Rehearse with a stopwatch. A run-through with even two speakers shows real lengths better than any promise — see the planning fallacy above.
What this looks like at a real meetup, with planned and actual minutes for every stage, is in the guide on running an event by the minute.
How to do it in Po minutam
The programme is a list of stages with minutes and hosts. During the meetup the host marks stages from a phone, speakers and the room see how much time is left, and the hall screen goes on the projector. If a stage runs long, you add minutes to the plan and the board recalculates the time to the end. After a rehearsal, one button resets the progress.