<?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>Service Desk Center &#187; Measuring</title>
	<atom:link href="http://www.servicedeskcenter.com/category/measuring/feed" rel="self" type="application/rss+xml" />
	<link>http://www.servicedeskcenter.com</link>
	<description>How I Am Keeping My Service Desk Alive</description>
	<lastBuildDate>Thu, 28 Feb 2008 09:09:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Induce Ad Hoc Quality Checks</title>
		<link>http://www.servicedeskcenter.com/induce-ad-hoc-quality-checks.html</link>
		<comments>http://www.servicedeskcenter.com/induce-ad-hoc-quality-checks.html#comments</comments>
		<pubDate>Mon, 17 Dec 2007 15:08:27 +0000</pubDate>
		<dc:creator>Amos W</dc:creator>
				<category><![CDATA[Improving]]></category>
		<category><![CDATA[Measuring]]></category>
		<category><![CDATA[helpdesk]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[service desk]]></category>

		<guid isPermaLink="false">http://www.servicedeskcenter.com/induce-ad-hoc-quality-checks.html</guid>
		<description><![CDATA[Your Service Desk is one of the most process oriented team compared to the rest of the IT groups in the organization.  What this means is that your team members are expected to follow procedures to the very last bit; especially if you attend to requests of security nature; e.g. resetting of passwords, creation of [...]]]></description>
			<content:encoded><![CDATA[<p>Your Service Desk is one of the most process oriented team compared to the rest of the IT groups in the organization.  What this means is that your team members are expected to follow procedures to the very last bit; especially if you attend to requests of security nature; e.g. resetting of passwords, creation of new users</p>
<p style="text-align: center"><img src="http://farm3.static.flickr.com/2178/2117383911_c4d33f17bb.jpg" alt="a red circular button with the word TEST embossed on it" height="219" width="300" /></p>
<p>Process and procedures can be rigid and restrictive.  Humans tend to slack after a while because over time, no incidents have happened even though they slacked.  Take my case for example; over a period of time, signature in forms are no longer verified because all the while, the requests that came into Service Desk are genuine, or rather, assumed to be genuine.  Just because no incidents has occurred, it does not mean that something has not happened; it also does not mean that nothing is ever going to happen.</p>
<p><span id="more-8"></span><br />
Being complacent is just so dangerous.  If one of your team members start to develop a lackadaisical attitude, it will spread to the rest of the team in no time.  Trust me, I&#8217;ve been there and it takes a huge effort to change that habit.  As the famous saying goes, <em>Prevention is Better Than Cure</em>, rings true in Service Desk too.  Once in a while, on an ad hoc basis, you have to press that Test button to check the quality of your team&#8217;s work.  To add on a weightage to your new ad hoc quality checks, build this into your team&#8217;s Key Performance Indicators so that they know you mean business.</p>
<p>Knowing that you will spring surprises on them, your team members will be constantly on their toes; bringing about a slight increase in work pressure, which can be reduced through appropriate rewards.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.servicedeskcenter.com/induce-ad-hoc-quality-checks.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
