<?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/"
		>
<channel>
	<title>Comments on: Criticism &#8211; Much Ado About &#8220;Nothing&#8221;</title>
	<atom:link href="http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/feed/" rel="self" type="application/rss+xml" />
	<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/</link>
	<description>Changing HR one post at a time.</description>
	<lastBuildDate>Tue, 24 Apr 2012 16:05:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: mark.stelzner</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16597</link>
		<dc:creator>mark.stelzner</dc:creator>
		<pubDate>Thu, 03 Sep 2009 13:52:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16597</guid>
		<description>@Rebecca - I really like your emphasis on observed behavior and outcomes. Thanks for your terrific thoughts!

@Steve Boese - Thanks for reminding me of the &#039;Abilene Paradox&#039;; it&#039;s a powerful example. I also agree with the idea of &quot;respectful debate&quot; and would love to see more of it in action. 

@Alicia Arenas - You really caught my attention with, &quot;In too many organizations, failure is not an option and that culture kills innovation.&quot; Spot on observation. Thanks Alicia.

@Dan McCarthy - Thanks for the wonderful links and the book recommendation Dan. Great content!

@Michael Benidt - We could all use a refresher on the &quot;LBs and NTs&quot;. Great comments.

@Trish McFarlane - I agree that we&#039;re not encouraged to fail (and learn from those failings) as children. And from where I sit, the pressure for kids to do it &quot;right&quot; the first time is greater than ever. Thanks Trish.

