<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: 99 Ways to Influence Change, #12: Remove status quo enablers	</title>
	<atom:link href="https://www.enclaria.com/2010/05/18/99-ways-to-influence-change-12-remove-status-quo-enablers/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.enclaria.com/2010/05/18/99-ways-to-influence-change-12-remove-status-quo-enablers/</link>
	<description>Equipping individuals and teams to influence organizational change</description>
	<lastBuildDate>Thu, 17 Mar 2011 00:59:30 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.2</generator>
	<item>
		<title>
		By: Martin Fenwick		</title>
		<link>https://www.enclaria.com/2010/05/18/99-ways-to-influence-change-12-remove-status-quo-enablers/comment-page-1/#comment-288</link>

		<dc:creator><![CDATA[Martin Fenwick]]></dc:creator>
		<pubDate>Fri, 21 May 2010 23:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.enclaria.com/?p=2611#comment-288</guid>

					<description><![CDATA[Really important point Heather. I often say to my clients &#039;its called change not same for a reason&#039;. Change often falls down because day to day processes and systems reflect the past and not the desired future.
I also like to consider &#039;Unwritten Rules&#039; (I think Richard Argyris wrote a book on this). These are the unstated but well know &#039;how we do things around here&#039; often accidentally promoted by managers with personal preferences around reports, spreadsheets etc.]]></description>
			<content:encoded><![CDATA[<p>Really important point Heather. I often say to my clients &#8216;its called change not same for a reason&#8217;. Change often falls down because day to day processes and systems reflect the past and not the desired future.<br />
I also like to consider &#8216;Unwritten Rules&#8217; (I think Richard Argyris wrote a book on this). These are the unstated but well know &#8216;how we do things around here&#8217; often accidentally promoted by managers with personal preferences around reports, spreadsheets etc.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
