In the rapidly evolving landscape of enterprise technology, the promise of network automation has long been heralded as the ultimate solution for increasing operational efficiency, reducing human error, and enabling the kind of agility required by modern digital businesses. However, a persistent and troubling trend has emerged across the industry: many of these ambitious automation initiatives are stalling or facing outright disruption. The root cause is rarely a lack of technical capability or engineering talent; rather, it is a fundamental disconnect between the technical execution of automation and the tangible business outcomes that executive management can see and measure.
When senior leadership cannot perceive a clear return on investment or a direct impact on the organization’s bottom line, the "merry-go-round of justification" begins. Technical teams find themselves in a perpetual cycle of defending their budgets and explaining their progress in terms that fail to resonate with business stakeholders. To address this critical challenge, a recent episode of the Packet Pushers podcast, sponsored by Meter, featured a deep-dive discussion into the philosophy and practice of Outcome-Oriented Automation.
The episode brought together Eric Chou, a prominent voice in the networking community, with two key experts from Gluware: Alex Henthorn-Iwane, Chief Marketing Officer, and Kyle Scarmardo, Senior Solutions Architect. Together, they explored how organizations can pivot their automation strategies to ensure they are not just "automating for the sake of automation," but are instead driving results that align with the broader goals of the enterprise.
Breaking the Cycle of Justification
The primary hurdle for many network teams is that automation is often treated as a series of isolated technical tasks rather than a holistic business strategy. A team might spend months developing scripts to automate a specific configuration change, but if that change doesn’t result in faster service delivery, improved security posture, or reduced downtime in a way that is visible to management, the project risks losing its momentum.
According to the experts from Gluware, the "merry-go-round of justification" is a symptom of a focus on inputs rather than outputs. In many legacy environments, success is measured by the number of scripts written or the percentage of devices touched by an automation tool. However, management is rarely interested in the mechanics of the "how." They are focused on the "what"—what did this do for the company?
By shifting toward an outcome-oriented approach, technical teams can begin to frame their work in terms of business value. This involves identifying the specific pain points that affect the organization’s performance—such as the time it takes to onboard a new branch office or the frequency of compliance violations—and designing automation workflows specifically to mitigate those issues. When the outcome is the starting point, the justification for the project becomes inherent in its success.
The Importance of Abstraction Choices
One of the most technical yet critical components of a successful automation strategy discussed by Henthorn-Iwane and Scarmardo is the concept of abstraction. In networking, abstraction refers to the layers between the human operator and the underlying hardware or software configurations. Choosing the right level of abstraction is essential for making automation scalable, repeatable, and, ultimately, outcome-oriented.
If the abstraction is too low, the automation remains tied to specific device commands and syntax, which requires constant maintenance and deep specialized knowledge for every hardware vendor in the environment. This "brittle" automation is difficult to scale and often fails when firmware is updated or new vendors are introduced. Conversely, if the abstraction is too high without the necessary underlying intelligence, the automation may lack the granularity required to handle complex network behaviors.
Gluware’s approach emphasizes finding the "sweet spot" of abstraction—one that allows engineers to define the desired state of the network without getting bogged down in the minutiae of command-line interfaces (CLI) for every single device. This allows the team to focus on the high-level outcome, such as "ensure all financial data traffic is encrypted across the WAN," while the automation platform handles the complex translations required to implement that policy across a diverse infrastructure. This level of abstraction not only speeds up deployment but also makes the results more predictable and easier to report to management.
Aligning Technical Skills with Business Needs
As the methodology of network management shifts toward automation, the role of the network engineer is also undergoing a significant transformation. The discussion highlighted the necessity of aligning technical skills with the outcomes the business actually cares about. It is no longer enough for an engineer to be an expert in a specific vendor’s CLI; they must also understand the business logic that drives the network’s requirements.
This transition often creates a skills gap that can further stall automation projects. Many organizations struggle to move their staff from a manual, "box-by-box" mentality to an automated, "system-wide" perspective. To bridge this gap, the experts suggest that teams should be encouraged to develop skills in architectural thinking and process design.
By focusing on outcomes, engineers are empowered to look at the network as a service delivery platform. This shift in mindset allows them to identify where automation can have the biggest impact on the business, such as improving security through automated exposure management or ensuring continuous compliance. When engineers understand the "why" behind their work, they are better equipped to build automation that delivers meaningful results, thereby providing the data points necessary to satisfy management’s need for tangible outcomes.
Episode Links:
The insights shared in this discussion are part of a broader effort by Gluware to provide the tools and education necessary for modern network teams to succeed. For those interested in viewing the full conversation and exploring the specific technologies mentioned, the following resources are available:
Titan Exposure Management: Overview
Titan Exposure Management Demo
Innovation in Exposure Management and AI
Central to the discussion of outcomes was Gluware’s recent focus on "Titan Exposure Management." In a world where security threats are evolving at an unprecedented pace, simply managing configurations is no longer sufficient. Organizations must be able to identify and remediate vulnerabilities in real-time.
Titan Exposure Management is designed to provide a comprehensive view of the network’s security posture, identifying "exposure" points that could be exploited by attackers. This includes detecting configuration drift—where a device’s settings deviate from the authorized standard—and identifying compliance gaps that could lead to regulatory fines or security breaches. By automating the detection and remediation of these issues, Gluware enables organizations to achieve the business outcome of a hardened, compliant network infrastructure.
The integration of AI into these processes further enhances the ability to manage complex environments. As network data grows in volume and complexity, AI-driven insights can help engineers identify patterns of drift or potential threats that would be impossible to spot manually. This proactive approach to network management is a prime example of how technology can be harnessed to deliver the specific outcomes that executive leadership demands.
A Creative Approach to Industry Pain Points
In a unique and engaging twist to their technical outreach, Gluware has also embraced the use of AI in creative ways to highlight the common frustrations of the networking world. The episode highlighted the release of the "Gluware Titan AI Metal Band" singles—songs generated with the help of AI that speak directly to the "headbanging" frustrations of network engineers.
The first track, "Slay Mythos," is described as an anthem for those tasked with slaying AI-driven threats, configuration drift, and compliance gaps. It serves as a high-energy representation of the battle engineers face every day to keep their networks secure and operational.
The second track, "The Quiet Drift," takes a different tone. Styled as a power ballad, it addresses the subtle and often dangerous phenomenon of configuration drift—the slow, silent changes that occur over time and can eventually lead to catastrophic network failures. These creative projects, while lighthearted, underscore the very real technical challenges that Gluware’s Outcome-Oriented Automation seeks to solve.
Gluware Titan AI Metal Band singles:
Slay Mythos: The ultimate headbanger for slaying AI threats, config drift, and compliance gaps: Spotify, Apple Music, and YouTube Music (and YouTube).
The Quiet Drift: Networking’s top power ballad to keep you and your network sanity in sync: Spotify, Apple Music and YouTube Music.
Ultimately, the conversation between Eric Chou and the Gluware team serves as a roadmap for organizations looking to move past the initial hurdles of network automation. By focusing on outcomes, making strategic abstraction choices, and aligning the workforce with business goals, enterprises can finally break free from the cycle of justification and realize the full potential of a modern, automated network.
