Online meetings rarely fail because the server is too slow. They fail because we plan for the ideal case and then reality turns up: different devices, poor Wi-Fi, ancient browsers and somebody who decides to install an update five minutes before the meeting.
Technology doesn't need to be clever here. It needs to work boringly well.
The biggest misconception
Many people assume the platform is the deciding factor: OpenSlides, Zoom, BigBlueButton or something else. Often the bottleneck isn't the platform at all.
It starts before that.
Unclear responsibilities, too many functions at once and nobody coordinating the technical side. If voting, presentations and discussion all need to happen simultaneously without a clear process, the organisation can collapse even while the server is perfectly happy.
Reliable online meetings start with planning, not hardware.
Three layers worth separating
Problems often start when everything is supposed to run through one system.
I prefer to think in three layers.
One: Communication. Video and audio need to be stable. They should have a single, clear job.
Two: Agenda and voting. OpenSlides or a similar system handles motions, speaker lists and ballots.
Three: Presentation. Slides and documents should remain usable independently, so one glitch doesn't stop the entire meeting.
An all-in-one platform can work, but it also gives a single fault more opportunity to bring everything to a halt.
Server capacity is rarely the only issue
For a typical club meeting with twenty to fifty participants, the load is often modest. Modern servers usually have no trouble with it.
What can cause real trouble:
- WebSocket connections behind misconfigured reverse proxies
- TLS or proxy settings that cause reconnect loops
- Aggressive power saving on participants' devices
The server may be healthy while users keep dropping offline. From the outside that looks like a server outage.
Often it isn't.
Preparation beats technical cleverness
Even the best setup fails if nobody has tested it.
A short rehearsal does more than another round of tuning:
- Test the login
- Run through one vote
- Open the presentation
- Check the roles and permissions
Ten minutes spent here can save a very long and embarrassing meeting.
What happens during the meeting
Somebody's microphone won't work. Somebody else can't hear. A camera refuses to start. That's normal.
So every online meeting needs someone responsible for technical support and nothing else. Don't ask that person to moderate and troubleshoot at the same time.
Without a clear technical owner, every small problem becomes a debate.
What actually makes it stable
Less complexity.
No unnecessary features. No experiments during the meeting. No updates on the day itself.
The best online meeting is one where nobody talks about the technology.
What I do differently now
Everything should be stable at least a day beforehand. No more changes. A server snapshot before the event. A fallback ready if something fails.
Above all, I've learnt that reliability doesn't necessarily come from adding technology. Often it comes from removing it.
Online meetings are organisational projects with technical constraints. Get the structure right and the technology has a much better chance of staying out of the way.