How to Build a Conference Programme Without Overloading It

How to build a conference programme around the attendee journey, cut unnecessary talks, separate tracks and protect time for transitions and breaks.

An overloaded conference programme rarely looks overloaded in a spreadsheet. It simply has a lot of strong topics, well-known speakers and useful formats. The problem becomes apparent later: an attendee chooses between equally important sessions, arrives late after a transition, skips lunch and by the finale can no longer take in the content.

At Aventura, we start the programme not with a list of talks but with the individual's journey. First we determine what question they arrive with and what they should take away. Then we keep only the blocks that move them towards that outcome. This makes the programme shorter but more useful.

Where should you start when planning a conference programme?

Start with a single sentence: “After the conference, a participant will be able to…”. The rest of the sentence should describe an action, a decision or a clear next step. The phrase “will learn a lot of new things” does not help you choose topics. The phrase “will compare three approaches and prepare a solution for their team” already sets the frame.

For a business conference, we define four levels of outcome:

1. For the client's business. What change the event supports: launching a business line, exchanging practices, developing a community, training partners.
2. For the audience. What task a person will be able to solve after the programme.
3. For each session. What question it answers and how it ends.
4. For the whole day. How the sessions form a coherent journey rather than a catalogue of talks.

If a session's thesis cannot be linked to any of these levels, it is a candidate for removal, for moving into the materials or for a separate meeting. A speaker's fame alone does not make a talk necessary in this particular programme.

It helps to separate essential content from possible additions straight away. The essential sessions form the semantic framework. Additions only go into the schedule once transitions, breaks and buffer time have appeared in it. When preparing a conference, forum or seminar, we protect this framework before we start inviting speakers: cutting talks that have already been promised is harder.

The day's framework is built around the participant's journey

The journey shows how many decisions a person has to make and how many times they have to switch modes. Registration, the plenary session, choosing a track, moving between rooms, a practical session and networking each require different types of attention. If you schedule them without varying the pace, even good presentations will start competing with each other.

We put together a draft framework in a table like this:

This table does not replace a minute-by-minute timing plan. It is needed earlier, to spot unnecessary repetition and gaps. For example, after a complex analytical presentation the audience may need a discussion or a break, rather than another presentation of the same density.

How to determine the right number of tracks?

The number of tracks is determined by the audience's different objectives, not by the number of available halls. A single track is simpler for the participant: no need to choose, less risk of missing something important. Multiple tracks are justified when groups come with different levels of expertise, roles, or practical tasks.

Before splitting, we ask three questions:

• can one common session provide value to all groups;
• does each track have a standalone outcome;
• can a participant understand the difference from the title and description without reading a long annotation.

If the answers are vague, it is better to combine the tracks. Parallelism for the sake of capacity shifts the problem to the participant: they are forced to choose between similar topics. We treat personal preferences and choice conflicts as a separate planning task. Therefore, we do not pit popular topics against each other without reason.

For a multi-track program, we create a conflict map. In the rows we indicate key audience segments, in the columns we place sessions. If two sessions are needed by the same group, we schedule them at different times. If overlap is inevitable, we determine in advance the main route, repeat, recording, or post-event material.

The duration of a block follows the task

A presentation, interview, panel, and practical work have different time requirements. We do not assign the same duration to all speeches just for a neat grid. First we describe the outcome of the block, then we check how many actions it includes.

A short presentation is suitable for one idea and a clear conclusion. An interview requires time for introductory context and clarifications. A panel makes sense when the participants' positions differ and the moderator can compare them within a common framework. A practical session includes instructions, execution, discussion, and recording the result. If only time for conversation is left, it is no longer practice.

In the timing, each block should show:

• speaker exit and seating;
• moderator introduction;
• main part;
• questions or recording the conclusion;
• technical completion and stage change.

We separately mark hard and soft boundaries. The start of the broadcast, lunch, transfer, and general session are hard. Questions from the audience or part of the discussion can be soft if the moderator knows in advance what to cut. This approach helps organize a business event without hidden minutes that later eat into the break.

Where to schedule transitions and breaks

A transition is part of the programme even if nothing is happening on stage. It includes leaving the hall, queuing for the cloakroom or coffee, moving between floors, finding the right door and taking a seat. That is why we measure the route on site rather than putting a conventional five minutes into the schedule.

A break also serves a purpose. Participants need to shift their attention, reply to messages, talk, recharge and get to the next block. Attention research offers no universal break length for every conference, so we do not promise a magic formula. Instead, we look at the density of the previous block, the distance between halls and the next format.

We protect pauses with three rules:

