2.1 · The promotion runway

IntermediateDuration ~10 min readTools Your master sheet, Runway tab

The big idea: promotion is not posting more, it is a short calendar with three phases, and a handful of announcement moments spaced across it on purpose instead of dumped in one post.

The analogy

You have watched this run a hundred times without calling it a campaign. A film does not get announced once. First there is a title and a date, maybe a single frame. Weeks later, a teaser. Then a first look image, a cast announcement, the full trailer, the poster, the press round. Every one of those is a separate day on which the film is news again, and none of them are accidents. Somebody sat in a room months earlier and decided which asset goes out in which week.

Now picture a distributor with exactly the same materials who posts the teaser, the trailer, the poster, the cast list and the interviews all on one Tuesday, then says nothing until opening weekend. Same film. Same assets. A fraction of the audience. Nothing was missing except spacing.

Your event has fewer assets than a film, which makes the spacing matter more, not less.

How it works

Start with length, because most first campaigns are too short.

Published promotion runways scale with the weight of the event. Flagship conferences run twelve to sixteen weeks of active promotion. A community event of a hundred and some people sits around six to ten weeks, and the shortness is a feature rather than a shortcut. A conference needs the longer stretch because its audience has to request budget, book flights, and clear three days off work. Yours needs to keep a Saturday free. Decisions that small get made late, so a campaign that opens too early runs out of things to say by week six and goes quiet exactly when it matters.

Inside that stretch sit three phases. They are not calendar decoration. Each has one job, and if you cannot say which job a post is doing, it is filler.

Launch establishes that the event exists and opens the door. That is the whole job. Not persuasion, not detail. A name, a date, a place, one line on who it is for, and a working registration link. Launch is short and loud, usually a week, and it is finished the moment somebody outside your circle can sign up without asking you a question.

Ramp is the long middle, and it is the phase almost everybody skips. Its job is to manufacture news. Between the launch and the final push nothing new happens by itself, so you make things happen: a guest revealed, the program published, the venue shown, a sponsor’s contribution shared. Skip ramp and the attention you earned at launch quietly evaporates, because the people who heard about you in week one have had six weeks to forget.

Convert is the last stretch, and its job is narrow. Remove the last reasons not to come. Not more excitement. Reasons. Where exactly is the venue, what time do doors open, is there parking, is it okay to come alone, what happens if you arrive late. Each of those is somebody hovering over the register button, and each answer you publish converts a few of them. Convert runs straight through the freeze from Lesson 1.3. The freeze stops countable things from moving. It never stops you posting.

Now the resource that makes ramp possible, and the one most organizers waste. An announcement moment is a piece of news about your event that genuinely earns a fresh post: a guest reveal, the program drop, the venue reveal, a sponsor’s booth, the last batch of spots. You get a handful of them for any given event, and they are the only ammunition ramp has. The instinct is to load everything into the launch post because it feels stronger that way. It is exactly backwards. That one post spends the entire campaign in an afternoon, and then you have five weeks of “don’t forget, we’re still happening.”

Stagger them instead. Roughly one a week, each a fresh reason to be noticed by someone who missed you last time, and a fresh reason for people already registered to bring somebody. DevOpsDays publishes this pattern from the other side. The moments when their registrations reliably spike are almost entirely announcements: tickets opening, early bird closing, speakers announced, agenda announced. Schedule no announcements and you have scheduled no spikes.

One announcement is special enough to carry its own name. Early bird is registration that costs less and closes on a date, and the reason it works has little to do with the discount. It is a deadline, and a deadline moves people who have already half decided. DevOpsDays reads it as a signal as well as a sale. If early birds come in around fifteen percent of expected registrations, you have evidence an audience exists. Treat that share as an anchor for reading your own pace, not a target to copy.

Your events are free, so read the mechanic one level up. The deadline converts, not the price. A free event can build a real one: a first batch of spots that closes, a perk for anyone registered by a date, a small Q&A slot only early registrants get into. What you never do is fake a sold out. Trust is the whole asset, and it takes one screenshot to lose.

