Mobile Customer Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, 14 February 2008

UC Complexity; Who, What, Why, and How

Posted on 14:42 by Unknown

February 14, 2008

The “Who,” “What,” “Why,” and “How” of Business UC

By Art Rosenberg, The Unified-View

I just read yet another article, “What Is Unified Communications?” written in NEC Newslink, a quarterly report for NEC distribution channels, attempting to explain what UC is all about. What was most interesting about this piece was that it quoted several different definitions of UC promoted by leading industry technology developers and analysts. The fact that UC is, indeed, that complex, that it requires everyone who talks about it to first define it, demands attention.

Part of the problem is that most people are mixing up the different perspectives of UC, and it is time that we started being more specific about which perspective we are talking about. The other part of the problem is that there is more than one target audience in the business market and they have different concerns for the value of UC to a business organization. So, the UC implementation “message” really is quite complex!

The UC “Who” in The Organization

In the business communications market, there are three main audiences who must have a common understanding of UC technologies before UC planning and implementation can take place properly. They are:

1. Business operations management responsible for providing common UC services to their end users for efficient business operations

2. The individual end users, both inside and outside of the organization, who need and want such services, i.e., their employees, business partners, customers, or service subscribers

3. The technology support responsible for selecting, managing, and maintaining the technologies for such services. Such support may be internal staff, outside support, or a combination of the two.

Each of these categories have different operational interests and responsibilities regarding UC capabilities, so their perspectives will never be identical. However, implementing UC capabilities has to satisfy all perspectives in order to achieve a successful transition. So, step one is really to recognize who the players are and what role they play in the migration to business UC.

The “What” of UC

The biggest source of confusion for all business use is to understand “what” UC really encompasses. Because it is a convergence of various forms of communications with people, it is actually more of a “mashup” of both legacy and new features and functions related to those modes of communications. These new combinations will let end users have greater flexibility, ease of use, and operational efficiencies than the current communication silos that still dominate the world of business.

It’s not enough to describe UC as the use of all the communication applications and modalities of communication applications, but rather the different impact of UC flexibility upon the more specific functional roles of an individual user as either a “contact initiator” or a “contact recipient/respondent. ”Business” contacts will also include people who receive messages and information from automated business process applications.

Viewing UC from the contact modality perspective, rather than the informational content view, will highlight what the end users will have to do to communicate effectively and efficiently regardless of the application. That is where the productivity benefits will pay off to end users for specific business process activities and the technologies that they have available to them to do so easily and efficiently. So, we must differentiate premise-based capabilities (wired, wireless) for those users who can use them, from public services that are available to anyone.

Clearly, all three categories of enterprise personnel need to understand the “what” of UC just so that they can be ready to exploit the new technologies effectively. (Stay tuned to UC Strategies.com for a forthcoming publication realistically defining the “what” of UC.)

The “Whys” of UC

The payoffs of using new UC technology must be realized directly or indirectly by the involved organizational categories described in the UC “Who” above. We can look at the ROI being both “hard” and “soft” dollars values as follows:

· Business Management Values

- Business operational performance and productivity

- Business competitive strategies

- Attract and retain staff

- Attract and retain business partners

- Attract retain customers

- Minimize costs

- Maximize sales, profits

· End User Values

- Convenience, flexibility, ease of use

- Increase personal time productivity

- Improves job performance quality

- Efficiencies as contact initiator or recipient for all business relationships

- Device choices and preferences

· Technology Support

- Ease of installation

- Ease of integration

- Ease of administration

- Remote management

- Ease of end user support

- Operational reliability management

- Scalability for usage flexibility

- Maintainability

- Minimal costs

- Security management

- Interoperability with public services (Partners, customers, Remote staff)

- Change management

The “How”

The “how” of UC implementation breaks down into several phases, including:

· Business strategy requirements analysis

· End user requirements analysis

· Network analyses (wired, wireless)

· Selective implementation planning

· Organizing for “change management”

· Choosing future-proof UC technology providers/partners

- Application software servers

o CPE procurements

o Managed service procurements

o Hosted service procurements

- End user devices

o Desktop, laptop, handheld

o Software clients

o Mobile services

· End user preparation and training

Clearly, the UC “how” will be the most difficult to do because it will be so dependent on individual enterprise operational business needs. “Best practices” can only be generalized and will still require the analyses to be done in a logical order. Also, because UC will be very software and application based, the technologies will be subject to ongoing evolutionary changes. So “change management” organizationally will be a key starting point that will always be needed.

