<?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/"
	>

<channel>
	<title>Leading at Light Speed by Eric Douglas &#187; managing tough conversations</title>
	<atom:link href="http://blog.leadingresources.com/tag/managing-tough-conversations/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.leadingresources.com</link>
	<description>Leadership Development, Strategic Planning, Change Management</description>
	<lastBuildDate>Wed, 11 Aug 2010 19:19:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<image>
<link>http://blog.leadingresources.com</link>
<url>http://blog.leadingresources.com/wp-content/mbp-favicon/LRI favicon.jpg</url>
<title>Leading at Light Speed by Eric Douglas</title>
</image>
		<item>
		<title>Managing Tough Business Conversations</title>
		<link>http://blog.leadingresources.com/5/managing-tough-conversations</link>
		<comments>http://blog.leadingresources.com/5/managing-tough-conversations#comments</comments>
		<pubDate>Wed, 28 May 2008 17:36:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[Leadership Development]]></category>
		<category><![CDATA[managing tough conversations]]></category>

		<guid isPermaLink="false">http://blog.leadingresources.com/?p=5</guid>
		<description><![CDATA[The CEO of a retail chain wanted his leadership team to learn how to have tough conversations... this is the result of the following conversations.]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fblog.leadingresources.com%2F5%2Fmanaging-tough-conversations"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fblog.leadingresources.com%2F5%2Fmanaging-tough-conversations" height="61" width="51" /></a></div><p><img class="alignnone" title="Managing Tough Business Conversations" src="http://www.cartoonstock.com/newscartoons/cartoonists/bbo/lowres/bbon52l.jpg" alt="" width="400" height="311" /></p>
<p>The CEO of a retail chain wanted his leadership team to learn how to have tough conversations. Too many issues were being buried, he said. Team members needed to bring their issues to the table and learn how to resolve them. He asked me to design a three-hour team-building workshop.</p>
<p>I began the workshop by asking the team to develop a set of operating principles. Here&#8217;s what they came up with:</p>
<ol>
<li>Our first responsibility is to the success of the entire organization, not to our own departments.</li>
<li>We are responsible for helping one another achieve important organizational goals. That is how we can be most effective as a team.</li>
<li>As team members, we need to view each other as supports, not threats.</li>
<li>As team members, we have a right to hear first from each other about issues that affect us, not second-hand or via the “grapevine.”</li>
<li>Since we have a responsibility to help each other, we must bring tough issues to the table and discuss them with each other.</li>
<li>When discussing difficult topics, we need to tackle the issue, not each other.</li>
<li>We have a responsibility to ask questions first before we reach conclusions.</li>
</ol>
<p>After they developed these principles, I introduced them to the GROW model of productive conversation (first described by John Whitmore in his book “Coaching for Performance” ). In a nutshell, the GROW model says that productive conversations follow this sequence: first, we need to understand the <strong>G</strong>oal (both of the current discussion and the long-range goal), then the current <strong>R</strong>eality, then our <strong>O</strong>ptions, and finally what we <strong>W</strong>ill do next and when.</p>
<p>Once the team understood the model, I asked them to practice it on two current, tough issues. The CTO immediately raised an issue that no one was aware of &#8211; but that affected the entire organization. Off they went! Then the CFO raised a second issue dealing with financial statements. Again, the discussion was electrifying. In each case the team followed the GROW model. After experiencing these two discussions, the team added three more operating principles:</p>
<ol>
<li>Our meetings must have an agenda and a facilitator.</li>
<li>We keep a record of our action items and hold each other accountable.</li>
<li>No interruptions &#8211; we honor this work as our highest priority.</li>
</ol>
<p>Afterwards, people raved about the quality of the teamwork. As one person said: &#8220;There are a lot of conversations we need to have now!&#8221;</p>
<p>Next blog article: &#8220;Our <a href="http://blog.leadingresources.com/79/our-change-management-model">Change Management Model</a> &#8211; Three Principles&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.leadingresources.com/5/managing-tough-conversations/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
