I've watched people spend a week comparing processor speeds, camera specs, and battery benchmarks before buying a new laptop or phone, cross-referencing review sites, reading spec sheets line by line, agonizing over a decision that will mostly get used for email, messages, and the odd video call.
Technology in physical spaces gets the opposite treatment, with far higher stakes attached.
That mismatch, obsessing over consumer purchases while rushing through decisions that shape how hundreds of people work every day, is basically the reason AVYA exists.
Over eighteen years in technology, the last fifteen of them focused specifically on AV and workplace systems across the GCC, I watched that gap play out again and again, on projects big and small, across industries that had almost nothing else in common. Different clients, different budgets, different ambitions. But the same thing kept happening: the technology conversation started too late, and by the time it did, most of the interesting decisions had already been made without it.
Technology Outgrew IT a While Ago
Not long ago, technology decisions sat almost entirely with IT teams, focused on infrastructure and uptime. That made sense at the time. It doesn't anymore.
Technology today shapes things that used to sit outside its lane entirely:
How people actually collaborate in a room, not just whether the screen turns on
How a visitor experiences a building the moment they walk in
How a company's culture shows up in its physical space
A meeting room isn't just a room with a screen bolted to the wall anymore. A workplace isn't just a floor plan with desks on it. Technology has become part of the experience itself, which means it needs a seat at the table far earlier than it usually gets one.
Early Beats Clever, Every Time
If there's one belief that pushed me to eventually start something of my own, it's this: technology should never be the last decision made on a project, and yet it almost always is.
By the time most teams bring technology into the conversation, the architecture is locked, the interiors are chosen, and the budget has already been spent elsewhere. Every decision from that point on becomes a workaround. Rooms get retrofitted. Cabling gets routed around finished walls. Costs creep up, not because the technology was wrong, but because it showed up too late to matter.
The projects I'm proudest of all shared one thing: technology planning started at the same table as workplace planning, not after it.
Nobody Builds a Good Workplace Alone
The other thing eighteen years in this industry taught me is that the best outcomes never come from one discipline working in isolation. They come from architects, designers, business leaders, and technology advisors actually talking to each other before anything gets specified.
That only works if the requirements get scoped independently first, before any vendor is in the room. Once a brand or a product enters the conversation too early, everything downstream tends to bend around that choice instead of around the actual need.
That's the gap AVYA was built to close:
Scope the problem on its own terms, with no product already picked
Bring vendors in afterward, to compete against the requirement rather than shape it
Stay unattached to any single manufacturer, so the advice has nothing riding on which brand wins
Start With the Problem, Not the Product Name
A mistake I saw constantly, and one I was determined not to repeat, is starting the conversation with a brand name instead of a business question. Teams would ask which system to install before anyone had asked what the space actually needed to achieve.
Flip that order, and everything changes. Room layouts shift. Infrastructure choices shift. The entire logic of a project shifts, simply because the first question was about outcomes instead of equipment.
Build for Change, Not for Perfect
Workplaces don't sit still. A few things that keep moving no matter how good the original plan was:
Hybrid schedules and shifting expectations around how teams use space
Technology that meaningfully improves every year or two
Business needs that look different in year three than they did on day one
I stopped chasing the "perfect" system a long time ago, because perfect has a shelf life. What actually matters is building something that can be upgraded or reconfigured without tearing the whole thing out later.
People, Still First
For everything technology in physical spaces has become, the core lesson hasn't moved an inch: it exists to serve people, not the other way around. The best systems are invisible. People stop noticing they're using technology at all, and just get on with the conversation.
Why AVYA Came to Being
After eighteen years watching this same pattern repeat across the region, starting AVYA felt less like a leap and more like the obvious next step. I wanted to build the kind of independent, product-agnostic voice I kept wishing every project had from day one, the one that asks what a business actually needs before anyone starts talking about brands.
That's the lesson that's followed me for eighteen years, and it's the one AVYA is built around: technology alone never made a great workplace. Thoughtful planning, honest collaboration, and a real understanding of people did that. Everything else is just equipment.
