<?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"
	>
<channel>
	<title>Comments on: </title>
	<atom:link href="http://leapcomp.com/2009/10/1049.html/feed" rel="self" type="application/rss+xml" />
	<link>http://leapcomp.com/2009/10/1049.html</link>
	<description></description>
	<pubDate>Mon, 21 May 2012 17:18:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Paul Hebert</title>
		<link>http://leapcomp.com/2009/10/1049.html#comment-20446</link>
		<dc:creator>Paul Hebert</dc:creator>
		<pubDate>Wed, 07 Oct 2009 10:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://leapcomp.com/2009/10/1049.html#comment-20446</guid>
		<description>You're missing the correct answer in your poll.  It is best to reward the team equally AND provide individual awards (non-cash is my recommendation depending on the goal and context of the work).

All of the above options create ill-will within the team.  

The biggest problem with team-based rewards is the free-rider problem where one (or more) team members will ride on the effort of the others - and the others will pick up the slack in order to ensure they get the reward.  Combining team and individual awards helps minimize that problem.</description>
		<content:encoded><![CDATA[<p>You&#8217;re missing the correct answer in your poll.  It is best to reward the team equally AND provide individual awards (non-cash is my recommendation depending on the goal and context of the work).</p>
<p>All of the above options create ill-will within the team.  </p>
<p>The biggest problem with team-based rewards is the free-rider problem where one (or more) team members will ride on the effort of the others - and the others will pick up the slack in order to ensure they get the reward.  Combining team and individual awards helps minimize that problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

