Meeting rooms and video conferencing

Neat’s 2026 round-up puts the delays down to rooms that are each set up differently, multiple remotes, complex AV systems, confusing interfaces and devices that are never updated. The problem is rarely one broken device; it is that every room behaves its own way.

The numbers bear it out. In Owl Labs’ 2025 US research, employees report losing more than six minutes getting a hybrid meeting started, and 27% lose more than ten minutes per meeting. Jabra’s June 2026 research found a technical fault in three quarters of meetings, costing roughly 11 minutes each.

Both are manufacturer studies on international samples (Jabra: 7 countries, more than 2,300 knowledge workers). They are useful for the order of magnitude rather than as precise figures, and neither covers Turkey specifically.

Two things work in practice: standardise the rooms — same hardware, same interface, same way to start a call — and do not treat that as a one-off. A meeting room that worked perfectly on handover can become the room nobody can start six months later.

The best-known cause is simple: more than one device in the room has joined with audio. If the room system is already running and someone’s laptop joins with its own microphone and speaker, the sound laps the room. The fix is to leave one audio source in the room.

The second cause is the microphone picking up the loudspeaker. In a room system an acoustic echo canceller (AEC) removes that, but for the AEC to work the far-end audio sent to the loudspeaker has to reach the AEC reference at the same level. Wire that reference wrongly and the AEC is quietly doing nothing.

Biamp lists loudspeakers set too loud, excessive microphone gain and overly reverberant (“live”) rooms among the causes of residual echo — so part of it is configuration and part of it is acoustics.

In Owl Labs’ 2026 UK research, 69% of employees name echo or distorted audio among their biggest problems. It is a complaint that stays near the top of the list.

When microphones sit far from the talkers or are placed by habit, background noise and the room’s acoustics mask the speech. What the microphone “hears” from a distant person is their voice mixed with the room; the further away they are, the worse that mix gets for them.

AVIXA’s round-up of recurring site mistakes recommends placing loudspeakers and microphones according to room size, seating layout, coverage calculations and the microphone’s polar pattern — not in default positions. A ceiling microphone and a table microphone do not cover the same area, and neither follows a “one per room” rule.

In practice this means the length of the table and the number of microphones are one decision. Putting a single microphone on a table for twelve writes off the two people at the far end before the first meeting.

When camera position, table layout and seating are each decided separately, the result is almost always the same: the table ends up too far from the camera, or one side falls outside the frame.

AVIXA’s guidance for Teams rooms is to mount the camera so it covers the room completely and to verify the angles during commissioning. That second step is the one that gets skipped: a mounting height that looks right on the drawing can be wrong once the chairs are in.

Past a certain room depth, one wide angle stops being enough. At that point the conversation has to be about moving the camera or changing the table layout — without one of those, the framing does not improve.

This is the most maddening kind of silent failure: the USB peripherals work, so the cable and the port look fine, but there is no picture and usually no error message at all.

The reason is that carrying video over USB-C requires DisplayPort Alt Mode, and that support is optional. Manufacturers rarely label it on the port, so of two ports that look identical one carries video and the other does not.

Thunderbolt is clearer: a Thunderbolt 3 port must provide at least one DisplayPort interface, and Thunderbolt 4 certification requires support for two 4K displays or one at 8K.

In a BYOD room there is only one practical answer: test with the laptop models people actually bring during commissioning, and leave a one-page note in the room saying which port to use. Expecting users to read port specifications does not work.

Microsoft’s Teams Rooms guidance strongly recommends connecting room devices to a wired network, and says plainly that wireless is exposed to interference and can degrade quality. The recommended capacity is 10 Mbps up and down per room.

Where Wi-Fi is unavoidable, it asks for 5 GHz preference, band steering, and channel utilisation kept below 50%.

For traffic prioritisation (QoS), the recommended DSCP values are:

Traffic	DSCP
Audio	46 (EF)
Video	34 (AF41)
Screen sharing	18 (AF21)

That table is the concrete output of the conversation with the IT team. “The internet is fast, it can’t be the network” is misleading here: freezing is usually not a bandwidth shortage but the absence of any prioritisation at all.

Microsoft’s certification page is explicit about what is tested: on video, noise, colour, detail, jitter, latency, frame rate and field of view; on audio, wideband sound free of echo and distortion, plus noise suppression. There is third-party testing and a three-stage internal process.

What the page does not cover is room acoustics, room design or network testing. Certification describes the device; it says nothing about the room you put it in.

So a certified bar still sounds reverberant in a reverberant hall, and a certified microphone still hears the person at the end of the table from a distance. Choosing the device is part of the job, not all of it — the room’s acoustics, the microphone coverage plan and the network configuration are each separate problems.

AVIXA reports two consequences of complex control interfaces: frequent support calls, and systems that go unused. The worst end for an expensive system is that nobody dares touch it.

Owl Labs’ 2025 US data puts a number on it: 67% of employees have tried to set up video technology for a meeting, given up, and gone back to their laptop.

AVIXA’s advice comes down to three things: simplify the interface around the actions people actually perform, label everything clearly, and provide basic user training. In practice that means three buttons on the panel instead of sixteen — “Present”, “Join meeting”, “Shut down”.

A one-page guide left in the room helps more than you would expect, particularly for the people who use that room once a week.