Last, where the calendar lives. It goes on the Runway tab of your master sheet, in among everything else. A launch post is a milestone like any other: a T-minus week, a date, one owner. Keep promotion in a separate marketing doc and the program-published date and the program-announcement post drift a week apart with nobody noticing. It also parks the calendar next to the number that judges it. DevOpsDays checks whether registrations are anywhere near target pace a month out, which in T-minus terms lands you mid ramp. If they are not, ramp is where you fix it. Pull an announcement forward, spend one you were holding back, ask partner communities to share now instead of later. The calendar changes. The date does not.

For August, the shape is already sitting there. The live podcast is an announcement moment, and so is each guest on it. Sponsor booths are a moment, told as what that sponsor makes possible rather than as a logo, which is TEDx’s own guidance and also better copy. The venue is a moment. That is a ramp with something real in it every week, without inventing a thing.

The pattern

Three phases, one job each. Announcement moments are ammunition, so space them. Launch says the event exists and opens the door. Ramp manufactures news, one moment a week. Convert removes the last reasons not to come. Every announcement is a milestone on the Runway tab with a T-minus week and an owner. If a post cannot name which of the three jobs it is doing, it is filler.

The receipts (evidence, if you want it)

• Promotion runway by event weight: 12 to 16 weeks for flagship conferences, 8 to 10 weeks for mid-size B2B events, 4 to 6 weeks for webinars, 2 to 4 weeks for executive roundtables (Samaaro, event promotion timelines). The 6 to 10 week figure this course uses for a 100 to 150 person community event is interpolated from that ladder in the course’s industry map. It is a derivation, not a published benchmark.
• The same source’s phase timings: launch 8 to 12 weeks out (save the dates, teasers, event page live, partner announcements), ramp up 4 to 6 weeks out (content, speaker previews, email nurture, countdowns, partner pushes), conversion 2 to 3 weeks out (urgency emails, reminders, retargeting, late incentives, final lineup names). It names the three failure modes too: launching late, overloading the final week, and neglecting mid-stage activity, which “often gets low signups because people are not convinced of your event’s true value” (Samaaro).
• The pre-launch, launch, ramp, convert phase structure is the consensus shape across published event marketing timelines, with guest and speaker announcements deliberately staggered to create multiple news moments (TeamGantt event marketing plan; Guidebook, event marketing timeline).
• DevOpsDays puts marketing activation at T-7 months, registration opening at T-6.5 months, and both the program launch and the early-bird close at T-3.5 months, pairing them on purpose: the program “absolutely drives visibility of your event,” and closing early bird alongside it rewards people who bought before there was a program (devopsdays.org/organizing). At community scale the whole shape compresses, but the pairing survives.
• The spike list, in their words, is where registrations actually move: when tickets are first announced, when early-bird sales end, when speakers are announced, when the agenda is announced, when ticket codes go out to sponsors, speakers, organizers and volunteers, after any reminder email, and in the last two weeks. They also confirm the last-two-weeks spike is normal and that you are not alone in seeing it (devopsdays.org/organizing).
• The early-bird datum: “Did we sell a good bit of early bird tickets? What to look for is probably 15% of the expected ticket sales (e.g., of 400, 60 early birds). Again, this shows an audience and interest” (devopsdays.org/organizing). Their mid-runway health check is 40 to 50% of expected registrations, excluding sponsors, speakers, organizers and volunteers, by about a month out, and they note that organizers who announced the agenda late or forgot the emails tend to sit closer to 25 to 30%. You run that check properly in Lesson 2.2.
• Community seeding tactics named in the sources: partnerships with partner communities and influencers, exclusive content previews, and sponsor channels amplifying the event (EventsAir, event promotion timeline).
• TEDx’s promotion chapter puts a “storyteller” on the blog and the social accounts, updating once or twice a week with speaker announcements and interviews, plus regular email updates to guests, because “while marketers get people interested, storytellers keep people interested” (ted.com, promotion and press). On sponsor posts specifically: “a logo on its own won’t serve your audience. Logo-only posts tend to feel like ads and are easy to scroll past. Instead, focus on creative posts that show what the sponsor made possible” (ted.com, sponsors on social media).
• The freeze that the convert phase runs through: vendor orders, catering counts and printed materials finalized by two weeks out (Crestline conference planning checklist).
• No credible published cost-per-registrant benchmark exists for community-scale events, so this course never quotes one. If someone shows you a CAC number for an event like yours, ask where it came from before you plan against it.

