For infrastructure leaders, the key management decision is not whether to โdo AIโ in NetOps, but what operational controls must exist before automation can be trusted at scale. The article makes the technical case; the leadership question is how to define decision rights, escalation paths and approval thresholds so automation reduces risk instead of moving it into a black box.
That means treating automation as a governed operating model, not a tool rollout. CIOs and operations directors should ask who owns the source of truth, who signs off on automated changes, and which workflows remain human-approved because the blast radius is too high. Without that clarity, automation can increase speed while weakening accountability during incidents, audits or vendor disputes.
The second implication is portfolio discipline. Not every network task deserves the same level of investment. Leaders should prioritise the repetitive, high-frequency activities that consume scarce engineering time and create avoidable error, then track benefits in terms of service stability, audit readiness, patch latency and recovered staff capacity. The trade-off is that quick wins may not align with the most visible transformation programmes, so funding criteria need to be explicit.
The workforce issue is also strategic, not just tactical. Automation changes the role of network engineers from task execution to policy design, exception handling and control validation. That shift needs training, revised job expectations and a new definition of expertise. The next questions for management are: where should humans retain final approval, what evidence will prove the controls are working, and which metrics will tell you automation is truly improving resilience rather than simply accelerating activity?
-
Market confusion. The concept of automation has been broadened and overcomplicated by including orchestration. Business leaders have a hard time differentiating between the two. Only a subset of companies, such as telcos and ISPs, use their networks as revenue generators. Those types of businesses need complex orchestration tools to support the heavy service deployments that generate business value. In contrast, the tasks that all companies must perform to maintain and manage their infrastructure are crucial in allowing it to be resilient, secure, compliant and reliable. Such tasks are simpler and can be easily automated. There’s no need for complicated and expensive orchestration capabilities.
-
Perceived skills gap. Activities such as device discovery, backup and recovery, patching, upgrades and compliance checks are highly automatable today, and don’t require network engineers to become coding experts. Instead of a blank-slate approach, low-friction solutions that include prebuilt automations for most of these everyday tasks and a no-code approach to customization make it easy to get started.
-
Distraction. Network infrastructure now consists of multiple hybrid clouds and campus networks, while on-prem networks and data centers still exist. The move to AI is driving additional modernization challenges related to bandwidth and availability requirements. Meanwhile, organizations acquire other businesses that use different vendors for their infrastructure.
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.

