<?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; People</title>
	<atom:link href="http://www.servicedeskcenter.com/category/people/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>Future Service Desk Characteristics</title>
		<link>http://www.servicedeskcenter.com/future-service-desk-characteristics.html</link>
		<comments>http://www.servicedeskcenter.com/future-service-desk-characteristics.html#comments</comments>
		<pubDate>Thu, 28 Feb 2008 09:09:09 +0000</pubDate>
		<dc:creator>Amos W</dc:creator>
				<category><![CDATA[People]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://www.servicedeskcenter.com/future-service-desk-characteristics.html</guid>
		<description><![CDATA[If you have worked in a Service Desk environment long enough, you will bound to notice some trends as to the directions people, processes and technologies are taking to.  Below are some of the points that I picked up while attending a seminar and I&#8217;ve added my comments for each item pointed out.

The characteristics that [...]]]></description>
			<content:encoded><![CDATA[<p>If you have worked in a Service Desk environment long enough, you will bound to notice some trends as to the directions people, processes and technologies are taking to.  Below are some of the points that I picked up while attending a seminar and I&#8217;ve added my comments for each item pointed out.</p>
<p style="text-align: center"><img src="http://farm4.static.flickr.com/3250/2297947586_08bd9b7887.jpg" alt="Future" /></p>
<p>The characteristics that Service Desk is moving towards are:</p>
<ol>
<li><strong>Increased use of self help</strong> &#8211; As customers and users become more technologically savvy, they are getting braver nowadays to execute remedial efforts.  Compared to a few years back, these group of customers have become bolder and have embraced technology quicker than ever before. It is therefore a good time for Service Desk manager to re-look into their FAQs and knowledge bases so that their customers can help themselves. <span id="more-13"></span></li>
<li><strong>Improved knowledge bases with contextual searching</strong> &#8211; the tools I work with today have appalling knowledge base design.  The categorization of knowledge leaves much to be desired as is with the search function.  Even a simple wizard-based kind of troubleshooting steps is non-existent.  I&#8217;m using a very famous and probably the world&#8217;s best helpdesk system but yet, the knowledge base module is not quite to my standard. In time to come, you will find better knowledge base designs with better search engines.  I will also expect vendors to adopt wizard based diagnostic/troubleshooting process; much like the current Microsoft&#8217;s Troubleshooter.</li>
<li><strong>Reduction or elimination of deskside support</strong> &#8211; With customers becoming bolder and technology-savvier, this characteristic is bound to follow suit. Now that customers are able to perform remedial actions on their own, deskside support will be reduced.  Furthermore, with technologies such as remote access becoming a common tool in all organizations, IT no longer need to be on-site to assist the customer.</li>
<li><strong>Provision of services through a fully integrated service catalog</strong> &#8211; a service catalog lists down your organization&#8217;s service provision along with the description of such services, the service level for service fulfilment, service entitlement, associated cost and procedures to obtain such services.  Comparing analogically, you can imagine the service catalog like a menu in a restaurant.  In time to come, your customers and users can order services right from their desktop where the system will only display the services that they are entitled to.  The request will then be automatically subjected to an automated approval workflow and service providers are constantly reminded of unfillled services so as to meet the service level.</li>
<li><strong>Remote rebuild &amp; self healing workstations</strong> &#8211; these are technologies that are available today.  For example, Microsoft Vista has an inbuilt self healing system where computers are kept running reliably by automatically detecting and resolving many known problems—requiring little or no effort from the user.  It&#8217;s here in the operating system and before long, it&#8217;s moving to specific applications.  Even software developers are improving their software with such technologies so as to minimize support.</li>
<li><strong>Tight integration with IP Telephony</strong> &#8211; Voice Over IP is cheap; Caller ID makes it personal; Service Desk professional can be mobile and yet reachable through a single number; audio conferencing can be made on the fly; video conversation is available; instant messaging communications is available &#8211; no wonder organizations are embracing IP Telephony.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.servicedeskcenter.com/future-service-desk-characteristics.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Should Service Desk Professionals Be Dressed?</title>
		<link>http://www.servicedeskcenter.com/how-should-service-desk-professionals-be-dressed.html</link>
		<comments>http://www.servicedeskcenter.com/how-should-service-desk-professionals-be-dressed.html#comments</comments>
		<pubDate>Tue, 05 Feb 2008 14:00:44 +0000</pubDate>
		<dc:creator>Amos W</dc:creator>
				<category><![CDATA[People]]></category>
		<category><![CDATA[Thoughts]]></category>

		<guid isPermaLink="false">http://www.servicedeskcenter.com/how-should-service-desk-professionals-be-dressed.html</guid>
		<description><![CDATA[Believe it or not, this question has popped up many times in the course of my career as a Service Desk manager.   Many young managers as I was have pondered on this and some managers have even had their subordinates asking if casual dressing is allowed in operations.

Just like many before me, I [...]]]></description>
			<content:encoded><![CDATA[<p>Believe it or not, this question has popped up many times in the course of my career as a Service Desk manager.   Many young managers as I was have pondered on this and some managers have even had their subordinates asking if casual dressing is allowed in operations.</p>
<p style="text-align: center"><img src="http://farm3.static.flickr.com/2224/2243592237_6a1c76b345.jpg" alt="Firemen Uniform" height="199" width="300" /></p>
<p>Just like many before me, I have asked the question before.  From what I gather, there are 3 situations that influence what Service Desk professionals should wear.  The 3 situations are:</p>
<p><span id="more-11"></span></p>
<ol>
<li><strong>Corporate Culture</strong> &#8211; If your organisation requires everyone to be dressed in uniforms, then it is a no-brainer that your Service Desk professional should dressed in that.  With free uniforms and possibly free laundry, I do not foresee any problems for your subordinates to be dressed in them.  If your organisation does not provide uniforms but expects everyone to be dressed in suit and tie, you can either follow suit or beg to change (read next point)</li>
<li><strong>Customer Facing</strong> &#8211; My rule of thumb for dressing is simple, if your Service Desk professional faces the customer; i.e. allow walk-ins or performs desk-side support, then the said professional should be dressed appropriately.  Yes, I would expect a long sleeve shirt and tie to begin with.  Either that or a nicely pressed tee-shirt with corporate logo for branding.</li>
<li><strong>Non-customer Facing</strong> &#8211; If your Service Desk professional does not leave their seat for 8 hours; and they do not accept walk-ins; chances are that it does not matter what they are dressed in as long as it is decent.  After all, we live, work and interact in a community.  Broadly speaking, uncontrolled dressing allows your team members to dress in what they are most comfortable in (pajamas not allowed).  Comfortable clothings in turn allow your Service Desk professionals to work longer and at ease.  It might even raise their productivity and efficiency.</li>
</ol>
<p>I guess the above pretty sums it all up.  The next time you hear someone raise this question, do point them to ServiceDeskCenter.com <img src='http://www.servicedeskcenter.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.servicedeskcenter.com/how-should-service-desk-professionals-be-dressed.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Deal With Resignation of Key Staff</title>
		<link>http://www.servicedeskcenter.com/how-to-deal-with-resignation-of-key-staff.html</link>
		<comments>http://www.servicedeskcenter.com/how-to-deal-with-resignation-of-key-staff.html#comments</comments>
		<pubDate>Wed, 30 Jan 2008 05:32:18 +0000</pubDate>
		<dc:creator>Amos W</dc:creator>
				<category><![CDATA[People]]></category>
		<category><![CDATA[Thoughts]]></category>

		<guid isPermaLink="false">http://www.servicedeskcenter.com/how-to-deal-with-resignation-of-key-staff.html</guid>
		<description><![CDATA[Let&#8217;s face the truth.  No employee is going to work for you at Service Desk for a long period of time.  Even if you have, it is a rare feat.  Long period here means something like 3 years and beyond.  If you have noticed, Service Desk is akin to a lightning [...]]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s face the truth.  No employee is going to work for you at Service Desk for a long period of time.  Even if you have, it is a rare feat.  Long period here means something like 3 years and beyond.  If you have noticed, Service Desk is akin to a lightning rod.  You always takes the first, hardest, most painful strike; while protecting the every entity you work for, you are generally not given a proper recognition of the sufferings you and your team go through.  It&#8217;s a fact, it is widely known but more often that not, management considers that a job they paid you for.</p>
<p align="center"><img src="http://farm3.static.flickr.com/2358/2229532783_af5db32aaf.jpg?v=0" alt="Lightning Strike on Town" align="middle" height="225" width="300" /></p>
<p>Given the high dynamic forces of incidents at attack you and your team, day and night, relentless as the sun rises and sets, human beings on Service Desk experiences burnouts.  <a href="http://en.wikipedia.org/wiki/Burnout_%28psychology%29">Wikipedia defines burnout</a> as &#8220;<em>a psychological term for the experience of long-term exhaustion and diminished interest (depersonalization or cynicism), usually in the work context</em>&#8221;  and further suggests that it is a &#8220;<em>result of a period of expending too much effort at work while having too little recovery</em>&#8220;.  Sounds familiar, doesn&#8217;t it?  Of course it does; it&#8217;s referring to your working environment.  It is said that the average lifespan of a Service Desk professional is 18 months.  That&#8217;s a short 1.5 years.  Based on my experience, this assumption seems to be holding water.</p>
<p><span id="more-10"></span><br />
So far, I have been assuming that Service Desk professional may leave you because of a highly stressed environment but that doesn&#8217;t discount the fact that people may leave the organisation for better pay, better benefits, career advancement, current bitchy boss, horrible clientele and a whole lot of other reasons.</p>
<p>When a key staff resigns, it is most attributed to burnouts.  The longest key staff I had is 3 years and she&#8217;s leaving for a same pay, less stressful work.  I can&#8217;t blame her because my team is truly the global lightning rod for my organisation.  We always get hit the hardest.  In this kind of situation, what would you have done?  The first response that any manager would make is to counteroffer whatever she is getting elsewhere.  In my humble opinion, that would only prolong her for a little while longer.  It&#8217;s not a permanent solution and you will continue to face such situations.</p>
<p>This is where foundation of your Service Desk is important.  It&#8217;s a long road to the illusive perfection; a long road to have your team work like a clock.  Things that need to be done are:</p>
<ol>
<li><strong>Be process oriented</strong> &#8211; like a clock, have your team move at their own gears&#8217; pace; everyone share the same goal, the same function, the same rotation and everyone knows when to chime.  This can only happen when you have standard operating procedures and standard methodologies.</li>
<li><strong>Document documents</strong> &#8211; for everything that your staff does, have it documented and verified.  Verification is simple; have a layman do what the document says.  If the layman is able to obtain the expected results, the document should pass with flying colours.</li>
<li><strong>Identify alternates</strong> &#8211; no one should be the sole custodian to a process.  Make sure there is at least another person who is able to perform the same function.</li>
<li><strong>Panic</strong> &#8211; If you do not have 1, 2 &amp; 3, offer your resigning staff and start working on 1, 2 &amp; 3.</li>
</ol>
<p>When you have the necessary in place, you should not fear when a key staff resigns.  It&#8217;s part of life and you are prepared for such a change.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.servicedeskcenter.com/how-to-deal-with-resignation-of-key-staff.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
