Hybrid Communications: Why Large Enterprises Need an Architecture, Not a Platform

By Steve Leaden, President, Leaden Associates, Inc. Independent ethics-based IT Communications ConsultantsShare

Enterprise communications have always evolved by solving one problem while, without realizing, creating another.

The telephone replaced the telegraph by adding speed. The PBX brought control to enterprise voice. VoIP converged voice and data networks. Unified Communications integrated messaging, conferencing, and presence. Cloud communications extended these capabilities beyond the enterprise perimeter.

Each wave represented meaningful progress. Yet each carried the same underlying assumption: that the next answer would still be a platform—a single deployment model that organizations could standardize on and extend everywhere.

That assumption no longer works. The next era of enterprise communications is not defined by a better platform. It is defined by architecture. The question has shifted from:

"Which platform should we standardize on?"

to:

"Which deployment model best fits each workload?"

For large enterprises, the answer is increasingly hybrid.

Why "Just Pick One" No Longer Works

Cloud communications have become a permanent fixture of enterprise IT. Public cloud services continue to grow rapidly, and few would argue that cloud is anything other than a critical component of modern communications strategies.

But a cloud-only model is not the sole solution available.

The widespread adoption of collaboration platforms illustrates this point. Microsoft Teams has become one of the most successful enterprise applications in history, yet only a fraction of Teams users rely on it as their complete PSTN voice solution. Collaboration decisions and voice architecture decisions are often separate choices made for different reasons.

At the same time, downtime has become increasingly expensive. Large enterprises can lose substantially from a major outage, on multiple levels, including:

Significant loss of money, time, and talent
Inability to deliver on critical services
Most importantly, irreparable damage and loss resulting in possible litigation as a result of being unavailable due to an outage.

Clinical systems, emergency operations centers, trading floors, and other mission-critical environments cannot afford single points of failure.

These realities highlight a fundamental truth, that cloud is the right answer for many workloads, but is not the right answer for all of them.

Large enterprises are not rigid, massive and unchanging organizations. They are networks of unequal sites—headquarters, regional campuses, branch offices, clinics, manufacturing facilities, remote workers, and customer engagement centers. Each has unique requirements for reliability, security, compliance, scalability, and user experience. The needs of the market are also evolving with customer experience (CX) and AI taking center stage.

Yet modernization discussions often continue to frame the decision as "move to the cloud" or "stay on-premises."

The reality is far more nuanced.

The Three-Sector Hybrid Model

A mature hybrid communications strategy consists of three distinct components, each designed around the needs of a different population.

Sector One: Premises UC for Mission-Critical Core Sites

Certain environments continue to demand the strengths of premises-based Unified Communications.

These include. Among others:

Corporate headquarters
Healthcare campuses
Emergency operations centers
Manufacturing command centers
Trading floors and other critical financial services groups
Public safety agencies

In these environments, reliability and control are paramount.

Calls remain within private enterprise networks rather than traversing the public internet. Organizations maintain control over latency, jitter, and packet loss. Call quality is determined by the enterprise's LAN and WAN design rather than external conditions beyond its control. A five 9s reliability model is critical in these kinds of environments.

Regulatory requirements also influence architecture decisions.

Healthcare organizations operating under HIPAA, government agencies subject to FedRAMP requirements, and financial institutions governed by SOX and PCI regulations frequently require clearly defined operational boundaries and tighter control over communications data.

While cloud providers have made tremendous progress in compliance certifications, provider compliance alone does not always satisfy organizational risk tolerance or audit expectations.

Feature depth matters as well. Many enterprises continue to rely on capabilities such as:

Shared line appearances
Supervisory barge and monitor functions
Survivable remote sites
Legacy analog integrations
CTI integrations with established business applications

For large, mission-critical environments, premises infrastructure continues to provide meaningful operational advantages.

Sector Two: Cloud UC for Distributed Sites

At the branch level, the equation changes.

A clinic with 25 employees, a small satellite office, or a remote workforce does not necessarily require the same level of infrastructure investment as a major campus.

Cloud Unified Communications excels in these environments.

Organizations gain:

