Home
About
Insights
Contact
Field Notes — 10

When It Goes Wrong

Things will go wrong. Not always, and not catastrophically, but there will be moments at every large event where something that was planned doesn't work as planned. A supplier doesn't show. A system goes down. The weather turns in a way that changes the operation completely. The act runs over and the catering schedule is now thirty minutes adrift.

The quality of a VIP operation is not measured by whether problems occur. It's measured by how they're managed.

The first thing that needs to be understood is that most problems are smaller than they feel in the moment. When you're in the middle of a situation — a queue backing up, a VIP guest being difficult, a wristband system that's stopped working — the pressure of the environment makes it feel larger and more urgent than it often is. The ability to take a breath, assess what's actually at stake, and respond proportionately is one of the most undervalued skills in live events work.

The second thing is that recovery is possible in more situations than people think, provided it starts quickly and quietly. A guest who has a bad experience in the first ten minutes can still have a good overall experience if someone intervenes properly within the next fifteen. A bar that runs out of a specific product isn't a disaster if a team member acknowledges it to affected guests and offers an alternative before they've had time to be annoyed about it. The window for recovery is almost always there — it just closes faster than you'd like.

What closes it permanently is defensiveness. An operation that responds to a problem by explaining why it happened, or by minimising it, or by making the guest feel that their concern is unwelcome, has lost the ability to recover. The posture that keeps the window open is acknowledgement and action — something went wrong, here's what we're doing about it, here's what we can offer.

The debrief after the event matters too. Not a blame exercise, but an honest account of what went wrong and why. Written down, not just discussed. The events that improve over multiple iterations are the ones where problems are captured properly and feed into the next plan.

The job is never perfect. But it can get better.

← Talking to Production and Security All insights