 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Business-Technology Weave &#187; HR management</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/business-technology/tag/hr-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/business-technology</link>
	<description>Closing divides, directing purpose, and achieving results.</description>
	<lastBuildDate>Tue, 21 May 2013 18:52:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>False “Solutions” Continued &#8211; Beware the “Solution” that Adds Layers of Effort to Business Process</title>
		<link>http://itknowledgeexchange.techtarget.com/business-technology/false-%e2%80%9csolutions%e2%80%9d-continued-beware-the-%e2%80%9csolution%e2%80%9d-that-adds-layers-of-effort-to-business-process/</link>
		<comments>http://itknowledgeexchange.techtarget.com/business-technology/false-%e2%80%9csolutions%e2%80%9d-continued-beware-the-%e2%80%9csolution%e2%80%9d-that-adds-layers-of-effort-to-business-process/#comments</comments>
		<pubDate>Tue, 30 Mar 2010 18:16:28 +0000</pubDate>
		<dc:creator>David Scott</dc:creator>
				<category><![CDATA[business management]]></category>
		<category><![CDATA[employee appraisals]]></category>
		<category><![CDATA[employee evaluation]]></category>
		<category><![CDATA[HR appraisals]]></category>
		<category><![CDATA[HR management]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/business-technology/false-%e2%80%9csolutions%e2%80%9d-continued-beware-the-%e2%80%9csolution%e2%80%9d-that-adds-layers-of-effort-to-business-process/</guid>
		<description><![CDATA[  So… what happened to XYZ Corporation’s employee appraisal process?   After implementation of the software, training, and completion of the first annual review of staff with the new appraisal system, something interesting was apparent.  The appraisal process was no better than before.  Appraisals that were supposed to “write themselves” turned out to be shallow, [...]]]></description>
				<content:encoded><![CDATA[<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"> </p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small;font-family: Times New Roman">So… what happened to XYZ Corporation’s employee appraisal process?</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small;font-family: Times New Roman"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small;font-family: Times New Roman">After implementation of the software, training, and completion of the first annual review of staff with the new appraisal system, something interesting was apparent.<span>  </span>The appraisal process was no better than before.<span>  </span>Appraisals that were supposed to “write themselves” turned out to be shallow, trite, and not particularly representative of the employee or their job.<span>  </span>Many managers stated that starting with, and editing, the system-generated material was more difficult than preparing their own fresh draft.<span>  </span>In fact, the “don’t know how to write” assessment was denied by fully articulated and expressive e-mails on the part of managers. </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span><span style="font-size: small;font-family: Times New Roman"> </span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small"><span style="font-family: Times New Roman">As far as the adherence to timeliness for submission of drafts and final appraisals: there was no improvement.<span>  </span>It turned out that automated reminders from the appraisal system were viewed no differently than the reminders that had been sent from HR in the past – and through the same e-mail system.<span>  </span>The recipient viewed appraisal reminders from any source no differently:<span>  </span>They were all essentially “HR.”<span>  </span>One is as easily ignored, or obeyed, as another.<span>  </span>As far as tracking the appraisals HR now had a new burden they hadn’t anticipated – the generation of status reports regarding appraisal production.<span>  </span>The reports capability was paired with the expectation they had set with their senior management; hence the new burden to produce and speak to these reports in management meetings.<span>  </span>Actually, efficiency for all concerned the first year was diminished due to the learning curve, and in everyone’s requirement to “machinate” the process surrounding production of simple text appraisals.<span>  </span></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small;font-family: Times New Roman"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small;font-family: Times New Roman">Even worse, the second year’s effectiveness was no better.<span>  </span>In fact, it seemed to be poorer.<span>  </span>Because appraisals were annual, the organization’s managers didn’t think about the appraisal application for 10 or 11 months (excepting special appraisals such as probationary).<span>  </span>They were “rusty” each year.<span>  </span>Some managers needed refresher training.<span>  </span>Everyone stumbled through the application inefficiently until reacquainting with it.<span>  </span>Therefore, what was supposed to be a “solution” was now a contributor to a larger, layered, problem – to say nothing of having another software suite for the organization to maintain.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span><span style="font-size: small;font-family: Times New Roman"> </span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small"><span style="font-family: Times New Roman">How could this have happened?<span>  </span>The organization was confused.<span>  </span>What happened to their investment?<span>  </span>Where was their return?<span>  </span>Indeed, there was no positive return – there was a <em>negative</em> return.<span>  </span>They were now saddled with expensive software, along with the upgrade schedule required by all business software, with the attendant support burden – HelpDesk, backoffice, and annual user refresher training.<span>  </span>Where did XYZ Corporation go wrong?<span>  </span></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small;font-family: Times New Roman"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0pt;text-align: justify"><span style="font-size: small;font-family: Times New Roman">Next, we’ll examine…</span></p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/business-technology/false-%e2%80%9csolutions%e2%80%9d-continued-beware-the-%e2%80%9csolution%e2%80%9d-that-adds-layers-of-effort-to-business-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
