Information technology is at the forefront of modern businesses.
It’s the core element that enables day-to-day operations in organizations. ITSM, or IT service management, takes care of this core element and optimizes it for better outcomes while driving business value.
It wraps around the IT infrastructure and streamlines processes in the service lifecycle, enabling teams to operate strategically. Furthermore, ITSM software available on the market facilitates it by enabling more efficient, standardized, and effective service delivery.
Let’s dive deeper into understanding ITSM and discover how it can help you optimize your IT infrastructure.
IT service management (ITSM) is a process that ensures maximum business value with efficient use of information technology, people, and processes involved in the lifecycle of IT services.
These services go beyond resolving day-to-day IT issues and IT support to include designing, creating, delivering, and managing activities with information technology at its forefront. It includes core information technology services like AWS and Azure in addition to IT-enabled services, e.g. access to resources, service actions, and so on.
The main objective of ITSM is to provide business value to stakeholders and end-users while improving services continuously. It considers risks and challenges that may arise and sets up proper measures to tackle them and obtain desired results. ITSM draws inspiration from the popular principles and practices in management, such as Agile, Lean-IT, DevOps, and so on.
Simply put, stakeholders are people or organizations who have a stake in the services and their outcomes and want to draw value either through provision or service consumption.
They are the primary customers who pay the bills for these services, sponsors who authorize budgets, individuals or organizations providing financial support, or an end-user. Suppliers, who are responsible for providing these services, are also regarded as stakeholders.
ITSM stakeholders can be divided into two categories:
Internal stakeholders: Professionals who work in the same organization. For internal IT service providers, these are also the customers.
External stakeholders: Parties that are not a part of the same organization. They can be vendors, suppliers, customers, and others.
Before adopting an ITSM framework, be clear on who the actual stakeholders of IT services are. This will help you define roles and responsibilities to supporting units as well as manage interfaces between different roles and business processes.
IT service management aims to reduce IT costs, improve service quality, enhance customer satisfaction, and nurture agility. Most importantly, it intends to deliver value, a perceived benefit or usefulness of a service to a stakeholder.
This value is a combination of both reality and perception of service in the minds of customers. So the outcome of these services must take care of both to prove beneficial. IT service management ensures that this value, encapsulated with good reality and perception, aligns with the business goals and objectives.
As technology evolves, your stakeholders' perception of service may change. ITSM ensures that your service delivery reflects the same. IT service management capabilities hold systems for providing both good reality and good perception over time in varying circumstances.
Altogether, the ITSM process helps you get outcomes enriched with the business value while keeping an untattered focus on costs and satisfaction rates.
Implementation of IT service management requires a cultural change. Stakeholders have to see IT as a service provider rather than recognizing it as just another department in the organization.
Naturally, the implementation process of ITSM differs for organizations as their business values are unique. There are different frameworks like ITIL (Information Technology Infrastructure Library), Cobit, ISO/IEC 20000, Microsoft Operations Framework (MOF), DevOps, and more that you can use for implementing ITSM in your organization.
There are a few things you ponder on while implementing IT service management.
In a company of 20 people, adopting ITSM may not deliver significant results, whereas it would be beneficial in an organization with a larger headcount. So before implementing ITSM, consider your team's size, ability to scale in the near future, possible introduction to new technology, and other similar factors.
It's possible you were doing ITSM informally when your company was small, but when you scale, adopting a formal method will be an advantage, as it would be replicable.
Without proper clarity on your IT service problems, chances are, you would be walking a bumpy road even after implementing ITSM. It's paramount that you define your critical issues first and then choose the ITSM framework.
Whether you want to reduce IT costs or improve service delivery quality, define your problems first and then list the desired outcomes that would be achieved by solving those problems. It will help you align your service toward obtaining results and driving the business value you seek.
After defining your problem statement, the next step is to select the framework that you would use to implement ITSM in your organization. Every framework (ITIL, Cobit, ISO 20000, etc.) will help you streamline your service, reduce friction, and ensure proper IT management. Still, choose one that aligns with your desired business values better, as the IT processes involved in these frameworks are different.
IT service management is an actual practice or a professional discipline for managing IT operations and processes, whereas ITIL is a guiding framework to implement ITSM. ITIL framework ensures standardization in managing IT services, provides common terminology, and facilitates effective communication between organizations and vendors.
People often misinterpret ITIL as a prescriptive framework, whereas it follows a descriptive model. ITIL lays down concepts and principles to implement ITSM with examples of what people do that works now. Remember, these examples are not prescriptions; they may or may not work for you.
If you see an example that looks like it works for you, it may make sense to leverage it, but ITIL's intentional focus is on getting the outcomes, the ends right and clear, and not on prescribing 100% effective forever practices. ITIL's guidance disperses the essence of what people do now that works, which clearly means it's commonly accepted and implemented and not a leading-edge practice.
ITIL is a framework for practitioners written by practitioners. But also, there are various other complementary frameworks and practices developed by different stakeholders for different reasons.
You can find whitepapers that map ITIL to almost any other framework or practice. ISO/IEC - 20000, the first international standard for service management, fits ITIL perfectly well for a purpose – in this case – providing the standard for organizational level certification and audits around IT service management. However, there are emerging practices like Agile, Lean-IT, and DevOps in particular that ITIL4 has embraced substantially.
ITIL v3 was introduced in 2007 back when most IT was on-premise and Cloud was just starting out. This means the practices listed in ITIL v3 resonates well with what you see as the traditional IT infrastructure.
Now, we work with a hybrid of on-premise IT and the cloud. In moving ahead from ITIL v3 to v4, you see that more or less the service outcomes remain the same, but the process of reaching the outcomes changes.
In ITIL v3, it's through a service lifecycle of 26 processes and four functions. In contrast, in ITIL v4, it's through 18 practices, which include processes and functions like DevOps, Agile, and Lean practices in a service value chain.
The basic concept of ITIL v3 is implementation of 4 Ps of ITSM. These 4 Ps refers to people, processes, products, and partners. You can think of them as a proper scope of consideration for project management, any change, or any risk in IT. It helps you add value to every interaction you make in IT while evaluating the surface risks people might face.
On the other hand, ITIL v4 introduces four dimensions of service management. These are organizations and people, information and technology, partners and suppliers, and lastly, value streams and processes. These are roughly similar to the four Ps in ITIL v3, but the key difference is combining information with technology and value stream with processes.
In ITIL v3, ITSM is achieved through five stages in the service lifecycle. These stages and the processes are mentioned as under:
The service operation stage focuses on the practical aspects of day-to-day business operations. It enables your IT department to realize frictionless operations while ensuring reliability, efficiency, and cost-effectiveness. It concentrates on providing value to both customers and the service provider with the processes and functions as follows:
The continual service improvement stage consists of just one process. It's the seven step improvement process. The strategy aims to enhance the IT service provider's efficiency and effectiveness by monitoring and improving performance. It defines and manages the steps needed to identify, gathers, process, analyze, present, and implement a process, service, or improvement.
ITSM or IT service management offers many benefits to organizations that implement it. The most prominent benefits of ITSM practice are as follows:
ITSM helps organizations to gain maximum output from their current IT infrastructure. Asset management, being one of the components here, promotes a better usage of IT products and technology, and facilitates cost-effective procurement and disposition of IT assets.
Altogether, ITSM practice empowers your organization to scale IT operations more effectively, without intensive hiring, as it brings automation to clear out the redundant workload.
ITSM ensures that new or changed services are gradually rolled out with the change management process while reducing the interruption of business operations. It helps you understand policies and roles that aid the process and enables you to adapt to the change progressively.
ITSM practice helps your business adhere to IT compliance by maintaining standard IT services and ensuring accountability. It mandates a service desk and IT helpdesk to exercise a formal procedure for delivering different types of IT services.
As a manager, the practice enhances your ability to track how incidents or service requests are addressed. It helps you achieve high-level visibility on how organizations are delivering IT services.
Adopting ITSM structures and processes helps you benefit from the formalized system that drives improvement over time. As an IT manager, you can identify and track defined key performance indicators (KPIs) and evaluate your team's performance.
When you have a structured incident response process, your average response time, and mean time to resolution can decrease. In contrast, a focus on crisis management will help you reduce your mean time to recover (MTTR) whenever a service interruption occurs.
ITSM offers a management framework to improve IT service delivery through a process of continual service improvement.
Improved service and customer experience
At an enterprise level, the customers are users within the business who depend on IT services to carry out their job. With the service strategy process, enterprises align the services with the need of the business, which means the enterprise is working on services that the business actually wants. It leads to better customer experience.
On the other hand, ITSM involves maintaining a formalized ticketing and incident response system. It improves the service quality as the IT department responds to every incident report or service request submitted.
While implementing ITSM in your organization you may face certain challenges. Take a look at the challenges mentioned below and create your strategy to address them as they emerge.
For successful incident resolution, technicians need to share their knowledge regarding how the issue was fixed. Placing comments like resolved or fixed would not help other technicians who are handling similar types of incidents.
It's important that before closing an incident, you should document your methods and steps involved in its resolution. It will help others to gain substantial inputs for future reference when a similar incident makes a mark.
As an IT admin who manages hundreds of applications on multiple servers, you receive tons of auto-generated monitoring alerts every day.
If one of these alerts slips past your focus, you may unintentionally welcome an unprecedented disaster. To avoid it, it's essential to categorize these alerts properly, prioritize them, and escalate them to application owners at the earliest. This precautionary action acts as a core component in the emergency management process.
Service requests can be as simple as "providing access to a software" or "unlocking a laptop." You can manage these with a self-service portal or by providing technical assistance. Whereas, incidents requests are those that may take more effort and time to resolve.
You should distinguish between the two, as it would take different resolution steps, and the service level agreements (SLAs) would vary. If you mix it up, it can increase the workload on your IT professional as well as the IT costs.
Many organizations are reluctant to adopt new methods or technologies. Some might feel uncomfortable to change if they have absorbed a predefined process into their muscle memory. But it's highly advisable if a certain process or tech helps you clear the redundancies in your routine, you must adopt it.
It helps you improve efficiency and gain productivity by leveraging automation for repetitive tasks. Also, place a standard operating procedure (SOP) and define workflows before implementing the change, so that your teams can be on the same page.
Sometimes, the technician may need assistance from the admin or application owner to resolve the issue for incident requests. Reaching them separately just adds up a delay in the resolution of the request.
Instead, if an incident request arrives where you need help from other teams, you can loop them as well as the customer in the incident. It will help you gain transparency over all conversations and actions taken to resolve the request, enhancing your customer's satisfaction.
* Below are the five leading ITSM software from G2's Fall 2020 Grid® Report. Some reviews may be edited for clarity.
Zendesk Support Suite enables your organization to have natural conversations with your customers. The suite is well-equipped to meet complex needs of the business and simple enough to understand and get up and running immediately.
“I think that Zendesk has made creating general support functionality very simple. It's easy to create triggers (for routing, automatic replies, etc.) and doesn't take a ton of work to implement other than testing the flow by creating tickets. Additionally, macros help create easy answers and replies for your tickets and for your support teams to use.
You can also use a macro to assign ticket values when replying, making it a one touch reply for your more common issues and known solutions. All in all, agent management is a breeze, and assigning groups is relatively straight forward.”
- Zendesk Support Suite Review, Brandon E.
“Unfortunately, the rating system can be a bit difficult to navigate. If a customer were to give a bad rating to a ticket and eventually change their rating to a good one, the metrics and the agent's statistics would not properly show this change.”
- Zendesk Support Suite Review, Aicha B.
Freshservice helps you modernize your service delivery using ITIL best practice while ensuring customer satisfaction. It’s a cloud-based service desk and ITSM solution that serves more than 40000 SMB, mid-market, and enterprise customers worldwide.
“It quickly adjusts to your needs, and the product is improving continually. Their support is fantastic. Even if you have a simple question via live chat, the guys are on it so fast. We have an end-user support base of approx 250 and increasing; Freshservice meets all of our requirements easily.”
- Freshservice Review, Ewan C.
“The only downside I've found so far is that you are allowed only one SLA chart in your dashboard. The way we have groups set up doesn't allow for us to see all the SLA information, by group, that we would like to see.”
- Freshservice Review, Zachary D.
SolarWinds Service Desk is a fully integrated cloud-based service desk and IT asset management solution. It’s based on ITSM best practices and uses automation, AI, and machine learning to optimize and streamline IT support services.
“I really like how easy it is to install, upgrade and manage. We are now taking advantage of the ability to track our assets, along with expiration dates, followed up with notification emails. This really is a phenomenal product, and it costs pennies to purchase and maintain.”
- SolarWinds Service Desk Review, Jennifer A.
“There are some limitations like how much you can customize when notifications are sent or not sent. Also some areas don't get any notifications which is annoying. The reporting is confusing and not straight forward. After a year of use and vendor training, we still don't quite understand how it works and just export our tickets into a CSV to do manually reporting.”
- SolarWinds Service Desk Review, Caleb K.
SysAid is a service management solution that drives value across organizations by enhancing end-user experience and increasing agents’ productivity. It resolves business complex challenges with a built-in asset management, automation, and orchestration capabilities.
“Incident management is the strongest feature of SysAid. It’s really easy to set up and use for experts and novices. Allow customize reports in no time, show lists, views and more, enabling you analyze your data. It has strong BI tools. SysAid's Team is continually working to update those features. You can design your lists for status, and KPIs and put on your dashboard. It’s highly customizable.
The BI section, perhaps, is new and powerful too. You can make almost every kind of stuff in there. Another cool feature is the flow management, you can decide how it works.”
- SysAid Review, Alejandro D.
“The out of the box reporting does not always suit my organization's needs. However, I have spoken to SySaid about this and they have taken many steps to improve reporting. They are currently working on new features to make the out of the box reports much more useful. It is nice that they take their customer's suggestions under consideration.”
- SysAid Review, Jaclyn S.
Jira Service Desk delivers a seamless service experience while catering to your unique needs. It promises a competitive set up time and pricing, making it suited for modern IT teams.
“Jira Service Desk is very user friendly and I can design my own dashboard for better visibility and monitoring our team. It can also generate reports to better interpret the number of tickets we handle everyday.”
- Jira Service Desk Review, Jefferson C.
“The least helpful thing about Jira Service Desk is the difficulty in creating queues for individual employees based on labels. This is a minor inconvenience and does not detract too much from the overall user experience for Jira Service Desk platform.”
- Jira Service Desk Review, Taylor B.
ITSM allows you to manage your IT infrastructure in the most efficient way possible, enabling coordinated planning, designing, and delivering IT services. It helps your organization adopt and adapt to new changes and processes more easily and profitably than before.
Now that you have an in-depth understanding of ITSM, learn more about how ITIL, DevOps, and SRE work together to deliver maximum efficiency in managing your IT infrastructure.
Sagar Joshi is a content marketing specialist at G2 in India. He is a firm believer in the potential of content and its role in helping people. Topics related to security and technology pique his interest and motivates him to write about them. In his free time, you can find him reading books, learning a new language, or playing pool.
How similar are a factory production floor and an office of software developers?
Never miss a post.
Subscribe to keep your fingers on the tech pulse.