Well, it’s official.  Cisco, the company that rebranded all its voice communications gear “Unified Communications” a couple of years ago, has demoted the term.  The ascendant star is “Collaboration”.  And I got some of the reasoning directly from John Chambers.  Here’s the story.

I’m at the Cisco “Collaboration Summit” in San Francisco where analysts, consultants, partners, and others have gathered to hear all about what’s new on the horizon.  If the title of the event didn’t give us a clue, then Alan Cohen’s opening remarks skewered it.  Third (or so) in a list of Cisco’s ongoing commitments was this gem:  “[Cisco will demonstrate] continued leadership in unified communications and other collaboration categories.”  In other words, UC is demoted to being one of a number of items under a collaboration umbrella.

Those of us toiling in these fields tend to view it in reverse — collaboration acceleration is one of a number of use case application classes under a UC umbrella.  It’s not just semantics.  There are many kinds of unified communications that have nothing to do with collaboration.  There are few if any kinds of collaboration that don’t involve communications.

Clearly, the foreshadowing was there.  Here’s one example.  Cisco offers a very helpful array of technical newsletters on their subscription page.  As I was scanning the list a month ago, I came across the following listing for one of the newsletters:  “Cisco Collaboration Insights (formerly Unified Communications Insight)”

Blink.  Not even a wake and decent burial.

Back at the Collaboration Summit, I asked John Chambers about this shift in positioning.  He had graciously turned up at the evening reception following his remarks on the opening day of the Summit.  I had the opportunity speak with him before he was whisked to his next event.  I pointed out the impeccable logic about our views regarding which umbrella covers what.  He quickly pointed out that logic has little to do with it; marketing and stirring up customer interest does.

What he said was simple, “When I talk with CIOs and CEOs, no one gets very excited about ‘unified communications’.  But everyone is interested in ‘collaboration’!”  Case closed.

What I have long feared and written about seems to be coming to pass.  “Unified communications” has been linked, apparently at least in the minds of the executives John speaks to, with what we call UC-User.  UC-U is about enhancing an individual’s ability to control personal communications.  And perhaps many also feel that UC is more closely associated with voice, rather than data, communications.

But the benefit seen from enhancing individual communications is often thought of as vaguely improving productivity — too often quantified as the dreaded “saving 15 minutes per user per day.”  We’ve walked that road to nowhere before.  It’s especially treacherous in this economic climate.  And a big yawn for CXOs.

Focusing on UC-U misses the other set of use cases, UC-B.  These solutions enhance business processes, and case studies show that UC-B produces ten times to benefits potential of UC-U.

Have we reached a tipping point?  IBM has long spoken about “unified communications and collaboration”.  Avaya had separated UC from CEBP (“communications enabled business processes”).  Now Cisco’s move.

My view is that “unified communications” is still the best descriptor for the array of capabilities that is transforming business workflows and processes — for individuals, for workgroups, for departments, for entire enterprises, and extending to partners and customers.  In the rush for market dominance, let’s not complicate the job.

What do you think?

[For comprehensive coverage of Unified Communications visit our Content Partner – UCStrategies.com]

[Editor’s Note: This post originally written by Don Van Doren at our partner blog UC Strategies, and is reposted with permission. –mrh]