Comments? Contact me at artr@ix.netcom.com

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • AVAYA Comments on Mobile UC Security Approach
    In response to my previous post and the reference to implementing application security for UC and multimodal smart-phone devices, Andy Zmol...
  • UC, Hyperconnectivity, Caller Text Messaging
    Copyright © 2007 Unified-View, All Rights Reserved Worldwide September 25, 2007 Why UC Needs “Hyperconnectivity” ...
  • Customer Satisfaction? UC Interaction Flexibility!
    By Art Rosenberg, The Unified-View / UC Strategies Expert   UC flexibility has always been more important for mobile users than for desktop...
  • UC Supports "Contextual" Contacts
    Copyright © 2012 The Unified-View, All Rights Reserved Worldwide February 24, 2012 The Heart of Business UC: “Contextual Contacts” B...
  • Business Users Want Their Own Smartphones For Both Company and Personal Use
    Copyright © 2010 The Unified-View, All Rights Reserved Worldwide January 10, 2010 Business Users Will Want Their Own Mobile “Smart-phones” F...
  • UC is More Than IP Telephony
    May 7, 2008 Confusion About IP Telephony vs. UC vs. Mobility vs. CEBP Art Rosenberg, The Unified-View Because the transition of ...
  • All Applications Can be "UC Enabled!"
    Copyright (C) Unified-View, All Rights Reserved. March 18, 2012 UC Is Not An Application! By Art Rosenberg, The Unified-View ...
  • The Third Business Communication Paradigm Shift – Using Search Technology to Contact People
    Copyright © 2006 Unified-View, All Rights Reserved Worldwide By Art Rosenberg, The Unified-View Business communication activity is compri...
  • Start UC Planning With " Business Performance ROI" (BPR)
    Copyright (C) Unified-View, All Rights Reserved. ãCopyright 2009, The Unified-View – All rights reserved worldwide August 26, 2009 UC “Perfo...
  • Enterprise Mobility Management For Shared, Personal Devices
    By Art Rosenberg, The Unified-View / UC Strategies Expert “Mobility” includes the different multi-modal mobile endpoint devices and the “mo...

Categories

  • analytics
  • ASAP Calling
  • contact center
  • contact center UC
  • Customer UC
  • Managing UC
  • Mobility
  • Smart-phones Affect Mobile UC
  • smartphones
  • TCO
  • TCU
  • UC
  • UC Analytics
  • UC Confusion
  • UC Cube

Blog Archive

  • ►  2013 (17)
    • ►  November (1)
    • ►  August (1)
    • ►  July (3)
    • ►  May (2)
    • ►  April (2)
    • ►  February (6)
    • ►  January (2)
  • ►  2012 (32)
    • ►  December (2)
    • ►  November (2)
    • ►  October (3)
    • ►  September (1)
    • ►  August (4)
    • ►  July (2)
    • ►  June (4)
    • ►  May (1)
    • ►  April (3)
    • ►  March (5)
    • ►  February (3)
    • ►  January (2)
  • ►  2011 (14)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  August (1)
    • ►  February (2)
  • ►  2010 (16)
    • ►  December (1)
    • ►  November (1)
    • ►  October (1)
    • ►  September (2)
    • ►  July (1)
    • ►  June (1)
    • ►  May (1)
    • ►  April (2)
    • ►  March (3)
    • ►  February (1)
    • ►  January (2)
  • ►  2009 (23)
    • ►  November (3)
    • ►  October (3)
    • ►  September (4)
    • ►  August (2)
    • ►  July (2)
    • ►  June (1)
    • ►  May (1)
    • ►  April (2)
    • ►  March (2)
    • ►  January (3)
  • ▼  2008 (39)
    • ►  December (1)
    • ►  November (3)
    • ►  October (3)
    • ►  September (2)
    • ►  August (5)
    • ►  July (4)
    • ►  June (1)
    • ►  May (3)
    • ►  April (5)
    • ►  March (6)
    • ▼  February (2)
      • What Do Users Really Want For Mobile UC?
      • UC Complexity; Who, What, Why, and How
    • ►  January (4)
  • ►  2007 (23)
    • ►  December (1)
    • ►  November (4)
    • ►  October (2)
    • ►  September (2)
    • ►  August (1)
    • ►  June (2)
    • ►  May (4)
    • ►  April (1)
    • ►  March (2)
    • ►  February (2)
    • ►  January (2)
  • ►  2006 (23)
    • ►  December (3)
    • ►  November (1)
    • ►  October (2)
    • ►  September (4)
    • ►  August (2)
    • ►  July (2)
    • ►  June (5)
    • ►  May (1)
    • ►  February (1)
    • ►  January (2)
Powered by Blogger.

About Me

Unknown
View my complete profile