<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Leadership In Action &#187; misinterpreted communication</title>
	<atom:link href="http://www.cmoe.com/blog/tag/misinterpreted-communication/feed" rel="self" type="application/rss+xml" />
	<link>http://www.cmoe.com/blog</link>
	<description>a podcast &#38; blog by CMOE consultants</description>
	<lastBuildDate>Tue, 07 Feb 2012 19:56:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<!-- podcast_generator="podPress/8.8" -->
		<copyright>&#xA9; </copyright>
		<managingEditor>cmoe@ioventuresinc.com ()</managingEditor>
		<webMaster>cmoe@ioventuresinc.com()</webMaster>
		<category></category>
		<ttl>1440</ttl>
		<itunes:keywords></itunes:keywords>
		<itunes:subtitle></itunes:subtitle>
		<itunes:summary>a podcast amp; blog by CMOE consultants</itunes:summary>
		<itunes:author></itunes:author>
		<itunes:category text="Society &amp; Culture"/>
		<itunes:owner>
			<itunes:name></itunes:name>
			<itunes:email>cmoe@ioventuresinc.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>no</itunes:explicit>
		<itunes:image href="http://www.cmoe.com/images/blog/leadership-in-action-iTunes-144.jpg" />
		<image>
			<url>http://www.cmoe.com/images/blog/leadership-in-action-iTunes-144.jpg</url>
			<title>Leadership In Action</title>
			<link>http://www.cmoe.com/blog</link>
			<width>144</width>
			<height>144</height>
		</image>
		<item>
		<title>Be Open To Receiving Feedback and Coaching</title>
		<link>http://www.cmoe.com/blog/be-open-to-receiving-feedback-and-coaching.htm</link>
		<comments>http://www.cmoe.com/blog/be-open-to-receiving-feedback-and-coaching.htm#comments</comments>
		<pubDate>Wed, 13 Oct 2010 16:50:07 +0000</pubDate>
		<dc:creator>Christopher Stowell</dc:creator>
				<category><![CDATA[character]]></category>
		<category><![CDATA[coaching skills]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[feedback]]></category>
		<category><![CDATA[corrective feedback]]></category>
		<category><![CDATA[effective communication]]></category>
		<category><![CDATA[impatient communication]]></category>
		<category><![CDATA[misinterpreted communication]]></category>
		<category><![CDATA[poor communication]]></category>

		<guid isPermaLink="false">http://www.cmoe.com/blog/?p=1401</guid>
		<description><![CDATA[People are like fingerprints, no two are alike.   Because each person has unique histories, talents, abilities, and behavior traits, we receive, internalize, and react to feedback just as differently.  Yet receiving and responding to feedback and coaching is critical if we are to grow, improve, and become better, more well rounded individuals.
This past week I [...]]]></description>
			<content:encoded><![CDATA[<p>People are like fingerprints, no two are alike.   Because each person has unique histories, talents, abilities, and behavior traits, we receive, internalize, and react to feedback just as differently.  Yet receiving and responding to feedback and <a title="coaching" href="http://www.cmoe.com/coachingskills.htm">coaching</a> is critical if we are to grow, improve, and become better, more well rounded individuals.</p>
<p><img class="alignleft size-full wp-image-1421" title="Truck_5999457_XS" src="http://www.cmoe.com/blog/wp-content/images/Truck_5999457_XS2.jpg" alt="Truck_5999457_XS" />This past week I took my family on an extended weekend trip to the lake to get our last summer fun in before school gets underway for the kids and the weather begins to turn cold.  As I was leaving my neighborhood in my truck (Bed full of cargo, and boat and trailer in tow), the individual driving a vehicle in front of me decided to make a turn into a supermarket parking lot.  This immediately created a problem for me.  Not only was the driver not in the turning lane/shoulder of the road, he didn’t put on his turn signal until the very last moment.  This chain of events could have caused an accident if I hadn’t  proactively hit my breaks and creep into the other lane in an attempt slow my truck and boat in order to avoid crashing into his car.</p>
<p>I was irritated by the situation and offered up some feedback to the driver.  In my attempt to slow tons of my steel truck and fiber glass boat, I gave a couple of honks on the horn followed by a quick flick of my heads lights (meaning get out of the way and quick or I will crash into you).  What really bothered me was the reaction this guy demonstrated to my warning.  He pulled to an immediate stop, and offered some crude hand gestures through his window and proceeded to drive slowly.  It was clear he wanted to turn this issue into heated verbal or physical argument by his behavior.  I told to my wife “that guy is a jackass.”  Not from his driving abilities, but from the way he responded to my feedback.  My feedback was not intended to show rage.   I did not lay on my horn and start yelling.  I gave a couple of honks and a flicker of my headlights telling this guy that his current behavior was going to cause an accident.  That’s why cars have horns.</p>
<p>His reaction caused me to evaluate my perceptions of both giving and receiving feedback.  I thought about how I would have reacted if I had been honked at.  My conclusion is that we all need to be more open to feedback and coaching and not take personal offense to it.  In order to grow, and develop we learn from others.  If we are to enhance our abilities and expertise, we need to receive feedback, either supportive or corrective.</p>
<p><strong>Supportive Feedback</strong><br />
This is all about reinforcing the positive.  When you see someone doing something great and want the behavior to continue, or simply recognizing someone for their work.  It is geared to continually improving performance.</p>
<p><strong>Corrective Feedback<br />
</strong>This is about changing behavior, performance, and results.  It occurs when an improvement or change in needed.  It is important to understand that corrective feedback is not negative or abusive in its style, it is only intended to correct the behavior at hand.<br />
While it is important for us who both give and receive feedback to understand these two types, we can hit higher levels of performance if we are a little more open, a little less sensitive (on the receiving end), and ensure our point of view is clearly communicated.  Let’s recommit ourselves to the concept of feedback.</p>]]></content:encoded>
			<wfw:commentRss>http://www.cmoe.com/blog/be-open-to-receiving-feedback-and-coaching.htm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Barrow Pit: A Case Of Communication Disparity</title>
		<link>http://www.cmoe.com/blog/the-barrow-pit-a-case-of-communication-disparity.htm</link>
		<comments>http://www.cmoe.com/blog/the-barrow-pit-a-case-of-communication-disparity.htm#comments</comments>
		<pubDate>Wed, 03 Dec 2008 06:00:59 +0000</pubDate>
		<dc:creator>Martha Rice</dc:creator>
				<category><![CDATA[communication]]></category>
		<category><![CDATA[relationships]]></category>
		<category><![CDATA[faulty communication]]></category>
		<category><![CDATA[misinterpretation]]></category>
		<category><![CDATA[misinterpreted communication]]></category>
		<category><![CDATA[poor communication]]></category>

		<guid isPermaLink="false">http://www.cmoe.com/blog/the-barrow-pit-a-case-of-communication-disparity.htm</guid>
		<description><![CDATA[A few days ago, I was talking with a friend about a recent automobile accident.  I told her the driver veered off the road into a barrow pit.  &#8220;A barrow pit?&#8221; she asked.  After a chuckle, I explained that a barrow pit is a wide, deep gutter dug along the roadside by [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.cmoe.com/blog/wp-content/images/car-crash_small.jpg" alt="Different words can cause communication disparity" align="left" border="2" height="148" vspace="2" width="198" />A few days ago, I was talking with a friend about a recent automobile accident.  I told her the driver veered off the road into a barrow pit.  &#8220;A barrow pit?&#8221; she asked.  After a chuckle, I explained that a barrow pit is a wide, deep gutter dug along the roadside by the transportation department for drainage purposes &#8211; it is usually dry.  &#8220;Oh,&#8221; she replied, &#8220;we call those ditches.&#8221; &#8220;Ditches?&#8221;  Well, okay, but when I hear the word, ditch, I think of a channel or canal used for the moving water primarily for irrigation.  So, when I told my friend, &#8220;the driver ran into the barrow pit,&#8221; I meant it was a dry accident.  If I had said ditch I would have meant the driver went into the water.</p>
<p>How often do we assume the instructions that we give others are perfectly clear when in reality they baffle our listeners or are misinterpreted?  Then, when we criticize their performance they look at us with blank gazes or defensively reply, &#8220;You didn&#8217;t tell me that.&#8221;</p>
<p>Leaders and team members will often assume that the other person will always have the same definition or understanding of a word used, so we need to check for clarification.  Several years ago, I was a manager of the pharmacy/cosmetics department in a department store.  And as with all organizations, we had certain words that had specific meanings only our organization, or trade.  One of our most used industry verb was &#8220;face&#8221;.  While this very common word, people do not think of it in the terms we used it.</p>
<p>Annie was still in high school when she became one of my department clerks.  She was fairly young, very enthusiastic, and somewhat naïve, but very sincere is doing a good job.  Company procedure was two days in orientation and then some training on the floor with a more experienced clerk.  On her third day on the job, I assigned Jeri to work with her.  Jeri was one of my most experienced clerks.  About an hour later, I went to see how she was doing and found her standing staring at the hair care section.  I asked if she had a problem.  &#8220;Oh no,&#8221; she said.  &#8220;Jeri told me to face the shampoo section.  I asked her why and she said that&#8217;s part of the job.&#8221;  Jeri assumed that Annie had been instructed about &#8220;facing aisles&#8221; in the orientation class.  Jeri also assumed Annie was being a bit cheeky like some teenagers were.  While it seemed very strange to her, Annie did what she thought she was told to do.  Of course, in retail, &#8220;facing&#8221; means pulling product from the back of a shelf and making certain the front of the package faces the customer.  Luckily, Annie had a good sense of humor and was able to accept the teasing the other clerks gave her for the next few months for being so naive.</p>
<p>Think about your own industry.  What phrases and buzz words do you or your organization use to convey job specific meaning?  Do all your team members understand the context in which these words might be used?  Do your employees mentally see ditches or barrow pits?</p>
<p><strong>Try this at your next team or department</strong> <strong>meeting:  </strong>Throughout the discussion, ask members of your team if they understand all the terminology being used to describe a process, project, or concept.   You might be surprised at how many people don&#8217;t know the meaning or have a different personal perception of what is going on.</p>]]></content:encoded>
			<wfw:commentRss>http://www.cmoe.com/blog/the-barrow-pit-a-case-of-communication-disparity.htm/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

