<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: How to Build A Successful Corporate Culture</title>
	<atom:link href="http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/</link>
	<description>Managed Services &#38; Cloud Services Blog for VARs &#38; MSPs</description>
	<lastBuildDate>Tue, 14 Feb 2012 18:25:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John Kilgore</title>
		<link>http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/comment-page-1/#comment-47352</link>
		<dc:creator>John Kilgore</dc:creator>
		<pubDate>Mon, 20 Apr 2009 19:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/#comment-47352</guid>
		<description>James - great comment and I couldn&#039;t agree more.  Frankly, some of my most attractive hires have been those looking for a step up from their current position and not a lateral one.  Lateral screams stagnation sometimes.</description>
		<content:encoded><![CDATA[<p>James &#8211; great comment and I couldn&#8217;t agree more.  Frankly, some of my most attractive hires have been those looking for a step up from their current position and not a lateral one.  Lateral screams stagnation sometimes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Panettieri</title>
		<link>http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/comment-page-1/#comment-47342</link>
		<dc:creator>Joe Panettieri</dc:creator>
		<pubDate>Mon, 20 Apr 2009 14:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/#comment-47342</guid>
		<description>James: Great points across the board, but your closing line was the real keeper.</description>
		<content:encoded><![CDATA[<p>James: Great points across the board, but your closing line was the real keeper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Foxall (Tigerpaw Software)</title>
		<link>http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/comment-page-1/#comment-47341</link>
		<dc:creator>James Foxall (Tigerpaw Software)</dc:creator>
		<pubDate>Mon, 20 Apr 2009 14:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mspmentor.net/2009/04/19/how-to-build-a-successful-corporate-culture/#comment-47341</guid>
		<description>Hi Joe!

Corporate culture is one of those things that can be really nebulous for a lot of peope. You&#039;ll study it in an MBA program, but the examples never seem to relate to your specific situation. There are dozens of angles to take on this subject, but since you mentioned avoiding bad hires, I want to chime in on that.

One thing I&#039;ve learned over the years is to find the right person for the job. Yeah, obvious I know. What I mean is that you will often get good applicants that aren&#039;t a perfect match for the job, and it might be tempting to hire them. Perhaps they&#039;re more suited to management but you don&#039;t have a management position available. You hire them anyway because they are sharp and you hope to move them into management someday. The problem is, if that opportunity doesn&#039;t present itself in a timely manner, you end up with an unhappy employee and one that is likely to jump ship for better opportunities.

An example: In the software business, I often see frustrated developers apply for QA positions. They aren&#039;t really dedicated to QA, they are looking for a foot in the door. It&#039;s tempting to think &quot;this guy would be great, his programming experience will really help him trouble-shoot the software&quot;, and that may be true. However, chances are good that he will never be a star at QA engineer and probably never be dedicated to the position. Instead, I look for a guy that wants to break things. By finding someone that has a passion for the job I am trying to fill, I increase the chances that the person will be content and productive.

Bad hires are expensive in both time and money, and turn-over has a negative effect on culture. Take your time and hire the right person. The old adage hire slowly fire quickly is still true today.

James Foxall
Senior Vice President
Tigerpaw Software</description>
		<content:encoded><![CDATA[<p>Hi Joe!</p>
<p>Corporate culture is one of those things that can be really nebulous for a lot of peope. You&#8217;ll study it in an MBA program, but the examples never seem to relate to your specific situation. There are dozens of angles to take on this subject, but since you mentioned avoiding bad hires, I want to chime in on that.</p>
<p>One thing I&#8217;ve learned over the years is to find the right person for the job. Yeah, obvious I know. What I mean is that you will often get good applicants that aren&#8217;t a perfect match for the job, and it might be tempting to hire them. Perhaps they&#8217;re more suited to management but you don&#8217;t have a management position available. You hire them anyway because they are sharp and you hope to move them into management someday. The problem is, if that opportunity doesn&#8217;t present itself in a timely manner, you end up with an unhappy employee and one that is likely to jump ship for better opportunities.</p>
<p>An example: In the software business, I often see frustrated developers apply for QA positions. They aren&#8217;t really dedicated to QA, they are looking for a foot in the door. It&#8217;s tempting to think &#8220;this guy would be great, his programming experience will really help him trouble-shoot the software&#8221;, and that may be true. However, chances are good that he will never be a star at QA engineer and probably never be dedicated to the position. Instead, I look for a guy that wants to break things. By finding someone that has a passion for the job I am trying to fill, I increase the chances that the person will be content and productive.</p>
<p>Bad hires are expensive in both time and money, and turn-over has a negative effect on culture. Take your time and hire the right person. The old adage hire slowly fire quickly is still true today.</p>
<p>James Foxall<br />
Senior Vice President<br />
Tigerpaw Software</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Content Delivery Network via Rackspace Cloud Files: c810422.r22.cf2.rackcdn.com

Served from: www.mspmentor.net @ 2012-02-14 13:46:19 -->