Minimal local infrastructure requirements
Centralized administration
Faster deployments
Elastic licensing models
Lower operational overhead

Rather than maintaining servers and telecommunications equipment at every location, endpoints register directly to cloud platforms while administration occurs centrally.

This flexibility is particularly valuable for organizations experiencing growth, acquisitions, seasonal fluctuations, or changing real estate strategies.

Network resiliency has also evolved. SD-WAN solutions can intelligently route communications traffic across multiple connectivity options—including private circuits, broadband, cable, and 5G—to optimize call quality and maintain service continuity.

Analog gateways can address remaining legacy requirements such as fax services and specialty devices.

For organizations operating under stricter regulatory requirements, private cloud deployments offer an additional option. Healthcare providers, government agencies, and research institutions can achieve many of the benefits of cloud administration and elasticity while maintaining greater control over data and network boundaries.

Hybrid accommodates all of these scenarios.

Sector Three: CCaaS as an Independent Service Layer

The contact center deserves its own architectural category.

Customer engagement environments have fundamentally different requirements than employee communications systems.

Modern contact centers must support:

Voice and digital channels
Omnichannel routing
Interactive Voice Response (IVR)
Workforce management
Quality assurance
AI-powered self-service
Agent assistance
Real-time analytics
Reporting and optimization

Demand patterns differ as well.

Patient access centers may experience sudden surges during public health events. Municipal service centers can see volumes spike after severe weather incidents. Universities experience enrollment peaks. Retail organizations prepare for holiday traffic levels that dwarf normal operations.

Traditional PBXs were never designed for this kind of elasticity, while modern CCaaS platforms are.

Equally important is resiliency. Well-architected CCaaS environments maintain independent PSTN connectivity, geographic failover capabilities, and carrier redundancy separate from enterprise telephony systems.

This separation is an architectural strength. It ensures customer-facing operations remain available even when disruptions affect other portions of the communications environment.

For organizations where contact center performance directly influences revenue, patient access, citizen services, or student support, this independence is not simply beneficial—it is essential. In these critical environments, reliability, redundancy, and resiliency still need to be addressed. Premises contact centers, while still a viable option, require a virtual server for each individual application.

Why Simplicity Can Be Misleading

The strongest argument against hybrid is administrative simplicity, one vendor, one platform, one support relationship.

For smaller organizations with limited complexity, this approach can make sense.
For large enterprises, however, simplicity on paper often translates into compromise in practice.

Consider a 10,000-user organization operating across dozens of sites. Clinical campuses may require advanced telephony capabilities and strict compliance controls. Administrative offices may center their work around collaboration platforms such as Microsoft Teams. Remote employees expect mobility and consistent user experiences. Contact centers require omnichannel engagement, AI capabilities, and integration with systems such as Epic, Salesforce, or ServiceNow.

No single platform excels equally across all of these requirements.

Organizations that force a single standard many times discover they are sacrificing functionality in some areas while overdesigning others. In many cases, they end up spending additional money for capabilities that already existed in the environments that were replaced. The result is often greater complexity—not less.

Hybrid acknowledges organizational reality rather than forcing reality to conform to technology limitations.

The Future Is Architectural

Enterprise communications have entered a new phase.

The next strategic decision is not identifying a single winning platform. It is designing an architecture that aligns technology with business requirements.

Premises solutions continue to deliver exceptional value where reliability, control, compliance, and feature depth are essential.
Cloud platforms provide agility, speed, and operational efficiency for distributed populations.
CCaaS platforms offer the elasticity and innovation necessary to meet rising customer expectations.

Hybrid brings these strengths together. It recognizes that different users have different needs and that the best outcomes occur when organizations match platforms to populations rather than forcing populations onto platforms.

One closing note, there is a growing movement termed “cloud repatriation”, where public cloud providers’ platforms are being reconsidered for premises or private-only cloud solutions. As a part of your hybrid strategy, it is worthwhile to take a look further into this movement and if it may have an impact on your organization’s strategy.

The future of enterprise communications is not all cloud or all premises. It needs to be intentional and engineered for that environment.

For large enterprises, it reflects an increasingly obvious reality: Hybrid is not a temporary transition strategy, it is actually the destination.

