<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Why any collaboration strategy must include email</title>
	<atom:link href="http://blog.groupswim.com/2008/01/22/why-any-collaboration-strategy-must-include-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.groupswim.com/2008/01/22/why-any-collaboration-strategy-must-include-email/</link>
	<description>Thoughts on Collaboration, Enterprise 2.0, and SaaS</description>
	<lastBuildDate>Wed, 06 Jan 2010 14:38:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jason</title>
		<link>http://blog.groupswim.com/2008/01/22/why-any-collaboration-strategy-must-include-email/#comment-4</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Tue, 22 Jan 2008 23:00:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/2008/01/22/why-any-collaboration-strategy-must-include-email/#comment-4</guid>
		<description>Deano,

Thanks for the comment.  Your points are well taken.  We are trying to be very deliberate in what we add and when.  Our priorities have been very foundational thus far i.e. engaging and easy to use UI, semantic technology to make best use of the content, adding email in capability, etc.  We definitely want to add IM at some point in the future.  We are also looking at wikis, polls, and other features.  One idea based on your comments is if you are having a really great discussion about an issue, it would be great to schedule a meeting directly from the tool and add it to people&#039;s calendars.  Thanks again for the post and keep them coming.

Jason</description>
		<content:encoded><![CDATA[<p>Deano,</p>
<p>Thanks for the comment.  Your points are well taken.  We are trying to be very deliberate in what we add and when.  Our priorities have been very foundational thus far i.e. engaging and easy to use UI, semantic technology to make best use of the content, adding email in capability, etc.  We definitely want to add IM at some point in the future.  We are also looking at wikis, polls, and other features.  One idea based on your comments is if you are having a really great discussion about an issue, it would be great to schedule a meeting directly from the tool and add it to people&#8217;s calendars.  Thanks again for the post and keep them coming.</p>
<p>Jason</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deano</title>
		<link>http://blog.groupswim.com/2008/01/22/why-any-collaboration-strategy-must-include-email/#comment-3</link>
		<dc:creator>Deano</dc:creator>
		<pubDate>Tue, 22 Jan 2008 22:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/2008/01/22/why-any-collaboration-strategy-must-include-email/#comment-3</guid>
		<description>I agree about the significance of email, but I&#039;d actually extend this to apply to all &quot;data exchange protocol standards&quot;... If you need to communicate general information/URLs immediately, your tool should work with email or even IM to do so; If the information is date-based, please send it to my calendar (or email as an ical/vcal file)... I&#039;m sick of re-inventing the wheel for each web app I buy. And it&#039;s not just communication, but authentication, storage, ACLs, etc. If I&#039;m a small business, I may be really excited that your solution has everything in one place, but if I&#039;m a larger business (or a growing smaller business), I want OPTIONS. 

But, specifically with email: I certainly can only rarely convince my workers to use a new collaboration tool every few years (if that), and I have no control over my outside folk. To be able to have everyone feed my system using email, I can get the direct benefits of the tool/app myself, and show that off to convince people to join me... But, if they never do, I&#039;m not stuck. With good email integration, I can still gain the benefits of collaboration/project management whether my partners/clients/etc realize it&#039;s happening or not. 

At work, we were able to integrate a PM tool with a helpdesk and mailing list precisely because each tool could send things along an &quot;email chain&quot;. Would it be great to have all the features in one tool, just the way I want it? Sure! But, I like the flexibility that if a better helpdesk comes along, we can swap that piece out, with a minimal impact on the other parts.</description>
		<content:encoded><![CDATA[<p>I agree about the significance of email, but I&#8217;d actually extend this to apply to all &#8220;data exchange protocol standards&#8221;&#8230; If you need to communicate general information/URLs immediately, your tool should work with email or even IM to do so; If the information is date-based, please send it to my calendar (or email as an ical/vcal file)&#8230; I&#8217;m sick of re-inventing the wheel for each web app I buy. And it&#8217;s not just communication, but authentication, storage, ACLs, etc. If I&#8217;m a small business, I may be really excited that your solution has everything in one place, but if I&#8217;m a larger business (or a growing smaller business), I want OPTIONS. </p>
<p>But, specifically with email: I certainly can only rarely convince my workers to use a new collaboration tool every few years (if that), and I have no control over my outside folk. To be able to have everyone feed my system using email, I can get the direct benefits of the tool/app myself, and show that off to convince people to join me&#8230; But, if they never do, I&#8217;m not stuck. With good email integration, I can still gain the benefits of collaboration/project management whether my partners/clients/etc realize it&#8217;s happening or not. </p>
<p>At work, we were able to integrate a PM tool with a helpdesk and mailing list precisely because each tool could send things along an &#8220;email chain&#8221;. Would it be great to have all the features in one tool, just the way I want it? Sure! But, I like the flexibility that if a better helpdesk comes along, we can swap that piece out, with a minimal impact on the other parts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
