Why Your Meeting Room Technology Is Already Failing — And It Started at the Design Stage

Part of the DITAM Framework Series  |  Chris Gore

Most meeting room technology doesn't fail because of the hardware. It fails because of the decisions made before anyone even placed an order.

That's the uncomfortable truth we see play out across organisations every single week and it's almost always avoidable.

What This Blog Is About

At SPOR Group, we manage over 1,500 meeting rooms across the UK, Europe, and the Asia. We've built a framework called DITAM:

Design, Integrate, Training, Asset Management, and Monitoring, to help organisations get their AV estates right for the long term.

We covered the full framework in our core guide found here. This blog goes deeper on the first element:

Design.

Design is where the quality of your long-term outcome is largely determined. It's also the stage that gets rushed, skimped on, or skipped entirely more than any other, usually in the name of saving time or cutting costs upfront. By the time the consequences show up, the bill is considerably higher.

The Problem: Design Gets Treated as a Shopping List

Here's a story we've lived through more times than we can count.

A company is moving into a new office. Twelve meeting rooms, two floors, a genuinely impressive space. Leadership is proud of it. The AV budget is healthy. They bring in a supplier, the install goes well, handover day is clean. The demo works perfectly.

Everyone nods. Sign off.

Now fast forward six months.

Room 7 has an audio issue nobody's officially reported, because people have stopped booking it and moved on. The camera in the boardroom, the one specified for a four-person huddle is cutting off half the room every time someone sits at the far end. Two of the Zoom Rooms haven't had a firmware update since installation and are starting to throw compatibility warnings. Three rooms are being actively avoided because people simply don't feel confident the technology will behave.

The organisation paid for twelve rooms. It's reliably getting the benefit of maybe eight.

The install cost around £180,000. The cost of that degraded performance over twelve months, in wasted time, IT support tickets, and lost confidence, is conservatively higher than the install itself.

That pattern plays out across almost every AV estate we've ever audited. The good news: all of it is preventable. Here's what it looks like when you map it over time.

Fig. 1 — Meeting room utilisation over 18 months: with vs. without a design framework

The Catalogue Mistake

Think of it like this. Imagine you asked an architect to design your office by handing them a catalogue and saying, "Pick something that looks good." No brief. No understanding of how many people would use each space, what they'd need to do there, or what the acoustics were like.

Just: pick something.

You'd think that was absurd. But that's more or less how a huge number of AV projects get designed.

A supplier gets called in. There's a quick site visit. Someone asks roughly how many people use each room. A spec gets put together based on what's in the supplier's preferred range at that price point. Job done.

The technology gets installed. It works on the day. And then the slow, quiet unravelling begins.

Fig. 2 — The Catalogue Approach vs. the Design-Led Approach: same starting point, very different outcomes

What Bad Design Actually Costs You

Research from Poly found that employees waste an average of 15 minutes per meeting dealing with technology issues. Across an organisation running 50 meetings a day, that's 750 minutes of productive time gone every single day. At average UK professional salary levels, that's somewhere between £30,000 and £50,000 a year — every year — in friction that shouldn't exist.

And that's just the measurable friction. It doesn't account for the client who loses confidence because your screen wouldn't connect during their pitch review. Or the senior leader who quietly writes off the technology and reverts to their laptop. Or the IT team spending hours every month on support tickets for problems that were baked in from day one.

The decision about how you design your meeting room technology is not a technical decision. It's a financial one. And the bill for getting it wrong keeps arriving long after the installation is done.

Fig. 3 — The business case for getting AV design right from the start

The Solution: What Good Design Actually Looks Like

Good AV design starts with questions, not products. Before anyone decides what goes in a room, they need to understand what that room is actually for. There are five principles that separate a design-led approach from a catalogue approach.

Fig. 4 — The 5 principles of good AV design within the DITAM framework

1. Understand the Use Case Before Choosing Technology

