2.5 · Program design: the show people remember

IntermediateDuration ~11 min readTools Pen and one page, Your guest list

The big idea: a program is an energy shape, not a list of segments. You are cutting a film that has to play live, in order, once, so the shape has to be decided before anyone walks on stage.

The analogy

You already know that a film is made twice. Once when it is shot, and once when it is cut. In the edit you are not asking whether each scene is good. You are asking what this scene does to the audience right after the last one. Two big emotional scenes in a row and the second one lands softer, because the audience has nothing left to give it. A quiet scene before a loud one is not filler. It is what makes the loud one hit.

A program is that cut. The difference, and it is the whole reason this lesson exists, is that you only get to play it. In order. Once. In front of everyone. There is no assembly, no test screening, no note from an editor at two in the morning saying the middle sags. Whatever shape you decided on paper is the shape the room gets.

Watch

Thumbnail for Make Better Events (Seth Ferguson) — **Watch for:** Listen for the moment he names the failure directly: same, same, same, too much in a row, and the audience's brain turns off. His comparison is a hotel ballroom where every hour looks like the hour before it. His fix is to mix formats, keynote and panel and fireside, and to vary who is standing up there. Notice the other half too, that a hard sales pitch from the stage shuts attention down faster than anything else on the schedule. One caveat before you press play. This is a for-profit conference run by a growth consultant, with a pitch bookending the video and a business model built on selling to the room afterwards. The pacing idea transfers to your event completely. Nothing about his scale, his prize giveaways, or his ticket economics does.

How it works

Start with what the word covers. Your program is the content of the day in order: who is on stage, what happens between them, and every block you have deliberately left empty. It is not the run of show you build next lesson. The program is what the audience experiences. The run of show is how the team delivers it.

Written as a list, a program looks like a menu, and a menu tells you nothing about how the meal feels. So draw it instead. The energy curve is the line you would sketch of how charged the room feels from the first minute to the last. TEDx publishes the method as three instructions. Start strong, so minds open early rather than halfway through. Mix it up, so nothing feels like the thing before it. End with emotion, because the last thing people feel is the thing they carry out the door and describe to their friends. One or two real peaks is plenty. A program that is all peak has no peak.

Now the part most programs get backwards. The gaps are not what is left over, they are load-bearing. TEDx insists on real breaks because people need time to think about what they have just seen. For Filmmakers Connect the stakes are higher than pacing, because the connect time is the product. Nobody crosses the city to watch a panel they could have streamed. They come to meet other filmmakers. So the connect block goes on the program with a start time, an end time, and a host, exactly like a stage segment, and it is the last block you shorten when the day runs long.

Filling the shape is curation, and curation is mostly the discipline of saying no. Every slot you fill is a slot you cannot give to someone better, so a yes you give early is quietly a no you gave to somebody you had not met yet. TEDx’s guiding line is the sharpest version of this: look for ideas, not speakers. If you describe a potential guest to a stranger and everything you say is about who they are rather than what they will actually say, you have not found a talk, you have found a name. They also tell organizers not to choose alone, because one person’s taste produces one person’s event. And the integrity rule from Lesson 1.5 stands without exception. No sponsor buys a program slot.

While you are choosing, notice that a panel is a choice and not a default. The ignite format is five minute talks on slides that advance themselves on a timer whether the speaker is ready or not. It sounds cruel and is a kindness. It makes a first time speaker impossible to derail, and gives your program a fast, funny stretch no keynote can produce.

Open space is the other one worth stealing. You block out time, attendees propose the sessions themselves on a board, and people go where the conversation they want is happening. DevOpsDays runs its whole afternoon this way. For a room full of filmmakers who each arrived with a different thing they are stuck on, it is close to a cheat code, and it costs you a whiteboard and some sticky notes.

Whoever ends up on that program then needs one person. The speaker liaison is a single named contact who owns a guest’s whole arc, from the invitation through the rehearsal to the moment they walk off. Not a channel, not the team chat, a person. A guest with two contacts effectively has none, because both will assume the other one sent the arrival time. Part of that job is getting the rider, the list of what a guest needs to do their thing: the mic they want, whether they sit or stand, water, a quiet stretch beforehand. Nobody at your scale will hand you a formal one, so the liaison asks in plain language and writes the answers down.

