<?xml version="1.0"?> 

<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>NetSpeed Learning Solutions &#187; Blog</title>
		<atom:link href="http://www.netspeedlearning.com/company/blog/rss_blog.php" rel="self" type="application/rss+xml" />
		<link>http://www.netspeedlearning.com/</link>
		<description>A periodic blog from members of the NetSpeed Learning Solutions team with thoughts on current trends, challenges and issues facing leadership training and development managers and executives</description>
		<language>en</language>
		<copyright>2012Clay &amp; Associates Inc.</copyright>
		<sy:updatePeriod>daily</sy:updatePeriod>
		<sy:updateFrequency>4</sy:updateFrequency>
		<lastBuildDate>Thu, 17 May 2012 07:23:19</lastBuildDate>
		<generator>NetSpeed Learning Solutions blog</generator>
		<webMaster>lbrodie@netspeedlearning.com</webMaster>
		<ttl></ttl>
		<item>
			<title>What we've got here is a failure to communicate</title>
			<link>http://www.netspeedlearning.com/company/blog/?l=what-weve-got-here-is</link>
			<comments></comments>
			<pubDate>Mon, 30 Apr 2012 18:23:13</pubDate>
			<!--<dc:creator>Leo</dc:creator>-->
			<category><![CDATA[Blog]]></category>
			<!--<category><![CDATA[XXX]]></category>-->
			<guid isPermaLink="false">http://www.netspeedlearning.com/company/blog/?l=what-weve-got-here-is</guid>
			<description><![CDATA[<p><em><img style="float: left; margin: 5px;" src="http://www.netspeedfasttracks.com/132/media_inline/communicate.jpg" alt="" width="195" height="198" /></em></p>
<p><em>What we've got here is a failure to communicate."</em> That's a famous line from the 1967 film <a href="http://en.wikipedia.org/wiki/Cool_Hand_Luke" target="_blank">Cool Hand]]></description>
			<content:encoded><![CDATA[<p><em><img style="float: left; margin: 5px;" src="http://www.netspeedfasttracks.com/132/media_inline/communicate.jpg" alt="" width="195" height="198" /></em></p>
<p><em>What we've got here is a failure to communicate."</em> That's a famous line from the 1967 film <a href="http://en.wikipedia.org/wiki/Cool_Hand_Luke" target="_blank">Cool Hand Luke</a>. And it also is the central finding of a recently reported study published in the April 26 issue of <a href="http://clomedia.com/" target="_blank">Chief Learning Officer Magazine</a>.</p>
<p>A study conducted by Accountemps&nbsp;of more than 1400 Chief Financial Officers (CFOs) found that<strong> lack of communication between staff and management</strong> is the most frequent misstep companies make in managing their teams, with 41% of respondents listing this as the single biggest problem. Coming in a distant second was <strong>lack of recognition and praise</strong>, cited by 28% of respondents. Coming in third at 11% was the complaint of <strong>lack of training, development and/or educational opportunities</strong>.</p>
<p>These results showing communication to be the biggest challenge should not be surprising. In study after study of employee morale, job satisfaction and causes behind employee turnover, poor communication between management and employees often ranks as the single biggest complaint. <a href="http://clomedia.com/articles/view/5080/" target="_blank">Read the study here</a>. And in the meantime, what are you doing to improve communication throughout your organization?</p>]]></content:encoded>
			<!-- <slash:comments>0</slash:comments> -->
		</item>
		<item>
			<title>Collaborative Manufacturing?</title>
			<link>http://www.netspeedlearning.com/company/blog/?l=collaborative-manufacturing</link>
			<comments></comments>
			<pubDate>Wed, 25 Apr 2012 16:09:25</pubDate>
			<!--<dc:creator>Leo</dc:creator>-->
			<category><![CDATA[Blog]]></category>
			<!--<category><![CDATA[XXX]]></category>-->
			<guid isPermaLink="false">http://www.netspeedlearning.com/company/blog/?l=collaborative-manufacturing</guid>
			<description><![CDATA[<p>I'm all about wanting to build community and collaboration. The Economist article,<a href="http://www.economist.com/node/21552902" target="_blank">&nbsp;All Together Now:&nbsp;The advantages of crowdsourcing</a>,&nbsp;has opened my eyes in a way I've never used my eyes]]></description>
			<content:encoded><![CDATA[<p>I'm all about wanting to build community and collaboration. The Economist article,<a href="http://www.economist.com/node/21552902" target="_blank">&nbsp;All Together Now:&nbsp;The advantages of crowdsourcing</a>,&nbsp;has opened my eyes in a way I've never used my eyes to see.</p>
<p>Have you heard of <a href="http://www.shapeways.com/" target="_blank">Shapeways</a>? Or <a href="http://www.quirky.com/" target="_blank">Quirky</a>? Both companies are fascinating in the manufacturing world. Both companies are the epitome of innovation. I highly recommend the six-minute video that's a part of the Economist article. Well worth the watch.&nbsp;</p>
<p>I don't dabble in the stock market, but with hearing what Shapeways and Quirky are doing...perhaps it's time to change my mind.</p>]]></content:encoded>
			<!-- <slash:comments>0</slash:comments> -->
		</item>
		<item>
			<title>Why Didn't Kodak Build Instagram?</title>
			<link>http://www.netspeedlearning.com/company/blog/?l=why-didnt-kodak-build-instagram</link>
			<comments></comments>
			<pubDate>Wed, 18 Apr 2012 21:09:49</pubDate>
			<!--<dc:creator>Leo</dc:creator>-->
			<category><![CDATA[Blog]]></category>
			<!--<category><![CDATA[XXX]]></category>-->
			<guid isPermaLink="false">http://www.netspeedlearning.com/company/blog/?l=why-didnt-kodak-build-instagram</guid>
			<description><![CDATA[<p>I think we've all heard, by now, that Facebook purchased Instagram for $1 billion. Yep, that photo app for your smart phone, that makes the picture look like something from]]></description>
			<content:encoded><![CDATA[<p>I think we've all heard, by now, that Facebook purchased Instagram for $1 billion. Yep, that photo app for your smart phone, that makes the picture look like something from your (at least my) childhood. Who knew a little start-up of thirteen employees could be worth so much? Apparently Facebook did.</p>
<p>But the bigger question still hasn't been answered. Why didn't a big power house (maybe post power, but big none the less) like Kodak create the Instagram concept?</p>
<p>Read <a title="here" href="http://bits.blogs.nytimes.com/2012/04/15/disruptions-innovation-isnt-easy-especially-midstream/" target="_blank">here </a>to find out why.</p>]]></content:encoded>
			<!-- <slash:comments>0</slash:comments> -->
		</item>
		<item>
			<title>Making the case for transparent leadership</title>
			<link>http://www.netspeedlearning.com/company/blog/?l=making-case-for-transparent-leadership</link>
			<comments></comments>
			<pubDate>Thu, 05 Apr 2012 15:14:48</pubDate>
			<!--<dc:creator>Leo</dc:creator>-->
			<category><![CDATA[Blog]]></category>
			<!--<category><![CDATA[XXX]]></category>-->
			<guid isPermaLink="false">http://www.netspeedlearning.com/company/blog/?l=making-case-for-transparent-leadership</guid>
			<description><![CDATA[<p><img style="float: left; margin: 5px;" src="http://www.netspeedfasttracks.com/132/media_inline/Transparent_Leadership.jpg" alt="" width="183" height="174" />When I was a young, inexperienced first time manager for a large, heavily unionized newspaper, I asked my boss whether I]]></description>
			<content:encoded><![CDATA[<p><img style="float: left; margin: 5px;" src="http://www.netspeedfasttracks.com/132/media_inline/Transparent_Leadership.jpg" alt="" width="183" height="174" />When I was a young, inexperienced first time manager for a large, heavily unionized newspaper, I asked my boss whether I could share some information with my team about upcoming plans. And he told me, <em>&ldquo;No, not now. They don&rsquo;t need to know this information.&rdquo; </em>For sure, there will always be situations in which certain sensitive information should not be communicated broadly until the right time.</p>
<p>Increasingly, however, forward-thinking managers are moving away from this old school concept of &ldquo;need to know&rdquo; information-sharing and moving towards a more open, collaborative model, even coining a term for this approach: <em>transparent leadership</em>.</p>
<p>Particularly in this age of social media sites like Facebook, Twitter and You Tube, very little is able to be kept secret these days. Access to information is easier and information &ndash; particularly embarrassing or potentially damaging information &ndash; can now be spread globally literally within minutes. Smart leaders are realizing the benefits of opening up the channels of communication, coaching and collaboration at all levels within organizations. Transparent leadership helps managers at all levels to make better decisions, improve employee morale, reduce turnover and &ndash; get this, increase profits.</p>
<p>In the April 3 issue of CLO Magazine Halley Bock, the CEO of Fierce. Inc. writes an article entitled <strong><em>The Case for Transparent Leadership</em></strong>. In this article she quotes a 2011 Corporate Executive Board survey, which concluded that &ldquo;organizations that successfully broke down barriers and eliminated the fear of retaliation for honest feedback substantially outperformed their peers, delivering 7.9 percent total shareholder return compared with 2.1 percent at other companies.&rdquo;</p>
<p>That&rsquo;s enough to get my attention! <a href="http://clomedia.com/articles/view/the-case-for-transparency-in-leadership/1">Read the complete article here</a>.</p>
<table style="width: 100%;" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>&nbsp;</td>
</tr>
</tbody>
</table>]]></content:encoded>
			<!-- <slash:comments>0</slash:comments> -->
		</item>
		<item>
			<title>What to do when you have one bad apple in the bunch</title>
			<link>http://www.netspeedlearning.com/company/blog/?l=what-to-do-when-you</link>
			<comments></comments>
			<pubDate>Mon, 05 Mar 2012 12:05:52</pubDate>
			<!--<dc:creator>Leo</dc:creator>-->
			<category><![CDATA[Blog]]></category>
			<!--<category><![CDATA[XXX]]></category>-->
			<guid isPermaLink="false">http://www.netspeedlearning.com/company/blog/?l=what-to-do-when-you</guid>
			<description><![CDATA[<p><img style="float: left; margin: 3px;" src="http://www.netspeedfasttracks.com/132/media_inline/one_bad_apple.jpg" alt="" width="175" height="215" />Many years ago, I worked at a newspaper where I managed an advertising sales team. I was pressured by the publisher]]></description>
			<content:encoded><![CDATA[<p><img style="float: left; margin: 3px;" src="http://www.netspeedfasttracks.com/132/media_inline/one_bad_apple.jpg" alt="" width="175" height="215" />Many years ago, I worked at a newspaper where I managed an advertising sales team. I was pressured by the publisher to hire a salesperson he had learned about with whom he was very impressed. But I had serious reservations that this salesperson might not fit in with the rest of the team. He was very experienced and had many contacts in the industry and a track record of success, but I sensed that he would be more concerned with his own self-interest than the team&rsquo;s.</p>
<p>My publisher overruled me, convinced that this person&rsquo;s industry experience and impressive rolodex of contacts with ad agencies would be a boon to our revenues. Against my better judgment, I offered the rep a job. In relatively short order this salesperson began to open up doors where we had previously had little or no success. For sure, his lengthy list of contacts, as my publisher had predicted, netted us several key new advertising clients in large part as a result of this salesperson&rsquo;s previous history with the decision makers. Within a few months, this rep became our #2 selling salesperson. So far so good, right? Not exactly.</p>
<p>It turns out that all my worst fears were realized and then some. He acted like the Big Man On Campus with the rest of the sales team and attempted to steal accounts from several other salespeople. He would have private conversations with customers he knew whose accounts belonged to other salespeople on my team, telling them they should contact me and tell me they would take their business elsewhere unless I would re-assign the account to this rep. By the end of his first year, he had alienated not only the rest of the sales team, but every other department in our newspaper. People did not trust him and he often spread false rumors about other members of the sales team, for his personal gain.</p>
<p>I found that roughly 75% of my conflict management time involved issues in which this salesperson was one of the litigants. I concluded that this person was a cancer on the sales team and needed to go. But my publisher refused to let me fire him because his sales numbers were so strong. It took me another 18 months to finally convince the publisher that this person&rsquo;s negative impact on team morale, chemistry, cooperation and success outweighed the positives in terms of his personal sales numbers.</p>
<p>So the question is: How long do you put up with an employee who is having success in some ways but is undermining your efforts as a manager in other ways, and damaging the success of the team?</p>
<p><strong><a href="http://www.libbywagner.com/about/bio.php">Libby Wagner</a></strong>, an industry thought leader and an expert in leadership, strategy, management, and executive team development, wrote about this very topic recently in an article called <a href="http://campaign.r20.constantcontact.com/render?llr=zsjuwybab&amp;v=001Fhn5qKCt466jDzUHVObJWuQ657wCo9E9BmHTLlg0PBM9dgLGYk7HeQNks-8JbfMrjD2SZusrMjE8KLqGz5obpK1eDCGqc1VUE-49iQJFFgRBh6uO5JG6CfuGAVKOBvkfq5Q8wGT_d--iQItaACC0Qq-iaxF2Z2Ql2Wmi9GCJeQFrAW1r9B5pI6ut4k5lftCDBFuTkVooJjRal8o5khSxpFRBvRAvNZS6f54lHofBusvq1skkjiA8Z4BDXljjDjVKgGi5P0TxCo-XLUXkDGiznfJcGV4agtW2WC28N2NYv2XxDARQ2LNGpQwlKQuKyASJorl1nBjjxwJ1hDgPnfgNoA%3D%3D#LETTER.BLOCK9"><strong><em>Does One Bad Apple Spoil the Bunch? Dealing with a Difficult Team Member</em></strong>.</a> In her article she writes that there comes a point at which no matter how great a star the employee may be in terms of their ability or great ideas or sales numbers, it may be time to get rid of the bad apple in the interest of preserving the success and productivity of the overall team. Wagner points to three highly likely negative consequences from keeping this person too long:</p>
<p><strong>Decrease in morale and loss of good workers.</strong> Your best employees may eventually conclude that it&rsquo;s not worth putting up with the negative impact and look elsewhere for better working conditions.</p>
<p><strong>Loss of credibility in leadership.</strong> If other team members perceive that this person is being held to a different set of standards from the rest of the team, it will erode their trust in and respect for you as their manager.</p>
<p><strong>Lower overall performance.</strong> Which is more important? Having one super star employee who by some metrics performs well but undermines the belief and commitment of the rest of the team? Or remove the cancerous element and watch the overall performance of the rest of the team rise?</p>
<p>Of course, I am not proposing that you simply terminate the difficult employee without first attempting to turn the situation around. Discuss with the employee their negative impact they are having on the team. It is possible they may not be fully aware of their impact. Discuss consequences for failing to change their behavior and if necessary, indicate a deadline by which you need to see substantial improvement.</p>
<p>In the end, if this bad apple&rsquo;s negative behavior does not improve, the risk of harm to the overall success of the team and the organization of keeping them on the team will eventually far outweigh any short-term benefits they may be providing.</p>
<table style="width: 4px; height: 6px;" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>&nbsp;</td>
</tr>
</tbody>
</table>]]></content:encoded>
			<!-- <slash:comments>0</slash:comments> -->
		</item>
 
	</channel>
</rss>

