<?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: Detailed case study of Twitter in the enterprise: Janssen-Cilag	</title>
	<atom:link href="https://rossdawson.com/detailed_case_s/feed/" rel="self" type="application/rss+xml" />
	<link>https://rossdawson.com/detailed_case_s/</link>
	<description>Keynote speaker &#124; Futurist &#124; Strategy advisor</description>
	<lastBuildDate>Thu, 23 Oct 2008 14:28:33 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Ross Dawson		</title>
		<link>https://rossdawson.com/detailed_case_s/#comment-447</link>

		<dc:creator><![CDATA[Ross Dawson]]></dc:creator>
		<pubDate>Thu, 23 Oct 2008 14:28:33 +0000</pubDate>
		<guid isPermaLink="false">http://rd.wpram.com/?p=617#comment-447</guid>

					<description><![CDATA[Hi Dirk, very interesting. I agree that categories and/ or tags are very important here, otherwise it feels (and is) unfocused...
]]></description>
			<content:encoded><![CDATA[<p>Hi Dirk, very interesting. I agree that categories and/ or tags are very important here, otherwise it feels (and is) unfocused&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dirk Röhrborn		</title>
		<link>https://rossdawson.com/detailed_case_s/#comment-446</link>

		<dc:creator><![CDATA[Dirk Röhrborn]]></dc:creator>
		<pubDate>Thu, 23 Oct 2008 14:06:46 +0000</pubDate>
		<guid isPermaLink="false">http://rd.wpram.com/?p=617#comment-446</guid>

					<description><![CDATA[Thank&#039;s a lot for making the enterprise needs on microblogging so clear in the second part of your post. In my eyes companies not only need 140-character status updates. What is needed is (micro-)sharing of resonably long messages that are cleary connected to a business topic. This means to follow a topic-centric approach rather than the only people-centric approach of Twitter and its clones. We are currently rolling out communote.com that combines blogging with tagging and sharing in a secure way. We are excited to how the usages spreads in out own company and how we are all still learning what to use microblogs for. For us, the main use is in projectblogs as well as routine work documentation e.g. systems maintenance.
]]></description>
			<content:encoded><![CDATA[<p>Thank&#8217;s a lot for making the enterprise needs on microblogging so clear in the second part of your post. In my eyes companies not only need 140-character status updates. What is needed is (micro-)sharing of resonably long messages that are cleary connected to a business topic. This means to follow a topic-centric approach rather than the only people-centric approach of Twitter and its clones. We are currently rolling out communote.com that combines blogging with tagging and sharing in a secure way. We are excited to how the usages spreads in out own company and how we are all still learning what to use microblogs for. For us, the main use is in projectblogs as well as routine work documentation e.g. systems maintenance.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