Then the part community organizers skip and then regret. Rehearsal. TEDx is blunt about it, up to and including permission to cut an unprepared speaker, and their sharpest line is that a speaker who sounds too rehearsed is not done rehearsing. You are not running months of coaching. You are running the day-before walkthrough: where they get their mic, where they sit, how they get on stage, how you signal that time is up, how they get off. A few minutes each, and it removes most of what goes wrong in front of an audience.

One last piece: where a guest waits. A green room does not have to be a room. It needs to be a space that is not the crowd, with water, a chair, and their liaison nearby, because a guest who spends the hour before their segment meeting strangers arrives on stage already spent.

For August, your live podcast is the peak of the curve, and it is also the segment that forces a producer and MC split, because the host cannot solve problems while recording. Give it its own rehearsal, one liaison per guest, and a real break on either side. And the program is itself an announcement moment. DevOpsDays publishes theirs about three and a half months out because a published program turns interest into registrations, which makes the program drop a dated post on the runway you built in 2.1.

The receipts (evidence, if you want it)

The three-instruction program shape is TEDx’s, published verbatim: “Start strong: You’ll want to open people’s minds right from the start… Mix it up: Break up your program with thrilling demonstrations and moving performances. Throw in a few shorter talks or counterpoints. End with emotion: Save the most gripping speakers and TED Talks for the end. This is when your attendees are most open to being moved” (TEDx Organizer Guide, Event program).
Same page, on pacing and slack: sessions of about 90 minutes, “pad each session with an extra 15 minutes, to account for transitions, introductions, and other small delays that inevitably occur,” no session longer than 105 minutes, and performances used as “palate cleansers” between serious or slower talks.
Same page, on breaks as designed space: “All TEDx events, regardless of length, should have breaks between sessions. People need time to think about what they’ve seen (and use the restroom),” with food, drink and hands-on activity stations recommended inside them.
Talk length as a curation tool: TEDx Talks run under 18 minutes, “many talks are even shorter, with 3-9 minutes being ideal for a focused idea,” and up to 30 minutes for a two-person dialogue or interview (TEDx Organizer Guide, What is a TEDx Talk).
“Look for ideas, not speakers… if you were to describe a potential talk to a stranger and say more about the speaker (‘this lady who runs that local charity,’ ‘this guy who made this film’) than a specific idea, that’s a clue that you need to go back to that speaker and find their idea, not their identity” (TEDx Organizer Guide, Select your speakers).
On not curating alone: “Choosing speakers and performers shouldn’t be the job of just one person. Having more people at the table will make for a more diverse and interesting group of speakers.” The guide also warns that too large a group ends up “always choosing the most agreeable options, not the most interesting” (TEDx Organizer Guide, Create a selection committee).
Rehearsal discipline, including the line worth taping to a wall: “When a speaker sounds too rehearsed, they’re not done rehearsing.” The day-before walkthrough list is theirs too: where they will get ready and be given their microphone, where they will sit, how they will step on stage, “how you will cue them when their time runs out,” and how to exit. Same page grants organizers permission to cut an unprepared speaker: “It’s never a fun thing to do, but it’s the fair thing to do for your TEDx community and for that speaker” (TEDx Organizer Guide, Rehearsals).
Green room practice: not required, but recommended as a private space with snacks and water where you check in with the speaker, and where micing happens “in advance to factor in any technical issues” (TEDx Organizer Guide, Day of the event).
The DevOpsDays program shape: talks in the morning at about 30 minutes each, “a set of several ignite talks: 5 minute talks with 20 slides that auto-advance,” and “openspaces in the afternoon: a self-organizing part where everybody gets to propose a session.” Their running notes for ignites are practical: collect slides ahead as PDF, run them off a dedicated laptop rather than the presenter’s, tell presenters again on the day that there are no presenter notes and the slides advance without them, and have presenters queue beside the stage (devopsdays.org/organizing; Ignite format; Open Space format).
The integrity rule, in their words: “No sponsor should be able to buy their way into the program. The schedule should be decided by your local organizers.” Sponsors “are never given attendee contact info… nor are they allowed to purchase speaking slots for talks or ignites” (devopsdays.org/organizing).
Why the program is a marketing asset and not just a schedule: DevOpsDays launches the program at T-3.5 months because “your program absolutely drives visibility of your event. Your speakers can help market the event and at the same time would-be buyers might be waiting on your program before purchasing a ticket.” They pair the program launch with the early-bird close (devopsdays.org/organizing).
One point of contact per guest: “It works best if you dedicate a person/pair to respond to proposals/speakers and handle communication” (devopsdays.org/organizing). A DevOpsDays Halifax organizer puts the day-of version of the same job plainly: “Designate a speaker wrangler who knows all the speakers and can track down anyone who might be missing just before their talk. This role is crucial for keeping the schedule on track” (Dewan Ahmed, Hosting a Tech Conference).
Be explicit with guests about length, or they will guess. Matt Stratton’s write-up records a speaker delivering 25 minutes for a 20 minute slot because they had not noticed the length changed: “This is a reminder to be extra explicit with details like this to your speakers!” (Matt Stratton, Hosting a Participant-First Conference).
On breaks as the networking product rather than the interval: open source event organizers report that “breaks should remain frequent and certainly placed between every talk,” because in physical events that is what enables “the always popular and beneficial hallway track” (TODO Group, Organizing and Managing Open Source Events).
The energy point from the video, in his own framing: at a conference where it is “the same same same too much in a row… your brain turns off,” and the fix he lands on is a deliberate mix of panels, keynotes and fireside chats, chosen partly by asking his own audience which formats they actually liked (Seth Ferguson, Make Better Events, from 9:24). Treat the pacing idea as the transferable part and nothing else about the event he is describing.
The producer and MC split, which your live podcast forces: “as soon as the program has cues (walk-on music, video rolls, livestream) someone must run the show from off-stage,” and the host cannot be the person solving problems mid-recording (industry map §1.3, drawing on MeyerPro). Lesson 3.1 makes this a command structure with names on it.

