Networking Reference
In-Depth Information
Another issue here is that IT department usually forgets to analyze all business
requirements or to understand their business benefits. When business divisions
are made to work with the IT department on a business case for the project, we
often noticed that the business divisions have difficulties understanding their
own business requirements and most of the time they are clueless about the
functionalities and capabilities of the communication and collaboration platform.
One key learning point of many organizations is that most IT departments are not
fully capable to drive an innovation project alone. Instead, it is highly recommended
to have a consultant with both technical and business background to lead the UC
project. Support from their management, budgetary limits, lack communication to
business divisions, or are too much focused comparing unified communication with
the existing legacy system that is in place could affect the success of the project.
This is not the situation we would like for our end users, partners, and of course,
the manufacturers of the solution. Before we start analyzing the different areas of
most common "mistakes" or "deiciencies and issues" with UC projects, let us first
summarize the most common key problem areas:
No stakeholder
support
UC does get
implemented in
companies'
communication
processes
Budgetary
issues
UC solutions
doesn't meet
business
requirements
Lack of training
for end users or
major issues in
UC adoption
Risks
Internal politics
and blocker for
change
What are the
KPIs for the
project success?
No or
insufficient RFP
process
Unsuccessful
pilot project
No professional
project
management
Key issues and blockers for technology projects inside a company
 
Search MirCeyron ::




Custom Search