January 5, 2012

Why UC Implementations Fail

  • Here are the top 10 reasons and how to avoid them
  • Avaya
Unified communications (UC) is increasingly viewed as a valuable platform that can offer numerous benefits across the entire enterprise. The technology is expected to play a key role in many organizations' ongoing efforts to grow their business and improve profitability.

UC implementations can fail for many reasons. Organizations planning to deploy a UC platform across their enterprise should keep the following pitfalls in mind as they move through the implementation process.

Download Report

(Webtorials registration required for downloads. Click here if you forgot your username/password.)


3 Comments

While most organizations are at least partially on the path to various forms of UC solutions, there are almost as many variations on the solutions as there are organizations. In fact, even the exact definition of "Unified Communications" will vary from organization to organization.

In this paper, Avaya offers a discussion of a number of reasons that UC implementations fail - or are sub-optimal to say the least. A lot boil down to setting reasonable expectations and offering the portions of UC that are most attractive to your organization.

For instance, being able to customize your approach is key. Just because there are a "gazillion" options doesn't mean that every option must be implemented. In fact, in some cases there may be so many options that users end up resisting using the capabilities due to the complexity.

Of course, in addition to pointing out the reasons for failure, the paper also offers suggestions as to how to avoid these pitfalls.

I would also add that there is lack of discovery on the interview as to the details of the customer requirements for the sale. I have reviewed many pre/post sales and the ability for any member of the team to state the customer requirements is often sputtered in sentence fragments. A good discovery will often lead to a more accurate sale and better customer experience. Know your customer needs.

I would have to disagree. Yes, discovery is part of the reason the implementation fails but it is discovery of existing applications and harware and the compatability with the new applications. Everyone sits at the table with the customer saying this is what we want, the salesman saying this is what you need, and the implementation engineer saying I think we can make this work. The truth of the matter is that no one actually does the research needed. Most failures are due to application incompatability and improper network configurations. Just my opinion.

Search Webtorials

Get E-News and Notices via Email


  

 



  

I accept Webtorials' Terms and Conditions.

Trending Discussions

Featured Sponsor Microsites






















Archives

Notices

Please note: By downloading this information, you acknowledge that the sponsor(s) of this information may contact you, providing that they give you the option of opting out of further communications from them concerning this information.  Also, by your downloading this information, you agree that the information is for your personal use only and that this information may not be retransmitted to others or reposted on another web site.  Continuing past this point indicates your acceptance of our terms of use as specified at Terms of Use.

Webtorial® is a registered servicemark of Distributed Networking Associates. The Webtorial logo is a servicemark of Distributed Networking Associates. Copyright 1999-2018, Distributed Networking Associates, Inc.