Why 'We'll Figure It Out on Site' Always Fails

There’s a phrase I hear in event production that always signals trouble ahead: “We’ll figure it out on site.”

It sounds like flexibility. Adaptability. A team that can handle whatever comes.

What it actually means is: we haven’t done the thinking yet, and we’re betting that pressure and exhaustion will produce better decisions than preparation would have.

That bet almost never pays off.

The Appeal of On-Site Problem Solving

I understand why teams default to this approach.

Planning is slow. Questions feel endless. The venue hasn’t sent final measurements. The client keeps changing requirements. The rental company can’t confirm availability until the week before.

At some point, it seems easier to just show up and deal with reality. You’ll have the actual space, the actual equipment, the actual constraints. Surely that’s better than planning around incomplete information.

Except the site comes with something else: the clock.

What Pressure Does to Decisions

On-site, time compresses. Doors open at a specific hour. The program starts at a specific minute. There’s no “let’s table this and revisit tomorrow.”

Under time pressure, decisions get made fast. But fast isn’t the same as good.

You optimize for speed, not quality. The first solution that works becomes the solution. Not the best solution — the fastest one to implement. You don’t have time to explore alternatives.

You lose context. The person making the decision on site may not know the full picture. Why did we want the stage positioned this way? What was the original concern about sight lines? The reasoning lived in a planning session two weeks ago, and it didn’t make it to the venue.

You can’t undo easily. Moving a stage once it’s set is hours of work. Rerouting cables after they’re run is expensive. Decisions made on site tend to be sticky, even when they’re wrong.

Fatigue accumulates. Event days are long. The same person who made a sharp decision at hour two is making decisions at hour twelve. Judgment degrades. Patience disappears. The quality of problem-solving drops.

The Hidden Cost

The immediate cost of on-site problem-solving is time. Decisions that could have been made in a conference room, with coffee and a whiteboard, now get made in a loading dock while the caterer waits.

But there are deeper costs.

Budget. Improvised solutions are usually more expensive. You need expedited rentals. You need more labor hours. You pay rush charges because you’re solving problems that should have been solved weeks ago.

Relationships. Vendors and crew get frustrated when they’re asked to adapt on the fly. The lighting designer who was told one thing in pre-production and another thing on site will charge more next time — or not work with you again.

Quality. The final product suffers. Not catastrophically, usually. Just… less good than it could have been. The stage placement that was figured out on site is functional but not optimal. The flow could have been better. The details weren’t refined.

People. Teams burn out faster when every event is a crisis. The best crew members avoid jobs where they know they’ll spend all day improvising. Over time, you lose access to talent because your reputation is chaos.

What “Figure It Out” Actually Means

When someone says “we’ll figure it out on site,” they’re often saying one of these things:

“I don’t want to have this conversation right now.” The decision requires thought, and thought requires time. Deferring feels easier.

“I don’t have the information I need.” Which is sometimes true — but often, the information could be obtained with a phone call or a site visit.

“I’m confident in our ability to improvise.” Which might be warranted for small adjustments. But systems-level decisions made under pressure are reliably worse than systems-level decisions made in advance.

“I’ve done this before.” Experience matters. But past success with improvisation often means you got lucky, not that the approach is sound.

The Line Between Flexibility and Negligence

Some amount of on-site adaptation is inevitable. The venue layout isn’t exactly like the drawings. The client makes a last-minute request. Something arrives damaged and needs replacement.

Good teams handle these surprises well. That’s different from planning to be surprised.

The line is whether you’re adapting within a framework or creating the framework on the fly.

If the stage position, power distribution, signal flow, and crew responsibilities are determined in advance, adapting when the venue door is narrower than expected is manageable. If none of that is settled and you’re making all those decisions while simultaneously dealing with the narrow door, you’re in chaos.

Flexibility means having enough slack in the system to absorb variance. “Figure it out on site” means having no system at all.

What Should Happen Instead

The site visit happens weeks before, not days. Measurements are confirmed. Photos are taken. Questions are asked.

Critical decisions are made in meetings, documented, and communicated. Stage position. Power requirements. Load-in schedule. Who owns what.

The advance includes specific scenarios. What if it rains? What if the keynote runs long? What if the projector fails? Not every scenario — the likely ones.

The site becomes a place for execution. The design work is done. The decisions are made. The team arrives knowing what they’re building, not figuring out what to build.

The Boring Truth

Events that run smoothly are boring to execute. The excitement happens in pre-production — the site visits, the planning sessions, the endless questions that feel tedious.

On event day, a well-planned show is mostly waiting. Waiting for the next cue. Waiting for the next transition. Making minor adjustments to a plan that already works.

The teams that “figure it out on site” look busy. Heroic, even. Running around solving problems, making quick decisions, pulling it together at the last minute.

But busyness isn’t quality. Heroics are a sign that something went wrong upstream. The goal isn’t to be good at improvising. The goal is to minimize how much improvising you need to do.

Figure it out before you arrive. The site is for execution, not design.

---

Related

• Article: What Live Events Teach You About Systems — The systems that survive pressure, fatigue, and imperfect people are worth studying.
• Deep Dive: Building Systems Inside Seasonal Chaos — How to create operational stability when your business has inherent unpredictability.