1. We do not use the break as a buffer for all late speakers.
2. We do not place important content only in the coffee area if it requires concentration.
3. We give the moderator a clear signal to wrap up so that delays do not snowball.

For a long day it helps to alternate the modes of perception: listening, discussion, movement, independent work. This is not entertainment filler but load management. When we inspect an event venue, we walk the future transitions with a stopwatch and take into account bottlenecks once the halls fill up.

The matrix helps cut unnecessary blocks

Once the draft is ready, we edit the programme. Each block gets one of four labels: keep, merge, move to materials, remove. We decide based on the contribution to the journey, not on who proposed the topic.

We pay special attention to panel discussions. Five mini-presentations in a row do not become a discussion just because they share a stage. You need a question on which positions differ, an order for comparing them and a final conclusion from the moderator. Otherwise it is better to keep two strong talks and full-fledged Q&A.

After cutting, we read the programme again through the eyes of a participant. If the titles differ only in professional jargon, the choice remains hard. In that case we rewrite the titles around the task: “how to choose”, “what to check”, “what decision to make”.

How to put together an online and hybrid programme

An online participant follows a different journey. They don't see staff at the venue, don't hear announcements in the lobby, and may join between work tasks. In a hybrid format, the livestream cannot be treated as a copy of the offline programme.

We add dedicated touchpoints to the online journey: connection check, waiting for the start, question rules, technical support, returning after a break, and access to materials. For an online conference, short instructions and a visible plan for the upcoming block are especially important.

Video meeting research links fatigue to a combination of factors. These include prolonged participation, a lack of breaks, seeing your own image, many faces on screen, restricted movement, and the effort of reading non-verbal cues. That's why we don't reduce the solution to a "cameras on or off" rule. It's more useful to rethink the programme itself: shorten continuous segments, provide clear breaks, allow different ways to participate, and avoid demanding constant on-camera reactions.

In a hybrid event, every interactive element must answer the question: what is the person in the room doing at this moment, and what is the person at the screen doing? If the online audience is only watching a discussion, we say so honestly. If they are taking part, we assign a separate question channel and a staff member who will pass their questions to the moderator.

Accessibility is built in before the final timing

An accessible programme explains the format, duration, breaks and way to participate in advance. W3C recommends planning presentation accessibility before the event, informing participants about available formats, and taking into account the needs of speakers and the audience. Canada's virtual events guidance also advises choosing an accessible platform in advance, preparing materials, and thinking through team roles.

For the programme, this means concrete actions:

• publish the current version and flag changes;
• state the session format, not just the topic;
• allow time for questions and technical switches;
• collect accessibility requests in advance without requiring disclosure of a diagnosis;
• prepare materials in a form that can be opened after the presentation;
• give advance notice of actions that require a separate device or app.

The US guidance on accessible meetings focuses on the participant journey, venue layout, communication, and the ability to request an accommodation. These principles are useful as checklist questions, but we verify the specific requirements of an event against the venue, format and applicable regulations.

How to run a final rehearsal of the programme

The final rehearsal takes place without an audience, but along the real route. We do not read out the row names in the spreadsheet. The team reproduces the actions: opens registration, brings up the holding slide, invites the speaker, changes the presentation, hands over the microphone, closes the block and leads people to the next hall.

We check five layers:

1. Content. Are there any repetitions, gaps or a block without an outcome?
2. Time. Are service actions, transitions and buffer time at critical junctions accounted for?
3. Space. Can the flow get through along the real route in time?
4. Technology. Do the programme, the director's script, the broadcast and the speakers' materials match?
5. Communication. Do the participant, the moderator and the team all receive the same up-to-date version?

We keep a change log: what changed, why, who confirmed it and where the information was updated. The latest version of the programme must have an owner. Otherwise a correction in the spreadsheet will not reach the website, the screen, the email to the participant or the host's script.

Before signing off, we ask ourselves a few short questions:

• can the logic of the day be explained in a minute;
• does every block have an observable outcome;
• are parallel tracks distinguishable;
• have the transitions been measured;
• are the breaks protected;
• does the moderator know what to cut in case of a delay;
• is the online participant's separate route clear;
• do all published versions match.

If even one answer is negative, the programme is not ready yet. It is better to remove one block before the announcement than to make a participant choose between promises that are physically impossible to keep.

Sources

• W3C Web Accessibility Initiative: Making Events Accessible
• Accessibility Standards Canada: Best practices for accessible virtual events
• U.S. Department of Justice: Accessible Meetings
• NIH PubMed Central: a review of fatigue factors in video conferencing