After discussing network code upgrades internally, there are some eerie similarities with going to the dentist. While all networking vendors claim the process to perform code upgrades is easy and straightforward (and yes, some vendors do this better than others), the process is often way more cumbersome than it should be. Gartner clients frequently cite this as a pain point and I’ve personally lived this as well. Here are 6 similarities between network code upgrades and a visit to the dentist (Sorry Dr. B).
- You have to schedule it weeks (if not months) in advance, and fill out a questionnaire/form before you can start.
- They are never fun and usually somewhat painful.
- They are supposed to take 20-30 minutes, but in reality are usually more than an hour.
- They are unavoidable – you have to do them at some point or you’ll have major problems.
- During the event, you usually uncover something else that is wrong (or at least “interesting”), which must be fixed/investigated in a subsequent visit.
- If you find something really really wrong, it will require more visits and more money to fix.
Comments including war-stories and other similarities welcome.
PS – Growing up, my orthodontist’s name was Dr. Bonebreak…you cannot make something like that up.
Read Complimentary Relevant Research
Top Strategic Predictions for 2019 and Beyond: Practicality Exists Within Instability
Technology-based change is happening continuously, and most organizations struggle to see the change in advance. Continuous change can...
View Relevant Webinars
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.