Most meetings are designed in the wrong order.
The planning team starts with the date, venue, speakers, titles, and familiar formats. A keynote is given thirty minutes because the person is important. A panel receives an hour because panels are expected. Group work is added because the agenda needs to look participatory. Only later does someone ask the facilitator to make it all engaging.
By then, the most important design decision has already been avoided: why does this event need to exist, and why does each session deserve a share of people's time?
'Bringing people together' is not a purpose
An event may aim to bring stakeholders together, exchange ideas, create awareness, strengthen collaboration, or discuss the way forward. These phrases sound respectable. They are also too vague to design from.
They describe activity or aspiration, not the difference the gathering must make. They do not tell us what participants should understand that they did not understand before, what views need to become visible, what decision must be informed, what relationship must change, or what commitment should exist when people leave.
A stronger why completes this sentence: By the end of this event, this group should be able, willing, or ready to ______, so that ______.
That sentence is difficult for a reason. It forces the sponsor to choose. A meeting cannot be equally responsible for informing, consulting, aligning, deciding, building trust, celebrating, and producing an action plan - especially in half a day. When everything is the purpose, nothing has design priority.
Define the difference, not merely the goal
One of the clearest influences on my thinking is Mark Collard, the experiential educator and founder of playmeo. In his writing on sequencing, he distinguishes a programme goal from the difference the programme is intended to make. The difference is expressed from the participant's perspective, and every activity is filtered through it.
Collard also argues that facilitators and participants should be able to answer why they are doing an activity at every point in the programme. His emphasis is not on finding more entertaining exercises. It is on sequencing appropriate experiences, framing them properly, and connecting them to what the group needs.
For institutional events, I would translate that principle this way: What should be different because these particular people spent this time together, in this room, now?
Priya Parker makes a closely related argument in her work on meaningful gatherings: determine why people are really gathering before deciding how they should spend their time together. The point is simple but demanding. Purpose is not decoration. It is a constraint on design.
The overall why is not enough
An event can have a clear headline purpose and still contain a weak agenda. This happens when individual sessions are inherited from previous years, negotiated around speaker availability, or included to satisfy stakeholders without identifying the job each session must perform.
'Panel discussion on financing youth innovation' tells us a topic and a format. It does not tell us why the session exists. Is the room meant to understand available financing? Diagnose why capital is not reaching young innovators? Hear competing views? Identify policy barriers? Choose priorities? Secure commitments from investors? Each answer requires a different method, amount of time, set of speakers, participant role, and evidence of success.
Every session therefore needs its own why - one that contributes logically to the purpose of the whole event. An agenda is not just a timetable. It is a theory of how one conversation prepares the room for the next.
Purpose determines methodology
Methodology should follow the work the room must do. Starting with a preferred format and then inventing a purpose for it is backwards design.
If the why is to inform
Use a focused briefing, demonstration, or concise presentation supported by questions that test understanding. Success is not that the speaker completed the slides. It is that participants can explain the issue and its implications well enough for the next session.
If the why is to surface perspectives
Use structured dialogue, small groups, interviews, written reflection, or anonymous digital input. A conventional panel followed by open Q&A will usually surface the most senior and confident voices, not the range of knowledge in the room. Success is that relevant differences, experiences, and recurring themes become visible and usable.
If the why is to prioritize or decide
Give participants clear options, decision criteria, evidence, and a legitimate decision rule. Protect time for testing trade-offs. Success is a decision or priority set with a visible rationale - not a lively discussion that ends with 'we will take this forward.'
If the why is to build commitment
Use action planning, role clarification, commitment rounds, or coordination across responsible actors. This session belongs after sufficient understanding and decision-making, not before. Success is expressed through owners, deadlines, dependencies, and the next point of accountability.
If the why is to build trust or connection
Use carefully framed and sequenced shared experiences, stories, paired exchanges, or collaborative challenges, followed by appropriate reflection. Success is not simply that people had fun. It is that the quality of interaction changes in a way that supports the work the group needs to do.
Purpose determines time
Time allocation is one of the most honest statements an agenda makes. An organizer may say the purpose is participation, but an agenda that gives ninety minutes to speeches and twenty minutes to group work says otherwise.
The right duration should be based on the cognitive, relational, and practical work required. Information can sometimes be transmitted quickly or shared in advance. Interpretation takes longer. Honest dialogue takes longer when trust or power differences matter. Decisions need time to examine trade-offs. Action planning needs protected time after the decision, when energy is usually lowest and the agenda is already running late.
Status should not determine minutes. Purpose should. A senior speaker may be central to the event, but that does not make every additional minute of remarks more valuable than the participant work needed to achieve the outcome.
Purpose determines what success means
Attendance, agenda completion, photographs, and satisfaction scores can be useful. They are not universal measures of success. The evidence should mirror the why.
For an awareness session, test what participants understood. For a consultation, show whose views were captured, where perspectives converged or differed, and how the input will be used. For an alignment session, identify what became clearer and what remains unresolved. For a decision session, record the decision, criteria, and authority behind it. For an action session, capture owners, deadlines, dependencies, and follow-up. For a relationship-building session, use careful qualitative evidence rather than pretending that a single numerical score proves trust.
This is why documentation must also be designed before the meeting. Rapporteurs cannot reconstruct the intended outcome afterward if nobody defined what evidence mattered in the first place.
Five questions every session should answer
Before a session is approved, the sponsor, designer, and facilitator should be able to answer five questions in plain language.
Why does this session exist?
Name the specific change it should create for participants or for the work of the event.
Why does this need to happen live?
If the content can be read, watched, or circulated in advance, protect live time for interpretation, dialogue, decisions, and relationships.
What must participants do?
Clarify whether they are expected to listen, question, contribute evidence, test options, prioritize, decide, commit, or connect.
What method gives that work the best chance?
Choose the format only after considering the audience, power dynamics, group size, language, risk, and desired output.
What evidence will show that it worked?
Define the output, capture method, success signal, and responsible owner before the session begins.
A session should earn its place
If a session has no distinct why, it should not occupy a separate block on the agenda. It may need to be removed, combined with another session, sent as pre-reading, reduced to a short briefing, or redesigned around a meaningful participant task.
This can be politically difficult. Agendas often carry protocol, visibility, representation, and institutional history. Not every item can be removed. But even fixed items can be framed honestly, timed proportionately, and connected to the wider purpose. The answer is not to ignore protocol. It is to stop confusing protocol with the outcome of the event.
The strongest agenda is not the one with the most impressive names or the widest variety of methods. It is the one in which every session performs a necessary job, the sequence makes sense, the time matches the work, and success can be recognized when it occurs.
The agenda begins after the why
A purpose-led event does not guarantee agreement, action, or transformation. Rooms are complex. Authority may be absent. Interests may conflict. Time may be cut. But a clear why gives the facilitator and organizer a basis for making intelligent trade-offs when conditions change.
It tells us which outcome to protect when a speaker runs over. It tells us whether to shorten a presentation or sacrifice group work. It tells us whether an energizer is useful, whether a poll is worth launching, what the moderator should bring forward, and what the final report must preserve.
Before asking what should be on the agenda, ask what should be different when the event is over. Then ask the same question of every session.
Only after that should we choose the method, assign the minutes, and decide how success will be measured.
Influences and further reading
- Mark Collard: How Do I Sequence My Activities? - on defining the difference a programme should make, sequencing for group needs, and framing the purpose of each activity.
- Mark Collard: Debriefing Tip - Begin With the End in Mind - on allowing intended learning and change to shape design, activities, leadership, and reflection.
- Priya Parker: The Art of Gathering course overview - on determining why people are really gathering before shaping how their time together is spent.