SHARE



ABOUT THE AUTHOR


Kevin Kieller
Kevin Kieller is a partner with enableUC, a company that helps measure, monitor and improve UC and collaboration usage and...
Read Full Bio >>
SHARE



Kevin Kieller | February 26, 2013 |

 
   

Ratings without Requirements

Ratings without Requirements In evaluating Cisco versus Microsoft, you do need ratings, but you must take the time to define and prioritize your requirements.

In evaluating Cisco versus Microsoft, you do need ratings, but you must take the time to define and prioritize your requirements.

Recently, my colleague Zeus Kerravala chose to "fuel the fire" of the Cisco/Microsoft debate by evaluating their solutions and assigning ratings in six key areas: Enterprise Voice, Audio and Web conferencing, Desktop Chat and Presence, Cloud UC, Mobile UC, UC-Enabled Applications.

Technology solutions must meet the specific, defined and prioritized requirements of an organization in order to be successful. W. Edwards Deming, the father of quality assurance, suggested that quality was "meeting or exceeding customer expectations." Deming states that the customer's definition of quality is the only one that matters. In this context, a "better solution" is only better if it more closely meets the requirements of the customer. In absence of defined customer requirements, there can be no valid ratings.

Let's explore several things that, alone, should not persuade you to select a particular technology solution. (Please note that this goes beyond a point-by-point rebuttal of Zeus's article--it is my list of some factors that are used, often erroneously, in evaluating technologies):

1. Others felt it was a good solution.
Based on the cited survey results, Zeus states, "62.3% felt that Cisco was the leader in enterprise voice," and in another area, "54% of the respondents felt Cisco was the leader". While these are nice statistics, it is also important to note that 47% of Americans believe in extrasensory perception (it seems almost half your users might not need communication devices at all!)

"Others believing something" is not a good basis for deciding a solution is a good match for your requirements. Of course, if no one believes the solution you are investigating is a good solution, then you may want to reconsider.

2. A solution has largest market share
Market share favors the incumbent and penalizes the new entrant. At some point every new technology had less market share than the old technology it hoped to displace: telegraph more than the telephone, horse-drawn carriages more than the automobile.

As per above, if a solution being considered has zero or virtually no market share, then you would need to be willing to be a founding or pilot customer.

3. Case studies
Case studies prove a solution worked for a specific organization. Most, however, are "watered-down" in terms of details and don't accurately address any challenges or trade-offs that were made. Even if the organization being profiled is similar to yours, it is not identical.

Case studies do prove a solution at least worked somewhere! This is useful for very new solutions. However, geographical, cultural, regulatory, existing infrastructure, financial constraints along with varying business priorities may make a solution that was perfect for another organization a poor match for yours.

4. Because of one key statistic
Cisco's Carl Wiese interprets the recent Cisco-commissioned survey saying "Nearly half (47%) of the IT leaders who said they have deployed Microsoft Lync in their organization indicated they do not use it for business-critical external communications." Cisco's interpretation of this statistic is that customers do not trust Microsoft Lync for business-critical external communications; this may be true. Or...an alternative interpretation is that half of customers have implemented Lync for IM and presence and will be working to deploy enterprise voice in 2013 and 2014. Clearly many organizations rely on Microsoft Exchange for business-critical email. And what about business-critical internal communications?

One general statistic or even a handful of statistics is not a sufficient basis to choose one solution over another. As Jean Baudrillard said "Like dreams, statistics are a form of wish fulfillment." And as Mark Twain stated, "Facts are stubborn, but statistics are more pliable."

I am not suggesting that researching any of the above elements is inherently bad. You do need ratings, but you must take the time to define and prioritize your requirements, rate various viable options against your specific requirements, analyze the cost of the options (initial and ongoing) and then select the best solution for your organization. This process does take time, but it also yields accurate results. (I explore a detailed assessment and selection process in my article "The Goldilocks Approach: 7 Steps to Get to 'Just Right'".)

Sure, let's put fuel on the fire, but then let us use the light from the fire to illuminate a transparent and methodological process to evaluate solutions against defined requirements. I suspect the RFP evaluation sessions at Enterprise Connect, amongst others, will provide excellent examples of how to do exactly this.

Do you want to throw water or fuel on the fire of this discussion? Please comment below or spark a debate with me via twitter >@kkieller

Follow Kevin Kieller on Twitter and Google+!
@kkieller
Kevin Kieller on Google+





COMMENTS



April 19, 2017

Now more than ever, enterprise contact centers have a unique opportunity to lead the way towards complete, digital transformation. Moving your contact center to the cloud is a starting point, quick

April 5, 2017

Its no secret that the cloud offers significant benefits to enterprises - including cost reduction, scalability, higher efficiency, and more flexibility. If your phone system and contact center are

March 22, 2017

As today's competitive business environments push workforces into overdrive, many enterprises are seeking ways of streamlining workflows while optimizing productivity, business agility, and speed.

April 20, 2017
Robin Gareiss, president of Nemertes Research, shares insight gleaned from the firm's 12th annual UCC Total Cost of Operations study.
March 23, 2017
Tim Banting, of Current Analysis, gives us a peek into what the next three years will bring in advance of his Enterprise Connect session exploring the question: Will there be a new model for enterpris....
March 15, 2017
Andrew Prokop, communications evangelist with Arrow Systems Integration, discusses the evolving role of the all-important session border controller.
March 9, 2017
Organizer Alan Quayle gives us the lowdown on programmable communications and all you need to know about participating in this pre-Enterprise Connect hackathon.
March 3, 2017
From protecting against new vulnerabilities to keeping security assessments up to date, security consultant Mark Collier shares tips on how best to protect your UC systems.
February 24, 2017
UC analyst Blair Pleasant sorts through the myriad cloud architectural models underlying UCaaS and CCaaS offerings, and explains why knowing the differences matter.
February 17, 2017
From the most basics of basics to the hidden gotchas, UC consultant Melissa Swartz helps demystify the complex world of SIP trunking.
February 7, 2017
UC&C consultant Kevin Kieller, a partner at enableUC, shares pointers for making the right architectural choices for your Skype for Business deployment.
February 1, 2017
Elka Popova, a Frost & Sullivan program director, shares a status report on the UCaaS market today and offers her perspective on what large enterprises need before committing to UC in the cloud.
January 26, 2017
Andrew Davis, co-founder of Wainhouse Research and chair of the Video track at Enterprise Connect 2017, sorts through the myriad cloud video service options and shares how to tell if your choice is en....
January 23, 2017
Sheila McGee-Smith, Contact Center/Customer Experience track chair for Enterprise Connect 2017, tells us what we need to know about the role cloud software is playing in contact centers today.