Skip to main content

The Real Currency of Enterprise IT Isn't Performance - It's Trust

Jeremy Rossbach
Broadcom

IT operations teams dedicate an enormous amount of energy to tracking performance metrics. We spend our days staring at telemetry dashboards monitoring packet loss, jitter, latency spikes, and server utilization. We treat response times as the ultimate badges of honor. Yet after years of collaborating with enterprise network leaders, I have arrived at a simple truth. Users rarely evaluate IT based on network throughput or CPU graphs. They measure us on confidence. They want absolute assurance that core tools will function reliably, and that when outages occur, someone knows precisely why and is actively fixing it. The ultimate measure of operational success is not raw speed. It is trust.

Maintaining that level of confidence has become vastly more complex over the last decade. Historically, enterprise applications lived within physical data centers that IT departments completely owned and operated. If an application stalled, network engineers could trace the physical path end-to-end and pinpoint the precise bottleneck. Today, corporate traffic flows across public cloud platforms, third-party SaaS applications, edge providers, and home broadband connections. The traditional corporate network perimeter has dissolved. While direct physical control over infrastructure has eroded, business expectations have done the exact opposite. Executive stakeholders and frontline staff still demand immediate answers, complete accountability, and rapid resolution, no matter where along the digital delivery chain a failure occurs.

The difference between operating on guesswork and operating with objective proof is starkest during high-stakes infrastructure cutovers. When teams execute a major migration without baseline telemetry, post-cutover operations quickly devolve into chaos. The moment end users report that core business tools feel sluggish, IT has no historical data to validate whether performance actually degraded. Instead of diagnosing genuine issues, engineers spend weeks combing through disparate server logs and running manual packet captures just to determine whether a real anomaly even exists.

Establishing pre-migration baselines across real user workloads fundamentally flips this dynamic. When live production metrics are measured directly against pre-cutover benchmarks, subjective user complaints are immediately replaced with empirical data. While the migration steps themselves remain demanding, deep visibility eliminates the ambiguity. Teams can validate application health instantly, bypass weeks of cross-departmental finger-pointing, and present executive leadership with concrete proof of operational stability.

This same principle governs how IT manages external third-party infrastructure. When distributed branch offices experience intermittent latency across global telecom routes, relying on carrier help desks typically produces little more than generic claims that provider backbones are green. With continuous hop-by-hop path telemetry, however, operations teams can isolate the exact transit node or upstream peering link causing performance degradation before regional disruptions are even acknowledged. Armed with hard telemetry rather than vague complaints, IT transforms a defensive vendor confrontation into a focused, evidence-based resolution.

In many corporate environments, application slowdowns trigger an immediate blame game. End users point at the network, network engineers fault the application code, and application developers point at cloud infrastructure or database servers. Without a single source of objective truth, every incident response call devolves into a guessing game. Conversely, when operations teams possess instant line-of-sight to historical context and path data, troubleshooting timelines drop from weeks down to minutes. Engineers stop chasing ghosts and spend their energy actually fixing root causes. When IT leadership can explain exact failure points using clear diagnostic proof, confidence rebuilds across every business unit.

In the long run, this trust fundamentally alters how IT operations is viewed across the enterprise. As user satisfaction scores climb and business leaders feel genuinely supported, the network team stops being treated as a reactive maintenance crew fixing broken pipes. They step into the role of strategic partners driving real business outcomes. The future trajectory of IT operations won't hinge on alert volume or dashboard counts. It depends on how effectively teams convert deep visibility into proof, proof into reliability, and reliability into enduring trust. Because in a borderless digital ecosystem, confidence is the only currency that truly counts.

Jeremy Rossbach is Chief Technical Evangelist - Network Observability at Broadcom

Hot Topics

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

The Real Currency of Enterprise IT Isn't Performance - It's Trust

Jeremy Rossbach
Broadcom

IT operations teams dedicate an enormous amount of energy to tracking performance metrics. We spend our days staring at telemetry dashboards monitoring packet loss, jitter, latency spikes, and server utilization. We treat response times as the ultimate badges of honor. Yet after years of collaborating with enterprise network leaders, I have arrived at a simple truth. Users rarely evaluate IT based on network throughput or CPU graphs. They measure us on confidence. They want absolute assurance that core tools will function reliably, and that when outages occur, someone knows precisely why and is actively fixing it. The ultimate measure of operational success is not raw speed. It is trust.

Maintaining that level of confidence has become vastly more complex over the last decade. Historically, enterprise applications lived within physical data centers that IT departments completely owned and operated. If an application stalled, network engineers could trace the physical path end-to-end and pinpoint the precise bottleneck. Today, corporate traffic flows across public cloud platforms, third-party SaaS applications, edge providers, and home broadband connections. The traditional corporate network perimeter has dissolved. While direct physical control over infrastructure has eroded, business expectations have done the exact opposite. Executive stakeholders and frontline staff still demand immediate answers, complete accountability, and rapid resolution, no matter where along the digital delivery chain a failure occurs.

The difference between operating on guesswork and operating with objective proof is starkest during high-stakes infrastructure cutovers. When teams execute a major migration without baseline telemetry, post-cutover operations quickly devolve into chaos. The moment end users report that core business tools feel sluggish, IT has no historical data to validate whether performance actually degraded. Instead of diagnosing genuine issues, engineers spend weeks combing through disparate server logs and running manual packet captures just to determine whether a real anomaly even exists.

Establishing pre-migration baselines across real user workloads fundamentally flips this dynamic. When live production metrics are measured directly against pre-cutover benchmarks, subjective user complaints are immediately replaced with empirical data. While the migration steps themselves remain demanding, deep visibility eliminates the ambiguity. Teams can validate application health instantly, bypass weeks of cross-departmental finger-pointing, and present executive leadership with concrete proof of operational stability.

This same principle governs how IT manages external third-party infrastructure. When distributed branch offices experience intermittent latency across global telecom routes, relying on carrier help desks typically produces little more than generic claims that provider backbones are green. With continuous hop-by-hop path telemetry, however, operations teams can isolate the exact transit node or upstream peering link causing performance degradation before regional disruptions are even acknowledged. Armed with hard telemetry rather than vague complaints, IT transforms a defensive vendor confrontation into a focused, evidence-based resolution.

In many corporate environments, application slowdowns trigger an immediate blame game. End users point at the network, network engineers fault the application code, and application developers point at cloud infrastructure or database servers. Without a single source of objective truth, every incident response call devolves into a guessing game. Conversely, when operations teams possess instant line-of-sight to historical context and path data, troubleshooting timelines drop from weeks down to minutes. Engineers stop chasing ghosts and spend their energy actually fixing root causes. When IT leadership can explain exact failure points using clear diagnostic proof, confidence rebuilds across every business unit.

In the long run, this trust fundamentally alters how IT operations is viewed across the enterprise. As user satisfaction scores climb and business leaders feel genuinely supported, the network team stops being treated as a reactive maintenance crew fixing broken pipes. They step into the role of strategic partners driving real business outcomes. The future trajectory of IT operations won't hinge on alert volume or dashboard counts. It depends on how effectively teams convert deep visibility into proof, proof into reliability, and reliability into enduring trust. Because in a borderless digital ecosystem, confidence is the only currency that truly counts.

Jeremy Rossbach is Chief Technical Evangelist - Network Observability at Broadcom

Hot Topics

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...