1.1 · Strategy before logistics

BeginnerDuration ~9 min read + 21 min videoTools Pen and one page, The master sheet from 0.3

The big idea: before anything gets booked, an event needs five written lines, its objective, its audience, its format, its two readers, and its feasibility test, because every logistics decision you are about to make is answering one of those five whether you wrote them down or not.

The analogy

No film gets made from a mood. It gets made from a logline, one sentence that says what the story is, who it’s for, and what shape it takes. Short or feature. Doc or narrative. That sentence is short enough to say at a table, and it’s the thing every later decision gets checked against. Camera package, location, cast size, all of it answers back to the logline.

Then there’s a second, less romantic step. The producer takes the logline and asks whether it can actually be made: can we get the locations, can we cover the money, can we get a crew, inside the schedule we have. That’s the green light. And when the answer is no, the film that gets made is a version with a smaller shape, not a different story.

An event works the same way. You need the logline, and you need the green light. This lesson is both.

Watch

The talk below is about online communities and never once says the word “event.” Ignore that. The discipline underneath it transfers whole, and it’s the discipline this lesson runs on.

Thumbnail for Is Your Community Strategy Working? Richard Millington at CMX — **Watch for:** Start with the NASCAR bit early on. His point is that on a race track you never need a map, you just need to go faster, and that most of us plan as if we're on a track when we're actually on open road. Then watch him build the chain in the middle: goal first, then specific objectives, then the emotional lever that makes people actually act, and only then the tactics, five to seven of them and no more. That chain is exactly what you're about to do for the August event, with 'community' swapped for 'event' and 'members' for 'the room.' Stay for the close, where he argues that anything you haven't priced in hours and money, with no named risk and nobody owning that risk, isn't a strategy yet. That's the feasibility test in different clothes.

How it works

Here’s the trap. The questions that feel most urgent are logistics questions. Which venue, what date, how many chairs, who’s on the panel, do we do booths. They feel like the real work because they produce visible progress, and progress feels good. But each of those questions only has a right answer if something upstream has already been decided. Ask the venue question first and you will absolutely get an answer. It just won’t be the right one, and you won’t find out until you’re standing in a room that feels slightly off and can’t say why.

So before anything gets booked, you write the event concept. It’s five lines. It fits on one page, it takes one sitting, and it is the thing everything later gets checked against.

The first line is the objective. Not “run a great event.” An objective says what is different in the world because this event happened, specifically enough that someone else could look at the room afterwards and tell you whether you hit it. “A full room” is attendance, not an objective. “Most of the room leaves having had a real conversation with someone they had never met, and a meaningful chunk of those people are at their first film event ever” is an objective, because it names behavior. Behavior is the thing you can design a room around. Attendance is just the thing you count.

The second line is the audience. Not a category, a person. “Filmmakers” is a category, and it’s too wide to make a single decision with. The newcomer who has never been to a film event and doesn’t know anyone is a person. The working crew member who wants better collaborators is a different person. You can absolutely serve several at once, and Filmmakers Connect is built to. But you have to know which one the room is primarily built for, because when a decision comes down to a coin flip, and several will, the audience line is what breaks the tie.

The third line is the format. Format is the shape: how long, how many segments, how much stage time against how much floor time, seated or standing, booths or no booths, podcast or no podcast. Here’s the discipline that matters. Format is downstream of the first two lines, always. The most common way an event goes sideways at this stage is falling in love with a format first, a panel, a booth row, a live podcast, and then reverse-engineering an objective that justifies it. Formats are seductive because they’re concrete and easy to picture. Choose them last anyway.

The fourth line is the two-readers rule. Every event concept you write gets read by two different people who want different things from it. A community member reads it and asks: is this for someone like me, will I feel welcome, is it worth my Saturday. A sponsor reads the same concept and asks: who is in that room, and what can we do with them. If your concept only satisfies the first reader, the room fills but nothing funds it. If it only satisfies the second, you have a trade show that nobody wants to attend twice. Write a concept that survives both readings, then keep the two versions of the copy strictly separate. Money language never appears in the community version.

