Skip to main content

Making the Case for Self-Help

HDI (formerly Help Desk Institute) recently released its 2009 Practices and Salary survey and reports that an incident resolved via the telephone costs $22, while an incident resolved via self-help costs $12. Furthermore, 11 percent of the organizations surveyed report that self-help tools are prompting a decrease in the number of incidents reported to the Service Desk. Having said that, these organizations also report that only three percent of incidents are resolved via self-help.

With the Baby Boomers retiring and technically savvy Gen Y joining the workforce – and, oh yeah, the economy – the time has come to get serious about self-help as a support channel.

Many think the solution lies in finding and installing the right technology; however, new technology projects often fail from a lack of preparation and management. Here’s where the four Ps come in to play. Introduced in the ITIL Service Design publication, the four Ps – in the context of self-help – include:

People – How can you incent people to capture and share their knowledge and to use self-help and Knowledge Management Systems?

Processes – How can you take a more formal approach to processes such as Request Fulfillment, Problem Management, and Knowledge Management?

Products – What tools can you use and how can you integrate those tools with existing technologies such as Incident Management Systems and web-based systems?

Partners – How can you convert partners’ knowledge and expertise into a capability?

In our busy society, people have become accustomed to using self-help and self-services. Our customers appreciate services that enhance their self-sufficiency and enable them to accomplish tasks at their own pace. Self-help can be as simple as a list of FAQs. Or, self-help services can provide customers the ability to search an online knowledge base, reset a password, or download approved software.

To make the most effective use of the four Ps when deploying self-help, you should first determine the roles of processes such as Request Fulfillment and Incident, Problem, and Knowledge Management. Then, determine the roles of the people who are stakeholders in those processes, including your customers. You can then determine your requirements, evaluate and implement the products required to automate those processes and enable people to fulfill their roles. Be sure you make the best possible use of partner (vendor, consultant, and contractor) resources along the way, whether by utilizing their self-help resources, or by adopting and adapting the experience and best practices offered by their staff.

Will all of your customers use self-help? No, and not always. You still need a great Service Desk on the front line. However, a well-trained Service Desk can encourage the use of self-help in a positive way, and promote its benefits. Benefits that go not only to your customers, but to your entire support organization as well.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…