<?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: Dead Man&#8217;s Curve</title>
	<atom:link href="http://angryweasel.com/blog/?feed=rss2&#038;p=471" rel="self" type="application/rss+xml" />
	<link>http://angryweasel.com/blog/?p=471</link>
	<description>notes and rants about testing and quality from alan page</description>
	<lastBuildDate>Fri, 07 Jun 2013 04:21:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: It’s your career, lead it! &#171; Testastic</title>
		<link>http://angryweasel.com/blog/?p=471&#038;cpage=1#comment-18745</link>
		<dc:creator>It’s your career, lead it! &#171; Testastic</dc:creator>
		<pubDate>Wed, 10 Oct 2012 12:56:06 +0000</pubDate>
		<guid isPermaLink="false">http://angryweasel.com/blog/?p=471#comment-18745</guid>
		<description><![CDATA[[...] Dead Man&#8217;s Curve [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Dead Man&#8217;s Curve [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James McCaffrey</title>
		<link>http://angryweasel.com/blog/?p=471&#038;cpage=1#comment-15865</link>
		<dc:creator>James McCaffrey</dc:creator>
		<pubDate>Sun, 15 Jul 2012 17:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://angryweasel.com/blog/?p=471#comment-15865</guid>
		<description><![CDATA[Very nicely written post Alan. I absolutely agree with your main theme (if I can paraphrase you): stack ranking is bad for employee morale, discourages collaboration, and inhibits innovation, but it&#039;s a price MS employees pay.

One side effect of stack ranking that I haven&#039;t seen mentioned at all is the policy&#039;s possible effect on bringing in top new talent to MS. I heard the following story and I am confident it actually happened. At an event a few weeks ago with 28 Microsoft technical people (developers, testers, program managers, and a couple of other categories), an impromptu straw poll asked, &quot;If the son or daughter of a close friend just graduated from college with a degree in computer science, would you recommend that they apply to Microsoft for a job?&quot;

The results were stunning to me -- zero of the 28 MS technical employees would recommend applying to MS. Follow-up conversations revealed that in all 28 cases, the MS stack-ranking policy was the reason for the no vote.

I&#039;ve worked with HR people for many years. In general most don&#039;t understand technical talent and don&#039;t truly understand how any technical company&#039;s success depends on the talent of the technical employees. I think the reason for this is that the difference between the best and worst HR employee is nowhere near as large as the delta between average and good-to-great technical talent (there is quite a bit of research on this). 

So, if stack-ranking at a company waters down the quality level of the pool of job applicants, then the stack-ranking policy has a very serious, very negative, long-term side effect.

I hope that Microsoft HR has carefully weighed the benefits of using stack-ranking against all the negative side effects.]]></description>
		<content:encoded><![CDATA[<p>Very nicely written post Alan. I absolutely agree with your main theme (if I can paraphrase you): stack ranking is bad for employee morale, discourages collaboration, and inhibits innovation, but it&#8217;s a price MS employees pay.</p>
<p>One side effect of stack ranking that I haven&#8217;t seen mentioned at all is the policy&#8217;s possible effect on bringing in top new talent to MS. I heard the following story and I am confident it actually happened. At an event a few weeks ago with 28 Microsoft technical people (developers, testers, program managers, and a couple of other categories), an impromptu straw poll asked, &#8220;If the son or daughter of a close friend just graduated from college with a degree in computer science, would you recommend that they apply to Microsoft for a job?&#8221;</p>
<p>The results were stunning to me &#8212; zero of the 28 MS technical employees would recommend applying to MS. Follow-up conversations revealed that in all 28 cases, the MS stack-ranking policy was the reason for the no vote.</p>
<p>I&#8217;ve worked with HR people for many years. In general most don&#8217;t understand technical talent and don&#8217;t truly understand how any technical company&#8217;s success depends on the talent of the technical employees. I think the reason for this is that the difference between the best and worst HR employee is nowhere near as large as the delta between average and good-to-great technical talent (there is quite a bit of research on this). </p>
<p>So, if stack-ranking at a company waters down the quality level of the pool of job applicants, then the stack-ranking policy has a very serious, very negative, long-term side effect.</p>
<p>I hope that Microsoft HR has carefully weighed the benefits of using stack-ranking against all the negative side effects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oren Reshef</title>
		<link>http://angryweasel.com/blog/?p=471&#038;cpage=1#comment-15862</link>
		<dc:creator>Oren Reshef</dc:creator>
		<pubDate>Sun, 15 Jul 2012 15:40:48 +0000</pubDate>
		<guid isPermaLink="false">http://angryweasel.com/blog/?p=471#comment-15862</guid>
		<description><![CDATA[I have to review my employees twice a year, and having the same complaints. But I still couldn&#039;t think of a better way to decide on bonuses and compensation while keeping them more-or-less uniform across a company of 10&#039;s of thousands, it can work though if the company has a few 100&#039;s employees so one HR team can manage everyone personally.
The same applies for promotions, and expected performance to title matching]]></description>
		<content:encoded><![CDATA[<p>I have to review my employees twice a year, and having the same complaints. But I still couldn&#8217;t think of a better way to decide on bonuses and compensation while keeping them more-or-less uniform across a company of 10&#8242;s of thousands, it can work though if the company has a few 100&#8242;s employees so one HR team can manage everyone personally.<br />
The same applies for promotions, and expected performance to title matching</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BrentMJensen</title>
		<link>http://angryweasel.com/blog/?p=471&#038;cpage=1#comment-15555</link>
		<dc:creator>BrentMJensen</dc:creator>
		<pubDate>Thu, 12 Jul 2012 15:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://angryweasel.com/blog/?p=471#comment-15555</guid>
		<description><![CDATA[In general, the review model appears to be defined by a classical economic theorist.   It&#039;s assuming it will be participated in by purely rational beings consistently out for their own self-interest.  It overvalues the role of competition and undervalues the irrational emotional behavior people make.

The problem I see with the &quot;distribute talent around the company&quot; theory is that there is massive friction in your way if you score in the low buckets in the curve.   There is an implicit assumption in the model (which has consistently held to be false in my experience)  that scoring low on one team means you will score 
low on another.

People seem to prefer to follow the path with least friction.

So, if you score high, you are motivated to stay.  The team loves you, right?
If you score low, you are also motivated to stay  (new teams don&#039;t want you and/or you are forced to stay (or leave the company))

That leaves the middle bucket, the 3.   If you view yourself as a superstar and got this message, you might choose to leave.   However, the bigger bet is that you&#039;ll stay.   Most people like the folks they are working with and I think most nowadays prefer collaboration as does Alan.

People do move around a lot, but I find it not due to review.   It&#039;s usually the people that individual is working with that&#039;s incenting them.]]></description>
		<content:encoded><![CDATA[<p>In general, the review model appears to be defined by a classical economic theorist.   It&#8217;s assuming it will be participated in by purely rational beings consistently out for their own self-interest.  It overvalues the role of competition and undervalues the irrational emotional behavior people make.</p>
<p>The problem I see with the &#8220;distribute talent around the company&#8221; theory is that there is massive friction in your way if you score in the low buckets in the curve.   There is an implicit assumption in the model (which has consistently held to be false in my experience)  that scoring low on one team means you will score<br />
low on another.</p>
<p>People seem to prefer to follow the path with least friction.</p>
<p>So, if you score high, you are motivated to stay.  The team loves you, right?<br />
If you score low, you are also motivated to stay  (new teams don&#8217;t want you and/or you are forced to stay (or leave the company))</p>
<p>That leaves the middle bucket, the 3.   If you view yourself as a superstar and got this message, you might choose to leave.   However, the bigger bet is that you&#8217;ll stay.   Most people like the folks they are working with and I think most nowadays prefer collaboration as does Alan.</p>
<p>People do move around a lot, but I find it not due to review.   It&#8217;s usually the people that individual is working with that&#8217;s incenting them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Page</title>
		<link>http://angryweasel.com/blog/?p=471&#038;cpage=1#comment-15537</link>
		<dc:creator>Alan Page</dc:creator>
		<pubDate>Thu, 12 Jul 2012 02:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://angryweasel.com/blog/?p=471#comment-15537</guid>
		<description><![CDATA[Good point - I&#039;d list that under positives (although the theory doesn&#039;t work 100% of the time - but what theory does).]]></description>
		<content:encoded><![CDATA[<p>Good point &#8211; I&#8217;d list that under positives (although the theory doesn&#8217;t work 100% of the time &#8211; but what theory does).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prasanna</title>
		<link>http://angryweasel.com/blog/?p=471&#038;cpage=1#comment-15536</link>
		<dc:creator>Prasanna</dc:creator>
		<pubDate>Thu, 12 Jul 2012 02:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://angryweasel.com/blog/?p=471#comment-15536</guid>
		<description><![CDATA[I have always thought that the curve and the internal interview policy was designed to distribute talent across the company and not end up with pockets of &#039;superstar&#039; teams and &#039;dysfunctional&#039; teams. From the company&#039;s perspective, it is probably better to have the superstars spread across different parts of the organization so the company ends up with multiple good teams rather than a single great team.

Of course, we can question the wisdom of such thinking but at least I tend to rationalize the curve to myself this way :)]]></description>
		<content:encoded><![CDATA[<p>I have always thought that the curve and the internal interview policy was designed to distribute talent across the company and not end up with pockets of &#8216;superstar&#8217; teams and &#8216;dysfunctional&#8217; teams. From the company&#8217;s perspective, it is probably better to have the superstars spread across different parts of the organization so the company ends up with multiple good teams rather than a single great team.</p>
<p>Of course, we can question the wisdom of such thinking but at least I tend to rationalize the curve to myself this way <img src='http://angryweasel.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
