<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-7496986701852108514</atom:id><lastBuildDate>Sun, 11 May 2008 02:43:44 +0000</lastBuildDate><title>Help Desk Journal</title><description/><link>http://helpdesk.wyopub.com/</link><managingEditor>noreply@blogger.com (Steven McElwee, CISSP)</managingEditor><generator>Blogger</generator><openSearch:totalResults>16</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-8643233968147518941</guid><pubDate>Fri, 02 Feb 2007 02:39:00 +0000</pubDate><atom:updated>2008-05-10T21:40:32.018-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Management</category><title>Competing for Performance</title><atom:summary type='text'>Motivation is one of the great challenges of help desk management. Keeping good morale among analysts and encouraging them to strive for continuous improvement is difficult in a line of work where there are so many customer requests, and most of them come from frustrated end users who have already tried everything to resolve their problem on their own.

One great enabler of positive morale in </atom:summary><link>http://helpdesk.wyopub.com/2007/02/competing-for-performance.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-211851445602913431</guid><pubDate>Fri, 02 Feb 2007 02:34:00 +0000</pubDate><atom:updated>2008-05-10T21:36:06.974-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Tools</category><title>Priority Reports for Support Teams</title><atom:summary type='text'>One of the greatest frustrations of customers and help desk associates alike is when a help case must be escalated outside of the help desk. These are the requests that fall into a black hole. The customer calls up regularly to inquire about the status. The help desk contacts the support technician assigned to the case for a status. The customer is frustrated because the delay is affecting her </atom:summary><link>http://helpdesk.wyopub.com/2007/02/priority-reports-for-support-teams.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-1518851755587386731</guid><pubDate>Fri, 02 Feb 2007 02:16:00 +0000</pubDate><atom:updated>2008-05-10T21:18:05.292-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Process</category><title>Finding the Voice of the Help Desk Customer</title><atom:summary type='text'>Do you know what your service desk customers think about the quality of service they receive from you? You may think that you understand their expectations and current performance. You may be unsure, but hope that you are doing well. Finding the voice of the customer and defining your service catalog and service levels around their expectations will guarantee a level of satisfaction higher than </atom:summary><link>http://helpdesk.wyopub.com/2007/02/finding-voice-of-help-desk-customer.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-4929893363414520945</guid><pubDate>Tue, 02 Jan 2007 02:40:00 +0000</pubDate><atom:updated>2008-05-10T21:41:39.005-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Management</category><title>The Help Desk: Dumping Ground or Focused Performance?</title><atom:summary type='text'>Many help desks become the dumping ground for security, administrative tasks, training, non-support communication, change management, and ID setup. In addition, many second or third level support teams use the help desk as a shield to keep away from customer interaction. Most of these things are distractions that cloud your main purpose and prevent you from serving your customers effectively.

</atom:summary><link>http://helpdesk.wyopub.com/2007/01/help-desk-dumping-ground-or-focused.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-5933412108499205613</guid><pubDate>Tue, 02 Jan 2007 02:37:00 +0000</pubDate><atom:updated>2008-05-10T21:39:06.929-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Tools</category><title>Help Desk Performance in a Single Chart</title><atom:summary type='text'>One of the challenges in measuring the performance of any support team is to create a meaningful view of performance. Although it is not possible in a single chart to capture all of the facets of peformance, there is one chart that provides a great monthly peformance dashboard.

This chart, shown below, provides a look at the backlog of open support cases at the beginning of a month, the number </atom:summary><link>http://helpdesk.wyopub.com/2007/01/help-desk-performance-in-single-chart.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-7698470514623103310</guid><pubDate>Tue, 02 Jan 2007 02:23:00 +0000</pubDate><atom:updated>2008-05-10T21:24:00.197-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Process</category><title>Service Catalogs and Service Level Agreements</title><atom:summary type='text'>The first step in creating Service Level Agreements (SLA) or Service Level Objectives (SLO) is to create a service catalog. At its most basic level, a service catalog is a list of all the services your help desk will provide. In most cases, an SLA is used to define the support requirements of a team to which the help desk escalates cases.

The helpdesk may have internal goals for first call </atom:summary><link>http://helpdesk.wyopub.com/2007/01/service-catalogs-and-service-level.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-8717916105817141845</guid><pubDate>Fri, 24 Nov 2006 02:46:00 +0000</pubDate><atom:updated>2008-05-10T21:47:09.344-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Training</category><title>Training for Help Desk Analysts</title><atom:summary type='text'>Help desks can create great entry level positions, since responsibilities can be divided according to skill level, with senior analysts handling the difficult calls and entry level analysts handling more routine calls or email. With this in mind, it's especially important to create a logical progression from entry level to senior level analyst. This will help you to retain the help desk analysts </atom:summary><link>http://helpdesk.wyopub.com/2006/11/training-for-help-desk-analysts.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-5844219648947891731</guid><pubDate>Tue, 05 Sep 2006 01:24:00 +0000</pubDate><atom:updated>2008-05-10T21:25:25.585-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Process</category><title>Daily Service Desk Metrics</title><atom:summary type='text'>The service desk or help desk is a high transaction function. In a perfect world, every case would be resolved in 15 minutes or less. While this is a lofty goal, it demonstrates the transactional characteristics of the service desk.

