<?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: A Toolbox Approach to BPM Methods is Best.</title>
	<atom:link href="http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Tue, 07 Feb 2012 18:21:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Sylvain Astier</title>
		<link>http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/comment-page-1/#comment-1819</link>
		<dc:creator>Sylvain Astier</dc:creator>
		<pubDate>Mon, 03 Aug 2009 23:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/#comment-1819</guid>
		<description>I am pro-toolbox as well. What you call the &quot;Pure Methods&quot; I regard as &quot;Raw Methods.&quot; For the creation of one&#039;s own toolbox, one must consider the input material. A wise man once said that previous success is a recipe for failure. The assumption is that a business is a chaotic environment and therefore similar causes might have extremely different consequences. So, intuitively, I would assume that every raw method needs further analysis and customization before it can be enacted and undergo improvement cycles.

Still, it is a difficult and context-dependent decision. For instance, in health care, they have to follow strict protocols, and as a patient I would feel much better if they weren’t locally interpreted and customized.

Sylvain Astier
Product Manager, BPM
Axway</description>
		<content:encoded><![CDATA[<p>I am pro-toolbox as well. What you call the &#8220;Pure Methods&#8221; I regard as &#8220;Raw Methods.&#8221; For the creation of one&#8217;s own toolbox, one must consider the input material. A wise man once said that previous success is a recipe for failure. The assumption is that a business is a chaotic environment and therefore similar causes might have extremely different consequences. So, intuitively, I would assume that every raw method needs further analysis and customization before it can be enacted and undergo improvement cycles.</p>
<p>Still, it is a difficult and context-dependent decision. For instance, in health care, they have to follow strict protocols, and as a patient I would feel much better if they weren’t locally interpreted and customized.</p>
<p>Sylvain Astier<br />
Product Manager, BPM<br />
Axway</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Sinur</title>
		<link>http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/comment-page-1/#comment-1706</link>
		<dc:creator>Jim Sinur</dc:creator>
		<pubDate>Fri, 17 Jul 2009 13:20:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/#comment-1706</guid>
		<description>Thomas,

I was talking more methods than tools, but I can see the same anology applying to tools. There are different kinds of BPM technologies, not just a BPMS. The latest features in the BPMSs are now supportnig a greater variety of process types going forward, however/ I am afraid of wholesale BPR as well, but some times it&#039;s necessary.

Jim</description>
		<content:encoded><![CDATA[<p>Thomas,</p>
<p>I was talking more methods than tools, but I can see the same anology applying to tools. There are different kinds of BPM technologies, not just a BPMS. The latest features in the BPMSs are now supportnig a greater variety of process types going forward, however/ I am afraid of wholesale BPR as well, but some times it&#8217;s necessary.</p>
<p>Jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas J. Olbrich</title>
		<link>http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/comment-page-1/#comment-1704</link>
		<dc:creator>Thomas J. Olbrich</dc:creator>
		<pubDate>Fri, 17 Jul 2009 07:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/jim_sinur/2009/07/16/a-toolbox-approach-to-bpm-methods-is-best/#comment-1704</guid>
		<description>Jim,
isn&#039;t the problem though that while many companies have become accomplished at using their BPM toolbox, they are starting to wonder if their tools are still the right ones?

I would have thought that a change of toolset - depending on what needs to be accomplished - might provide a better perspective than relying on tried and tested toolsets which don&#039;t adress current problems. 

The strategy of sticking to one toolset might explain the re-emergence of BPR, which sends shivers down my spine as this particular approach does anything but improve flexibility and allow for management of processes.

What&#039;s needed is more transparancy about which toolset to use under which circumstances. Otherwise any initiative is bound to create motion instead of progress.

(Just my two cents worth)

Thomas</description>
		<content:encoded><![CDATA[<p>Jim,<br />
isn&#8217;t the problem though that while many companies have become accomplished at using their BPM toolbox, they are starting to wonder if their tools are still the right ones?</p>
<p>I would have thought that a change of toolset &#8211; depending on what needs to be accomplished &#8211; might provide a better perspective than relying on tried and tested toolsets which don&#8217;t adress current problems. </p>
<p>The strategy of sticking to one toolset might explain the re-emergence of BPR, which sends shivers down my spine as this particular approach does anything but improve flexibility and allow for management of processes.</p>
<p>What&#8217;s needed is more transparancy about which toolset to use under which circumstances. Otherwise any initiative is bound to create motion instead of progress.</p>
<p>(Just my two cents worth)</p>
<p>Thomas</p>
]]></content:encoded>
	</item>
</channel>
</rss>

