<?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: How Delays Affect Processes and Change</title>
	<atom:link href="http://www.bizmanualz.com/information/2005/03/24/how-delays-affect-processes-and-change.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.bizmanualz.com/information/2005/03/24/how-delays-affect-processes-and-change.html</link>
	<description>Articles, tips and helpful information on Policies, Procedures and Processes</description>
	<lastBuildDate>Mon, 06 Feb 2012 17:47:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Bizmanualz</title>
		<link>http://www.bizmanualz.com/information/2005/03/24/how-delays-affect-processes-and-change.html/comment-page-1#comment-31442</link>
		<dc:creator>Bizmanualz</dc:creator>
		<pubDate>Wed, 07 Nov 2007 21:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bizmanualz.com/blog/?p=49#comment-31442</guid>
		<description>Continual improvement strongly implies change management.  In other words, for any organization to continually improve itself, it has to accept change as the norm.  There is no getting around that.  The whole point is to improve incrementally; another way to put that is &quot;to manage change&quot;.

The ISO 9001 standard states (in section 8.5.1) that &quot;(t)he organization shall continually improve the effectiveness of the quality management system...&quot;.  Though it doesn&#039;t come out and say it, QMS implementation and change management do go hand-in-hand.  You can&#039;t have one without the other.  Similarly, neither concept is more important than -- or subordinate to -- the other.</description>
		<content:encoded><![CDATA[<p>Continual improvement strongly implies change management.  In other words, for any organization to continually improve itself, it has to accept change as the norm.  There is no getting around that.  The whole point is to improve incrementally; another way to put that is &#8220;to manage change&#8221;.</p>
<p>The ISO 9001 standard states (in section 8.5.1) that &#8220;(t)he organization shall continually improve the effectiveness of the quality management system&#8230;&#8221;.  Though it doesn&#8217;t come out and say it, QMS implementation and change management do go hand-in-hand.  You can&#8217;t have one without the other.  Similarly, neither concept is more important than &#8212; or subordinate to &#8212; the other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Eysink</title>
		<link>http://www.bizmanualz.com/information/2005/03/24/how-delays-affect-processes-and-change.html/comment-page-1#comment-27722</link>
		<dc:creator>Paul Eysink</dc:creator>
		<pubDate>Wed, 05 Sep 2007 06:42:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.bizmanualz.com/blog/?p=49#comment-27722</guid>
		<description>What a brilliant series! The issue of change management is so often over-looked when implementing a QMS, and yet the requirement is a given. I have also ready your articles on implementing a QMS, but perhaps one should consider the implementation more of a change management exercise than a formal implementation? Perhaps this can help avoid the risk of Task Layering during implementation.</description>
		<content:encoded><![CDATA[<p>What a brilliant series! The issue of change management is so often over-looked when implementing a QMS, and yet the requirement is a given. I have also ready your articles on implementing a QMS, but perhaps one should consider the implementation more of a change management exercise than a formal implementation? Perhaps this can help avoid the risk of Task Layering during implementation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

