<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Managers are from Mars, Performance Appraisals from Venus</title>
	<atom:link href="http://runningagile.com/2008/02/02/of-rewards-and-teams/feed/" rel="self" type="application/rss+xml" />
	<link>http://runningagile.com/2008/02/02/of-rewards-and-teams/</link>
	<description>A Practitioner&#039;s View To Lean &#38; Agile</description>
	<lastBuildDate>Sat, 28 Jan 2012 15:46:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Are Annual Performance Reviews Pointless? &#171; Peter Hobday&#39;s Blog</title>
		<link>http://runningagile.com/2008/02/02/of-rewards-and-teams/#comment-1286</link>
		<dc:creator><![CDATA[Are Annual Performance Reviews Pointless? &#171; Peter Hobday&#39;s Blog]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 21:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://runningagile.wordpress.com/?p=66#comment-1286</guid>
		<description><![CDATA[[...] This is divisive and demoralising, especially as most people over-rate their own performance. William M Fox argues that effort should only be made to solicit ratings for the extreme performers. My own [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This is divisive and demoralising, especially as most people over-rate their own performance. William M Fox argues that effort should only be made to solicit ratings for the extreme performers. My own [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William M. Fox</title>
		<link>http://runningagile.com/2008/02/02/of-rewards-and-teams/#comment-217</link>
		<dc:creator><![CDATA[William M. Fox]]></dc:creator>
		<pubDate>Wed, 03 Sep 2008 21:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://runningagile.wordpress.com/?p=66#comment-217</guid>
		<description><![CDATA[Perhaps these research-based observations about performance appraisals will be of interest:
 
GIVE CREDIT FOR GOOD FORM.  If the only dimension of performance we needed to be concerned with were the number of widgets produced each hour - without reference to how this was achieved (regarding waste of material impact upon fellow workers, being on time, etc.) - then no formal, performance-appraisal system would be needed. 
 
However, rarely is this the case. Usually, physical conditions, external events, and the behavior of others (e.g. time required for the best team-building efforts to have effect) interact to determine outcomes. Therefore, adequate attention should be given to productive, work-relevant behaviors - not just immediate, physical output - on the part of each individual.
 
IDENTIFY WORK-RELEVANT BEHAVIORS VIA THE  CRITICAL INCIDENT TECHNIQUE. Court decisions stress the need for appraisal criteria that are based upon explicit, job-analysis data, rather than general characteristics; such as, attitude toward people, resourcefulness, leadership, capacity for growth, and loyalty to the organization.
 
The Critical Incident Technique (CIT) produces quite explicit data. Those who are most knowledgeable about a job (supervisors, incumbents, peers, subordinates, clients, etc.) are asked to describe, independently, specific incidents of efffective and ineffective job behavior they have observed over the past 6-12 months.  Next, they meet to classify those incidents that they agree are positively or negatively critical into different perforrmance dimensions and assign relative weights to these. These incident data can then be used to inform new job inductees, guide remedial action, and indicate the the types of behavioral documentation that will be required for supporting &quot;star&quot; and &quot;inadequate performer&quot;
nominations.
 
EXCLUDE THE MIDDLE - SOLICIT RATINGS FOR ONLY EXTREME PERFORMERS. In virtually any organization, you will obtain much better agreement as to who are the &quot;stars,&quot; and who are the &quot;inadequate performers,&quot; than you will as to who is &quot;above average,&quot;  &quot;average,&quot; and &quot;below average.&quot;  Yet, in most organizations, assignment of these middle-three ratings consumes a disproportionate amount of supervisory time and causes the most dissension and resentment among the troops. 
 
The label &quot;average&quot; has a negative conotation to good employees, for we know that average performance in a superior organization is not the same thing as average performance in a mediocre one. Why not simply tell these middle people that they are valued menbers of the team and give them CIT data on how to be &quot;stars&quot; and avoid being &quot;inadequate performers.&quot;
 
USE MULTIPLE SOURCES AND, WHERE FEASIBLE, MULTIPLE RATERS FOR A SOURCE. Studies show that ratings from those closest to the performance dimension being rated - in terms of knowledge about the dimension and opportunity to observe behavior relative to it - are more valid than ratings from other sources.  In addition, the pooling of ratings from several knowledgeable raters for the same source, when available, are preferable to one rater for that source, in terms of measurement reliability and inclusiveness. Of course, all &quot;star&quot; and &quot;inadequate performer&quot; ratings should be documented with CIT determined behaviors.
 
USE A COORDINATION PANEL TO PROCESS EVALUATIONS WHEN THERE IS MORE THAN ONE ORGANIZATIONAL UNIT.  A Coordination Panel (comprising a representative from each organizational unit and chaired by a top-level officer) should be established to check on the adequacy of each unit&#039;s CIT preparation, review inputs from the various units to assure interunit fairness, handle appeals from aggrieved personnel, and otherwise monitor the operation of the system.  The panel also determines how to make trade-offs between goal achievement and goal difficulty.
 
SOLICIT FEEDBACK FROM RATEES.  No supervisor or other rater is all-seeing and all-knowing.  In a rating-review session, the supervisor should regard the overall rating of a ratee to be tentative until the ratee (previously given all CIT data about his or her job) has had the opportunity to input any additional critical-incident data not communicated by the supervisor or challenge any communicated data.  Then, if necessary, the supervisor may need to confirm the validity of such data before continuing the performance review. 
 
A more complete presentation will be found in my article: &quot;Improving Performance Appraisal Systems,&quot;  NATIONAL PRODUCTIVITY REVIEW.  Winter 1987-1988, Vol. 7, No. 1, pages 20-27.
 
William M. Fox
gryfox@bellsouth.net
Professor Emeritus, Management and Organizational Behavior
University of Florida
6605 SW 37th Way
Gainesville, FL 32608
(352) 376-9786]]></description>
		<content:encoded><![CDATA[<p>Perhaps these research-based observations about performance appraisals will be of interest:</p>
<p>GIVE CREDIT FOR GOOD FORM.  If the only dimension of performance we needed to be concerned with were the number of widgets produced each hour &#8211; without reference to how this was achieved (regarding waste of material impact upon fellow workers, being on time, etc.) &#8211; then no formal, performance-appraisal system would be needed. </p>
<p>However, rarely is this the case. Usually, physical conditions, external events, and the behavior of others (e.g. time required for the best team-building efforts to have effect) interact to determine outcomes. Therefore, adequate attention should be given to productive, work-relevant behaviors &#8211; not just immediate, physical output &#8211; on the part of each individual.</p>
<p>IDENTIFY WORK-RELEVANT BEHAVIORS VIA THE  CRITICAL INCIDENT TECHNIQUE. Court decisions stress the need for appraisal criteria that are based upon explicit, job-analysis data, rather than general characteristics; such as, attitude toward people, resourcefulness, leadership, capacity for growth, and loyalty to the organization.</p>
<p>The Critical Incident Technique (CIT) produces quite explicit data. Those who are most knowledgeable about a job (supervisors, incumbents, peers, subordinates, clients, etc.) are asked to describe, independently, specific incidents of efffective and ineffective job behavior they have observed over the past 6-12 months.  Next, they meet to classify those incidents that they agree are positively or negatively critical into different perforrmance dimensions and assign relative weights to these. These incident data can then be used to inform new job inductees, guide remedial action, and indicate the the types of behavioral documentation that will be required for supporting &#8220;star&#8221; and &#8220;inadequate performer&#8221;<br />
nominations.</p>
<p>EXCLUDE THE MIDDLE &#8211; SOLICIT RATINGS FOR ONLY EXTREME PERFORMERS. In virtually any organization, you will obtain much better agreement as to who are the &#8220;stars,&#8221; and who are the &#8220;inadequate performers,&#8221; than you will as to who is &#8220;above average,&#8221;  &#8220;average,&#8221; and &#8220;below average.&#8221;  Yet, in most organizations, assignment of these middle-three ratings consumes a disproportionate amount of supervisory time and causes the most dissension and resentment among the troops. </p>
<p>The label &#8220;average&#8221; has a negative conotation to good employees, for we know that average performance in a superior organization is not the same thing as average performance in a mediocre one. Why not simply tell these middle people that they are valued menbers of the team and give them CIT data on how to be &#8220;stars&#8221; and avoid being &#8220;inadequate performers.&#8221;</p>
<p>USE MULTIPLE SOURCES AND, WHERE FEASIBLE, MULTIPLE RATERS FOR A SOURCE. Studies show that ratings from those closest to the performance dimension being rated &#8211; in terms of knowledge about the dimension and opportunity to observe behavior relative to it &#8211; are more valid than ratings from other sources.  In addition, the pooling of ratings from several knowledgeable raters for the same source, when available, are preferable to one rater for that source, in terms of measurement reliability and inclusiveness. Of course, all &#8220;star&#8221; and &#8220;inadequate performer&#8221; ratings should be documented with CIT determined behaviors.</p>
<p>USE A COORDINATION PANEL TO PROCESS EVALUATIONS WHEN THERE IS MORE THAN ONE ORGANIZATIONAL UNIT.  A Coordination Panel (comprising a representative from each organizational unit and chaired by a top-level officer) should be established to check on the adequacy of each unit&#8217;s CIT preparation, review inputs from the various units to assure interunit fairness, handle appeals from aggrieved personnel, and otherwise monitor the operation of the system.  The panel also determines how to make trade-offs between goal achievement and goal difficulty.</p>
<p>SOLICIT FEEDBACK FROM RATEES.  No supervisor or other rater is all-seeing and all-knowing.  In a rating-review session, the supervisor should regard the overall rating of a ratee to be tentative until the ratee (previously given all CIT data about his or her job) has had the opportunity to input any additional critical-incident data not communicated by the supervisor or challenge any communicated data.  Then, if necessary, the supervisor may need to confirm the validity of such data before continuing the performance review. </p>
<p>A more complete presentation will be found in my article: &#8220;Improving Performance Appraisal Systems,&#8221;  NATIONAL PRODUCTIVITY REVIEW.  Winter 1987-1988, Vol. 7, No. 1, pages 20-27.</p>
<p>William M. Fox<br />
<a href="mailto:gryfox@bellsouth.net">gryfox@bellsouth.net</a><br />
Professor Emeritus, Management and Organizational Behavior<br />
University of Florida<br />
6605 SW 37th Way<br />
Gainesville, FL 32608<br />
(352) 376-9786</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curious Cat Management Improvement Blog &#187; Don&#8217;t Use Performance Appraisals</title>
		<link>http://runningagile.com/2008/02/02/of-rewards-and-teams/#comment-59</link>
		<dc:creator><![CDATA[Curious Cat Management Improvement Blog &#187; Don&#8217;t Use Performance Appraisals]]></dc:creator>
		<pubDate>Mon, 11 Feb 2008 13:44:36 +0000</pubDate>
		<guid isPermaLink="false">http://runningagile.wordpress.com/?p=66#comment-59</guid>
		<description><![CDATA[[...] Managers are from Mars, Performance Appraisals from Venus discusses Mary Poppendieck&#8217;s recent presentation - Appraisals and Compensation: The Elephant in the Room Mary says that there is no valid research showing benefits of performance appraisals. Simply said, &#8220;it doesn’t work&#8221;. Her biggest complain is that appraisals target individuals (sometimes teams) rather the system itself. She also condemns judgment rather than feedback (system dynamic). [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Managers are from Mars, Performance Appraisals from Venus discusses Mary Poppendieck&#8217;s recent presentation &#8211; Appraisals and Compensation: The Elephant in the Room Mary says that there is no valid research showing benefits of performance appraisals. Simply said, &#8220;it doesn’t work&#8221;. Her biggest complain is that appraisals target individuals (sometimes teams) rather the system itself. She also condemns judgment rather than feedback (system dynamic). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hunter</title>
		<link>http://runningagile.com/2008/02/02/of-rewards-and-teams/#comment-58</link>
		<dc:creator><![CDATA[John Hunter]]></dc:creator>
		<pubDate>Mon, 11 Feb 2008 03:44:17 +0000</pubDate>
		<guid isPermaLink="false">http://runningagile.wordpress.com/?p=66#comment-58</guid>
		<description><![CDATA[Great post.  For those interested in what management should do about performance appraisal I suggest reading what &lt;a href=&quot;http://curiouscat.com/deming/performanceappraisal.cfm&quot; rel=&quot;nofollow&quot;&gt;Dr. Deming and Peter Scholtes say about abolishing performance appraisal&lt;/a&gt;.]]></description>
		<content:encoded><![CDATA[<p>Great post.  For those interested in what management should do about performance appraisal I suggest reading what <a href="http://curiouscat.com/deming/performanceappraisal.cfm" rel="nofollow">Dr. Deming and Peter Scholtes say about abolishing performance appraisal</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pages tagged "agile"</title>
		<link>http://runningagile.com/2008/02/02/of-rewards-and-teams/#comment-47</link>
		<dc:creator><![CDATA[Pages tagged "agile"]]></dc:creator>
		<pubDate>Mon, 04 Feb 2008 19:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://runningagile.wordpress.com/?p=66#comment-47</guid>
		<description><![CDATA[[...] bookmarks tagged agile   Of rewards and teams&#160;saved by 4 others  &#160;&#160;&#160;&#160;EverybodyONEartH bookmarked on 02/04/08 &#124; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] bookmarks tagged agile   Of rewards and teams&nbsp;saved by 4 others  &nbsp;&nbsp;&nbsp;&nbsp;EverybodyONEartH bookmarked on 02/04/08 | [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

