November 22, 2026

Bridging the Value Gap: How Outcome-Oriented Automation Rescues Stalled Network Projects

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.