<?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: Witnessing major process failure in action</title>
	<atom:link href="http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/</link>
	<description>A Blog about Enterprise BPM and Business Process Improvement by the folks at BP3</description>
	<lastBuildDate>Sun, 12 Feb 2012 05:30: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: Lance Gibbs</title>
		<link>http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/comment-page-1/#comment-69</link>
		<dc:creator>Lance Gibbs</dc:creator>
		<pubDate>Wed, 28 Jan 2009 17:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=411#comment-69</guid>
		<description>BUT, we can&#039;t give up. We just need to keep spreading the message and delivering the best solutions out there...always hoping the penny will finally drop for many of these companies and groups.</description>
		<content:encoded><![CDATA[<p>BUT, we can&#8217;t give up. We just need to keep spreading the message and delivering the best solutions out there&#8230;always hoping the penny will finally drop for many of these companies and groups.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lance Gibbs</title>
		<link>http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/comment-page-1/#comment-4567</link>
		<dc:creator>Lance Gibbs</dc:creator>
		<pubDate>Wed, 28 Jan 2009 17:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=411#comment-4567</guid>
		<description>BUT, we can&#039;t give up. We just need to keep spreading the message and delivering the best solutions out there...always hoping the penny will finally drop for many of these companies and groups.</description>
		<content:encoded><![CDATA[<p>BUT, we can&#8217;t give up. We just need to keep spreading the message and delivering the best solutions out there&#8230;always hoping the penny will finally drop for many of these companies and groups.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lance Gibbs</title>
		<link>http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/comment-page-1/#comment-68</link>
		<dc:creator>Lance Gibbs</dc:creator>
		<pubDate>Wed, 28 Jan 2009 17:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=411#comment-68</guid>
		<description>Your absolutely right Neil about culture. Question is, is it possible to fix things at a lower level without changing the culture. In my experience, absolutely, but can those &quot;fixes&quot; be sustained without changing the culture, no. Culture inevitably has to come along, problem is its like evolution...slow, painfully so much of the time. You just have to keep getting wins where you can and hope it comes along at the executive level. Logic makes people think (yes, we should invest in our customer) but emotion makes them act. In my view to get culture change to happen rapidly requires an event, something profound, &quot;shock and awe&quot; type of stuff. Unfortunately, those &quot;events&quot; are few and far between and are rarely positive ones...my two cents.</description>
		<content:encoded><![CDATA[<p>Your absolutely right Neil about culture. Question is, is it possible to fix things at a lower level without changing the culture. In my experience, absolutely, but can those &#8220;fixes&#8221; be sustained without changing the culture, no. Culture inevitably has to come along, problem is its like evolution&#8230;slow, painfully so much of the time. You just have to keep getting wins where you can and hope it comes along at the executive level. Logic makes people think (yes, we should invest in our customer) but emotion makes them act. In my view to get culture change to happen rapidly requires an event, something profound, &#8220;shock and awe&#8221; type of stuff. Unfortunately, those &#8220;events&#8221; are few and far between and are rarely positive ones&#8230;my two cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lance Gibbs</title>
		<link>http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/comment-page-1/#comment-4566</link>
		<dc:creator>Lance Gibbs</dc:creator>
		<pubDate>Wed, 28 Jan 2009 17:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=411#comment-4566</guid>
		<description>Your absolutely right Neil about culture. Question is, is it possible to fix things at a lower level without changing the culture. In my experience, absolutely, but can those &quot;fixes&quot; be sustained without changing the culture, no. Culture inevitably has to come along, problem is its like evolution...slow, painfully so much of the time. You just have to keep getting wins where you can and hope it comes along at the executive level. Logic makes people think (yes, we should invest in our customer) but emotion makes them act. In my view to get culture change to happen rapidly requires an event, something profound, &quot;shock and awe&quot; type of stuff. Unfortunately, those &quot;events&quot; are few and far between and are rarely positive ones...my two cents.</description>
		<content:encoded><![CDATA[<p>Your absolutely right Neil about culture. Question is, is it possible to fix things at a lower level without changing the culture. In my experience, absolutely, but can those &#8220;fixes&#8221; be sustained without changing the culture, no. Culture inevitably has to come along, problem is its like evolution&#8230;slow, painfully so much of the time. You just have to keep getting wins where you can and hope it comes along at the executive level. Logic makes people think (yes, we should invest in our customer) but emotion makes them act. In my view to get culture change to happen rapidly requires an event, something profound, &#8220;shock and awe&#8221; type of stuff. Unfortunately, those &#8220;events&#8221; are few and far between and are rarely positive ones&#8230;my two cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Ward-Dutton</title>
		<link>http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/comment-page-1/#comment-67</link>
		<dc:creator>Neil Ward-Dutton</dc:creator>
		<pubDate>Wed, 28 Jan 2009 10:47:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=411#comment-67</guid>
		<description>If I understand you right, Lance, then another way of looking at this problem is to think about the distinction between focusing on delivering a product, and focusing on delivering a service. What these companies seem to have done is to try to optimise around delivering a (one-off) product transaction, rather than seeing what most customers want, which is ongoing delivery of service across multiple transactions and interactions, over a considerable amount of time. 
This is a mistake that many many organisations make, and not only externally; it&#039;s also a problem that internal IT shops often have when dealing with their own &quot;customers&quot;. We&#039;re all in this to deliver service; the question is whether we know it or not.
Of course the failure to figure out the &quot;big picture&quot; of the service proposition is something that would have come from top-down culture... is it possible to fix the process and service delivery pieces in the middle and lower layers of such an organisation without addressing the kind of culture that will drive this kind of behaviour and narrow targets?</description>
		<content:encoded><![CDATA[<p>If I understand you right, Lance, then another way of looking at this problem is to think about the distinction between focusing on delivering a product, and focusing on delivering a service. What these companies seem to have done is to try to optimise around delivering a (one-off) product transaction, rather than seeing what most customers want, which is ongoing delivery of service across multiple transactions and interactions, over a considerable amount of time.<br />
This is a mistake that many many organisations make, and not only externally; it&#8217;s also a problem that internal IT shops often have when dealing with their own &#8220;customers&#8221;. We&#8217;re all in this to deliver service; the question is whether we know it or not.<br />
Of course the failure to figure out the &#8220;big picture&#8221; of the service proposition is something that would have come from top-down culture&#8230; is it possible to fix the process and service delivery pieces in the middle and lower layers of such an organisation without addressing the kind of culture that will drive this kind of behaviour and narrow targets?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Ward-Dutton</title>
		<link>http://www.bp-3.com/blogs/2009/01/witnessing-major-process-failure-in-action/comment-page-1/#comment-4565</link>
		<dc:creator>Neil Ward-Dutton</dc:creator>
		<pubDate>Wed, 28 Jan 2009 10:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.bp-3.com/blogs/?p=411#comment-4565</guid>
		<description>If I understand you right, Lance, then another way of looking at this problem is to think about the distinction between focusing on delivering a product, and focusing on delivering a service. What these companies seem to have done is to try to optimise around delivering a (one-off) product transaction, rather than seeing what most customers want, which is ongoing delivery of service across multiple transactions and interactions, over a considerable amount of time. 
This is a mistake that many many organisations make, and not only externally; it&#039;s also a problem that internal IT shops often have when dealing with their own &quot;customers&quot;. We&#039;re all in this to deliver service; the question is whether we know it or not.
Of course the failure to figure out the &quot;big picture&quot; of the service proposition is something that would have come from top-down culture... is it possible to fix the process and service delivery pieces in the middle and lower layers of such an organisation without addressing the kind of culture that will drive this kind of behaviour and narrow targets?</description>
		<content:encoded><![CDATA[<p>If I understand you right, Lance, then another way of looking at this problem is to think about the distinction between focusing on delivering a product, and focusing on delivering a service. What these companies seem to have done is to try to optimise around delivering a (one-off) product transaction, rather than seeing what most customers want, which is ongoing delivery of service across multiple transactions and interactions, over a considerable amount of time.<br />
This is a mistake that many many organisations make, and not only externally; it&#8217;s also a problem that internal IT shops often have when dealing with their own &#8220;customers&#8221;. We&#8217;re all in this to deliver service; the question is whether we know it or not.<br />
Of course the failure to figure out the &#8220;big picture&#8221; of the service proposition is something that would have come from top-down culture&#8230; is it possible to fix the process and service delivery pieces in the middle and lower layers of such an organisation without addressing the kind of culture that will drive this kind of behaviour and narrow targets?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

