<?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: Should Collaborations Be Organic or Institutional?</title>
	<atom:link href="http://blog.digidave.org/2010/06/should-collaborations-be-organic-or-institutional/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.digidave.org/2010/06/should-collaborations-be-organic-or-institutional</link>
	<description>Journalism is a Process, Not a Product</description>
	<lastBuildDate>Mon, 30 Jan 2012 12:45:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Social Hour follow-up: Links and resources &#171; Digital Journalism Portland</title>
		<link>http://blog.digidave.org/2010/06/should-collaborations-be-organic-or-institutional/comment-page-1#comment-67069</link>
		<dc:creator>Social Hour follow-up: Links and resources &#171; Digital Journalism Portland</dc:creator>
		<pubDate>Wed, 17 Nov 2010 20:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digidave.org/?p=2438#comment-67069</guid>
		<description>[...] digidave.org: Should Collaborations Be Organic or Institutional?  [...]</description>
		<content:encoded><![CDATA[<p>[...] digidave.org: Should Collaborations Be Organic or Institutional?  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everything Old is New Again &#171; Groundswell</title>
		<link>http://blog.digidave.org/2010/06/should-collaborations-be-organic-or-institutional/comment-page-1#comment-66503</link>
		<dc:creator>Everything Old is New Again &#171; Groundswell</dc:creator>
		<pubDate>Fri, 09 Jul 2010 18:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digidave.org/?p=2438#comment-66503</guid>
		<description>[...] the recent Future of News and Civic Media conference at MIT, I led a discussion on journalism collaborations. Scott Rosenberg, the co-founder of Salon, captured the tone of the [...]</description>
		<content:encoded><![CDATA[<p>[...] the recent Future of News and Civic Media conference at MIT, I led a discussion on journalism collaborations. Scott Rosenberg, the co-founder of Salon, captured the tone of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Smith</title>
		<link>http://blog.digidave.org/2010/06/should-collaborations-be-organic-or-institutional/comment-page-1#comment-66436</link>
		<dc:creator>Phillip Smith</dc:creator>
		<pubDate>Wed, 23 Jun 2010 19:18:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digidave.org/?p=2438#comment-66436</guid>
		<description>Great summary, Dave. Many thanks for putting this post together. 

Phillip.</description>
		<content:encoded><![CDATA[<p>Great summary, Dave. Many thanks for putting this post together. </p>
<p>Phillip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne-Marie McReynolds</title>
		<link>http://blog.digidave.org/2010/06/should-collaborations-be-organic-or-institutional/comment-page-1#comment-66435</link>
		<dc:creator>Anne-Marie McReynolds</dc:creator>
		<pubDate>Tue, 22 Jun 2010 23:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digidave.org/?p=2438#comment-66435</guid>
		<description>Prioritizing collaboration over specialization prevents professionals from developing expertise. Author Morten Hansen argues in “Collaboration” that sometimes the goal of collaboration is collaboration in and of itself—which is dead wrong. Too many communities of practice translate to collaboration run amok. As Hansen states, the first rule of good collaboration entails evaluating whether or not there is a compelling benefit to working together. Hansen advocates saying no to projects that offer no ROI.

Hansen, Morten. 2009. Collaboration: How Leaders Avoid the Traps, Create Unity, and Reap Big Results
 http://bit.ly/cV4NyF</description>
		<content:encoded><![CDATA[<p>Prioritizing collaboration over specialization prevents professionals from developing expertise. Author Morten Hansen argues in “Collaboration” that sometimes the goal of collaboration is collaboration in and of itself—which is dead wrong. Too many communities of practice translate to collaboration run amok. As Hansen states, the first rule of good collaboration entails evaluating whether or not there is a compelling benefit to working together. Hansen advocates saying no to projects that offer no ROI.</p>
<p>Hansen, Morten. 2009. Collaboration: How Leaders Avoid the Traps, Create Unity, and Reap Big Results<br />
 <a href="http://bit.ly/cV4NyF" rel="nofollow">http://bit.ly/cV4NyF</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne-Marie McReynolds</title>
		<link>http://blog.digidave.org/2010/06/should-collaborations-be-organic-or-institutional/comment-page-1#comment-66434</link>
		<dc:creator>Anne-Marie McReynolds</dc:creator>
		<pubDate>Tue, 22 Jun 2010 23:53:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digidave.org/?p=2438#comment-66434</guid>
		<description>Prioritizing collaboration over specialization prevents professionals from developing expertise. Author Morten Hansen argues in &quot;Collaboration&quot; that sometimes the goal of collaboration is collaboration in and of itself—which is dead wrong. Too many communities of practice translate to collaboration run amok. As Hansen states, the first rule of good collaboration entails evaluating whether or not there is a compelling benefit to working together. Hansen advocates saying no to projects that offer no ROI. 

Source: http://bit.ly/cV4NyF</description>
		<content:encoded><![CDATA[<p>Prioritizing collaboration over specialization prevents professionals from developing expertise. Author Morten Hansen argues in &#8220;Collaboration&#8221; that sometimes the goal of collaboration is collaboration in and of itself—which is dead wrong. Too many communities of practice translate to collaboration run amok. As Hansen states, the first rule of good collaboration entails evaluating whether or not there is a compelling benefit to working together. Hansen advocates saying no to projects that offer no ROI. </p>
<p>Source: <a href="http://bit.ly/cV4NyF" rel="nofollow">http://bit.ly/cV4NyF</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

