<?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 for Earned Lessons</title>
	<atom:link href="http://www.earnedlessons.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.earnedlessons.com</link>
	<description>Customer Joy. Employee Success. Investor Wealth.</description>
	<lastBuildDate>Mon, 30 Nov 2009 22:51:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Fold The Company vs Doing Everything You Can by Guy Startup</title>
		<link>http://www.earnedlessons.com/2009/11/30/fold-the-company-vs-doing-everything-you-can/comment-page-1/#comment-186</link>
		<dc:creator>Guy Startup</dc:creator>
		<pubDate>Mon, 30 Nov 2009 22:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=411#comment-186</guid>
		<description>I can relate to this.  I just ended a two-year stint during which I put all the time, money and energy I had into my startup.  I find that there is another litmus test: whether or not you feel like you&#039;re working.  I&#039;m the kind of guy that when I&#039;m doing a think with every fibre of my being, it&#039;s not work.  It&#039;s living.</description>
		<content:encoded><![CDATA[<p>I can relate to this.  I just ended a two-year stint during which I put all the time, money and energy I had into my startup.  I find that there is another litmus test: whether or not you feel like you&#8217;re working.  I&#8217;m the kind of guy that when I&#8217;m doing a think with every fibre of my being, it&#8217;s not work.  It&#8217;s living.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Other people&#8217;s postings by Kate Mats</title>
		<link>http://www.earnedlessons.com/2009/08/19/other-peoples-postings/comment-page-1/#comment-79</link>
		<dc:creator>Kate Mats</dc:creator>
		<pubDate>Tue, 15 Sep 2009 23:54:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=360#comment-79</guid>
		<description>Thanks for the highlight! :)
xoxo, kate</description>
		<content:encoded><![CDATA[<p>Thanks for the highlight! <img src='http://www.earnedlessons.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
xoxo, kate</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Better Meetings &#8212; Openspace Technology by Earned Lessons &#187; Blog Archive &#187; SCRUM Project Planning</title>
		<link>http://www.earnedlessons.com/2009/05/05/openspace-technology/comment-page-1/#comment-72</link>
		<dc:creator>Earned Lessons &#187; Blog Archive &#187; SCRUM Project Planning</dc:creator>
		<pubDate>Wed, 05 Aug 2009 02:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=235#comment-72</guid>
		<description>[...] In running  a project using SCRUM, the activities bear a strong resemblance to what is done with Openspace Technology to run meetings. In using both techniques to communicate and plan, we were able to create an [...]</description>
		<content:encoded><![CDATA[<p>[...] In running  a project using SCRUM, the activities bear a strong resemblance to what is done with Openspace Technology to run meetings. In using both techniques to communicate and plan, we were able to create an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interviewing &#8212; Early Hires (Co-Founders / First Employees) by Robel Alemu</title>
		<link>http://www.earnedlessons.com/2009/05/27/interviewing-early-hires-co-founders-first-employees/comment-page-1/#comment-65</link>
		<dc:creator>Robel Alemu</dc:creator>
		<pubDate>Tue, 14 Jul 2009 20:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=281#comment-65</guid>
		<description>That was very useful!... I myself is passing through the process and its not an easy task,
Thanks for sharing Ruben</description>
		<content:encoded><![CDATA[<p>That was very useful!&#8230; I myself is passing through the process and its not an easy task,<br />
Thanks for sharing Ruben</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Compensation: Transparent/Open systems by Dylan McNamee</title>
		<link>http://www.earnedlessons.com/2009/06/18/compensation-transparentopen-systems/comment-page-1/#comment-58</link>
		<dc:creator>Dylan McNamee</dc:creator>
		<pubDate>Sat, 20 Jun 2009 02:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=325#comment-58</guid>
		<description>My company, Galois, adopted an open, results-based, compensation system last year. The transition from the previous closed system to the new one was a bit painful/awkward, but now that we&#039;re used to it, people seem comfortable with it.</description>
		<content:encoded><![CDATA[<p>My company, Galois, adopted an open, results-based, compensation system last year. The transition from the previous closed system to the new one was a bit painful/awkward, but now that we&#8217;re used to it, people seem comfortable with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interviewing &#8212; Hire or No Hire by Mark</title>
		<link>http://www.earnedlessons.com/2009/03/13/interviewing-hire-or-no-hire/comment-page-1/#comment-31</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 20 May 2009 20:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=175#comment-31</guid>
		<description>Ruben, thanks for the interviewing tips. These are quite helpful.

Do you have any specific advice for finding co-founders or early employees?</description>
		<content:encoded><![CDATA[<p>Ruben, thanks for the interviewing tips. These are quite helpful.</p>
<p>Do you have any specific advice for finding co-founders or early employees?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Search Engine Relevance: User Feedback Loop by Laurel</title>
		<link>http://www.earnedlessons.com/2009/05/19/search-engine-relevance-human-feedback/comment-page-1/#comment-30</link>
		<dc:creator>Laurel</dc:creator>
		<pubDate>Wed, 20 May 2009 14:38:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=266#comment-30</guid>
		<description>One other type of user feedback is asking the user to alter or add to the result.  Wikipedia makes this most prominent, but most sites have this to some degree (yelp, 43 things, wolfram alpha...).

Even google has their &quot;SearchWiki&quot; thing, but it supposedly doesn&#039;t affect other users.</description>
		<content:encoded><![CDATA[<p>One other type of user feedback is asking the user to alter or add to the result.  Wikipedia makes this most prominent, but most sites have this to some degree (yelp, 43 things, wolfram alpha&#8230;).</p>
<p>Even google has their &#8220;SearchWiki&#8221; thing, but it supposedly doesn&#8217;t affect other users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You are what you index by Greg Linden</title>
		<link>http://www.earnedlessons.com/2009/05/12/you-are-what-you-index/comment-page-1/#comment-27</link>
		<dc:creator>Greg Linden</dc:creator>
		<pubDate>Tue, 12 May 2009 16:21:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=244#comment-27</guid>
		<description>I seem to recall that a few years back both Amazon and Microsoft had problems with this.  Amazon vastly expanded their index by adding in the content of many books.  Microsoft Live Search made a big push to increase the size of their web crawl.

In both cases, the index bloat caused many new false positives, and relevance plummeted.  They both took years and much time and effort to improve their rankers to the point that they could weed out all the false positives and get back to their former level of relevance.</description>
		<content:encoded><![CDATA[<p>I seem to recall that a few years back both Amazon and Microsoft had problems with this.  Amazon vastly expanded their index by adding in the content of many books.  Microsoft Live Search made a big push to increase the size of their web crawl.</p>
<p>In both cases, the index bloat caused many new false positives, and relevance plummeted.  They both took years and much time and effort to improve their rankers to the point that they could weed out all the false positives and get back to their former level of relevance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Performance Reviews &#8212; Keep it focused by Greg Linden</title>
		<link>http://www.earnedlessons.com/2009/04/14/performance-reviews-keep-it-focused/comment-page-1/#comment-26</link>
		<dc:creator>Greg Linden</dc:creator>
		<pubDate>Tue, 12 May 2009 16:17:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=209#comment-26</guid>
		<description>The HBS article understates the amount of data arguing for the ineffectiveness of tying pay to performance (e.g. forced rank).  A good book summarizing that work is The Human Equation.

Briefly, the problem is that forced rank and similar systems create a zero sum game where employee is pitted against employee.  It creates a system where people can win by tearing others down inside the company rather than focusing their efforts on working together to compete against those outside the company.

Combine this with the fact that managers rarely are able to do performance reviews correctly -- due to lack of information and gaming of the system -- and you have a recipe for disaster.

In the end, forced rank typically hurts morale and aggravates attrition because no one perceives it as fairly and correctly done.

A good alternative is to use performance reviews solely to help people improve their skills, give non-monetary compensation for individual rewards, and focus monetary compensation on rewarding teams.

If you&#039;re interested in details, there is much more on that in The Human Equation, Strategic Human Resources, and other good books on human resource management.</description>
		<content:encoded><![CDATA[<p>The HBS article understates the amount of data arguing for the ineffectiveness of tying pay to performance (e.g. forced rank).  A good book summarizing that work is The Human Equation.</p>
<p>Briefly, the problem is that forced rank and similar systems create a zero sum game where employee is pitted against employee.  It creates a system where people can win by tearing others down inside the company rather than focusing their efforts on working together to compete against those outside the company.</p>
<p>Combine this with the fact that managers rarely are able to do performance reviews correctly &#8212; due to lack of information and gaming of the system &#8212; and you have a recipe for disaster.</p>
<p>In the end, forced rank typically hurts morale and aggravates attrition because no one perceives it as fairly and correctly done.</p>
<p>A good alternative is to use performance reviews solely to help people improve their skills, give non-monetary compensation for individual rewards, and focus monetary compensation on rewarding teams.</p>
<p>If you&#8217;re interested in details, there is much more on that in The Human Equation, Strategic Human Resources, and other good books on human resource management.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interviewing &#8212; What to ask during an Interview by Greg Linden</title>
		<link>http://www.earnedlessons.com/2009/03/06/interviewing-what-to-ask-during-an-interview/comment-page-1/#comment-25</link>
		<dc:creator>Greg Linden</dc:creator>
		<pubDate>Tue, 12 May 2009 16:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=143#comment-25</guid>
		<description>Good advice here, Ruben.

I see you mentioned expanding in depth during the interview.  That is closest to my personal style of interviewing.

I usually am looking for enthusiasm for a problem, depth of knowledge on that problem, and a willingness to admit the limits to their knowledge.  My strategy is to keep asking probing questions about an area of their previous work, going deeper and deeper, asking them to express why it is important, what they tried, and what they could also have tried.

Ideally, not only does the candidate infect you with their enthusiasm for the problem, but they teach you something.

At least in fast-paced software companies, I think these characteristics best determine someone&#039;s likelihood of success.  I think it selects for people that can get things done quickly using small teams.

That being said, interviewing is difficult and full of false positives and negatives.  Companies like Amazon and Google bias their selection criteria to encourage false negatives -- deeming them less risky than false positives -- but that sadly does prevent many good people from getting through the door.</description>
		<content:encoded><![CDATA[<p>Good advice here, Ruben.</p>
<p>I see you mentioned expanding in depth during the interview.  That is closest to my personal style of interviewing.</p>
<p>I usually am looking for enthusiasm for a problem, depth of knowledge on that problem, and a willingness to admit the limits to their knowledge.  My strategy is to keep asking probing questions about an area of their previous work, going deeper and deeper, asking them to express why it is important, what they tried, and what they could also have tried.</p>
<p>Ideally, not only does the candidate infect you with their enthusiasm for the problem, but they teach you something.</p>
<p>At least in fast-paced software companies, I think these characteristics best determine someone&#8217;s likelihood of success.  I think it selects for people that can get things done quickly using small teams.</p>
<p>That being said, interviewing is difficult and full of false positives and negatives.  Companies like Amazon and Google bias their selection criteria to encourage false negatives &#8212; deeming them less risky than false positives &#8212; but that sadly does prevent many good people from getting through the door.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
