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

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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

Search