Author Bio

Steve Leaden is Founder and President of Leaden Associates, Inc., an ethics-based independent communications and IT advisory firm with more than 30 years of experience helping organizations navigate complex technology decisions and large-scale transformation initiatives. A recognized expert in customer experience (CX), contact centers, Agentic AI, Unified Communications, and cloud technologies, Steve and his team advise executive teams across healthcare, education, manufacturing, financial services, publishing, and government. Known for his vendor-neutral approach, he helps enterprises align technology strategies with business objectives, reduce risk, improve operational performance, and deliver measurable business outcomes.

Reimagine Collaboration and Communications with Enterprise Connect

All In on What’s Next

For over 35 years, Enterprise Connect has been the premier event where IT leaders, solution providers, and industry analysts come together to define the future of enterprise communications. As the most trusted conference in the industry, we deliver cutting-edge insights, world-class networking opportunities, and hands-on solutions that drive real business success.

Enterprise Connect is more than an event—it’s an experience that empowers enterprise communications leaders to reimagine the future of work. With elevated content, curated networking, and an engaging atmosphere, it remains the must-attend conference for professionals shaping the industry’s evolution.

Our mission is to equip you with the tools, strategies, and actionable insights needed to address your organization’s unique challenges. With industry transformation in mind, this year’s program introduces fresh new conference tracks, including:

Legacy Unleashed: Optimizing Your Communications Backbone
Workplace Reimagined: Engineering Tomorrow's Collaboration
Tech Disruption Zone: Implementing Without Imploding
Achieving Transformation: Architecting Your 3-5 Year Roadmap
Future Shock: Communications Tech Beyond the Horizon

Featuring the most comprehensive program of objective content and an expansive vendor-neutral expo hall, Enterprise Connect is your ultimate resource for advancing collaboration, CX, and AV strategies. Join us to stay ahead, connect with industry trailblazers, and lead the transformation of enterprise communications.

Subscribe Today

Can We Really Reduce "Work About the Work?

How To Get Your AI Project to Deliver Measurable ROI

Bridging the Gap: 5 Tips for Cross-Functional Collaboration That Enables AI Transformation

Ask ten executives who owns AI at their company, and you’ll get ten different answers. IT says it’s not their call. Legal gets blamed for slowing everything down. HR figures it’s someone else’s department. Meanwhile, teams are buying tools nobody signed off on, duplicating work and hoping it all sorts itself out. Sound familiar?

Lisa Duerre spent the last year studying why that happens. As part of an applied research project for her leadership consulting collective, RLD Group, she studied where AI adoption breaks down inside organizations, and where it works. The findings from RLD Group’s research helped inform a collaboration on the CONVERSATIONS WORTH HAVING®: The Human Accelerator for Artificial Intelligence Quick Start Guide, which is available as a digital download.

Duerre views organizations through what she calls an I–WE–US leadership framework, defined like this:

I: individual judgment and accountability
WE: workflows and cross-functional coordination
US: governance, decision rights and organizational measures

“All three levels are contributing to the breakdown or the alignment, whether people realize it or not,” Duerre says. “AI is amplifying whatever’s already true in your system. The teams that were disconnected before AI showed up are more disconnected now. The ones that talked to each other are moving faster, together.”

If your company is ready to collaborate better with AI tools, Duerre shared the following tips. Take a look.

Form a cross-functional AI committee

Duerre’s background is in HR, and she says most HR leaders assume AI ownership belongs to IT. It doesn’t, at least not exclusively.

“Ownership needs to sit at the system level,” Duerre says. “Each function carries a piece of it, based on what they do, how well they understand that part of the business and how their work depends on everyone else’s. AI is flattening how we work. You can’t just keep it in your own business unit anymore. You have to look all around you.”

For starters, she suggests building a cross-functional AI committee instead of having one department make all the AI decisions. Legal, IT, cybersecurity and HR should be on the committee, Duerre says.

“If you have a C in front of your title, you should be on that committee,” Duerre says. “That’s how I look at it, because it’s a system-level solution.”

During these meetings, Duerre says you’ll find out that some departments are racing ahead with AI and others are holding back.

