<?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: Tag-Based Workflow</title>
	<atom:link href="http://blog.groupswim.com/2008/06/18/tag-based-workflow/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.groupswim.com/2008/06/18/tag-based-workflow/</link>
	<description>Thoughts on Collaboration, Enterprise 2.0, and SaaS</description>
	<lastBuildDate>Wed, 06 Jan 2010 14:38:35 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason</title>
		<link>http://blog.groupswim.com/2008/06/18/tag-based-workflow/#comment-142</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 25 Jun 2008 00:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://groupswim.wordpress.com/?p=70#comment-142</guid>
		<description>Thorsten,

I appreciate the feedback.  I do think this would require discipline, but it could be useful for small teams as a precursor to other things we do in the future.

I actually see the mixture of files and discussions across groups as a plus, not a minus.  In this case, if I was assigned or managing multiple items, I could cut across all of them using the tags.  You can also predefine and prioritize tags using our tag training so this will help as well.

I&#039;ll pass on more as we give it a shot.  Please share your experience as well if you try it.  I&#039;m happy to brainstorm with you if you are interested.

Jason</description>
		<content:encoded><![CDATA[<p>Thorsten,</p>
<p>I appreciate the feedback.  I do think this would require discipline, but it could be useful for small teams as a precursor to other things we do in the future.</p>
<p>I actually see the mixture of files and discussions across groups as a plus, not a minus.  In this case, if I was assigned or managing multiple items, I could cut across all of them using the tags.  You can also predefine and prioritize tags using our tag training so this will help as well.</p>
<p>I&#8217;ll pass on more as we give it a shot.  Please share your experience as well if you try it.  I&#8217;m happy to brainstorm with you if you are interested.</p>
<p>Jason</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thorsten Arndt</title>
		<link>http://blog.groupswim.com/2008/06/18/tag-based-workflow/#comment-141</link>
		<dc:creator>Thorsten Arndt</dc:creator>
		<pubDate>Tue, 24 Jun 2008 16:36:41 +0000</pubDate>
		<guid isPermaLink="false">http://groupswim.wordpress.com/?p=70#comment-141</guid>
		<description>Curious about your experience... I see too major faults: 
a) It requires too much discipline
b) any kind of &quot;Discussion&quot; or &quot;File&quot; that I apply this too will be mixed up with other topics. Obviously, I could use a separate group for &quot;Task&quot;, but why would I want to separate a task from the group that it belongs to?

One option that might work: Add a new section in a group called &quot;Tasks&quot;, and then allow the manager to be more rigid in terms of tagging, e.g. allowing him/her to predefine tags without the option for users to add tags... not sure whether this would work as I&#039;ve never worked anywhere where a task mgmt system was employeed... just a thought...</description>
		<content:encoded><![CDATA[<p>Curious about your experience&#8230; I see too major faults:<br />
a) It requires too much discipline<br />
b) any kind of &#8220;Discussion&#8221; or &#8220;File&#8221; that I apply this too will be mixed up with other topics. Obviously, I could use a separate group for &#8220;Task&#8221;, but why would I want to separate a task from the group that it belongs to?</p>
<p>One option that might work: Add a new section in a group called &#8220;Tasks&#8221;, and then allow the manager to be more rigid in terms of tagging, e.g. allowing him/her to predefine tags without the option for users to add tags&#8230; not sure whether this would work as I&#8217;ve never worked anywhere where a task mgmt system was employeed&#8230; just a thought&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
