Skip to main content

Value of the Service Desk

Respond more quickly to urgent business needs and incidents while simultaneously providing stable, secure and predictable IT services, despite the fact that the systems on which the business operates are typically fragile and hostile to change.  Sound familiar?  Improving operational reliability and communications between ITSM functions and processes begins at the Service desk.

I have to quote a coworker of mine at this point “All things flow through incident management”.  The service desk is the eyes and the ears of the IT organization.  If you think about it and utilize the service desk from both an operational and tactical perspective , ensuring that all of the other ITSM processes and functions are feeding accurate and up to date information and data that the service desk needs, they can become the glue that that binds the entire organization together in alignment with both IT and strategic business  goals.  A single great process alone cannot deliver as much value to the organization as many processes working together in a coordinated effort.  We must be able to effectively capitalize on the entire support organizations knowledge and expertise, forcing it to the lowest common denominator, where it can be utilized when engaging the customer /user.
The value statement here is reduced re-work, less downtime, better utilization of higher cost resources by eliminating the need to escalate incidents and requests to a higher level of technical expertise; increasing the stability of the overall environment and delivering predictable levels of IT services (Quality).
Today in ITSM circles there is much talk of IT being a strategic partner with the business and in my view we are.  Almost everything the business undertakes has some IT component and cost to it.  However, the perception of most senior business managers is that IT is just a cost of doing business, nothing strategic about that. So it is imperative that before we begin the journey of changing that perception we have to show how IT provides value for money.  That begins with delivering the right set of services, at a consistent and predictable level to meet those Agreed SLAs and of course that begins with a high performance Service Desk.

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…