<?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: links for 2009-04-22</title>
	<atom:link href="http://www.column2.com/2009/04/links-for-2009-04-22/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.column2.com/2009/04/links-for-2009-04-22/</link>
	<description>BPM, Enterprise 2.0 and technology trends in business.</description>
	<lastBuildDate>Fri, 20 Jan 2012 09:15:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tom Shepherd</title>
		<link>http://www.column2.com/2009/04/links-for-2009-04-22/comment-page-1/#comment-11115</link>
		<dc:creator>Tom Shepherd</dc:creator>
		<pubDate>Thu, 23 Apr 2009 14:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.column2.com/2009/04/links-for-2009-04-22/#comment-11115</guid>
		<description>I happen to agree on the increased buzz around dynamic processes.  I don&#039;t think it has as much to do with reduced workforces (as Sandy states) but less &quot;low hanging fruit&quot;.  Repeatable processes that are well documented tend to be easier to automate.  Dynamic (or unstructured, ad-hoc, etc) processes tend to be a lot harder to codify by nature, so companies seem to have optimized the easier ones first.  With those efficiency gains under their proverbial belts, they have nowhere to turn but to the more complex problems to try and shave cost and increase productivity.</description>
		<content:encoded><![CDATA[<p>I happen to agree on the increased buzz around dynamic processes.  I don&#8217;t think it has as much to do with reduced workforces (as Sandy states) but less &#8220;low hanging fruit&#8221;.  Repeatable processes that are well documented tend to be easier to automate.  Dynamic (or unstructured, ad-hoc, etc) processes tend to be a lot harder to codify by nature, so companies seem to have optimized the easier ones first.  With those efficiency gains under their proverbial belts, they have nowhere to turn but to the more complex problems to try and shave cost and increase productivity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy Kemsley</title>
		<link>http://www.column2.com/2009/04/links-for-2009-04-22/comment-page-1/#comment-11114</link>
		<dc:creator>Sandy Kemsley</dc:creator>
		<pubDate>Thu, 23 Apr 2009 13:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.column2.com/2009/04/links-for-2009-04-22/#comment-11114</guid>
		<description>Chris, the article states that &quot;We caution ITOs and business professionals to ensure they pay close attention to the importance of designing process models that accurately reflect how work ‘really gets done&#039;-or how it will be done if the process includes moving to a ‘to be&#039; state of improvement.&quot; -- not exactly breaking news. I agree with your point about dynamic processes, but I&#039;m not sure that reduced workforces will result in more unstructured process needs: in general, as people have to pick up tasks that were done by their former colleagues, they may need a more structured process to ensure that it&#039;s done correctly since they are not as familiar with the process.</description>
		<content:encoded><![CDATA[<p>Chris, the article states that &#8220;We caution ITOs and business professionals to ensure they pay close attention to the importance of designing process models that accurately reflect how work ‘really gets done&#8217;-or how it will be done if the process includes moving to a ‘to be&#8217; state of improvement.&#8221; &#8212; not exactly breaking news. I agree with your point about dynamic processes, but I&#8217;m not sure that reduced workforces will result in more unstructured process needs: in general, as people have to pick up tasks that were done by their former colleagues, they may need a more structured process to ensure that it&#8217;s done correctly since they are not as familiar with the process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Adams</title>
		<link>http://www.column2.com/2009/04/links-for-2009-04-22/comment-page-1/#comment-11109</link>
		<dc:creator>Chris Adams</dc:creator>
		<pubDate>Wed, 22 Apr 2009 17:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.column2.com/2009/04/links-for-2009-04-22/#comment-11109</guid>
		<description>Sandy, here is another recent post on how processes should ideally have traits of being &quot;defined&quot; and &quot;dynamic&quot;.

http://www.it-director.com/enterprise/technology/content.php?cid=11201

I am seeing the topic of &quot;dynamic&quot; processes having quite a buzz as of late.  Process modeling and process discovery has always had great value and is practiced by many.  But I have to also wonder if today&#039;s reduced workforce in a company, resulting in more people wearing multiple hats, is resulting in greater reliance in &quot;unstructured&quot; process needs.</description>
		<content:encoded><![CDATA[<p>Sandy, here is another recent post on how processes should ideally have traits of being &#8220;defined&#8221; and &#8220;dynamic&#8221;.</p>
<p><a href="http://www.it-director.com/enterprise/technology/content.php?cid=11201" rel="nofollow">http://www.it-director.com/enterprise/technology/content.php?cid=11201</a></p>
<p>I am seeing the topic of &#8220;dynamic&#8221; processes having quite a buzz as of late.  Process modeling and process discovery has always had great value and is practiced by many.  But I have to also wonder if today&#8217;s reduced workforce in a company, resulting in more people wearing multiple hats, is resulting in greater reliance in &#8220;unstructured&#8221; process needs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

