<?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: Four Facets of Measuring Change	</title>
	<atom:link href="https://www.enclaria.com/2016/09/13/four-facets-of-measuring-change/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.enclaria.com/2016/09/13/four-facets-of-measuring-change/</link>
	<description>Equipping individuals and teams to influence organizational change</description>
	<lastBuildDate>Tue, 13 Sep 2016 21:23:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.2</generator>
	<item>
		<title>
		By: Michael Taylor		</title>
		<link>https://www.enclaria.com/2016/09/13/four-facets-of-measuring-change/comment-page-1/#comment-91906</link>

		<dc:creator><![CDATA[Michael Taylor]]></dc:creator>
		<pubDate>Tue, 13 Sep 2016 21:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.enclaria.com/?p=8117#comment-91906</guid>

					<description><![CDATA[Heather,

I enjoyed this article, thanks. 

For several reasons. In section 1. you also advocate the &#039;Ends vs. Means&#039; method that has a group first surface and agree on what outcomes they want to produce before jumping into what to do - (which is where most prefer to talk - actions). In SchellingPoint, users model this as Financial Outcomes and Non-Financial Outcomes. 

Regarding the changes, section 2, we found across the 118 business topics we&#039;ve currently templated that the average number of change types is 17; roles, skills, processes, technology, services, culture, governance, structure, finances, and many others.

One item I would add, to round this out as three pieces of comment :-), is that our users also calculate their Alignment Index - their &#039;leading indicator of the group&#039;s likelihood of coordinated action.&#039; As a predictive analytic, this enables program and change managers to proactively &#039;maximize alignment&#039; before inaction, delayed action, conflicting action, or errant action can occur.

Best,
Michael.]]></description>
			<content:encoded><![CDATA[<p>Heather,</p>
<p>I enjoyed this article, thanks. </p>
<p>For several reasons. In section 1. you also advocate the &#8216;Ends vs. Means&#8217; method that has a group first surface and agree on what outcomes they want to produce before jumping into what to do &#8211; (which is where most prefer to talk &#8211; actions). In SchellingPoint, users model this as Financial Outcomes and Non-Financial Outcomes. </p>
<p>Regarding the changes, section 2, we found across the 118 business topics we&#8217;ve currently templated that the average number of change types is 17; roles, skills, processes, technology, services, culture, governance, structure, finances, and many others.</p>
<p>One item I would add, to round this out as three pieces of comment :-), is that our users also calculate their Alignment Index &#8211; their &#8216;leading indicator of the group&#8217;s likelihood of coordinated action.&#8217; As a predictive analytic, this enables program and change managers to proactively &#8216;maximize alignment&#8217; before inaction, delayed action, conflicting action, or errant action can occur.</p>
<p>Best,<br />
Michael.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
