<?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: &#8216;Slackers&#8217; may actually be more productive, study says</title>
	<atom:link href="http://www.hrtechnews.com/slackers-may-actually-be-more-productive-study-says/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hrtechnews.com/slackers-may-actually-be-more-productive-study-says/</link>
	<description>HRMS, Internet Monitoring, Payroll Software, Time and Attendance, and more</description>
	<lastBuildDate>Thu, 04 Aug 2011 15:58:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: JParr</title>
		<link>http://www.hrtechnews.com/slackers-may-actually-be-more-productive-study-says/comment-page-1/#comment-8708</link>
		<dc:creator>JParr</dc:creator>
		<pubDate>Tue, 28 Apr 2009 23:57:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.hrtechnews.com/?p=1223#comment-8708</guid>
		<description>This may not work for everyone, but here is my approach:

I try to set MBOs as part of the performance management process that include things like learning new skills -- even ones that are IT-related, but may not be directly related to a particular position.  As an example, I encourage my Network folks to learn Windows Server Administration, or my developers to learn networking.

Assuming we have resource capacity, I encourage my staff to research these topics, perform online training, and use non-production equipment for development and testing.  This keeps them engaged, while providing a productive outlet during breaks and slow periods.

I also like to make sure that every team member in any position has a list of either group or individual &quot;back burner&quot; projects that they can work on in spare time.  Ideally, these align with personal goals, like building a Linux desktop image, developing a group-level &quot;status board&quot;, setting up a Wiki, upgrading a non-critical system, etc...

Success Stories:
- Numerous employees worked their way from Help Desk to either Network or Server administration.

- A few employees promoted to leadership roles, and eventually to IT Management roles.

- Numerous &quot;pet projects&quot; that developed in to time saving tools, procedures, and applications.

- Employee was promoted from Help Desk to Business Analyst.  This person worked with the ERP business analysts, learned the application in their spare time, and eventually got promoted.

- Employee worked on a &quot;pet project&quot; that became a corporate-wide standard, and this person became the Subject Matter Expert on implementing it throughout the company (with a healthy promotion and raise thrown in).

This approach can be really good during difficult economic times, when salaries may be fixed or cut, and when bonuses are scarce.

I tend to have people stay with me for 3-5 years, even though the average IT job span is less than 2 years.  Many of them find that when they do leave, there are a variety of opportunities because they have diverse skillsets.  I have had a few people tell me that after a layoff, they were able to find work almost immediately, because some specific skill or project on their resume put them ahead of another candidate.

The other benefit is that you never have the CEO tell you that they just came from the Help Desk, and so-and-so was surfing the net instead of working....</description>
		<content:encoded><![CDATA[<p>This may not work for everyone, but here is my approach:</p>
<p>I try to set MBOs as part of the performance management process that include things like learning new skills &#8212; even ones that are IT-related, but may not be directly related to a particular position.  As an example, I encourage my Network folks to learn Windows Server Administration, or my developers to learn networking.</p>
<p>Assuming we have resource capacity, I encourage my staff to research these topics, perform online training, and use non-production equipment for development and testing.  This keeps them engaged, while providing a productive outlet during breaks and slow periods.</p>
<p>I also like to make sure that every team member in any position has a list of either group or individual &#8220;back burner&#8221; projects that they can work on in spare time.  Ideally, these align with personal goals, like building a Linux desktop image, developing a group-level &#8220;status board&#8221;, setting up a Wiki, upgrading a non-critical system, etc&#8230;</p>
<p>Success Stories:<br />
- Numerous employees worked their way from Help Desk to either Network or Server administration.</p>
<p>- A few employees promoted to leadership roles, and eventually to IT Management roles.</p>
<p>- Numerous &#8220;pet projects&#8221; that developed in to time saving tools, procedures, and applications.</p>
<p>- Employee was promoted from Help Desk to Business Analyst.  This person worked with the ERP business analysts, learned the application in their spare time, and eventually got promoted.</p>
<p>- Employee worked on a &#8220;pet project&#8221; that became a corporate-wide standard, and this person became the Subject Matter Expert on implementing it throughout the company (with a healthy promotion and raise thrown in).</p>
<p>This approach can be really good during difficult economic times, when salaries may be fixed or cut, and when bonuses are scarce.</p>
<p>I tend to have people stay with me for 3-5 years, even though the average IT job span is less than 2 years.  Many of them find that when they do leave, there are a variety of opportunities because they have diverse skillsets.  I have had a few people tell me that after a layoff, they were able to find work almost immediately, because some specific skill or project on their resume put them ahead of another candidate.</p>
<p>The other benefit is that you never have the CEO tell you that they just came from the Help Desk, and so-and-so was surfing the net instead of working&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

