How to Push Back on an Event Brief: Whether You're Two Days or Six Months Out

There's a skill nobody teaches you in this industry, and I wish someone had taught it to me early: how to push back when you know, in your gut, that a decision is going to hurt the event.

If you've been planning for more than three years, you know exactly what I'm talking about. Someone throws out an idea in a meeting. Or a client makes a call a week out. And something in you tightens. You know it's wrong. But you can't always say why fast enough, or with enough confidence, to stop it before it becomes real.

I've been there more than three times in very different ways but wanted to share some of the cringe moments. Here's what each one taught me, and the framework that finally gave me the words.

Scenario One: The Performer Who Killed the Room

I was hired to plan an inaugural nonprofit fundraiser. Like I always do, I started with a purpose statement and mapped the emotional arc of the night: entrance, peak moment, closing gift, designing each beat to move the room from belonging to community to joy, because that's the environment where people actually open their wallets.

One week out, my client added a performer. Wrong fit for the audience, wrong slot in the program, right after the speech and the check presentation, the exact moment we needed the room's energy to carry straight into the next ask.

I didn't push back. I was exhausted, and it felt easier to let it go.

The performance was bad enough that people didn't just lose interest. They turned around and walked away before it ended. The momentum we'd built toward more giving was gone.

I should have used my voice. I had the arc mapped. I knew exactly where that slot sat in the emotional journey. I just didn't say it out loud.

Scenario Two: The Mechanical Bull in the Corner

This one was a longtime corporate client, the request was western-themed milestone event, and the classic too-many-cooks situation. Three people were involved in planning, only one of them actually owned the budget, and ideas were flying with no filter. That's how we ended up staring at "let's throw a mechanical bull in the corner."

I didn't have a clear framework to hold the line yet, so it went in.

Here's the lesson: clients want fun, engaging moments. That instinct isn't the problem. The problem is dropping an activation into the room just because it sounds fun, with nothing tying it back to the goal. That's how you end up with a janky event, a bunch of disconnected "cool ideas" instead of one experience that's actually building toward something.

Once you have a clear purpose and a mapped guest journey, you get to say: "No, and here's why. Because that doesn't move us toward this outcome." That's not you being difficult. That's you doing your job.

Scenario Three: The Vodka Luge That Actually Worked

Not every unconventional idea is a bad one, and this is the case that proves it. A big-budget holiday client requested a vodka luge midway through planning. Every instinct says that sounds dangerous. But it fit the theme, and it fit the goals.

So we designed it as an actual experience instead of a stunt. Guests chose from a few signature cocktails, grabbed their glass, and watched the bartender mix their drink right at the luge, the branded ice glowing in front of them the whole time the drink traveled down and into their glass. People weren't just walking up and taking a shot. They were standing there, having a moment, before the drink even arrived.

That's the difference between "can we throw in another element" as a tactic, and "can we throw in another element" as something tied to an outcome.

The Real Skill Isn't Saying No, It's Knowing Why

All three of these come back to the same thing: Purpose → Behavior → Emotion → Activation → Outcome. When you can map that chain before the brief ever lands, you're not reacting off a gut feeling anymore. You're pointing to exactly which link a bad idea breaks.

That's the shift from running the show to designing why it works. The planner absorbs the request and finds a way to make it happen. The strategist asks what the request is actually trying to accomplish, and if the ask won't get the client there, says so, and offers what will.

Next time someone hands you a tactic instead of a goal, a performer, a bull, a luge, whatever it is, don't just execute it. Translate it into an outcome first. Then decide if it belongs.

If you're ready to build that framework for yourself instead of relying on gut instinct alone, enroll now.