<?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: 6: Performance=Results</title>
	<atom:link href="http://www.ldscio.org/2007/01/19/6-performanceresults/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ldscio.org/2007/01/19/6-performanceresults/</link>
	<description>Chief Information Officer for The Church of Jesus Christ of Latter-day Saints</description>
	<lastBuildDate>Mon, 26 Jul 2010 01:33:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: M. McEwen</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-501</link>
		<dc:creator>M. McEwen</dc:creator>
		<pubDate>Fri, 16 Feb 2007 00:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-501</guid>
		<description>A classic on this very subject is Thomas Gilbert&#039;s Book: Human Competence: Engineering Worthy Performance
[Lots to digest, main points made in first several chapters]

Gilbert defines the measure of performance as the ratio of the Accomplishment (A) to the Cost (C).  Therefore a &quot;Worthy performance&quot; is one where this ratio is greater than 1, (W = A/C; where W &gt; 1) i.e. the accomplishment is greater (or of more worth) than the cost of the behavior that brought about the accomplishment.  To increase worthy performance we can increase the value of the Accomplishment or decrease the Cost.  As you can see, more effort (read:Cost) without an increase in Accomplishment only decreases the value of the Worthy performance.  Even if the effort is &quot;unpaid&quot; (overtime, etc.) there is still a very real &quot;cost&quot;.  To make use of this formula one must understand the real value of the accomplishment as well as the real cost to obtain it.

