<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Unified Communications Dissent</title>
	<atom:link href="http://thethomashowecompany.com/353/unified-communications-dissent/feed" rel="self" type="application/rss+xml" />
	<link>http://thethomashowecompany.com/353/unified-communications-dissent</link>
	<description>Mashing Voice and Process without Mercy</description>
	<lastBuildDate>Thu, 08 Apr 2010 12:50:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Martin Geddes</title>
		<link>http://thethomashowecompany.com/353/unified-communications-dissent/comment-page-1#comment-380</link>
		<dc:creator>Martin Geddes</dc:creator>
		<pubDate>Sun, 17 Feb 2008 22:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://thethomashowecompany.com/353/unified-communications-dissent#comment-380</guid>
		<description>I&#039;d say that vendors fail to understand the value that users perceive in being able to partition their communications channels, and keep them separate.  There are obvious reasons why you wouldn&#039;t want an SMS every time you got a new email, but the same thinking usually finds flaws in almost every other example of cross-media unification.

Also, the idea that there&#039;s one &quot;right&quot; way of doing it strikes me as fundamentally false.  UC is an experience, not a product or service.  It&#039;s delivering the right things to each user as an individual.  The urge to build a monolithic application seems strong.  The reality is probably closer to a bunch of APIs into the underlying separate services, and then very lightweight point solutions to very specific business problems.

RIP UC, long live CEBP...?</description>
		<content:encoded><![CDATA[<p>I&#8217;d say that vendors fail to understand the value that users perceive in being able to partition their communications channels, and keep them separate.  There are obvious reasons why you wouldn&#8217;t want an SMS every time you got a new email, but the same thinking usually finds flaws in almost every other example of cross-media unification.</p>
<p>Also, the idea that there&#8217;s one &#8220;right&#8221; way of doing it strikes me as fundamentally false.  UC is an experience, not a product or service.  It&#8217;s delivering the right things to each user as an individual.  The urge to build a monolithic application seems strong.  The reality is probably closer to a bunch of APIs into the underlying separate services, and then very lightweight point solutions to very specific business problems.</p>
<p>RIP UC, long live CEBP&#8230;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
