<?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 Fundamental Responses to Change	</title>
	<atom:link href="https://www.enclaria.com/2019/12/10/four-fundamental-responses-to-change/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.enclaria.com/2019/12/10/four-fundamental-responses-to-change/</link>
	<description>Equipping individuals and teams to influence organizational change</description>
	<lastBuildDate>Tue, 17 Dec 2019 16:43:58 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.5.2</generator>
	<item>
		<title>
		By: Ada Crenshaw		</title>
		<link>https://www.enclaria.com/2019/12/10/four-fundamental-responses-to-change/comment-page-1/#comment-159944</link>

		<dc:creator><![CDATA[Ada Crenshaw]]></dc:creator>
		<pubDate>Tue, 17 Dec 2019 16:43:58 +0000</pubDate>
		<guid isPermaLink="false">https://www.enclaria.com/?p=19462#comment-159944</guid>

					<description><![CDATA[What Iâ€™ve come across in the 20 years in my industry is attachment and doubt.  When people have been using a certain type of software application for several years or more, they become comfortable with their job and what they do. When they hear of a change coming, letâ€™s say a new software change (example: Windows), they instantly think â€œWhat am I not going to be able to find now??â€ The fear of the unknown is all too familiar.  

[In my experience] Most of the time when a change of this magnitude occurs, there is a lot of push back and resentment.  This is because upper management makes the decision to enact a change and does not even bother to ask the people who work with the product/software on a daily basis. These decisions are made by people higher up the corporate ladder looking at how much money they can save. 
There are many ways to help employees deal with change only if it is done properly. Change starts from the top down. One of the reasons there is so much doubt in regards to change is because most of the time the change that affects the group most is left out of the decision making. I am not saying all employees have to have a say-so when a company decides to make changes, but at least involve the people who will be affected by the change.]]></description>
			<content:encoded><![CDATA[<p>What Iâ€™ve come across in the 20 years in my industry is attachment and doubt.  When people have been using a certain type of software application for several years or more, they become comfortable with their job and what they do. When they hear of a change coming, letâ€™s say a new software change (example: Windows), they instantly think â€œWhat am I not going to be able to find now??â€ The fear of the unknown is all too familiar.  </p>
<p>[In my experience] Most of the time when a change of this magnitude occurs, there is a lot of push back and resentment.  This is because upper management makes the decision to enact a change and does not even bother to ask the people who work with the product/software on a daily basis. These decisions are made by people higher up the corporate ladder looking at how much money they can save.<br />
There are many ways to help employees deal with change only if it is done properly. Change starts from the top down. One of the reasons there is so much doubt in regards to change is because most of the time the change that affects the group most is left out of the decision making. I am not saying all employees have to have a say-so when a company decides to make changes, but at least involve the people who will be affected by the change.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
