The Decisions That Get Made Before Event Planning Even Begins
The most important event planning decisions get made before anyone books a venue, signs a vendor, or opens a project plan.
By the time most teams start “planning,” the event has already been shaped by choices that may not have even been treated as decisions.
What is this event supposed to do?
Who is it for?
What kind of event makes sense for that goal?
What are we measuring?
And where should the budget go based on those answers?
If those questions haven't been answered, the team is starting with assumptions, not a strategy.
And then they're about to build an entire event on top of them.
Event planning starts earlier than the kickoff meeting
A kickoff meeting can feel like the beginning.
The team is assembled. There's a timeline. Someone has created the project plan. Venue sourcing may already be underway.
But a surprising amount has already been decided by that point.
Maybe the format was inherited from last year. The budget was based on last year's spend. The audience is “customers and prospects.” Leadership wants the event to be “bigger and better.” And everyone starts building.
But… bigger for whom? Better at what?
More attendees? More sponsors? More leads? More content? More pipeline?
Those aren't interchangeable goals, and they don't necessarily lead to the same event.
This is why I think some of the most important event work happens before the traditional planning process begins. It's the point where you can ask whether you're building the right thing before you get very, very good at building it.
Make these decisions before you build the event
There are a handful of questions I want answered early because they affect almost everything that comes after them.
What is the event supposed to accomplish?
Get more specific than “engagement” or “a great customer experience.”
Are you trying to generate new pipeline? Move existing opportunities? Increase customer retention? Build a user community? Support a product launch? Strengthen relationships with a particular group of customers?
An event can contribute to several business goals. But you still need to know which outcomes are driving the decisions.
Who specifically needs to be there?
“Our customers and prospects” is a starting point, not an audience strategy.
Which customers? Which prospects? What roles? Which accounts? What do they care about? Why would they give you a day, two days, or three days of their time?
The clearer the audience is, the easier it becomes to make decisions about content, sponsors, pricing, promotion, experience, and follow-up.
What format fits the goal?
Sometimes the answer IS a 1,200-person conference.
Sometimes it might be a smaller executive program, a customer roadshow, a series of dinners, a virtual program, or something else entirely.
And “this is what we did last year” isn't enough reason to keep doing it.
If the business goal has changed, the audience has changed, or the economics have changed, the format deserves another look too.
How will you know whether it worked?
This is where I want to look beyond registration + attendance.
What generated pipeline? What moved existing opportunities? What strengthened customer relationships? What did sponsors get from participating? What will leadership use to decide whether to fund the event again?
You don't need every answer before planning begins. You do need to know what you're trying to measure so you can build the tracking into the event from the ground up.
Where should the budget go?
Not every line item. Not yet.
I mean the shape of the investment.
If customer relationships are the priority, maybe more of the budget belongs in hospitality or smaller high-value experiences. If content is the draw, that changes the investment. If pipeline is a major goal, registration volume alone probably shouldn't determine where the money goes.
A budget is more than a list of costs. It reflects what the team believes will make the event work.
A lot of event strategy gets decided by default
I don't think teams intentionally skip these conversations.
Usually, the event just needs to start moving.
There are venue holds to worry about. Dates need to get on calendars. Leadership wants to know when registration will open. Someone needs to start talking to production.
Those things are visible and urgent.
Sitting down and asking, “Wait, are we sure this is still the right event?” doesn't create the same sense of progress.
So last year's format gets inherited. Last year's budget becomes this year's starting point. The audience stays broad. “We want a great event” turns into a workback plan without anyone defining what great needs to accomplish for the business.
And once money has been committed and plans are moving, those assumptions become harder to revisit.
That's how decisions that nobody remembers making can end up shaping the whole event.
Good upstream decisions make downstream decisions easier
When the objective, audience, format, measurement plan, and budget direction are clear, they give the team something incredibly useful: a way to make decisions.
Should we add another activation?
Does this sponsor request make sense?
Is this speaker right for the audience?
Is this production upgrade worth the cost?
Do we need this session?
Should this money go here, or would it do more somewhere else?
Without a clear framework, every question becomes its own debate. And when nobody knows what should win, decisions tend to bounce upward to whoever has enough authority to make the call.
That's how you end up with a VP maintaining a death grip on every decision, even though nobody particularly wants the VP deciding what goes on a breakout-room sign.
With a clear strategy, the team has something to make those calls against.
You can say no to an idea because it doesn't serve the audience. You can move money because another investment supports the goal better. You can push back on something leadership requests because you have a reason beyond “the event team doesn't like it.”
And when something inevitably changes, because something ALWAYS changes, you have a better way to decide what to do next.
The event isn't always where the problem started
When an event underperforms, it's easy to look at the execution.
Maybe registration was lower than expected. The audience mix was off. Sponsors weren't thrilled. Sales didn't follow up. Leadership can't see the pipeline impact. The team was underwater for three months.
Those are event problems.
But the event may just be where the problem became visible:
If nobody defined the audience clearly, Marketing had a harder job filling the room with the right people.
If nobody decided how the event would connect to Sales, the post-event handoff was always going to be shaky.
If nobody defined success until the recap deck, measurement was always going to be messy.
If the budget was inherited instead of built around the goals, some of the spending may have been pointed at the wrong things before the event team ever touched it.
This is why I don't think the answer to every struggling event is “execute better.”
Sometimes we're solving the WRONG problem.
Before kickoff, can you answer these?
Before the project gets deep into execution, I want a team to be able to answer:
What is this event for?
Who specifically is it for?
Why is this the right format?
How will we know whether it worked?
Where are we choosing to invest the budget, and why?
The answers don't need to fit into one perfect sentence. And there may still be unknowns.
But the team should understand the decisions well enough that they can use them.
Because that's what strategy is supposed to do. It isn't a page at the front of the event brief that everyone reads once.
It should help you decide what to build, what not to build, where to spend, what to measure, and what to do when the plan inevitably changes.
The venue, vendors, registration, production, speakers, sponsors, content, attendee communications, onsite execution, and reporting all come after that.
And they're a whole lot easier to lead when everyone knows what they're building toward.
Frequently Asked Questions
When should these event strategy decisions be made?
As early as possible, and ideally before major commitments limit your options.
The specific timeline depends on the size and complexity of the event. A large annual conference may require decisions far in advance because venue availability, contracting, budgeting, and launch timelines start early. A smaller program may have much more flexibility.
The important part is making these decisions before the team is so far into execution that changing direction becomes unnecessarily expensive or disruptive.
Who should be involved?
The people responsible for the business outcome and the people who understand what it will take to produce the event.
That might include a CMO or VP of Marketing, an event lead, Sales leadership, Customer Success, or other stakeholders depending on the event.
You don't need every stakeholder in every conversation. But you do need enough business context and event expertise in the room to understand the tradeoffs you're making.
What if we've already started planning?
Go back and answer the questions anyway.
You may discover that the existing plan still makes sense. Great. Now you know why.
Or you may find something that needs to change.
The further you are into planning, the fewer options you may have, but that's not a reason to keep building around an assumption you no longer believe.
How is this different from a kickoff meeting?
A kickoff meeting is usually about mobilizing the team around the work: roles, responsibilities, timelines, workstreams, dependencies, and next steps.
The work in this article determines what that team is being mobilized to accomplish.
If these questions haven't been answered before kickoff, make room for them. Don't let the existence of a project plan convince everyone the strategy is already settled.
Planning an event that's getting bigger, more complex, or more important to your business?
I help teams bring structure, strategy, and experienced leadership to conferences and complex events, from figuring out what needs to change through making it happen.