Your one move

Take one page and draw a horizontal line for the August event, doors on the left and close on the right. Above the line, sketch the energy curve you want: where it opens, where the peak sits, where it dips on purpose, where it ends. Below the line, write the blocks that produce that shape, with a format next to each one, including the connect block and the podcast. Then, on the same page, list every guest by name and write exactly one liaison name beside each. Twenty minutes. Done when every block has a format and no guest name is missing a liaison, or is carrying two.

A worked shape for August (illustrative, not a locked schedule)

Times and names are invented to show the shape. Yours will differ.

Block	Format	Energy
Doors and open floor	Hosted mingling, music playing, booths open	Warm and rising
Welcome	MC, short, names why the room exists	First small peak
Opening guest	One story, tight, under twenty minutes	Rising
Ignite round	Four community members, five minutes each, auto-advancing slides	Fast and loud
Break	Real break, food, booths, photo wall	Deliberate dip
Live podcast	Host plus guests, recorded	The peak
Connect block	Hosted, structured, the actual product	High and horizontal
Close	MC, thanks, one line about what happens next	Ends on feeling

Two things to notice. The dip before the podcast is not wasted time, it is what makes the podcast land. And the connect block sits after the peak on purpose, because that is when people most want to talk to each other and have something to talk about.

Want to go further?

Take your sketch and mark every point where something has to be cued: a walk-on, a music roll, a mic swap, a slide deck starting, the podcast recording rolling. Those marks are the first draft of the cue sheet you will build in the next lesson, and the count of them tells you whether one person can still run this event from the floor.

The needle: an event is won before doors open, and the energy curve is you deciding what the room will feel like at four in the afternoon while you still have the power to change it.

Terms introduced

Check

You can move on when you can… describe your event’s shape as a curve rather than a list, say which block you would cut first when the day runs long and which one you would never cut, and name the single person responsible for each guest.

Go deeper

Next up: 2.6 · The paper stack: run of show, cue sheet, production schedule, where the shape you just drew becomes the three documents that let other people run it with you.
The TEDx Organizer Guide, Speakers and program section is the source text under most of this lesson. The Event program, Select your speakers, and Rehearsals pages are the three worth reading end to end, even though it is written for a talks-only format you are not running.
The DevOpsDays organizing guide has the community-scale version. Read Setting your program, Running Ignites, and Running Open Space together, then the Open Space format page if you want to try one in August.
The full Seth Ferguson video, Make Better Events, runs about sixteen minutes. The pacing section you watched is the part that transfers. The rest is a paid-conference growth model with a consultancy pitch at both ends, so read it as someone else’s business rather than as advice for yours.