Your one move

Open the Runway tab on your master sheet, the one you built in Lesson 0.3 and filled in Lesson 1.3. Add these rows in among the milestones already there, each with a real calendar date and one owner:

T-minus	Row	Phase
T-8 weeks	Launch post live, registration open	Launch
T-7	Announcement moment 1	Ramp
T-6	Announcement moment 2	Ramp
T-5	Announcement moment 3	Ramp
T-4	Program published	Ramp
T-3	Early-batch deadline closes	Ramp
T-2	Convert push begins, logistics answered	Convert
T-1	Final call, reminders	Convert

Then name the three ramp moments. Real ones, from what August actually has: the podcast, each guest, the sponsor booths, the venue. Squeeze or stretch the weeks to the runway you have, and do not reorder them. Twenty minutes, done when every row has a date, an owner, and no announcement moment is sharing a week with another.

Want to go further?

Count the announcement moments you just placed. If you have more than you have weeks, you are in a good position and can hold one back as insurance for a slow month-out check. If you have fewer weeks’ worth than the ramp needs, that gap is a real finding, and it usually means a guest or a sponsor has not been confirmed early enough to be announced on time. That is a booking problem showing up as a marketing problem.

The needle: an event is won before doors open, and a room fills on a calendar written weeks earlier. The night you have nothing to post is not a bad night. It is an empty row you left on this tab today.

Terms introduced

Terms introduced in this lesson

• Launch, ramp, convert
• Announcement moment
• Early bird
• Runway
• Milestone
• T-minus
• Freeze

Each term links to the glossary, where it is defined by the way you just used it.

Check

Check yourself

1. You publish one enormous launch post eight weeks out. It has the date, the venue, the full guest list, the sponsors, the program, and the link. It does well. Then the page goes quiet for three weeks because there is nothing new to say. What actually happened?

   The post was too long, and length is what killed the reachYou launched too early, and eight weeks is too much runway for a community eventNothing bad, a strong launch post is worth several small onesYou spent every announcement moment in one afternoon, so the ramp phase has no ammunition left

2. Your August event is free, so a teammate says early bird does not apply to you. Is that right?

   Yes, early bird is a pricing tool and free events have no price to discountNo, but the only honest workaround is to say the event is nearly sold out when it is notNo. The mechanic that works is the deadline, not the discount, so you build a real one: a first batch of spots that closes, or a perk that only people registered by a date getYes, and you should charge a small fee purely so early bird becomes available

3. One month out, registrations are sitting at about a fifth of your target. What is the correct response?

   Nothing, promotion pace is not something you can steer once the campaign is runningWait it out, because registrations always spike in the final two weeksLower the target to match the pace so the numbers look healthy againChange the promotion calendar. Pull an announcement moment forward, add one you were holding back, and ask partner communities to share now rather than later

Check answers

You can move on when you can… name the three phases and the single job each one does, point at your own runway and say which week each announcement moment lands in, and explain why an early-bird deadline works on a free event even though there is no discount.

Mark this lesson complete

Go deeper

• Next up: 2.2 · Registration ops: the no-show math, where the calendar you just built meets the only number that judges it, and you find out how many registrations a room of a hundred people actually needs.
• Samaaro’s promotion timelines article is the clearest published version of the three phases. It is written for enterprise B2B events, so halve every timeline in it and ignore the paid-media sections, but the phase logic transfers cleanly.
• devopsdays.org/organizing, the “Timing” subsection under registration, is worth reading once for the spike list alone. It is the closest thing published to a volunteer conference telling you honestly where its registrations come from.