@Laura - Thanks for your thoughts Laura. I love the fact that you actively seek constructive criticism (I&#039;m the same way) but am disheartened (but not surprised) that your superiors are weak in this area.

@Sarah Knife - Hmm. &quot;Tell me more about this&quot; is a very disarming approach. Do you find the recipient self-discovers why you&#039;re posing that question? Very interesting Sarah, thank you.</description>
		<content:encoded><![CDATA[<p>@Rebecca &#8211; I really like your emphasis on observed behavior and outcomes. Thanks for your terrific thoughts!</p>
<p>@Steve Boese &#8211; Thanks for reminding me of the &#8216;Abilene Paradox&#8217;; it&#8217;s a powerful example. I also agree with the idea of &#8220;respectful debate&#8221; and would love to see more of it in action. </p>
<p>@Alicia Arenas &#8211; You really caught my attention with, &#8220;In too many organizations, failure is not an option and that culture kills innovation.&#8221; Spot on observation. Thanks Alicia.</p>
<p>@Dan McCarthy &#8211; Thanks for the wonderful links and the book recommendation Dan. Great content!</p>
<p>@Michael Benidt &#8211; We could all use a refresher on the &#8220;LBs and NTs&#8221;. Great comments.</p>
<p>@Trish McFarlane &#8211; I agree that we&#8217;re not encouraged to fail (and learn from those failings) as children. And from where I sit, the pressure for kids to do it &#8220;right&#8221; the first time is greater than ever. Thanks Trish.</p>
<p>@Laura &#8211; Thanks for your thoughts Laura. I love the fact that you actively seek constructive criticism (I&#8217;m the same way) but am disheartened (but not surprised) that your superiors are weak in this area.</p>
<p>@Sarah Knife &#8211; Hmm. &#8220;Tell me more about this&#8221; is a very disarming approach. Do you find the recipient self-discovers why you&#8217;re posing that question? Very interesting Sarah, thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Knife</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16560</link>
		<dc:creator>Sarah Knife</dc:creator>
		<pubDate>Wed, 02 Sep 2009 17:12:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16560</guid>
		<description>On receiving criticism - especially where you disagree strongly on its merits - its taken me 30 years to discover the third option (options A and B being to agree with it or to disagree). I look forward to asking people &quot;Tell me more about this....&quot;</description>
		<content:encoded><![CDATA[<p>On receiving criticism &#8211; especially where you disagree strongly on its merits &#8211; its taken me 30 years to discover the third option (options A and B being to agree with it or to disagree). I look forward to asking people &#8220;Tell me more about this&#8230;.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16546</link>
		<dc:creator>Laura</dc:creator>
		<pubDate>Wed, 02 Sep 2009 13:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16546</guid>
		<description>I could not agree with this article more! I love constructive criticism and wish I could get more of my bosses to provide it for me. It is the best way that I learn, but despite my requests, very few are good at providing with this information. The scenario I use when offering criticism to co-workers is: start with an overall opinion like, &quot;I think the message of xxx gets across well in this article.&quot; Then I offer some suggestions to improve it, i.e., &quot;But I think that people would understand the initial problem more if you said something like xxx.&quot; Then, depending on whether it is a co-worker or somebody I supervise, I end with my expectation for suggestions such as, &quot;So, please make these changes and we&#039;ll relook at it.&quot; Or &quot;These are just my thoughts, do as you see fit for the project.&quot;</description>
		<content:encoded><![CDATA[<p>I could not agree with this article more! I love constructive criticism and wish I could get more of my bosses to provide it for me. It is the best way that I learn, but despite my requests, very few are good at providing with this information. The scenario I use when offering criticism to co-workers is: start with an overall opinion like, &#8220;I think the message of xxx gets across well in this article.&#8221; Then I offer some suggestions to improve it, i.e., &#8220;But I think that people would understand the initial problem more if you said something like xxx.&#8221; Then, depending on whether it is a co-worker or somebody I supervise, I end with my expectation for suggestions such as, &#8220;So, please make these changes and we&#8217;ll relook at it.&#8221; Or &#8220;These are just my thoughts, do as you see fit for the project.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trish McFarlane</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16403</link>
		<dc:creator>Trish McFarlane</dc:creator>
		<pubDate>Tue, 01 Sep 2009 15:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16403</guid>
		<description>Mark-
You got so many good comments already that the only insight I have to add is possibly why people are not good at constructive criticism.  From a very young age, all we are told (and all we tell our kids) is &quot;NO&quot;.  Don&#039;t do this, don&#039;t do that, you&#039;re doing it wrong, no- like this.  I rarely see a parent take the time to say &quot;Great try kid, just turn this a little more this way...there, you&#039;re doing great.  Keep trying&quot; or things along those lines.  
If those messages are drilled into our heads as kids, it is really a mind shift to try to give feedback in another way.  We have to be re-taught. Just my thoughts.
Trish</description>
		<content:encoded><![CDATA[<p>Mark-<br />
You got so many good comments already that the only insight I have to add is possibly why people are not good at constructive criticism.  From a very young age, all we are told (and all we tell our kids) is &#8220;NO&#8221;.  Don&#8217;t do this, don&#8217;t do that, you&#8217;re doing it wrong, no- like this.  I rarely see a parent take the time to say &#8220;Great try kid, just turn this a little more this way&#8230;there, you&#8217;re doing great.  Keep trying&#8221; or things along those lines.<br />
If those messages are drilled into our heads as kids, it is really a mind shift to try to give feedback in another way.  We have to be re-taught. Just my thoughts.<br />
Trish</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Benidt</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16359</link>
		<dc:creator>Michael Benidt</dc:creator>
		<pubDate>Sun, 30 Aug 2009 13:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16359</guid>
		<description>Hi Mark,

I can&#039;t take credit for it, but when I went through Pryor/CareerTrack training we evaluated each others speeches with this approach.

First, always start with &quot;What I Liked Best about your speech, paper, idea....&quot; (substitute whatever you are evaluating)

Second, &quot;Next Time I&#039;d like to see more......&quot;

It&#039;s called &quot;LB&#039;s and NT&#039;s&quot; for short.</description>
		<content:encoded><![CDATA[<p>Hi Mark,</p>
<p>I can&#8217;t take credit for it, but when I went through Pryor/CareerTrack training we evaluated each others speeches with this approach.</p>
<p>First, always start with &#8220;What I Liked Best about your speech, paper, idea&#8230;.&#8221; (substitute whatever you are evaluating)</p>
<p>Second, &#8220;Next Time I&#8217;d like to see more&#8230;&#8230;&#8221;</p>
<p>It&#8217;s called &#8220;LB&#8217;s and NT&#8217;s&#8221; for short.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan McCarthy</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16358</link>
		<dc:creator>Dan McCarthy</dc:creator>
		<pubDate>Sun, 30 Aug 2009 12:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16358</guid>
		<description>Mark - 
You are right on. Feedback can be one of the most powerful tools for behavioral change, but we tend to dread giving it and receiving it. We&#039;re  not good at it and hard-wired (fight or flight) to reject it. I&#039;ve written a few &quot;how to&quot; posts on the topic (search under feedback):
18 Tips for Receiving Feedback: http://www.greatleadershipbydan.com/2008/02/tough-feedback-tips.html
Tough Feedback Tips: http://www.greatleadershipbydan.com/2008/01/18-tips-for-receiving-feedback.html
I&#039;ve also found the book &quot;Crucial Conversations&quot; to be one of the best &quot;how-to&quot; guides for how to have that tough love talk with someone. And I agree with Steve, Abilene Paradox is a classic for teams on the importance of speaking up.</description>
		<content:encoded><![CDATA[<p>Mark &#8211;<br />
You are right on. Feedback can be one of the most powerful tools for behavioral change, but we tend to dread giving it and receiving it. We&#8217;re  not good at it and hard-wired (fight or flight) to reject it. I&#8217;ve written a few &#8220;how to&#8221; posts on the topic (search under feedback):<br />
18 Tips for Receiving Feedback: <a href="http://www.greatleadershipbydan.com/2008/02/tough-feedback-tips.html" rel="nofollow">http://www.greatleadershipbydan.com/2008/02/tough-feedback-tips.html</a><br />
Tough Feedback Tips: <a href="http://www.greatleadershipbydan.com/2008/01/18-tips-for-receiving-feedback.html" rel="nofollow">http://www.greatleadershipbydan.com/2008/01/18-tips-for-receiving-feedback.html</a><br />
I&#8217;ve also found the book &#8220;Crucial Conversations&#8221; to be one of the best &#8220;how-to&#8221; guides for how to have that tough love talk with someone. And I agree with Steve, Abilene Paradox is a classic for teams on the importance of speaking up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alicia Arenas (@AliciaSanera)</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16342</link>
		<dc:creator>Alicia Arenas (@AliciaSanera)</dc:creator>
		<pubDate>Sat, 29 Aug 2009 23:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16342</guid>
		<description>Mark, this is a great post. I think your comment &quot;most of us do not have the benefit of working in a safe culture where failure is encouraged&quot; is spot on. In too many organizations, failure is not an option and that culture kills innovation. And innovation is the only way companies will be able to obtain and/or keep market share.

Giving people language to use when giving constructive feedback can be helpful. I&#039;ve found three simple phrases (which can be customized to fit most situations) work extremely well:

&quot;When you...&quot;

&quot;It&#039;s an issue/problem because...&quot;

&quot;What I would like to see in the future is...&quot; 
or 
&quot;What would be helpful in the future is... because...&quot;</description>
		<content:encoded><![CDATA[<p>Mark, this is a great post. I think your comment &#8220;most of us do not have the benefit of working in a safe culture where failure is encouraged&#8221; is spot on. In too many organizations, failure is not an option and that culture kills innovation. And innovation is the only way companies will be able to obtain and/or keep market share.</p>
<p>Giving people language to use when giving constructive feedback can be helpful. I&#8217;ve found three simple phrases (which can be customized to fit most situations) work extremely well:</p>
<p>&#8220;When you&#8230;&#8221;</p>
<p>&#8220;It&#8217;s an issue/problem because&#8230;&#8221;</p>
<p>&#8220;What I would like to see in the future is&#8230;&#8221;<br />
or<br />
&#8220;What would be helpful in the future is&#8230; because&#8230;&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Boese</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16338</link>
		<dc:creator>Steve Boese</dc:creator>
		<pubDate>Sat, 29 Aug 2009 22:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16338</guid>
		<description>Excellent post, Mark.  Point number one in particular reminds me of the story of the &#039;Abilene Paradox&#039;, where each member of a group about to make a decision that every individual member disagrees with, all fail to raise an objection, and the &#039;wrong&#039; decision is carried out.  Each person fears raising an objection because they don&#039;t want to be seen as &#039;rocking the boat&#039; and raising an objection or otherwise criticizing the idea. So many times the unwillingness or  perceived lack of support to criticize leads to bad corporate decisions. 

My advice would be to try to instill an environment that not only welcomes all ideas, but also welcomes open and honest discussion of those ideas.  Drive home the need to respectful debate and that it is ok to say, &#039;I disagree&#039; and give your reasons why.  Easier said that done I know, but that is a start in my opinion.</description>
		<content:encoded><![CDATA[<p>Excellent post, Mark.  Point number one in particular reminds me of the story of the &#8216;Abilene Paradox&#8217;, where each member of a group about to make a decision that every individual member disagrees with, all fail to raise an objection, and the &#8216;wrong&#8217; decision is carried out.  Each person fears raising an objection because they don&#8217;t want to be seen as &#8216;rocking the boat&#8217; and raising an objection or otherwise criticizing the idea. So many times the unwillingness or  perceived lack of support to criticize leads to bad corporate decisions. </p>
<p>My advice would be to try to instill an environment that not only welcomes all ideas, but also welcomes open and honest discussion of those ideas.  Drive home the need to respectful debate and that it is ok to say, &#8216;I disagree&#8217; and give your reasons why.  Easier said that done I know, but that is a start in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thedailyreviewer</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16315</link>
		<dc:creator>Thedailyreviewer</dc:creator>
		<pubDate>Sat, 29 Aug 2009 03:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16315</guid>
		<description>Congratulations! Our selection committee compiled an exclusive list of the &lt;a href=&quot;http://thedailyreviewer.com/top/human-resources&quot; rel=&quot;nofollow&quot;&gt;Top 100 human-resources Blogs&lt;/a&gt;, and yours was included! Check it out at http://thedailyreviewer.com/top/human-resources

You can claim your &lt;a href=&quot;http://thedailyreviewer.com/blog/9414&quot; rel=&quot;nofollow&quot;&gt;Top 100 Blogs Award Badge&lt;/a&gt; at http://thedailyreviewer.com/blog/9414

Cheers!

Angelina...</description>
		<content:encoded><![CDATA[<p>Congratulations! Our selection committee compiled an exclusive list of the <a href="http://thedailyreviewer.com/top/human-resources" rel="nofollow">Top 100 human-resources Blogs</a>, and yours was included! Check it out at <a href="http://thedailyreviewer.com/top/human-resources" rel="nofollow">http://thedailyreviewer.com/top/human-resources</a></p>
<p>You can claim your <a href="http://thedailyreviewer.com/blog/9414" rel="nofollow">Top 100 Blogs Award Badge</a> at <a href="http://thedailyreviewer.com/blog/9414" rel="nofollow">http://thedailyreviewer.com/blog/9414</a></p>
<p>Cheers!</p>
<p>Angelina&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rebecca</title>
		<link>http://inflexionadvisors.com/blog/2009/08/28/criticism-much-ado-about-nothing/comment-page-1/#comment-16308</link>
		<dc:creator>Rebecca</dc:creator>
		<pubDate>Fri, 28 Aug 2009 21:57:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.inflexionadvisors.com/blog/?p=179#comment-16308</guid>
		<description>I used to conduct weeklong train-the-trainer sessions (format designed by another company that I had to get certified in) wherein 5 strangers would individually have to get up and teach a section of the program to each other. After their section we did a round robin feedback session, where we pointed out one thing done well and one developmental area (we stayed away from the word &quot;critique&quot; given the negative connotations exacerbating anxiety of having to get up in front of people whom you know will be judging your performance). We used a formula that still serves me well today in the business environment, which is simply stating observed behavior and outcomes. The trick is that many people are not specific enough when it comes to observed behavior (it has to be something you can see or hear), so the feedback comes across more negatively. For example, telling an employee they have a bad attitude is not stating observed behavior.  Rather, the focus should be on what that employee did (that you saw or heard) to make you think it was reflective of a bad attitude. So the first part of the statement would be something to the effect of: &quot;I noticed when the customer asked you about policy, you rolled your eyes.&quot; As important is remembering to state the outcome or impact of said behavior. Too often we assume that the reciever logically knows the outcome, which is often not the case and leads to defensiveness and confusion. Focusing on the outcome helps to diffuse the perception of personal attack because now the feedback is around how behavior impacted something else (customer, project, etc.). So in our previous example you&#039;d follow up with something like: &quot;When you roll your eyes at the customer we risk losing their business.&quot; The &quot;advanced&quot; methodology goes on to step 3 which would be either a suggestion on how to improve OR asking the receiver for a suggestion on how to improve depending on scenario. Additionally, if you know the skill of empathy, you can throw that in to lessen the personal impact and focus on improvement: &quot;It can be annoying when you hear the same question about policy 10 times a day. Knowing that won&#039;t change, what can we do to lessen the annoyance and ensure our customers are served respectfully?&quot; I&#039;m using some simplistic examples but I&#039;ve used this technique for almost 10 years in all types of circumstances when I knew I was going to have a difficult conversation with someone or a group of people, and it works. It helps me focus on the issue rather than the person, and helps the person focus on improvement.</description>
		<content:encoded><![CDATA[<p>I used to conduct weeklong train-the-trainer sessions (format designed by another company that I had to get certified in) wherein 5 strangers would individually have to get up and teach a section of the program to each other. After their section we did a round robin feedback session, where we pointed out one thing done well and one developmental area (we stayed away from the word &#8220;critique&#8221; given the negative connotations exacerbating anxiety of having to get up in front of people whom you know will be judging your performance). We used a formula that still serves me well today in the business environment, which is simply stating observed behavior and outcomes. The trick is that many people are not specific enough when it comes to observed behavior (it has to be something you can see or hear), so the feedback comes across more negatively. For example, telling an employee they have a bad attitude is not stating observed behavior.  Rather, the focus should be on what that employee did (that you saw or heard) to make you think it was reflective of a bad attitude. So the first part of the statement would be something to the effect of: &#8220;I noticed when the customer asked you about policy, you rolled your eyes.&#8221; As important is remembering to state the outcome or impact of said behavior. Too often we assume that the reciever logically knows the outcome, which is often not the case and leads to defensiveness and confusion. Focusing on the outcome helps to diffuse the perception of personal attack because now the feedback is around how behavior impacted something else (customer, project, etc.). So in our previous example you&#8217;d follow up with something like: &#8220;When you roll your eyes at the customer we risk losing their business.&#8221; The &#8220;advanced&#8221; methodology goes on to step 3 which would be either a suggestion on how to improve OR asking the receiver for a suggestion on how to improve depending on scenario. Additionally, if you know the skill of empathy, you can throw that in to lessen the personal impact and focus on improvement: &#8220;It can be annoying when you hear the same question about policy 10 times a day. Knowing that won&#8217;t change, what can we do to lessen the annoyance and ensure our customers are served respectfully?&#8221; I&#8217;m using some simplistic examples but I&#8217;ve used this technique for almost 10 years in all types of circumstances when I knew I was going to have a difficult conversation with someone or a group of people, and it works. It helps me focus on the issue rather than the person, and helps the person focus on improvement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

