Network downtime is a hot topic, especially with the recent headlines including Southwest and Peak Web, and as many organizations transition to digital business models. Along these lines, we’ve just updated our written guidance regarding how to reduce network downtime. Overall, we make six specific recommendations in the research, which comprise a mix of modern antifragile practices with “old-school” network hygiene.
For example, we recommend embracing a blameless postmortem culture to network outages. While the concept of blameless postmortems aren’t new (as Gartner wrote in 1996 “During the post-mortem, project goals should be assessed against actual deliverables in an open and blameless environment)— they have not typically been applied to the networking domain yet… Further, organizations should reward people based on the problems they prevent, not the problem they fix. Similarly, as blogger Greg Ferro recently tweeted:
To support this culture shift, senior network leaders must motivate staff to increase the level of automation and identify fragile designs proactively as part of their performance reviews. Other recommendations in the research touch on the details regarding applying antifragile principals for network changes and testing, reducing the networking “blast radius”, reducing technical debt, and generalized good hygiene such as network automation and use of specific tools. You can access the full research here:
Summary: Network outages negatively impact revenue, productivity and brand reputation, and are increasingly impactful as organizations implement digital business initiatives. This research identifies how I&O leaders responsible for networking can reduce the number and duration of network outages.
Regards, Andrew Lerner
PS – Here’s another perspective (and decent playlist) on network downtime.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.