<?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>Don&#039;t Just Talk, Blog! &#187; leadership</title>
	<atom:link href="http://www.dontjusttalkbeheard.com/blog/tag/leadership/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dontjusttalkbeheard.com/blog</link>
	<description>Communication Coaching with David Levin</description>
	<lastBuildDate>Wed, 14 Jul 2010 20:42:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Avoiding the &#8220;Bonehead Move.&#8221;</title>
		<link>http://www.dontjusttalkbeheard.com/blog/avoiding-the-bonehead-move/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/avoiding-the-bonehead-move/#comments</comments>
		<pubDate>Tue, 15 Jun 2010 13:12:46 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[david levin]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=148</guid>
		<description><![CDATA[People can make such bonehead moves, can’t they? I’m sorry, but it’s true! Take this story, for example &#8230; A sales team of twenty people were competing with each other in a friendly, month-long contest. At their end-of-month meeting, the manager got up and announced the two winners. Everything was fun and upbeat &#8230; until [...]]]></description>
			<content:encoded><![CDATA[<p>People can make such bonehead moves, can’t they? I’m sorry, but it’s true! Take this story, for example &#8230;</p>
<p>A sales team of twenty people were competing with each other in a friendly, month-long contest. At their end-of-month meeting, the manager got up and announced the two winners. Everything was fun and upbeat &#8230; until he said this: “If the rest of you slackers were as intelligent and hard-working as these two, maybe <em>you’d</em> have been up here!”</p>
<p>See what I mean? “Motivation through Shame and Insults!” What was he thinking? (It didn’t work, by the way. The team was furious.) Sadly, this sort of thing happens every day, and it boggles the mind. How can you explain it?  I mean, seriously, don’t they <em>know?</em></p>
<p>Here’s the thing: they <em>don’t</em> know. And that’s the key to the whole problem.<span id="more-148"></span></p>
<p>If you asked him, I’m sure that manager would agree that insulting and shaming people was a bad idea. But he did it anyway. Why? From what I’ve seen, the most likely explanation is that he simply didn’t realize his words were insulting and shaming.</p>
<p>The truth is, people don’t generally do things they think are stupid. In fact, people usually have the <em>opposite</em> intentions: they think what they’re doing will be <em>helpful</em>, or that it will connect them with others. It doesn’t seem like it at times, but people’s intentions are almost always good, even when their actions send a different message. I know this was the case with the manager in our story. But instead of running what he was going to say past someone ahead of time, he went in there with only his good intentions, and winged it. The result? Bonehead move! And a major hit to his effectiveness as a leader.</p>
<p>The lesson?</p>
<p><strong>“Don’t Wing it. Work on it!”: Plan and Get Feedback.</strong></p>
<p>Bonehead moves like these happen to all of us, and they cost us more than you can imagine. They keep us from having the influence and impact we could, and from being as successful as we &#8211; and the whole team &#8211; otherwise would.</p>
<p>Don’t make the same mistake. Start planning what you’re going to say and getting feedback on your plans. I know it takes a little more time, and you need to find the right person to give you feedback. But you won’t believe the difference it will make in your work and life. And not doing it is simply too costly.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/avoiding-the-bonehead-move/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Case Study: Difficult Conversation Between Peer-Level Teams.</title>
		<link>http://www.dontjusttalkbeheard.com/blog/case-study-difficult-conversation-between-peer-level-teams/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/case-study-difficult-conversation-between-peer-level-teams/#comments</comments>
		<pubDate>Tue, 25 May 2010 14:06:55 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=129</guid>
		<description><![CDATA[I had a conversation this past week with a physician/administrator who needed to address an on-going problem with another team. Here’s the email she was planning to send: “Hi guys, There was a patient last night [ who was transferred to our unit without you briefing us on the case ]. If you would like [...]]]></description>
			<content:encoded><![CDATA[<p>I had a conversation this past week with a physician/administrator who needed to address an on-going problem with another team. Here’s the email she was planning to send:</p>
<p style="padding-left: 30px;">“Hi guys,</p>
<p style="padding-left: 30px;">There was a patient last night [ who was transferred to our unit without you briefing us on the case ]. If you would like help in managing these cases, you need to page us. It’s not acceptable or safe to expect the nurse who wasn&#8217;t present for the case to try to relay the message of what happened and what needs to be done. In general, if you want us to see any of your patients we would appreciate a page, but especially when there are unstable patients or urgent situations. If you call the central operator (x-xxxxxx-x) they can promptly connect you to us.</p>
<p style="padding-left: 30px;">Thanks.”</p>
<p>Based on the facts, she seemed to have a reasonable position. Also, this was not the first communication on the subject, so there was a certain amount of frustration on her part, which I think you can hear in her note.</p>
<p>But, to me, her email had real problems. It was antagonistic, judgmental and condescending, even calling into question the other team’s commitment to patient’s safety. Bottom line, if I had received the note, I would have felt attacked and likely dug in my heels, and been even <em>less</em> open to anything she had to say in the future. In other words, her note would have had the opposite effect of what she wanted.</p>
<p>As we talked about the situation, it seemed to me the biggest problem was the tension in their work relationship. I didn’t feel she was going to be heard on her main points until she first addressed that reality. In addition, I thought the points themselves would be more effective if presented in a more inclusive, respectful, and non-confrontational way. Here’s what we came up with as an alternate:<span id="more-129"></span></p>
<p style="padding-left: 30px;">&#8220;Hi guys,</p>
<p style="padding-left: 30px;">Sorry to have this conversation by email, but there was a situation last night that I think we need to address.</p>
<p style="padding-left: 30px;">First, I want to say I know there&#8217;s been a lot of tension between us, and I am truly sorry for my role in that. I know I don&#8217;t communicate as effectively as I should &#8211; or would like to &#8211; and FYI, I&#8217;m going to start working on that. I also want to apologize if I&#8217;ve ever given you the impression that I don&#8217;t appreciate what you do or respect your work, because of course I do. I think you do a great job, and I know you only want what&#8217;s best for the patients &#8211; as we all do.</p>
<p style="padding-left: 30px;">Which brings us to last night. There was a patient [ who was transferred to our unit without you briefing us on the case ].</p>
<p style="padding-left: 30px;">I know we&#8217;ve talked about this sort of thing before, but I just don&#8217;t feel it works to expect the nurse who wasn&#8217;t present for the case to try to relay the message of what happened and what needs to be done. It makes things very awkward, and, more importantly, raises real concerns about patient safety. We really need to get that information directly from you, especially when there are unstable patients or urgent situations.</p>
<p style="padding-left: 30px;">I know it can be difficult to find the time &#8211; or even remember sometimes &#8211;  to page us, but that&#8217;s the only way I know for us to get the information we need. And, by the way, if you have any other suggestions how we can help improve these situations, please let us know. But for now, if you can please remember to page us, that will make a huge difference in our ability to quickly provide the level of care we both want for your patients.</p>
<p style="padding-left: 30px;">As a reminder, you can call the central operator (x-xxxxxx-x) and they can promptly connect you to us.</p>
<p style="padding-left: 30px;">Thanks for your help!&#8221;</p>
<p>Note that the facts themselves are presented identically. But everything else has a completely different tone. There’s empathy and humility. It calls them all to a common purpose rather than being adversarial. Most important, it addresses the relationship issues first.</p>
<p>The result? One person wrote back and said, “No problem, I’ll try to be better about paging you guys.” The other, more problematic individual said he wasn’t aware of the tension, had never felt a lack of respect, and was very appreciate of the work they did, too. (Nice surprise!) So the email laid the groundwork for them coming together and finding a solution that worked for everyone. <em>Success! </em></p>
<p>Now, this case was a very specific situation. But I had a couple of other conversations around the same time that each spoke to the same primary recommendation:</p>
<p style="text-align: center;"><strong>In any communication &#8211; especially those with tension<br />
involved &#8211; make sure you lead with the relationship. </strong></p>
<p>What that means is, whatever state your relationship is in with the other person, address that first before you get to the actual content of your message. If the relationship is tense, as in the above example, talk about that. If it’s fine, just lead with some normal inter-personal conversation. Whatever the situation, tend to the relationship first, then get to the message itself.</p>
<p>Why? Because it’s a great way to be heard. The fact is, the quality of your relationship with someone dictates how open they are to what you have to say.</p>
<p>Think of it this way: The message you want to communicate is like a hot, fresh pizza. You’re the delivery person. The other person is in their house, and the relationship is the door. If the relationship is good, the door opens, the pizza is received. (Yum!) If not, the door stays closed. No pizza. Very sad.</p>
<p>Don’t let those pizzas go to waste! Take the time, plan out what you’re going to say, and as much as possible, lead with the relationship.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/case-study-difficult-conversation-between-peer-level-teams/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Fired for being unhappy?</title>
		<link>http://www.dontjusttalkbeheard.com/blog/fired-for-being-unhappy/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/fired-for-being-unhappy/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 15:48:48 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=119</guid>
		<description><![CDATA[Do you know anybody who is clearly not happy in their job? Someone who’s always whining and complaining about this or that, always spreading their negativity around to the rest of the team? Me too. I’m sure every organization has them. For me, whenever I meet someone like that I always think, since they’re so [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-family: arial,helvetica,sans-serif;"><span style="font-size: 11pt;">Do you know anybody who is clearly not happy in their job? Someone who’s always whining and complaining about this or that, always spreading their negativity around to the rest of the team? Me too. I’m sure every organization has them. For me, whenever I meet someone like that I always think, since they’re so obviously unhappy, why do they stay? I mean, I know it’s not that simple, but still, I can’t help but wonder.</p>
<p>And then I found the answer. A friend sent me <a rel="this article" href="http://www.dontjusttalkbeheard.com/lib/downloads/HR001.pdf" target="_blank">this article</a> the other day, and it really clarified for me what I think is the ultimate reason unhappy people stick around: it’s because <em>the organization lets them</em>. For whatever reason, the organization hasn’t included “happiness in the position” as an essential requirement for the job, so the individual is allowed to stick around even though they’re bringing down the whole team.</p>
<p>As if to reinforce the point, a couple of days later I heard about a study on the impact of “bad apples” on a team’s performance. The researchers assigned different teams identical tasks, and the team with the bad apple came in last every time.</p>
<p>Now, before you launch into all the reasons why “firing the unhappy” is over-simplistic, unreasonable, inhuman, or whatever, please read the piece. It’s actually very thoughtful and sensitive to the people involved. Also, understand that I always err on the side of the individual and what they can do for themselves first. But at some point, someone has to enforce standards, and that ultimately comes down to managers and leaders taking action. Besides, you’re not really firing someone because they’re unhappy anyway, you’re just helping them find somewhere where they <em>are</em> happy. How is that not a good thing?</p>
<p>However you approach it, the bottom line is that if someone who reports to you is truly unhappy, you can’t just ignore it. You need to do something about it and help them find a position that’s a better fit. The change doesn’t have to happen today, necessarily. Don’t make it a bigger problem than it needs to be. But at least talk about it, get it out into the open, and start putting some energy into finding a better fit. Because having someone stick around in a position that’s a bad fit serves no one. It’s no good for the individual. And it’s deadly for the organization.</span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/fired-for-being-unhappy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>2020 Vision (Not for your eyes. For your life.)</title>
		<link>http://www.dontjusttalkbeheard.com/blog/2020-vision-not-for-your-eyes-for-your-life/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/2020-vision-not-for-your-eyes-for-your-life/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 21:12:01 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[david levin]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=95</guid>
		<description><![CDATA[Four years ago, we started a new family tradition. During the last week of the year, we all sit on the couch, turn the video camera on ourselves, and recap everything that’s happened during the year. At this stage, with two kids under five, the videos are very sweet. I can also already tell how [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: 11pt;"><span style="font-family: arial, helvetica, sans-serif;">Four years ago, we started a new family tradition. During the last week of the year, we all sit on the couch, turn the video camera on ourselves, and recap everything that’s happened during the year. At this stage, with two kids under five, the videos are very sweet. I can also already tell how fantastic they’re going to be for all of us as time goes on—watching the kids grow up, and ourselves grow, well, let’s just say wiser. :-)</span></span></p>
<p>The idea grew out of a habit of mine to take this week between Christmas and New Year’s to reflect on the year past, and think about the one to come. But really, it’s a <em>little </em>reflection and a <em>lot</em> of thinking about the year to come. <em>What am I going to do next year? What am I excited about? Where are things going to be this time next year?</em> It’s a fun and helpful process, but since this New Year’s Day will also New <em>Decade’s</em> Day, I’m changing things a bit this year. Instead of focusing only on 2010, I’m also thinking about 2020.</p>
<p>How about you? Where do you want to be in ten years? What’s your 2020 Vision? How different will things be then from the way they are today? Most important, what choices will you make, starting today, to put you on a path to getting there?</p>
<p>There’s an old proverb that says, “The best time to plant a tree was 20 years ago. The second best time is right now.” What better time than the start of a new decade to take that idea to heart? Let’s plant some trees, shall we?<span id="more-95"></span></p>
<p>Here’s a great gift to give yourself this holiday season: 1) Come up with a ten-year vision for yourself that you’re excited about. 2) Start making choices today that support that vision.</p>
<p>One last thought. As it says in <em>Don’t Just Talk, Be Heard!</em>, “The single most important factor in a person’s success is not their knowledge, education, experience, or charisma, it’s their ability to communicate effectively with others.” Whatever vision you come up with for yourself (or your team), your communication skills are going to be key to getting there. After you come up with your 2020 Vision, let’s find a few minutes to talk about ways I could help you get there. Drop me a note or give me a call.<span style="font-family: arial, helvetica, sans-serif;"><span style="font-size: 10pt;"> </span></span><span style="font-size: 11pt;"><span style="font-family: arial, helvetica, sans-serif;">I’d love to have the conversation. And I’d be honored to help.</span></span></p>
<p>Happy New Decade!</p>
<p><em>Be Heard!</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/2020-vision-not-for-your-eyes-for-your-life/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>You Can&#8217;t Take It Back</title>
		<link>http://www.dontjusttalkbeheard.com/blog/you-cant-take-it-back/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/you-cant-take-it-back/#comments</comments>
		<pubDate>Sat, 14 Nov 2009 02:56:07 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[david levin]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=56</guid>
		<description><![CDATA[Ever said something you wish you could take back? Me too. Here&#8217;s one from 25 years ago. (It&#8217;s not that I have to go back that far to find an example. Just to find one that doesn&#8217;t still hurt.) :-) Back then, I was on the road full-time playing music, and had a band of [...]]]></description>
			<content:encoded><![CDATA[<p>Ever said something you wish you could take back? Me too. Here&#8217;s one from 25 years ago. (It&#8217;s not that I have to go back that far to find an example. Just to find one that doesn&#8217;t still hurt.) :-)</p>
<p>Back then, I was on the road full-time playing music, and had a band of my own, called, originally enough, <em>T</em><em>he David Levin Band</em>. We played a lot of places in the middle of nowhere and had a good bit of fun doing it. (A sad sort of fun, in retrospect. But hey, we were young!) I should also say that I wasn&#8217;t much of a band leader. In those days, I was generally more interested in hanging out with my buddies than running a business. But during one particular band meeting I apparently felt some sudden misguided impulse to take charge or something because I distinctly remember saying to the band, &#8220;Guys, this is not a democracy!&#8221;</p>
<p>Twenty-five years later, I&#8217;m still paying for it.<br />
<span id="more-56"></span><br />
Actually, we laugh about it now. (I&#8217;m still friends with several of the guys.) But the point is, we <em>remember</em> it. And I have no doubt it played a role in that band breaking up not long afterward.</p>
<p>There&#8217;s a famous quotation, attributed to Grace Hopper, that says, &#8220;It&#8217;s easier to ask forgiveness than to get permission.&#8221; I&#8217;ve always liked the quote, and I&#8217;m sure it&#8217;s true in a lot of situations. But communication is not one of them. In fact, with communication it&#8217;s the opposite. Once you drop that bomb, that&#8217;s it. There&#8217;s no taking it back. No do-overs. And the truth is, it&#8217;s ten times harder to undo a communication mistake than it is to get it right in the first place, <em>if</em> the mistake can even be undone at all.</p>
<p>Communication is too important to just go with your gut in the moment. If you have something that needs to be said, take the time to say it right. Think it through ahead of time. Plan it out. Be on the lookout for any disconnects. And, of course, make sure to run it past a feedback buddy first.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/you-cant-take-it-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Got a problem with someone? Try saying, &#8220;I&#8217;m sorry.&#8221;</title>
		<link>http://www.dontjusttalkbeheard.com/blog/try-saying-im-sorry/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/try-saying-im-sorry/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 13:19:29 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[Be Heard!]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[customer service training]]></category>
		<category><![CDATA[david levin]]></category>
		<category><![CDATA[Don't Just Talk]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=50</guid>
		<description><![CDATA[Here&#8217;s something you can take to the bank: If you&#8217;re having some sort of trouble with someone—conflict, tension, bad blood, whatever—nothing gets things back on track like a good old-fashioned apology. &#8220;But I didn&#8217;t do anything wrong!&#8221; you say, &#8220;It wasn’t my fault.&#8221; I understand. And I didn&#8217;t say it was. But who&#8217;s at fault [...]]]></description>
			<content:encoded><![CDATA[<div>
Here&#8217;s something you can take to the bank: If you&#8217;re having some sort of trouble with someone—conflict, tension, bad blood, whatever—nothing gets things back on track like a good old-fashioned apology.</p>
<p>&#8220;But I didn&#8217;t do anything wrong!&#8221; you say, &#8220;It wasn’t my fault.&#8221;</p>
<p>I understand. And I didn&#8217;t say it was. But who&#8217;s at fault is not the point. The point is that the relationship has gone bad, and that&#8217;s no good for either of you.</p>
<p>Besides, I&#8217;m not saying you should apologize for whatever it is you&#8217;re disagreeing about. In fact, doing so might do more harm than good. The most important thing here is that whatever you say has to be authentic and heartfelt. Apologizing for something that you didn&#8217;t actually do is likely to be neither. And it could even be seen as being manipulative, which is even worse.<br />
<span id="more-50"></span><br />
What you can—and should—do, however, is express sorrow over the state of the relationship and apologize for whatever you&#8217;ve contributed to it.</p>
<p>Example: &#8220;I&#8217;m really sorry for the way things have been lately between us. I know I&#8217;ve done some things that have offended or hurt you in some way, but I sure didn&#8217;t mean to. I&#8217;ve always [enjoyed/liked/respected] you, and don&#8217;t know why things should have to be  this way. I&#8217;d sure like them to be better. Anyway, I just wanted to let you know.&#8221;</p>
<p>The beauty of this approach is that by focusing you on the relationship rather than the conflict, it puts you in a more open, humble, and generous place, which tends to bring out similar feelings in the other person. Will it fix every problem? No. Sometimes people are too attached to a conflict to open up and let go of it. But a lot of times it will. And either way, it will always make <em>you</em> feel better—a lot better, in fact—and that by itself is reason enough in my book.</div>
<div></div>
<div>Next time you&#8217;re having difficulty with someone, try giving them a good, heartfelt apology. It&#8217;s surprising the difference it can make.</div>
<div></div>
<div></div>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/try-saying-im-sorry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wise Guy</title>
		<link>http://www.dontjusttalkbeheard.com/blog/wise-guy/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/wise-guy/#comments</comments>
		<pubDate>Mon, 21 Sep 2009 20:52:25 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[david levin]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://dontjusttalkbeheard.com/blog/?p=27</guid>
		<description><![CDATA[My good friend John Miller recently sent a note to his QBQ! mailing list announcing the release of my new book, Don’t Just Talk, Be Heard! The piece included an excerpt from the book’s introduction that tells a story about my getting pulled over by the police. The short version is, I was so focused [...]]]></description>
			<content:encoded><![CDATA[<p><span>My good friend John Miller recently sent a note to his <em>QBQ!</em> mailing list announcing the release of my new book, <em>Don’t Just Talk, Be Heard!</em> The piece included an excerpt from the book’s introduction that tells a story about my getting pulled over by the police. The short version is, I was so focused on the literal words the officer spoke that when he said “Do you have your license and registration” all I answered was, “Yes,” and well, things sort of went downhill from there. </span></p>
<p><span><span> </span>In my mind, it’s a funny, self-deprecating story that introduces the idea of “communication gaps”—the difference between our intentions and the perceptions of others—and shows that even the author of a book on effective communication is not immune to them. Unfortunately, not everyone saw it that way. The day after John’s email went out, he got this response:</span></p>
<blockquote><p><span><em>&#8220;Has this guy ever been pulled over? What kind of wise guy just says “yes”? A real QBQ’er would have followed up with “would you like to see them” or even better have them already out and hanging out the window. Not just “YES”. The world does not speak literally most of the time it is sporadic and figuratively. Good communication involves listening and follow up. Your buddy was being a wise guy, he was endangering the public by going 50% faster than he should have in a residential zone and then wasted an officers time by splitting hairs.</em></span><br />
<span id="more-27"></span><br />
<span><em></em></span></p>
<p><span><em>QBQ: What can I do to not waste this officers time and endanger the public?&#8221;</em></span></p></blockquote>
<p><span><span> </span>It goes without saying that he missed the point. But really, he missed pretty much <em>everything</em>. Where did I suggest that this was an example of </span><em>QBQ!</em><span> behavior on my part, or that I thought I had handled it well? The answer is: nowhere. In fact, the whole story was really sending the <em>opposite</em> message. But he saw it differently. </span></p>
<p><span><span> </span>The more I thought about it, what struck me was that the writer essentially had the same reaction as the officer: <em>wise guy; thinks he’s clever; endangering the public</em>. (For the record, it was not in a residential zone. Also, I would never intentionally go 50% faster than the posted speed limit. I thought the limit was 35. Doesn’t make it okay, of course, but 42 in a 35 is a lot better than 42 in a 30—and frequently would not even have been ticketed.) So even after all the explanation, <em>I was still having a communication gap</em>, at least with this one reader. I thought that was funny. </span></p>
<p><span><span> </span>I must confess, though, that before I found it funny, I was tempted to think things like, “What an idiot! He totally missed the point. And what sort of jerk would think it was his duty to “educate” the author by sending them this sort of negative, judgmental garbage?!” </span></p>
<p><span><span> </span>OK, that was a lame confession. I wasn’t just tempted—that’s <em>exactly</em> what I was thinking. Not pretty, I know, but true. And I imagine many people would have had similar thoughts. But <em>that’s</em> the problem, especially for managers and leaders. What if I worked with this person? What if I was his manager? </span></p>
<p><span><span> </span>The real point of this story to me is that we have to find a way to be effective with those around us, no matter who they are or how different from us they may be. And negative thoughts like mine, even when they’re justified, only stand in our way of doing that. No, some people never get past their sour, negative, judgmental ways—and this can make them extremely difficult to deal with. That’s one of the reasons we have to be so careful about who we hire and put on our team in the first place. But once they’re there, it becomes our job to make it work. </span></p>
<p><span><span> </span>If you’re wondering, there <em>are</em> some specific communication techniques that may help. Which ones I’d recommend would depend on having a deeper understanding of the situation between you and the other person. But the most important thing is to get into the right frame of mind to begin with. In other words, to take ownership of the problem. We can deny and avoid and complain all we want. But the only accountable choice is to look to ourselves and do our best to figure it out. Will we solve every problem? No. Will better communication make a difference? Not every time. But we still have to try. </span></p>
<p><span><span> </span>Got a wise guy on your team? I feel for you. Now get to work on making it better.  :-)</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/wise-guy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Complicated</title>
		<link>http://www.dontjusttalkbeheard.com/blog/complicated/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/complicated/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 18:37:03 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://dontjusttalkbeheard.com/blog/?p=3</guid>
		<description><![CDATA[Man, communicating can be tricky. You know what you want to say &#8211; and you think you have it right &#8211; but the other person hears it completely differently.   It&#8217;s almost like you&#8217;re speaking in a foreign language but your translator is in a bad mood &#8211; and drunk. In any case, that&#8217;s the [...]]]></description>
			<content:encoded><![CDATA[<p>Man, communicating can be <em>tricky.</em> You know what you want to say &#8211; and you think you have it right &#8211; but the other person hears it completely differently.   It&#8217;s almost like you&#8217;re speaking in a foreign language but your translator is in a bad mood &#8211; and drunk.</p>
<p>In any case, that&#8217;s the sort of stuff we&#8217;ll be talking about in these pages:   How can we close the gaps between what we mean to say and what people hear?<br />
<span id="more-3"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/complicated/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
