We’ve all heard some pretty outrageous myths and urban legends. You know, your mom probably warned you that if you swallow chewing gum, it will remain undigested in your gut for seven years.
Or did you hear that penguins will fall on their backs trying to see airplanes flying overhead?
And, finally, you may have heard that a “good enough” network will work just fine for video, voice, and mission-critical applications.
The truth is, none of these myths is true.
And there was some major mythbusting going on yesterday during the “Debunking the Myth of the Good Enough Network” webcast.
Bob Cagnazzi, CEO of BlueWater Communications Group (Cisco Master Partner); Rob Lloyd, Cisco’s EVP of Worldwide Operations; and Mike Rau, Cisco’s VP and CTO of Borderless Networks helped to debunk the seven most misleading myths of the “good enough” network. They talked about the dreaded Single Purpose Myth, the horrific Security as a Bolt On Myth, and the scary Application and Endpoint Ignorant Myth, just to name a few.
After he debunked those myths, Mike then provided key questions for our partners to ask their customers to find out if their network is ready.
Yesterday, I blogged about the “good-enough” network. You know, it’s a network that just good enough to send out a quick email or watch a video, but not quite fast or reliable enough to do everything you need.
It may be easier to think of the good-enough network in terms of other areas of your life where good enough just doesn’t cut it.
For instance, a 19-inch tube TV is certainly good enough for watching reruns of “Magnum P.I.,” but not for watching the big game.
Or using SPF 5 sunscreen may be good enough, but SPF 30 is a way better option if you want to avoid a sunburn.
Just imagine if your customers settled for a good-enough network? It may go something like this:
What are the seven myths about the good-enough network? Read More »
It would be hard to believe that any user of technology has not faced this question at one time or another. Something stopped doing what it is supposed to do, and we’re wondering whether to raise the white flag or try to fix it. In many cases, the answer is a long way from clear-cut. Part of us wants to take a crack at it. That same part of us doesn’t want to come across as less than knowledgeable. Also, that same part of us might not want to wait for someone to come in and fix it. After all, we are very busy.
On the other hand, just as a horse can perceive a nervous rider, technology issues often have an uncanny ability to go from bad to worse when someone with just a little knowledge goes “under the hood.” But depending on your skill level, there are certain things you might be able to do in order to try to get things up and running again.
With all the interest and decisions around the products and new capabilities involved in your next IT upgrade, it’s easy to have key questions about the service plans slip through the cracks. Don’t worry. I’ve got your back. Here are a few suggestions:
Who delivers the services?
In this wild, woolly world of contracting and subcontracting, you can’t necessarily assume that the company that closes the service contract will actually be the one that fulfills that contract. This is especially true if you have facilities in multiple locations. So if subcontractors are involved, you’ll want to know who those subcontractors are, what specializations, certifications, or other qualifications they have in place, and what their customer satisfaction scores look like.
Which organization is the point of contact for engaging the services?
If more than one provider is involved, does one organization serve as the entry point for access to services, or do you have to pinball around until you find the subcontractor who maps to the specific need?