<?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: What Will We Call BPM in 2018?</title>
	<atom:link href="http://blogs.gartner.com/dave_mccoy/2009/11/05/what-will-we-call-bpm-in-2018/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/dave_mccoy/2009/11/05/what-will-we-call-bpm-in-2018/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Fri, 04 Nov 2011 16:57:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Craig</title>
		<link>http://blogs.gartner.com/dave_mccoy/2009/11/05/what-will-we-call-bpm-in-2018/comment-page-1/#comment-3300</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Wed, 09 Dec 2009 06:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/dave_mccoy/2009/11/05/what-will-we-call-bpm-in-2018/#comment-3300</guid>
		<description>I would also prefer that it would be called workflow.  But it will probably have some totally unrelated yet marketable name.  Something along the lines of &quot;Uber Organisation Super Software 5000.0&quot;, &quot;Death Panther&quot; or silly acronymn like &quot;BART&quot;</description>
		<content:encoded><![CDATA[<p>I would also prefer that it would be called workflow.  But it will probably have some totally unrelated yet marketable name.  Something along the lines of &#8220;Uber Organisation Super Software 5000.0&#8243;, &#8220;Death Panther&#8221; or silly acronymn like &#8220;BART&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robby Slaughter</title>
		<link>http://blogs.gartner.com/dave_mccoy/2009/11/05/what-will-we-call-bpm-in-2018/comment-page-1/#comment-3259</link>
		<dc:creator>Robby Slaughter</dc:creator>
		<pubDate>Fri, 06 Nov 2009 22:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/dave_mccoy/2009/11/05/what-will-we-call-bpm-in-2018/#comment-3259</guid>
		<description>The biggest problem with BPM is that it&#039;s a TLA---a three letter acronym. Terms that are so complex they need to be shortened seem like they might be fluff or are at least unapproachable.

In our practice, we prefer the word &quot;workflow.&quot;  This term contains two smaller words, each of which are well understood. The connotation of &quot;work&quot; is effort, labor and exhaustion. The word &quot;flow&quot; makes us think of smooth, continuous movements and steady, inexorable progress.

Therefore &quot;work&quot; and &quot;flow&quot; seem a little contradictory when placed together, and in that contradiction there is appeal. Imagine if effort/labor/exhaustion was actually replaced by something smooth, continuous and progressive. Work would be not just about &lt;em&gt;producing&lt;/em&gt;, but about being &lt;em&gt;productive.&lt;/em&gt;

Workflow in 2018!</description>
		<content:encoded><![CDATA[<p>The biggest problem with BPM is that it&#8217;s a TLA&#8212;a three letter acronym. Terms that are so complex they need to be shortened seem like they might be fluff or are at least unapproachable.</p>
<p>In our practice, we prefer the word &#8220;workflow.&#8221;  This term contains two smaller words, each of which are well understood. The connotation of &#8220;work&#8221; is effort, labor and exhaustion. The word &#8220;flow&#8221; makes us think of smooth, continuous movements and steady, inexorable progress.</p>
<p>Therefore &#8220;work&#8221; and &#8220;flow&#8221; seem a little contradictory when placed together, and in that contradiction there is appeal. Imagine if effort/labor/exhaustion was actually replaced by something smooth, continuous and progressive. Work would be not just about <em>producing</em>, but about being <em>productive.</em></p>
<p>Workflow in 2018!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