Older book, worth the read - if nothing else to bring a new perspective about defining and evaluating worthy performance.</description>
		<content:encoded><![CDATA[<p>A classic on this very subject is Thomas Gilbert&#8217;s Book: Human Competence: Engineering Worthy Performance<br />
[Lots to digest, main points made in first several chapters]</p>
<p>Gilbert defines the measure of performance as the ratio of the Accomplishment (A) to the Cost (C).  Therefore a &#8220;Worthy performance&#8221; is one where this ratio is greater than 1, (W = A/C; where W &gt; 1) i.e. the accomplishment is greater (or of more worth) than the cost of the behavior that brought about the accomplishment.  To increase worthy performance we can increase the value of the Accomplishment or decrease the Cost.  As you can see, more effort (read:Cost) without an increase in Accomplishment only decreases the value of the Worthy performance.  Even if the effort is &#8220;unpaid&#8221; (overtime, etc.) there is still a very real &#8220;cost&#8221;.  To make use of this formula one must understand the real value of the accomplishment as well as the real cost to obtain it.</p>
<p>Older book, worth the read &#8211; if nothing else to bring a new perspective about defining and evaluating worthy performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Philpot</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-479</link>
		<dc:creator>Nathan Philpot</dc:creator>
		<pubDate>Thu, 08 Feb 2007 15:44:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-479</guid>
		<description>Excellent posting. I have been wanting to tell my managers this for years.</description>
		<content:encoded><![CDATA[<p>Excellent posting. I have been wanting to tell my managers this for years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-428</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 31 Jan 2007 10:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-428</guid>
		<description>This reminds me to two experiences:
1.  In Japan, where I currently work, sales people are rewarded for effort.  Working hard is rewarded even if they do not make any sales.  A very strange way to run a sales department.

2.  As an IT director, I had an employee who I was having a hard time motivating.  Finally, during an interview with him, I found his motivation to be free time to play ping pong and foosball.  I told him if he delivered, he could play games as much as he wanted.  Within a few weeks, the servers and systems he was responsible for had nearly no problems, the backups worked each night, and there were virtually no user-reported problems.  He got to play as much as he wanted.  The one drawback was he was very persuasive, and persuaded folks from other groups to play with him, thus lowering their productivity.</description>
		<content:encoded><![CDATA[<p>This reminds me to two experiences:<br />
1.  In Japan, where I currently work, sales people are rewarded for effort.  Working hard is rewarded even if they do not make any sales.  A very strange way to run a sales department.</p>
<p>2.  As an IT director, I had an employee who I was having a hard time motivating.  Finally, during an interview with him, I found his motivation to be free time to play ping pong and foosball.  I told him if he delivered, he could play games as much as he wanted.  Within a few weeks, the servers and systems he was responsible for had nearly no problems, the backups worked each night, and there were virtually no user-reported problems.  He got to play as much as he wanted.  The one drawback was he was very persuasive, and persuaded folks from other groups to play with him, thus lowering their productivity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KyleM</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-420</link>
		<dc:creator>KyleM</dc:creator>
		<pubDate>Mon, 29 Jan 2007 22:58:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-420</guid>
		<description>Richard,

My boss does it for me.  He knows it will end up costing more to replace me than to give me projects and let me get it done my own way.  I put in 20 hours one week and well over 40 another.  He lets me coach football in the fall (still covering the normal responsibilities of my job), and knows I&#039;ll make it up to him in the winter and spring.  I&#039;ve been here 7 years, and he knows it&#039;s the only reason I&#039;m still here.  He&#039;s OK with it because he knows I get the job done.

The only difference between me and Joel&#039;s employee is that I&#039;m not anoying to be around.  I hope.</description>
		<content:encoded><![CDATA[<p>Richard,</p>
<p>My boss does it for me.  He knows it will end up costing more to replace me than to give me projects and let me get it done my own way.  I put in 20 hours one week and well over 40 another.  He lets me coach football in the fall (still covering the normal responsibilities of my job), and knows I&#8217;ll make it up to him in the winter and spring.  I&#8217;ve been here 7 years, and he knows it&#8217;s the only reason I&#8217;m still here.  He&#8217;s OK with it because he knows I get the job done.</p>
<p>The only difference between me and Joel&#8217;s employee is that I&#8217;m not anoying to be around.  I hope.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd R. Jensen</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-388</link>
		<dc:creator>Todd R. Jensen</dc:creator>
		<pubDate>Thu, 25 Jan 2007 06:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-388</guid>
		<description>I like your focus and in my experience teams that focus on results tend to start &#039;winning&#039; and succeeding, which solves a host of internal problems and distractions (not to mention improving the lives of their customers). I&#039;ve managed performance in the Church for many years and believe employees want clear expectations. Team members appreciate managers who see and reward results rather than monitor and dictate behavior. We shouldn&#039;t forget, in all this, that results must equate to something the customer values.</description>
		<content:encoded><![CDATA[<p>I like your focus and in my experience teams that focus on results tend to start &#8216;winning&#8217; and succeeding, which solves a host of internal problems and distractions (not to mention improving the lives of their customers). I&#8217;ve managed performance in the Church for many years and believe employees want clear expectations. Team members appreciate managers who see and reward results rather than monitor and dictate behavior. We shouldn&#8217;t forget, in all this, that results must equate to something the customer values.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Masters</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-382</link>
		<dc:creator>Justin Masters</dc:creator>
		<pubDate>Wed, 24 Jan 2007 03:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-382</guid>
		<description>Today&#039;s management often wants impossible schedules met in which to satisfy impossible &quot;features&quot; that were sold to customers.

I often say &quot;If you don&#039;t want to spend the time doing it right the first time, when are you going to find the time to do it later?&quot;  

Some managers don&#039;t care, and rely on &quot;Good enough&quot; or &quot;Hope for the best&quot;.  Outstanding companies will listen to their customers and go beyond giving them what they want - they give them GREAT SERVICE.  It seems to be sorely lacking in today&#039;s workplace in so many ways when &quot;going that extra mile&quot; may not always be recognized.  But you&#039;d be surprised when it is...</description>
		<content:encoded><![CDATA[<p>Today&#8217;s management often wants impossible schedules met in which to satisfy impossible &#8220;features&#8221; that were sold to customers.</p>
<p>I often say &#8220;If you don&#8217;t want to spend the time doing it right the first time, when are you going to find the time to do it later?&#8221;  </p>
<p>Some managers don&#8217;t care, and rely on &#8220;Good enough&#8221; or &#8220;Hope for the best&#8221;.  Outstanding companies will listen to their customers and go beyond giving them what they want &#8211; they give them GREAT SERVICE.  It seems to be sorely lacking in today&#8217;s workplace in so many ways when &#8220;going that extra mile&#8221; may not always be recognized.  But you&#8217;d be surprised when it is&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-380</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Tue, 23 Jan 2007 15:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-380</guid>
		<description>It sounds very nice in theory but I have yet to meet the first manager who actually works like that. Why pay a person for a full week when he can apparently do his job properly in 20 hours. Doesn&#039;t make sense to me.

&lt;em&gt;[Joel: The point I was trying to make was really the opposite. If you work 40 hours per week and don&#039;t produce value then you&#039;re not performing. Performance equals results, not effort.]&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>It sounds very nice in theory but I have yet to meet the first manager who actually works like that. Why pay a person for a full week when he can apparently do his job properly in 20 hours. Doesn&#8217;t make sense to me.</p>
<p><em>[Joel: The point I was trying to make was really the opposite. If you work 40 hours per week and don't produce value then you're not performing. Performance equals results, not effort.]</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-375</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Sun, 21 Jan 2007 14:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-375</guid>
		<description>A good manager will also understand what &quot;results&quot; really means. I work in software development (not for the Church), and I see many software engineers getting &quot;results&quot;, but often not &quot;true value&quot; in those results - meaning they constantly finish tasks quickly, but not effectively. But often those tasks do not &quot;hold up&quot; - meaning when the software is moved to production, bugs are everywhere, and then large chunks of code needs to be rewritten and redesigned. I always encourage my team to take a little longer to make sure that their tasks are completed correctly before they are completed quickly. I would rather have a software engineer on my team who completes 10 tasks correctly than 20 tasks partially incorrectly within the same time frame. I will take a quality-conscience employee over a results-conscience employee anyday. Over time, quality is far more productive, and really produces results.</description>
		<content:encoded><![CDATA[<p>A good manager will also understand what &#8220;results&#8221; really means. I work in software development (not for the Church), and I see many software engineers getting &#8220;results&#8221;, but often not &#8220;true value&#8221; in those results &#8211; meaning they constantly finish tasks quickly, but not effectively. But often those tasks do not &#8220;hold up&#8221; &#8211; meaning when the software is moved to production, bugs are everywhere, and then large chunks of code needs to be rewritten and redesigned. I always encourage my team to take a little longer to make sure that their tasks are completed correctly before they are completed quickly. I would rather have a software engineer on my team who completes 10 tasks correctly than 20 tasks partially incorrectly within the same time frame. I will take a quality-conscience employee over a results-conscience employee anyday. Over time, quality is far more productive, and really produces results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Nielsen</title>
		<link>http://www.ldscio.org/2007/01/19/6-performanceresults/comment-page-1/#comment-374</link>
		<dc:creator>Larry Nielsen</dc:creator>
		<pubDate>Sat, 20 Jan 2007 18:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/2007/01/19/6-performanceresults/#comment-374</guid>
		<description>Thanks for the Performance = Results commentary. Upon my first observation of the title (Performance = Results), and the subsequent reading of the content, I translated your meaning to be that performance does not really equal results, but rather it equals only performance be it successful or not. What I did read and understand from between the lines of your message was that success in the acquisition of desired and expected result has much more to do with preparation than performance and that in fact without preparation our performance is somewhat of a charade. I paraphrase Henry Ford: The secret to success is getting ready!</description>
		<content:encoded><![CDATA[<p>Thanks for the Performance = Results commentary. Upon my first observation of the title (Performance = Results), and the subsequent reading of the content, I translated your meaning to be that performance does not really equal results, but rather it equals only performance be it successful or not. What I did read and understand from between the lines of your message was that success in the acquisition of desired and expected result has much more to do with preparation than performance and that in fact without preparation our performance is somewhat of a charade. I paraphrase Henry Ford: The secret to success is getting ready!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
