Everyone in the events industry talks about hybrid events as if the problem has been solved. It hasn't.
In the years since organisations discovered they could broadcast a physical event to a remote audience, two things have happened. First, the tools have got significantly better. Second, the execution has got significantly worse. The gap between what a hybrid event could be and what most hybrid events actually are has never been wider.
I've been in broadcast and live events for twenty years, and the hybrid events I see most often aren't really hybrid at all. They're in-person events with a camera pointed at the stage and a Zoom link in the calendar invitation.
That's not hybrid. It's an in-person event that happens to be streaming - and the remote audience can tell the difference.
The remote audience is not a second-class problem
Here's the belief that kills most hybrid events before they start: the idea that the remote audience is an afterthought, a courtesy, a box to be ticked for the people who couldn't make it on the day.
It isn't. The remote audience is often the majority of your audience. For a national all-hands event, you might have two hundred people in a room and two thousand watching online. For an AGM, the shareholders attending physically might represent a fraction of the register. For a product launch, the journalists and analysts calling in remotely might be exactly the people you most want to impress.
When you treat the remote audience as secondary, you're making a decision about who matters. And your remote audience knows it.
They can tell when the camera is positioned for the room, not for them. They can tell when the audio is mixed for the speakers in the hall, not for the microphones feeding the stream. They can tell when the Q&A moderator ignores the chat window because managing two audiences at once is too complicated. They can tell when nobody has tested the slides on a stream and the resolution has made half the data illegible.
The fundamental mistake in hybrid event production is designing for one audience and tolerating the other.
The technical problems are symptoms, not causes
When a hybrid event goes wrong - and most of them go wrong in some way - the postmortem tends to focus on technical failure. The stream dropped. The audio was terrible. The slides didn't display correctly. The Q&A platform crashed.
These are real problems. But they're symptoms of a deeper failure: the failure to treat the remote broadcast as a separate production that happens to share a venue with a physical event.
A hybrid event is two events in one. The in-room event has its own director - usually whoever is running the meeting. The broadcast event needs its own director too: someone whose sole job is to manage what goes out on the stream, monitor audio levels, handle the platform, respond to technical issues, and make decisions about the remote experience in real time.
In most hybrid events, this person doesn't exist. The AV team is focused on the room. The event manager is focused on the schedule. Nobody is watching what the stream actually looks like to someone sitting at their desk in another city.
The moment something goes wrong - a presenter moves away from the podium, a question comes from the floor without a roving microphone, a slide transition doesn't match what's on screen - there's no one in position to catch it.
This is the single most common failure mode in hybrid events. Not the technology. The absence of someone whose job it is to care about the broadcast.
Internet connectivity is assessed, not assumed
The second most common failure mode is internet connectivity, and it's also the most preventable.
Venue Wi-Fi is a shared resource. On event day, you're competing for bandwidth with every other device in the building - delegates checking emails, staff managing logistics, other events running simultaneously. For a live broadcast requiring sustained, stable upload bandwidth, shared Wi-Fi is fundamentally unsuitable. We've written more about this specific problem and how to solve it.
This needs to be assessed as part of pre-event planning, not discovered on the day. The right answer for your event might be the venue's dedicated business line or a bonded mobile connection - but whichever it is, it needs to be confirmed, tested, and ideally backed up before anyone gets on stage.
The events industry has a tendency to treat internet connectivity as an afterthought because it's invisible until it fails. Experienced broadcast professionals treat it as infrastructure - something you plan around, not something you hope for.
The Q&A problem nobody talks about
Live Q&A is one of the most valuable parts of any event. It's also the element most likely to fail in a hybrid format.
The in-room experience is familiar: a microphone gets passed around, questions are asked, the presenter responds. Simple, effective, human.
The remote experience, left unmanaged, is isolating. Questions go into a chat window. Someone may or may not read them. If they do, they might summarise them inadequately, or skip them entirely when time runs short. The remote audience has no way to tell whether their question was seen, considered, or deliberately ignored.
This isn't a technology problem. It's a facilitation problem. A properly run hybrid Q&A has a dedicated moderator managing the online submissions, filtering and feeding questions to the presenter at the right moment, reading them aloud clearly for both audiences, and acknowledging remote participants as equal contributors to the conversation.
It takes one person, a clear process, and the decision to treat remote questions as real questions rather than optional extras. Most hybrid events never make that decision.
What good looks like
The standard to aim for is simple to describe and genuinely difficult to achieve: a remote attendee should have an experience that is different from the in-room experience, but not inferior to it.
Different because they're watching a curated broadcast rather than sitting in a room. Inferior in none of the ways that matter - audio quality, visual clarity, information content, ability to participate.
Achieving that standard consistently requires:
A separate production mindset. The broadcast is its own event. It has its own director, its own audio mix, its own graphics and lower thirds, its own vision mixer making active decisions about what to show and when.
Genuine pre-event testing. Not a five-minute check on the morning, but a full technical rehearsal with presenters in position, slides running, Q&A platform tested, stream monitored from a remote device by someone asking: would I be happy watching this?
A dedicated remote audience manager. One person whose job on the day is to watch the stream, manage the online chat, feed questions to the moderator, and be the advocate for everyone who isn't in the room.
Honest connectivity planning. Internet access confirmed, tested, and backed up before event day. Never assumed, never hoped for.
The conversation we need to have
The events industry is still having the wrong conversation about hybrid events. The conversation is about platforms and tools and which software has the best breakout room functionality.
The right conversation is about commitment. A hybrid event is a commitment to two audiences simultaneously. It requires the production resource, the planning time, and the deliberate decision-making that commitment demands.
Most hybrid events fail not because they lacked the technology, but because they lacked the commitment. They were in-person events that happened to be streaming, rather than genuine hybrid productions designed for both audiences from the start.
The difference between those two things is everything.