To keep such transactional work on track, it is not sufficient to have a monthly or weekly meeting to review performance. To be successful you need a daily view of </atom:summary><link>http://helpdesk.wyopub.com/2006/09/daily-service-desk-metrics.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-3518004845343277774</guid><pubDate>Tue, 03 Jan 2006 02:42:00 +0000</pubDate><atom:updated>2008-05-10T21:42:54.969-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Management</category><title>Case-by-Case Customer Satisfaction</title><atom:summary type='text'>One of the most revealing ways to measure your help desk or service desk performance is to survey your customers. There are many approaches to surveying, but some are more effective than others.

Many companies will annually send a customer satisfaction survey to the whole company to gauge performance. There are several problems with this approach. First not everyone surveyed will have used your </atom:summary><link>http://helpdesk.wyopub.com/2006/01/case-by-case-customer-satisfaction.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-1125041115987841262</guid><pubDate>Fri, 04 Nov 2005 02:27:00 +0000</pubDate><atom:updated>2008-05-10T21:28:03.021-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Process</category><title>Create Clear Channels</title><atom:summary type='text'>How easy is it for your help desk or service desk customers to understand how to communicate with you? Many times, it is assumed that the end users know how to follow your predefined processes and that they will follow them naturally. The exact opposite is generally true.

Contacting You By Phone
Let’s start with your phone prompts - when end users call your help desk. Your prompts must </atom:summary><link>http://helpdesk.wyopub.com/2005/11/create-clear-channels.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-3831426624012064561</guid><pubDate>Tue, 23 Aug 2005 01:44:00 +0000</pubDate><atom:updated>2008-05-10T21:44:52.023-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Management</category><title>Erlang What?</title><atom:summary type='text'>So what's all the hype about Erlang C? What does this have to do with leading a help desk?

Erlang is a unit of traffic measurement. It is measured by looking at the usage time for all resources divided by the total time interval. It is used for telecommunications design, architecture, and call centers. It's a great fit for the help desk as well.

On the help desk, Erlang C is a way of </atom:summary><link>http://helpdesk.wyopub.com/2005/08/erlang-what.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-216729700304768516</guid><pubDate>Tue, 23 Aug 2005 01:43:00 +0000</pubDate><atom:updated>2008-05-10T21:43:47.767-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Management</category><title>Why Knowledge Management?</title><atom:summary type='text'>One of the worst labels that is often stuck on help desks at many companies is, "helpless desk." This name is a reaction to what end users feel when they call. Too often they get an analyst who knows less than they themselves know about supporting the product. As a result, the analyst takes up some of the end user's valuable time, only to create a ticket and assign it to a more specialized </atom:summary><link>http://helpdesk.wyopub.com/2005/08/why-knowledge-management.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-149901049607003613</guid><pubDate>Tue, 23 Aug 2005 01:28:00 +0000</pubDate><atom:updated>2008-05-10T21:29:43.391-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Process</category><title>Six Sigma for Help Desks</title><atom:summary type='text'>You've heard the hype about Six Sigma. How companies like GE, Allied Signal, Motorola, and Amazon.com have dramatically improved the quality of their products and services by using it. Did you know that Six Sigma is a perfect fit for Help Desks? If your Help Desk is not meeting your or your customers' expectations, Six Sigma will help you quickly make measurable improvements.

Let's take a look </atom:summary><link>http://helpdesk.wyopub.com/2005/08/six-sigma-for-help-desks.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-3107380872758635623</guid><pubDate>Sat, 20 Aug 2005 01:30:00 +0000</pubDate><atom:updated>2008-05-10T21:30:51.652-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Process</category><title>Measuring the Whole Picture</title><atom:summary type='text'>The biggest key to running an effective Help Desk is measurement. The volume of requests from end users is too high to use subjective measurements. Each request has important data that must be translated into meaningful performance metrics.     In the world of projects, you see the execution unfold over several months. You know what the handful of sponsors and participants of the project think </atom:summary><link>http://helpdesk.wyopub.com/2005/08/measuring-whole-picture.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-7944086224667696392</guid><pubDate>Sat, 02 Jul 2005 01:31:00 +0000</pubDate><atom:updated>2008-05-10T21:32:40.238-04:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Process</category><title>Service Level Agreement (SLA) Boot Camp</title><atom:summary type='text'>Service Level Agreements, or "SLA's" are tricky but useful mechanisms for managing the risk of an on-going relationship with IT service providers. Unfortunately, most SLA's that show up in service contracts as worthless, cosmetic paper additions. SLA's can be extremely powerful tools to help you and your service provider get the most out of a relationship.

What is an SLA?
A service level </atom:summary><link>http://helpdesk.wyopub.com/2005/07/service-level-agreement-sla-boot-camp.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-7496986701852108514.post-3925573399129423708</guid><pubDate>Thu, 02 Jun 2005 00:42:00 +0000</pubDate><atom:updated>2008-05-10T22:43:44.312-04:00</atom:updated><title>Privacy Policy</title><atom:summary type='text'>Your privacy is important to us. Please review our privacy policy.

This privacy policy applies to all publications and web sites offered by Wyomissing Publishing.

If you have questions about this privacy policy, please write to: Wyomissing Publishing, 259 Church Road, Mohnton, PA 19540.

Information Collected During Your Visit

Most Wyomissing Publishing web sites offer free information that </atom:summary><link>http://helpdesk.wyopub.com/2005/06/privacy-policy.html</link><author>noreply@blogger.com (Steven McElwee, CISSP)</author></item></channel></rss>