When a global network fails, the business impact is immediate: idle employees, disappointed customers, and lost revenue. What’s less obvious is that most of those failures were set in motion long before the first outage alert fired. They were baked in at the design stage.
Network Design Authority is a critical but misunderstood concept in enterprise connectivity. As data spreads across clouds and workforces go mobile, the old “good enough” approach to network design is no longer viable.
To explore what defines a true design authority, Zayo’s Managing Director for Global Reach, Alissa Clousing, sat down with Jim Campbell, SVP of Solutions Architecture. Their conversation cuts to the heart of why design decisions are the primary driver of connectivity failures that emerge 6 to 18 months post-implementation.
Watch the full interview below, then read on for a deeper look at the insights that matter most for global enterprises evaluating their network strategy.
What Is Network Design Authority?
Network Design Authority is the practice of taking full, consultative ownership of a network solution across its entire lifecycle. It means asking the hard questions upfront, engaging stakeholders beyond the immediate network team, and continuously revisiting whether the design still aligns with the evolving needs of the business.
It’s the difference between a provider that hands you a solution and a partner that owns the outcome.
For global enterprises managing distributed applications, mobile workforces, and complex cloud architectures, design authority is not a nice-to-have. It’s a business-critical discipline.
The Real Source of Connectivity Failures
There’s a persistent myth in enterprise networking: if a solution works on day one, the design is sound. Months later, when latency spikes or a failover doesn’t behave as expected, the instinct is to blame the technology or the contract terms.
That instinct is almost always wrong.
More customers are telling us that what actually burns them in connectivity decisions isn’t commercial terms. It’s design assumptions that don’t hold up in the real world.
“More customers are telling us that what actually burns them in connectivity decisions isn’t commercial terms,” says Jim Campbell. “It’s design assumptions that don’t hold up in the real world.”
The most common failure pattern is straightforward: the business evolves, and the design doesn’t. What was fit-for-purpose at deployment becomes a constraint six, twelve, or eighteen months down the line. Applications move to new cloud regions. Traffic volumes shift. New user groups come online in markets the original design never accounted for.
The second, equally dangerous failure mode is more subtle: design requirements that were never fully understood in the first place. Unknown variables that seemed insignificant during the design phase suddenly become critical when the business scales. By then, retrofitting a solution is expensive, disruptive, and sometimes impossible.
As Campbell puts it, “the unknowns all of a sudden became important and weren’t a part of the design or the discussion early on. And that’s where you end up in trouble.”
Why “Good Enough” Design Has a Shelf Life
Five years ago, network design was relatively predictable. Applications lived in a handful of data centers. Employees worked from fixed office locations. Traffic patterns were stable enough that a well-designed network could serve a business reliably for years without significant adjustment.
That model is gone.
Applications and data are now scattered globally. Workforces are distributed across time zones and geographies. The intersection of where a user is, where an application runs, and where data is stored creates a constantly shifting matrix that static design simply cannot accommodate.
“As applications have gone into the cloud, exactly where someone is accessing that application varies depending on where they are,” Campbell explains. “All of that makes the underlying network design a lot more complicated. You have to account for all those different factors.”
The enterprises that recognize this shift and partner with providers equipped to design for it are the ones that avoid the most painful and costly surprises.
What a True Design Authority Actually Does
Most providers will tell you they do design. Fewer will tell you what that design process actually involves. The distinction has huge implications for your business outcomes.
A genuine design authority does three things that other vendors routinely skip:
1. Asks the right questions, relentlessly.
The foundation of good design is rigorous discovery. That means asking where applications live, where data resides, where users are located, how mobile they are, what traffic volumes look like, and what the business will look like in three to five years.
“Asking questions is the most important thing a design authority can do,” says Campbell. “Because that ultimately gets at what are the underlying requirements for the overall environment and how do you satisfy those.”
2. Engages beyond the network team.
Most vendors engage with whoever is responsible for network procurement and stop there. A true design authority goes further by talking directly with application owners, end-user groups, and business stakeholders who understand how the network will actually be used. That broader perspective identifies requirements that would otherwise remain invisible until they cause a failure.
3. Maintains the design across the lifecycle.
Design authority doesn’t end at deployment. It’s an ongoing commitment to revisit whether the solution still fits every six, nine, or twelve months, depending on how fast the business is changing. “When we act as a design authority,” Campbell notes, “it’s not a set-it-and-forget-it engagement. It’s an ongoing engagement to evolve what a customer’s network environment looks like over time.”
The Cost of Getting Design Wrong
The cost of poor design is more than just technical problems. It creates business consequences that far exceed the cost of doing it right the first time.
Network outages idle employees and delay operations. Latency issues degrade application performance and user experience. Customers notice. Revenue suffers. And when the root cause is traced back to a design decision made eighteen months earlier, there’s rarely a clean or inexpensive fix.
“When you don’t design something right, and you think you do, the surprise is awful,” says Campbell. “When it becomes apparent that what you thought was going to work doesn’t work in particular circumstances, it’s usually catastrophic because of the impact you have on your business.”
The inverse is equally true: good design is largely invisible. When it works, no one talks about it. When it doesn’t, everyone notices.
How Zayo’s Global Reach Capability Enables Better Design
Design authority is only as strong as the underlying infrastructure it can draw from. This is where Zayo’s global footprint becomes a meaningful differentiator.
Zayo’s network spans over 19 million fiber miles and connects businesses to more than 400 key global markets. Rather than forcing enterprises to navigate fragmented relationships with multiple regional carriers, Zayo simplifies global networking through partnerships with 75+ international network carriers and removes complexity without sacrificing reach or resilience.
For enterprises operating across high-growth markets, Zayo’s strategically located Points of Presence in Singapore, Tokyo, Hong Kong, Sydney, and São Paulo enable direct access to the regions where business is accelerating fastest. These PoPs are supported by integration with 30+ subsea cables, providing the high-capacity, low-latency transatlantic and transpacific connectivity that global performance demands.
That kind of infrastructure depth allows Zayo’s teams to design solutions that are genuinely fit for purpose, not solutions limited by what a single provider happens to own.
How to Evaluate Whether a Provider Has Real Design Authority
When assessing a provider’s design credentials, Campbell points to two primary signals:
The quality of their questions. A provider that rushes to close a deal without thorough discovery is not acting as a design authority. If they take your requirements at face value and move straight to fulfillment, that’s a warning sign.
Their willingness to challenge you. “If it’s always just, ‘Tell me what you need, and I’ll give you whatever you need,’ that’s a concern,” says Campbell. A real design authority will push back on assumptions, raise scenarios you haven’t considered, and sometimes tell you that what you’re asking for isn’t possible or isn’t right.
Campbell also recommends a question most buyers never ask: “What would you do if you were me?” Engineers, he notes, are often honest to a fault. That question tends to surface the most candid thinking about what the right design actually looks like.
The Zayo Commitment to Design Authority
Zayo’s approach to design authority is built on a straightforward premise: the network exists to serve the business, not the other way around. That means designing for performance, scalability, and long-term evolution beyond the requirements of a given moment.
As Campbell puts it, “we are consultative and focused on making sure the overall application environment performs to the way users want it to.”
That commitment extends through the full lifecycle of the customer relationship. Zayo’s design teams regularly revisit underlying assumptions, ensuring that as the business evolves, the network evolves with it. Not six months behind it.
Build a Network That Scales With Your Business
Enterprises that treat network design as a strategic discipline over the next decade will outperform enterprises that treat it like a checkbox. The cost of a poorly designed network is measured in business disruption, delayed growth, and lost competitive advantage.
Zayo’s Global Reach capability exists to ensure that global enterprises have both the infrastructure depth and design expertise to build networks that perform today and scale for what comes next.