Ask most organizations how they approach an AV project and the conversation starts in the same place: equipment. What displays do we need? What’s the camera situation? What’s the budget?

Those are all reasonable questions. But the organizations that consistently end up with technology that actually works — rooms people want to be in, systems that don’t generate support tickets, spaces that hold up three years after installation — tend to start somewhere else entirely.

They start with people.

The Spec Sheet Doesn’t Know Your Team

When AV systems are designed around technical specifications alone, they’re designed for a hypothetical user. Someone who understands input switching. Someone who knows what the “source” button does. Someone who has time to troubleshoot before a meeting starts.

That person rarely exists in real life.

Real users are the department head who has back-to-back meetings all day. The professor who is managing thirty students while trying to share their screen. The government administrator presenting to a council chamber full of people who are already impatient. These are the people your AV system needs to serve, and their needs look very different from what ends up on a spec sheet.

The best organizations bring those people into the conversation early. Not to make technology decisions, that’s still the job of the integrator and the IT team, but to make sure the design actually reflects how the space will be used by the humans in it.

Technology That Communicates Something

Here’s the part that often gets overlooked: your AV environment sends a message, whether you intend it to or not.

When a new employee walks into a meeting room for the first time and the system is intuitive, well-lit, and easy to use, it communicates that the organization values their time. When a remote participant can see and hear clearly without having to ask three times to be heard, it communicates that they’re a real part of the team.

The inverse is also true. A room with a taped-over button, a camera that cuts off half the table, and audio that drops in and out communicates something too. It says that nobody thought carefully about this experience, or worse, that it was considered and deprioritized.

That’s a hard message to walk back, especially with employees who are already evaluating how much they want to show up.

Where the Best Projects Start

The organizations that get AV right tend to ask a different first question. Not “what do we need to install?” but “what does success look like for the people using this space?”

That question surfaces things a standard needs assessment misses. It turns out the executive team hates the existing room because the camera makes everyone look like they’re testifying before Congress. The faculty have stopped using the lecture capture system because it takes four steps to activate. The hybrid team has started defaulting to everyone joining separately on their laptops, not because the room system is broken, but because it was never designed for the way they actually meet.

These aren’t technology problems. They’re experience problems. And they’re only visible if someone asks.

What Changes When You Design for People First

When organizations shift the framing — from “what technology do we need” to “what experience do we want people to have” — a few things happen.

The design process gets more specific. Instead of a generic conference room, you end up with a space calibrated to the actual meeting patterns, room geometry, and user habits of the team that will live in it. That specificity almost always produces better outcomes than a standard deployment of even premium equipment.

Adoption goes up. Systems that feel intuitive get used. Systems that feel complicated get worked around. The difference between a room that becomes central to how a team operates and one that sits empty most of the week often comes down to whether users feel confident in it on their first try.

And support costs go down. Rooms designed around real use cases generate fewer support tickets, fewer workarounds, and fewer “can someone come look at this?” emails. That’s not a side benefit — it’s a direct return on the investment made in the design phase.

The Ask Is Simple

None of this requires a bigger budget or a longer timeline. It requires one thing: bringing the right people into the conversation before decisions get made.

Before the next AV project kicks off, talk to the people who will use the space every day. Find out what frustrates them about the current setup. Ask what a perfect meeting looks like from their seat. Then bring that to the design conversation.

That’s it. That’s the move that separates organizations with AV environments people appreciate from the ones with expensive equipment nobody quite trusts.