“Both sides need to name the trade-offs aloud,” Duerre says. “With teams moving too cautiously, you have to talk about the opportunity cost of falling behind. With teams sprinting ahead, you have to ask them what happens if they don’t bring everyone else along with them.”

Figure out how to use AI strategically

Most companies spent the past two years telling employees to use AI with anything, without much strategy behind it. Duerre says that’s starting to catch up with organizations as finance teams scrutinize the cost.

Her rule of thumb: if you can’t articulate the goal and how you’ll measure success, don’t roll it out yet.

“Teams that use AI well have a strategy behind it,” Duerre says. “They’ve kicked the tires on what they’re trying to solve it for. You need to ask yourself, ‘Which business outcome are we trying to improve, and what must be aligned for AI to create measurable value?’”

Here are a few examples of how to use AI strategically:

A company could select a workflow that regularly creates delays, redesign it with AI and test the new approach. Then, measure whether it improves time, cost, quality or capacity.
Use AI to support early sales outreach and qualification across markets and languages. AI can help a business reach and assess more potential opportunities, while people remain responsible for understanding the customer and building trust.
Flag patterns in customer complaints across multiple channels with AI, so leadership can see recurring problems before it shows up in satisfaction scores.

Check-in regularly during an AI rollout

Duerre recommends a minimum weekly check-in during any AI rollout, sometimes daily depending on complexity. But the format matters more than the frequency. Status updates don’t cut it.

“Ask, ‘What are we learning and what are we surprised by?’ That’s a question that helps you with your check-ins, versus, ‘It’s in three products now and we’ve tested six,’” Duerre says. “That doesn't help, because you’re having these meetings to figure out what’s working and why. If you ask more strategic questions, you can move even faster.”

Publish AI guardrails

Employees who don’t know what’s allowed with AI will either freeze or go around the system entirely, Duerre says. She recommends publishing clear, specific guardrails on what’s okay and what’s not. Come up with some real examples, and pair them with an intake process that doesn’t require writing a thesis to get an approval for using it.

"The approval path should be lightweight, not bureaucratic,” Duerre says. “Something like, ‘If you’re going to use AI, here’s the path. And if it needs approval, here’s three or four quick questions for you to answer.’”

Take employee anxiety about AI seriously

“AI is just a tool” is a phrase Duerre hears at nearly every conference she attends, but she doesn’t buy it.

“Saying it’s a tool is underselling what’s happening at companies right now,” Duerre says. “AI is changing how we work. It’s changing how we lead teams.”

Duerre wants leaders to remember that a lot of employees are fearful of AI. Pew Research Center found 52% of U.S. workers are worried about the future impact of AI in the workplace.

Employees who feel AI is being “done to them,” instead of built alongside them are especially anxious, she says.

“Leaders need to recognize that anxiety is contagious,” Duerre says. “As a leader, this is your opportunity to show up as the safe, steady person who is showing what you’re learning with AI. And don’t be afraid to show how you’ve failed using AI, too.”

Duerre asks every executive she works with: “Who am I with AI?” and encourages them to pass this mindset question along to their employees, too.

“AI is now your teammate,” Duerre says. “Phrasing it as, ‘who am I with AI?’ is different than, ‘what’s going to happen to me with AI?’ You really want your team to feel empowered with AI and show them how it can help accelerate their career.”

Put these ideas into action

Rewiring your organization for AI requires more than the right tools. It takes shared language, practical frameworks, and a willingness to keep learning. Here are a few resources to help you take the next step.

Enterprise AI Playbook: Practical frameworks and executive discussion questions to help IT, HR, and business leaders align around AI that delivers measurable value.
Work-First AI Use Case Assessment: Identify the workflows where AI can have the greatest impact before you invest in new tools.
The REWIRED Brief: Get weekly insights, real-world case studies, and practical advice on leading AI transformation.

4 Ways to Get Your Team Ready For Their Future Career

The World Economic Forum states that 39% of the skills your team relies on today will change by 2030. Most organizations have not built a plan to prepare their teams for that shift. At my company, we are still debating how to manage this upcoming shift.

Informa helps businesses and professionals in hundreds of ways.