How many people typically use this space? What's the likely split between people in the room and people dialling in remotely? Is this a presentation space, a collaborative working room, a quick huddle area, or a high-stakes board environment? What are the acoustics like? What are the sight lines from every seat?

These aren't optional questions. The answers directly determine the right technology specification — and getting the spec wrong is expensive to undo.

A wide-angle camera designed for a four-person huddle doesn't just look wrong in a thirty-seat boardroom — it creates a bad experience for every remote participant in every single meeting that room hosts, for the life of the technology. That's a long time to live with a fixable mistake.

2. Standardise Across Room Types — It Changes Everything That Comes Next

One of the highest-leverage decisions in AV design is standardisation. When every medium-sized meeting room in your estate has the same core components and the same interface, your people can walk into any of them and know how it works. Your IT team supports them all with the same knowledge base. Your refresh cycle becomes predictable rather than chaotic.

Industry research consistently shows that standardised AV estates cost between 20 and 35 percent less to support than mixed estates. Across a large estate, that is a serious number.

Standardisation also dramatically improves user confidence. When your people know that every room works the same way, they stop second-guessing and start actually using the technology — which is the whole point.

3. Future-Proof Without Over-Engineering

Good design doesn't try to predict the future. What it does is make decisions now that don't lock you in unnecessarily.

That means favouring open platforms over proprietary ones where you have a choice. It means building infrastructure that gives you flexibility for the next refresh, not just this one. It means choosing vendors based on their development roadmaps and long-term support commitments — not just what's cheapest this quarter.

The organisations that get this right are the ones who, when the next generation of video conferencing technology arrives, can adapt without ripping everything out and starting again.

4. Think About Your Estate, Not Just Individual Rooms

This is where most design processes stop short. They design individual rooms in isolation rather than thinking about the estate as a whole.

Every decision you make in design has downstream consequences for integration, training, asset management, and monitoring — the other four elements of DITAM. A poorly designed estate is harder to integrate, harder to train people on, harder to manage, and harder to monitor. The problems compound at every stage.

Good design thinks about what this estate needs to look like in five years, how IT will support it day to day, and what a refresh cycle will look like when the time comes. Those aren't afterthoughts. They're part of the design conversation.

5. Document Everything — Properly

A design that exists only in the installer's head isn't a design. It's a liability.

Good AV design produces documentation that genuinely describes what's in each room, why it was specified that way, what firmware version was installed, and what the intended configuration is. Not a sign-off sheet. Not a quote. Actual, useful documentation that your IT team can work from six months down the line.

This documentation becomes the foundation for everything in DITAM that follows. Without it, you're starting from scratch every time something needs fixing or upgrading.

If You're Designing Meeting Rooms Right Now, We Built Something For You

If you're in the planning phase of a move, a refurbishment, or a significant AV upgrade, the design stage is your highest-leverage point. Decisions made now will shape the performance of your meeting rooms for the next five to ten years.

Getting it right doesn't require a massive budget — it requires the right process. That's why we put together our AV Bundle. It gives you everything you need to design your meeting room technology properly from the start:

•  Room configuration templates built around real-world use cases, not guesswork

•  A budget calculator that maps technology to room type

•  A risk mapping tool covering the most common specification mistakes

•  Design guidance built directly around the DITAM framework

It's the fastest way to get your thinking properly organised before supplier conversations start and commitments get made.

Access the AV Bundle at spor-group.net/avbundle.

If you'd rather talk it through first, get in touch. We're happy to do a no-obligation design review and give you an honest read on where your current plans are strong and where the risks are.

What's Next in the DITAM Series

Design is the foundation. Get it right and everything else in DITAM is working with the grain. Get it wrong and everything else is working against it.

In the next blog in this series, we'll go deep on the I in DITAM:

Integration.

We'll cover what proper integration actually involves, why it's invisible when it's done well and painful when it isn't, and what the most common failure points look like in practice.

In the meantime, if you haven't read the full DITAM guide, you can find it here:

How to Design and Deploy Meeting Room Technology Solutions That Actually Work for the Long Term.