<?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: Three Tips for Implementing Change Across Functions	</title>
	<atom:link href="https://www.enclaria.com/2017/04/11/three-tips-for-implementing-change-across-functions/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.enclaria.com/2017/04/11/three-tips-for-implementing-change-across-functions/</link>
	<description>Equipping individuals and teams to influence organizational change</description>
	<lastBuildDate>Thu, 13 Apr 2017 11:59:07 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.2</generator>
	<item>
		<title>
		By: gail severini		</title>
		<link>https://www.enclaria.com/2017/04/11/three-tips-for-implementing-change-across-functions/comment-page-1/#comment-96157</link>

		<dc:creator><![CDATA[gail severini]]></dc:creator>
		<pubDate>Thu, 13 Apr 2017 11:59:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.enclaria.com/?p=8459#comment-96157</guid>

					<description><![CDATA[Another great post Heather.  Your photo made me squeamish but your suggestions calmed me down.  Love the practicality of the tactics.  Great comments from others as well.]]></description>
			<content:encoded><![CDATA[<p>Another great post Heather.  Your photo made me squeamish but your suggestions calmed me down.  Love the practicality of the tactics.  Great comments from others as well.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael Taylor		</title>
		<link>https://www.enclaria.com/2017/04/11/three-tips-for-implementing-change-across-functions/comment-page-1/#comment-96138</link>

		<dc:creator><![CDATA[Michael Taylor]]></dc:creator>
		<pubDate>Tue, 11 Apr 2017 22:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.enclaria.com/?p=8459#comment-96138</guid>

					<description><![CDATA[Heather,
To build on your advice on &#039;how&#039; to do these things, practitioners should note that resistance in interdependent change is of two types - Barriers, and Unintended consequences. 

To use your example, in a supply chain transformation project, where the consultant was using Advanced Management Consulting, the supply chain, procurement, finance, R&#038;D, and other functions expressed 48 Barriers to a successful program and 13 concerns for Unintended consequences. 

Barriers: 
- They all agreed on 5 of them and quickly identified mitigating solutions. 
- Of the 43 concerns (48-5) around which they were misaligned, they triaged 27 where they said: &quot;We need to come to an agreement whether or not these are barriers.&quot; 
- Of these 27, 4 were invalidated, (insufficient reasoning was expressed to validate them even using virtual reasoning input forms.)
- 11 were validated and mitigating actions designed. 
- The last 12 (27-4-11) were taken from &quot;You think this is a barrier, well we don&#039;t.&quot; to &quot;We all agree that will be a barrier.&quot; then mitigating actions created.
i.e. Every concern was 1. surfaced, 2. validated, 3. misalignment reconciled, then 4. mitigated if valid. 

The same process was used on the 13 concerns for Unintended consequences expressed as...&quot;You want to do x. but if you do, that will hurt me/us/them in this way.&quot;  

The other key point here is that just working on one or two items is valuable but insufficient. The volume of Barriers and Unintendeds referenced above is typical. Facilitation that resolves single digit concerns feels good but rarely created genuine, full endorsement. 

Great article.
Michael]]></description>
			<content:encoded><![CDATA[<p>Heather,<br />
To build on your advice on &#8216;how&#8217; to do these things, practitioners should note that resistance in interdependent change is of two types &#8211; Barriers, and Unintended consequences. </p>
<p>To use your example, in a supply chain transformation project, where the consultant was using Advanced Management Consulting, the supply chain, procurement, finance, R&amp;D, and other functions expressed 48 Barriers to a successful program and 13 concerns for Unintended consequences. </p>
<p>Barriers:<br />
&#8211; They all agreed on 5 of them and quickly identified mitigating solutions.<br />
&#8211; Of the 43 concerns (48-5) around which they were misaligned, they triaged 27 where they said: &#8220;We need to come to an agreement whether or not these are barriers.&#8221;<br />
&#8211; Of these 27, 4 were invalidated, (insufficient reasoning was expressed to validate them even using virtual reasoning input forms.)<br />
&#8211; 11 were validated and mitigating actions designed.<br />
&#8211; The last 12 (27-4-11) were taken from &#8220;You think this is a barrier, well we don&#8217;t.&#8221; to &#8220;We all agree that will be a barrier.&#8221; then mitigating actions created.<br />
i.e. Every concern was 1. surfaced, 2. validated, 3. misalignment reconciled, then 4. mitigated if valid. </p>
<p>The same process was used on the 13 concerns for Unintended consequences expressed as&#8230;&#8221;You want to do x. but if you do, that will hurt me/us/them in this way.&#8221;  </p>
<p>The other key point here is that just working on one or two items is valuable but insufficient. The volume of Barriers and Unintendeds referenced above is typical. Facilitation that resolves single digit concerns feels good but rarely created genuine, full endorsement. </p>
<p>Great article.<br />
Michael</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Marti Fenwick		</title>
		<link>https://www.enclaria.com/2017/04/11/three-tips-for-implementing-change-across-functions/comment-page-1/#comment-96135</link>

		<dc:creator><![CDATA[Marti Fenwick]]></dc:creator>
		<pubDate>Tue, 11 Apr 2017 20:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.enclaria.com/?p=8459#comment-96135</guid>

					<description><![CDATA[&#039; What gets measured gets done&#039; doesn&#039;t it, so a good CEO will see the need for cross boundary change, and set it up that way including adjustment of measures for both parts of the organisation. Part of the problem of not being interested or not making change a priority is that they are still chasing existing results I.e measures, that haven&#039;t been changed. Only the most agile can keep BAU going and implement change, but the bigger the change is the harder that is even if your organisation is naturally agile. So instead of change being delivered on hope, set the measures up, align them to those goals Heather mentions and then start talking about how to fix the problem.]]></description>
			<content:encoded><![CDATA[<p>&#8216; What gets measured gets done&#8217; doesn&#8217;t it, so a good CEO will see the need for cross boundary change, and set it up that way including adjustment of measures for both parts of the organisation. Part of the problem of not being interested or not making change a priority is that they are still chasing existing results I.e measures, that haven&#8217;t been changed. Only the most agile can keep BAU going and implement change, but the bigger the change is the harder that is even if your organisation is naturally agile. So instead of change being delivered on hope, set the measures up, align them to those goals Heather mentions and then start talking about how to fix the problem.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
