NAN113: What Works, and What Doesn’t, in Network Automation Projects

Today, we are joined by Matt Remke, a seasoned consultant with years of experience in the field of network automation projects. With a non-technical perspective, Matt offers insights into scaling network automation in real-world, complex environments for some of the world's largest companies. He shares what worked, what backfired, and the hard-earned lessons he has gained from navigating the challenges of implementing network automation at scale.

Matt begins by highlighting the importance of understanding the unique needs of each organization. He emphasizes that every network automation project is different, and what works for one company may not be suitable for another. The first step, according to Matt, is to clearly define the goals and objectives of the project. This involves engaging with stakeholders across the organization to ensure that everyone is aligned and understands the benefits of automation.

One of the key challenges Matt has encountered is the resistance to change that often comes with implementing network automation. He recalls a project where the team faced pushback from IT staff who were concerned about job security. To overcome this, Matt's team focused on communication and education, demonstrating how automation would enhance efficiency and allow staff to focus on higher-value tasks. This approach not only helped gain buy-in from the team but also improved morale and productivity.

Another critical aspect of successful network automation projects, as Matt points out, is the selection of the right tools and technologies. He warns against adopting overly complex solutions that may not be necessary for the organization's needs. Instead, he advocates for a balanced approach that leverages existing infrastructure while introducing new tools where they provide the most value. This helps to minimize disruption and ensure a smoother transition.

Matt also discusses the importance of pilot testing before rolling out network automation solutions organization-wide. He recalls a project where a company attempted to implement a new automation tool across all its data centers simultaneously. The result was chaos, with widespread issues that took months to resolve. By contrast, Matt's team successfully implemented a similar solution by starting with a small pilot in one data center, allowing them to identify and address potential issues before expanding.

In addition to technical considerations, Matt underscores the need for strong project management. He shares a cautionary tale of a project that failed due to poor planning and execution. The team lacked clear roles and responsibilities, leading to confusion and duplicated efforts. Matt stresses the importance of establishing a project management framework that includes regular check-ins, clear milestones, and accountability.

Matt also touches on the role of monitoring and feedback in network automation projects. He believes that continuous monitoring is essential to ensure that the automation tools are functioning as intended and to identify any issues that may arise. Furthermore, he advocates for a culture of feedback, where team members are encouraged to share their experiences and suggestions for improvement.

Finally, Matt reflects on the long-term benefits of network automation. He notes that while the initial implementation can be challenging, the rewards include increased efficiency, reduced operational costs, and improved network reliability. However, he cautions that the success of automation projects depends on ongoing investment and adaptation. As network environments continue to evolve, organizations must be prepared to refine their automation strategies to remain competitive.

In conclusion, Matt Remke's insights offer a valuable perspective on the complexities of network automation projects. By focusing on clear goals, effective communication, the right tools, pilot testing, strong project management, and continuous monitoring, organizations can increase their chances of success in scaling network automation. As the field continues to evolve, Matt's hard-earned lessons serve as a roadmap for those navigating the ever-changing landscape of network automation.