The fifth line is feasibility, and it’s three questions asked against the runway you actually have. Can I get a venue that fits this format, on a date this close? Can I cover what this format costs, from income I can realistically land in that window? Can I get the people this format needs to run, named and committed, not hoped for? Answer honestly, in hours and pesos, the way Millington insists you price every tactic before committing to it. And when one of the three comes back no, here’s the rule: the format bends. Not the objective, and not the date. That’s what makes this a test rather than a wish.

Run it on the August event and you can feel it working. Objective, a room where people who arrived alone leave with someone. Audience, first-timers and early-career filmmakers, with working crew welcome. Format, a hundred plus in the room, sponsor booths along one wall, a live podcast recorded in front of everyone, and connection time that’s scheduled rather than hoped for. Two readers, community sees a warm night that’s actually for them, sponsors see a concentrated room of the exact people they want to reach. And feasibility, a venue that holds that headcount with booth space, money that lands mostly from sponsorship, and a team where the booths and the podcast are somebody’s named job. That last clause is the one that quietly decides whether the format survives contact with reality, which is why the very next lesson is the org chart.

None of this is a document you defend in a meeting. It’s a tiebreaker you keep on the first tab, so the small decisions coming at you over the next weeks all get answered by the same five lines instead of by whoever asked most recently.

The receipts (evidence, if you want it)

The goal to objectives to strategy to tactics chain, the “slim down to five to seven tactics” rule, and the insistence that every tactic be costed in both hours and money come from Richard Millington’s CMX Summit talk (full talk). His closing argument is that a strategy with no named risk and nobody responsible for that risk is not a strategy. The talk is about online communities, so the vocabulary needs a translation pass, which this lesson does.
CMX’s own playbook puts strategy ahead of programming for community-led events, sequencing business goals through their Three Level Strategy Framework before any event design happens (The CMX Guide to Community-Led Events). The full guide is email-gated, so only its public framing is cited here.
TEDx tells organizers to size the effort to the event rather than the ambition: “Scale your team appropriately; quality is more important than quantity… if you’re having a smaller event, you may not need a team of 10 or more. Figure out what is the best number based on the kind of event you’re having” (TEDx Organizer Guide, Build your team).
DevOpsDays makes team feasibility a precondition, not an afterthought: an event needs at least three organizers from three different organizations before it is green-lit at all (devopsdays.org/organizing). The same guide ties spend commitments to go/no-go dates as sponsorship money lands, which is the feasibility test running continuously rather than once.
Runway benchmarks for the feasibility question: large conferences typically need 6 to 12 months, mid-size events 3 to 6 (Lyyti, event planning timeline). At community scale the same shape compresses to roughly 10 to 16 weeks, which you’ll build in Lesson 1.3.
The two-readers rule is a course label, not an industry term. It comes from the Filmmakers Connect brand bible, which requires every piece of copy to identify its reader before it’s written: community members and attendees get one tone, sponsors and partners get another.

Your one move

Write the August event’s concept in five lines. Objective, audience, format, two readers, feasibility. Put it at the very top of the Runway tab in the master sheet you built in Lesson 0.3, so it sits above every date you’re about to add. Twenty minutes, done when all five lines exist and the feasibility line either says yes on venue, money and team, or names exactly which one is a no.

Want to go further?

Take the objective line and write it twice more. Once the way a first-timer needs to read it, warm and clearly for them, no jargon and nothing that sounds like an industry gate. Once the way a sponsor needs to read it, concrete about who is in the room and what access looks like. If you can’t write the sponsor version without making the community version feel colder, your audience line is doing too much guessing. Fix that line, and you’ve just done most of the work for Lesson 1.5.

The needle: an event is won before doors open, and this page is the earliest decision there is. Every venue call, budget line and sponsor conversation from here just performs the five lines you wrote today.

Terms introduced

Check

You can move on when you can… write the five lines for any event you’re planning, in the right order, and say out loud which of venue, money, or team is the one most likely to fail the feasibility test.

Go deeper

Next up: 1.2 · The org chart: who you actually need, which turns the third question of the feasibility test into an actual chart of owned functions with named people on them.
The DevOpsDays Organizing Guide is the closest published twin to what Filmmakers Connect is becoming: volunteer-run, community-first, funded by sponsors. Its “Essential Rules” section is a concept statement written as constraints, and it’s worth reading once in full before Level 1 is over.