<?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: Quick Review of &#8220;Social #BPM&#8221;</title>
	<atom:link href="http://www.bp-3.com/blogs/2009/09/quick-review-of-social-bpm/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bp-3.com/blogs/2009/09/quick-review-of-social-bpm/</link>
	<description>A Blog about Enterprise BPM and Business Process Improvement by the folks at BP3</description>
	<lastBuildDate>Sat, 11 Feb 2012 20:01:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Scott Francis</title>
		<link>http://www.bp-3.com/blogs/2009/09/quick-review-of-social-bpm/comment-page-1/#comment-393</link>
		<dc:creator>Scott Francis</dc:creator>
		<pubDate>Fri, 25 Sep 2009 19:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1085#comment-393</guid>
		<description>Dick - 

I think you&#039;re right that it isn&#039;t always appropriate.  I think for the collaborative/consensus-building phases of defining the process, it is very appropriate - but during execution, it isn&#039;t clear that the &quot;social&quot; aspects add more value, rather than adding more risk.  And yet I can still come up with some interesting mashup use cases there - for example, interview feedback on a candidate; post-mortem on a sales process or other non-structured process; capturing tips-n-tricks for future users.</description>
		<content:encoded><![CDATA[<p>Dick &#8211; </p>
<p>I think you&#8217;re right that it isn&#8217;t always appropriate.  I think for the collaborative/consensus-building phases of defining the process, it is very appropriate &#8211; but during execution, it isn&#8217;t clear that the &#8220;social&#8221; aspects add more value, rather than adding more risk.  And yet I can still come up with some interesting mashup use cases there &#8211; for example, interview feedback on a candidate; post-mortem on a sales process or other non-structured process; capturing tips-n-tricks for future users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Francis</title>
		<link>http://www.bp-3.com/blogs/2009/09/quick-review-of-social-bpm/comment-page-1/#comment-4616</link>
		<dc:creator>Scott Francis</dc:creator>
		<pubDate>Fri, 25 Sep 2009 19:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1085#comment-4616</guid>
		<description>Dick - 

I think you&#039;re right that it isn&#039;t always appropriate.  I think for the collaborative/consensus-building phases of defining the process, it is very appropriate - but during execution, it isn&#039;t clear that the &quot;social&quot; aspects add more value, rather than adding more risk.  And yet I can still come up with some interesting mashup use cases there - for example, interview feedback on a candidate; post-mortem on a sales process or other non-structured process; capturing tips-n-tricks for future users.</description>
		<content:encoded><![CDATA[<p>Dick &#8211; </p>
<p>I think you&#8217;re right that it isn&#8217;t always appropriate.  I think for the collaborative/consensus-building phases of defining the process, it is very appropriate &#8211; but during execution, it isn&#8217;t clear that the &#8220;social&#8221; aspects add more value, rather than adding more risk.  And yet I can still come up with some interesting mashup use cases there &#8211; for example, interview feedback on a candidate; post-mortem on a sales process or other non-structured process; capturing tips-n-tricks for future users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Hirsch</title>
		<link>http://www.bp-3.com/blogs/2009/09/quick-review-of-social-bpm/comment-page-1/#comment-388</link>
		<dc:creator>Dick Hirsch</dc:creator>
		<pubDate>Fri, 25 Sep 2009 07:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1085#comment-388</guid>
		<description>I also view Social BPM as a positive development but I&#039;m reluctant to say that its usage is always appropriate. I&#039;m trying to discover exactly when and how such technology should be used. If used incorrectly, Social BPM could cause more harm than good and lead to inefficiency based on time lags, etc.  My blog series is an attempt to examine these issues in more detail. 

Dick</description>
		<content:encoded><![CDATA[<p>I also view Social BPM as a positive development but I&#8217;m reluctant to say that its usage is always appropriate. I&#8217;m trying to discover exactly when and how such technology should be used. If used incorrectly, Social BPM could cause more harm than good and lead to inefficiency based on time lags, etc.  My blog series is an attempt to examine these issues in more detail. </p>
<p>Dick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Hirsch</title>
		<link>http://www.bp-3.com/blogs/2009/09/quick-review-of-social-bpm/comment-page-1/#comment-4615</link>
		<dc:creator>Dick Hirsch</dc:creator>
		<pubDate>Fri, 25 Sep 2009 07:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1085#comment-4615</guid>
		<description>I also view Social BPM as a positive development but I&#039;m reluctant to say that its usage is always appropriate. I&#039;m trying to discover exactly when and how such technology should be used. If used incorrectly, Social BPM could cause more harm than good and lead to inefficiency based on time lags, etc.  My blog series is an attempt to examine these issues in more detail. 

Dick</description>
		<content:encoded><![CDATA[<p>I also view Social BPM as a positive development but I&#8217;m reluctant to say that its usage is always appropriate. I&#8217;m trying to discover exactly when and how such technology should be used. If used incorrectly, Social BPM could cause more harm than good and lead to inefficiency based on time lags, etc.  My blog series is an attempt to examine these issues in more detail. </p>
<p>Dick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Process for the Enterprise » Blog Archive » Quick Review of “Social #BPM” -- Topsy.com</title>
		<link>http://www.bp-3.com/blogs/2009/09/quick-review-of-social-bpm/comment-page-1/#comment-366</link>
		<dc:creator>Tweets that mention Process for the Enterprise » Blog Archive » Quick Review of “Social #BPM” -- Topsy.com</dc:creator>
		<pubDate>Tue, 22 Sep 2009 20:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=1085#comment-366</guid>
		<description>[...] This post was mentioned on Twitter by bp3 bpm. bp3 bpm said: Blog Post: Quick Review of &quot;Social #BPM&quot; http://bit.ly/9geC6 [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by bp3 bpm. bp3 bpm said: Blog Post: Quick Review of &quot;Social #BPM&quot; <a href="http://bit.ly/9geC6" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/bit.ly/9geC6?referer=');">http://bit.ly/9geC6</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

