 




<?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: A spare second for Microsoft SharePoint</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/cio/a-spare-second-for-microsoft-sharepoint/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/cio/a-spare-second-for-microsoft-sharepoint/</link>
	<description>A SearchCIO-Midmarket.com blog</description>
	<lastBuildDate>Tue, 02 Apr 2013 15:16:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Robgray</title>
		<link>http://itknowledgeexchange.techtarget.com/cio/a-spare-second-for-microsoft-sharepoint/#comment-20</link>
		<dc:creator>Robgray</dc:creator>
		<pubDate>Tue, 10 Jun 2008 09:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/cio/a-spare-second-for-microsoft-sharepoint/#comment-20</guid>
		<description><![CDATA[Hi, Rob Gray from blueKiwi here. Just to clarify what we mean: in blueKiwi, ideas are shared in multiple communities. A large org will have many communities. Often these would end up being silos with no transparency. The aggregated view of conversations is a personalised view of everything that an end user has permissions to see, from the communities that they are a part of. If a community is private (for example perhaps the board will have a private community), these conversations are not shown (unless the person logging in belongs to the board community).  This type of capability is very useful for execs to get &quot;their finger on the pulse of the organisation&quot;, it&#039;s also useful for those people lower down the corporate ladder to get the visibility of management if they have a good idea, because the &#039;noisiest&#039; conversations are surfaced to the top. I find that often the best ideas come from people who may not be the most vocal, and certainly they come from people who are not senior managers.

The problem with most internal blogging tools is that you just end up with these isolated silos that not many people participate in.

useful?]]></description>
		<content:encoded><![CDATA[<p>Hi, Rob Gray from blueKiwi here. Just to clarify what we mean: in blueKiwi, ideas are shared in multiple communities. A large org will have many communities. Often these would end up being silos with no transparency. The aggregated view of conversations is a personalised view of everything that an end user has permissions to see, from the communities that they are a part of. If a community is private (for example perhaps the board will have a private community), these conversations are not shown (unless the person logging in belongs to the board community).  This type of capability is very useful for execs to get &#8220;their finger on the pulse of the organisation&#8221;, it&#8217;s also useful for those people lower down the corporate ladder to get the visibility of management if they have a good idea, because the &#8216;noisiest&#8217; conversations are surfaced to the top. I find that often the best ideas come from people who may not be the most vocal, and certainly they come from people who are not senior managers.</p>
<p>The problem with most internal blogging tools is that you just end up with these isolated silos that not many people participate in.</p>
<p>useful?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
