<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: When Will The Enterprise 2.0 Workflow Take Hold?</title>
	<atom:link href="http://www.fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/</link>
	<description></description>
	<lastBuildDate>Fri, 20 Nov 2009 20:29:35 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bill Ives</title>
		<link>http://www.fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/comment-page-1/#comment-22</link>
		<dc:creator>Bill Ives</dc:creator>
		<pubDate>Thu, 21 Dec 2006 21:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/#comment-22</guid>
		<description>I agree with the great blog comment. In the early 90s when I first got involved with what became to be called knowledge management, we were designing new workflows for insurance underwriting and claims processing. Then we decided that these underwriters and claims agents needed access to the necessary documents and resources (experts) aligned with each step in the work processes. We used old stye technology (Visual Basic front end) to align these resources with the workflow. It was very popular with the people who used the system, especially since we asked them what documents they needed. Then the term knowledge management came out and we thought that was what we were doing so we used that term. I got excited about the possibiities  I was later disappointed to see the term used for siloed document repositories. It is the alignment with workprocesses that will drive integration and the tools are so much more powerful now. As you said, &quot;a delicious widget setting nicely beside say, a sales order.&quot; I have regained my excitment. Thanks.</description>
		<content:encoded><![CDATA[<p>I agree with the great blog comment. In the early 90s when I first got involved with what became to be called knowledge management, we were designing new workflows for insurance underwriting and claims processing. Then we decided that these underwriters and claims agents needed access to the necessary documents and resources (experts) aligned with each step in the work processes. We used old stye technology (Visual Basic front end) to align these resources with the workflow. It was very popular with the people who used the system, especially since we asked them what documents they needed. Then the term knowledge management came out and we thought that was what we were doing so we used that term. I got excited about the possibiities  I was later disappointed to see the term used for siloed document repositories. It is the alignment with workprocesses that will drive integration and the tools are so much more powerful now. As you said, &#8220;a delicious widget setting nicely beside say, a sales order.&#8221; I have regained my excitment. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Dearing</title>
		<link>http://www.fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/comment-page-1/#comment-21</link>
		<dc:creator>George Dearing</dc:creator>
		<pubDate>Thu, 21 Dec 2006 20:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/#comment-21</guid>
		<description>Very simply and effectively put Nic. My fear however is quantifying the usage. Do we really have to do a web 2.o show-and-tell for IT? I&#039;m relying on guys like you to champion the cause. Part of your effort, like it or not,will be helping your company (and clients) make sure they make the right choices when choosing vendors. You can&#039;t get away from the fact (especially in the enterprise) that many of the big vendors will drive user adoption just by virtue of critical mass.</description>
		<content:encoded><![CDATA[<p>Very simply and effectively put Nic. My fear however is quantifying the usage. Do we really have to do a web 2.o show-and-tell for IT? I&#8217;m relying on guys like you to champion the cause. Part of your effort, like it or not,will be helping your company (and clients) make sure they make the right choices when choosing vendors. You can&#8217;t get away from the fact (especially in the enterprise) that many of the big vendors will drive user adoption just by virtue of critical mass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nic Brisbourne</title>
		<link>http://www.fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/comment-page-1/#comment-19</link>
		<dc:creator>Nic Brisbourne</dc:creator>
		<pubDate>Thu, 21 Dec 2006 18:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2006/12/20/when-will-the-enterprise-20-workflow-take-hold/#comment-19</guid>
		<description>Great blog.

Enterprises and traditional enterprise IT vendors will take e2.0 seriously when lots of people are using it.  Driving bottom up adoption is the anser here IMHO.  It may be that the notion of people determining their own IT environment is so antithetical to IT Directors and trad IT vendors that until the evidence that people use it and it works is staring them in the face they won&#039;t believe.</description>
		<content:encoded><![CDATA[<p>Great blog.</p>
<p>Enterprises and traditional enterprise IT vendors will take e2.0 seriously when lots of people are using it.  Driving bottom up adoption is the anser here IMHO.  It may be that the notion of people determining their own IT environment is so antithetical to IT Directors and trad IT vendors that until the evidence that people use it and it works is staring them in the face they won&#8217;t believe.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
