A conference schedule is not a list of accepted talks in an order. It is a design problem with a few hard rules, and most of what makes a day feel good or exhausting is decided here rather than in the programme committee. This page covers slot length, keynote placement, how breaks are sized, and why a single-track day is the harder of the two to build.
Slot length decides the talk
Thirty, forty-five and sixty minutes are the usual lengths, and each produces a different kind of talk. Thirty minutes holds one idea with one example. Forty-five holds an idea, a worked example and a caveat, and is the default at most regional events. Sixty minutes is a tutorial in disguise: it needs a structure with sections, and a speaker who has not planned for that will fill it by talking more slowly.
The length has to be in the call for papers, because a proposal is written to a length. Changing it after acceptance means the speaker rewrites, and it is one of the few scheduling changes worth apologising for.
Breaks are not gaps
The corridor is where most of a conference’s value is produced, and the schedule either makes room for it or does not. Fifteen minutes between sessions is enough to move rooms and nothing else; twenty-five to thirty is enough for a conversation to start and finish. Lunch under an hour produces a queue and a rush; ninety minutes produces conversations that carry through the afternoon.
The 2008 edition ran a ninety-minute lunch on both days and put lightning talks against breakfast, which is the same instinct: use the low-attention parts of the day for low-commitment content, and leave the middle of the day clear.
Nobody remembers the fourth talk. Everyone remembers the corridor.
Where a keynote goes
There are two defensible placements and one common mistake. Opening keynotes set a tone and give latecomers something to arrive into. Closing keynotes send people out with a single shared reference, and they hold the room to the end of the day, which matters at a two-day event, where the Saturday afternoon is where attendance visibly drains.
Both Hoedown editions closed each day with a keynote: 2007 with Bruce Tate on the Friday and Marcel Molina, Jr. on the Saturday, 2008 with Chris Wanstrath and David A. Black. The mistake is scheduling a keynote against anything else, in any track. A talk billed as the one everybody should see, opposite a talk somebody worked on for months, wastes both.
Single track is the harder design
It is tempting to assume that one track is the simple case. It is not, because every attendee sees every talk, so the ordering carries the whole day’s rhythm. Three dense sessions in a row will empty the room regardless of how good each one is, and a graveyard slot cannot be hidden: there is no parallel option to absorb the people who need a break.
The workable pattern alternates weight: something demanding, then something lighter or more practical, then a break long enough to matter. Lightning talks are the most useful tool here. They are short, low-stakes, and they reset a room’s attention better than a coffee break does, which is why both editions used them as a block rather than as an afterthought. They also give first-time speakers a way onto the programme; that is covered under lightning talks.
What a published schedule has to say
The schedule page is read by people planning travel, not by people browsing. It needs the start and end time of each day in plain sight, the room for each session if there is more than one, and the meal breaks marked, an attendee deciding whether a train gets them there in time should not have to infer it from a talk title. A programme that announces “doors 8:30” and starts at 9:00 has answered the only question most readers came with.
How the talks got there in the first place is covered under organising and the review process.
The shape described here is set out as a one-page reference in how a two-track single-day programme is laid out.
Questions
How long should a conference talk be?
Forty-five minutes suits most subjects and is the regional default. Thirty minutes is enough for a single idea with an example, and sixty needs a sectioned structure or it drifts. Whichever is chosen has to be stated in the call for papers, because proposals are written to a length.
How long should the breaks be?
Twenty-five to thirty minutes between sessions and an hour and a half for lunch. Fifteen minutes moves people between rooms without allowing a conversation, which removes the part of the day attendees most often say they valued.
Opening or closing keynote?
Both work, for different reasons: an opening keynote sets a tone, a closing one holds the room to the end and leaves everyone with a shared reference. What does not work is a keynote scheduled opposite another session.
Where do lightning talks belong?
Wherever attention needs resetting: after lunch, or attached to breakfast as in 2008. They are also the lowest-risk route onto a programme for a first-time speaker, which makes them worth scheduling deliberately rather than using as filler.