ServiceNow for IT
Service Management

Manage, Transform, and Deliver IT
Operations and Services with Incident, Problem
and Change Management Using ServiceNow
and ITSM Framework

Mohammad Khaleelullah Khan

www.orangeava.com

Copyright © 2025 Orange Education Pvt Ltd, AVA ®

All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.

Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author nor Orange Education Pvt Ltd or its dealers and distributors, will be held liable for any damages caused or alleged to have been caused directly or indirectly by this book.

Orange Education Pvt Ltd has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capital. However, Orange Education Pvt Ltd cannot guarantee the accuracy of this information. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.

First Published: September 2025

Published by: Orange Education Pvt Ltd, AVA ®

Address: 9, Daryaganj, Delhi, 110002, India

275 New North Road Islington Suite 1314 London,

N1 7AA, United Kingdom

ISBN (PBK): 978-93-49888-54-8

ISBN (E-BOOK): 978-93-49888-69-2

Scan the QR code to explore our entire catalogue

www.orangeava.com

Dedicated To

Every Man and Woman Navigating Hardship.

This Book is Also Dedicated to Your Strength,
Your Resilience, and Your Enduring Spirit.

And

To The Families Who Stand beside Them.

About the Author

Mohammad Khaleelullah Khan is a seasoned IT professional with over 12 years of experience in IT Service Management. With a passion for helping organizations optimize their IT operations, he has held key roles such as ITSM Consultant and ITIL Implementation Specialist. Over the past five years, he has also delivered ITIL training to multinational IT organizations, sharing the principles detailed in this book with global teams.

Throughout his career, the author has successfully implemented and managed the critical ITSM frameworks discussed in these chapters, including Incident, Problem, and Change Management. This practical experience is backed by ITIL certifications demonstrating a mastery of the latest advancements in the field. In this book, he brings a unique perspective and valuable insights, distilling wealth of experience into a practical guide for every ITSM professional.

When he is not focused on optimizing IT operations, he enjoys life in Pune with his family. An avid writer of stories and poems, he draws inspiration from both technology and travel. As an ardent motorcycle enthusiast, Khaleelullah Khan has explored the country extensively on two wheels, and co-founded the bike rental company, " Zing Bikes ," turning a personal passion into an entrepreneurial venture.

He approaches life with a simple philosophy: "If a problem has a solution, there is no need to worry. If there is no solution, worrying will do no good."

About the Technical Reviewer

"Time and experience have taught me that, in the long run, we are remembered and recognized for our actions and attitude—not our designation or position. So, let’s embrace the mantra of Learn Together and Grow Together ."

Dr. Atul Grover , also known as Learn N Grow (LNG) on LinkedIn and YouTube, brings over 16 years of extensive experience in the IT industry, specializing in Business Process Consulting and Business Analysis. He has a strong background in Service Management (ITIL/ITSM) and ServiceNow ecosystem. As a veteran and passionate ServiceNow trainer, Atul has delivered more than 37 guest lectures at colleges across India and London. He has conducted 24 training batches across various ServiceNow modules, successfully training more than 5,000 participants.

A passionate YouTuber, Atul believes in the power of knowledge sharing. He has been recognized with the Most Valuable Professional (MVP) award by ServiceNow three times and was honoured with the Creative Catalyst Award in 2025 . Atul holds a post-graduation in computer applications and has recently been awarded a Doctorate in Business Management for his research in the Metaverse domain.

Atul has worked with several multinational companies and is currently based in the UK, providing his expertise to various clients. He has collaborated with major brands such as Accenture , Infosys , Wipro , and Vodafone Shared Services . Additionally, Atul has authored two books and presented at multiple international conferences, earning the Best Paper Award in 2023 at one such event.

Acknowledgements

There are a few people, I would like to thank for their continued and unwavering support throughout the writing of this book. First and foremost, I would like to thank my family and friends for continuously encouraging me to write the book — I could have never completed this book without their wholehearted support.

My heartfelt thanks goes to my colleagues and the leadership at AVEVA for fostering a supportive environment that made this book possible. I am profoundly grateful to all the people who have crossed my path—whether in a boardroom or a coffee shop—every interaction has been a lesson, and I carry a piece of that wisdom with me. I gratefully acknowledge Mr. Atul Grover for his thoughtful technical review of this book. It was a privilege to have a respected expert in the ServiceNow field take time to evaluate this work, and his contribution has been invaluable.

Lastly, I extend my sincere gratitude to the team at Orange Education Pvt. Ltd. for their unwavering support and patience in giving me ample time to complete this book.

Preface

In today's digitally driven world, the effective management of IT services is no longer just a technical function, it is the backbone of business success. From ensuring seamless daily operations to enabling strategic innovation, IT Service Management (ITSM) is the discipline that aligns technology with the needs of the organization. Yet, for many, the world of ITSM can seem complex, filled with frameworks, processes, and tools that can be daunting to a newcomer. This book was written to demystify that world!

Whether you are an IT professional new to service management, a business leader curious about how technology services are efficiently delivered, or a student aspiring to build a career in this dynamic field, this guide is ideal for you. Our journey will begin with the foundational concepts of ITSM, breaking down the essentials in plain language. We will then introduce you to ServiceNow, the powerful, cloud-based platform that has become a global standard for automating and streamlining digital workflows.

With theory and platform established, we will embark on a practical, deep dive into the core processes that make IT run smoothly. From the front lines of the Service Desk to the strategic management of Incidents, Problems, and Changes, each chapter is designed to build upon the last, providing you with a comprehensive understanding of not just the "what" and " why ," but also the " how ."

Thus, my goal is to provide a clear, practical, and accessible roadmap to the principles and practices of modern IT Service Management. By the end of this book, you will not only understand how technology supports business needs, but will also be equipped with the foundational knowledge to navigate and contribute to the digital workflows that power today's enterprises.

Chapter Summaries

Chapter 1: This chapter will help you understand how IT services are managed to support business needs. Hence, whether you are new to IT, or simply curious about how organizations deliver tech services efficiently, this chapter breaks down the essentials in plain and simple language.

Chapter 2: This chapter provides a comprehensive introduction to ServiceNow, a powerful cloud-based platform designed to streamline and automate IT and business processes. It will equip you with a foundational knowledge of how ServiceNow works, and why it is a leading platform in the digital workflow space, preparing you to explore and navigate it confidently in real-world scenarios.

Chapter 3: In this chapter, we will discuss the functionality of the Service Desk. It will provide the foundational knowledge of its purpose in IT Service Management, and how it operates as the central point of contact within ServiceNow.

Chapter 4: This chapter introduces Service Requests, which are formal requests from users for access to IT services, hardware, software, or information. It also delves into Request Fulfilment, the process by which these requests are handled from initiation to completion. Understanding the Request Fulfilment Lifecycle within ServiceNow will provide insight into how automation, approvals, and workflows collaborate to ensure timely and accurate delivery.

Chapter 5: This chapter provides a foundational understanding of Incident Management, a necessary practice within the IT Service Management framework. We will introduce the role of the Incident Manager, a central figure responsible for coordinating the resolution process, and provide a comprehensive breakdown of the Incident Lifecycle, from detection to resolution, designed to minimize service disruption.

Chapter 6: In this chapter, we will explore the complete journey of Problem Management, from its core concepts to its importance within ITSM. We will highlight how effective Problem Management delivers value by reducing incident volumes and improving service

Chapter 7: In this chapter, we will explore the fundamental components of Change Management, including its identification, assessment, planning, implementation, and post-change review. We will also examine the importance of key elements such as Change Requests (RFCs), Change Models, and Change Advisory Boards (CABs) to ensure that changes are evaluated and implemented efficiently. Additionally, we will provide a practical overview of how Change Management is executed using ServiceNow.

Chapter 8: This chapter explores the interconnected disciplines that collectively support the stability, efficiency, and growth of IT service delivery. We will also cover Event Management, Knowledge Management, the Configuration Management Database (CMDB), Release and Deployment Management, DevOps, and the vital practice of Continuous Service Improvement (CSI).

Get a Free eBook

We hope you are enjoying your recently purchased book! Your feedback is incredibly valuable to us, and to all other readers looking for great books.

If you found this book helpful or enjoyable, we would truly appreciate it, if you could take a moment to leave a short review with a 5 star rating on Amazon. It helps us grow, and lets other readers discover our books.

As a thank you, we would love to send you a free digital copy of this book, and a 30% discount code on your next cart value on our official websites:

www.orangeava.com

www.orangeava.in (For Indian Subcontinent)

Here's how:

Leave a review for the book on Amazon.

Take a screenshot of your review, and send an email to info@orangeava.com (it can be just the confirmation screen).

Once, we receive your screenshot, we will send you the digital file, within 24 hours.

Thank you so much for your support - it means a lot to us!

Colored Images

Please follow the links or scan the QR codes to download the Images of the book:

You can find code bundles of our books on our official Github Repository. Go to the following link to and QR code to explore the further:

https://github.com/orgs/ava-orange-education/repositories

Please follow the link to download the Colored Images of the book:
https://rebrand.ly/ae15523

In case there's an update to the code, it will be updated on the existing GitHub repository.

Errata

We take immense pride in our work at Orange Education Pvt Ltd , and follow best practices to ensure the accuracy of our content to provide an indulging reading experience to our subscribers. Our readers are our mirrors, and we use their inputs to reflect and improve upon human errors, if any, that may have occurred during the publishing processes involved. To let us maintain the quality and help us reach out to any readers who might be having difficulties due to any unforeseen errors, please write to us at :

errata@orangeava.com

Your support, suggestions, and feedback are highly appreciated.

DID YOU KNOW

Did you know that Orange Education Pvt Ltd offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.orangeava.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at: info@orangeava.com for more details.

At www.orangeava.com , you can also read a collection of free technical articles, sign up for a range of free newsletters, and receive exclusive discounts and offers on AVA ® Books and eBooks.

PIRACY

If you come across any illegal copies of our works in any form on the internet, we would be grateful if you would provide us with the location address or website name. Please contact us at info@orangeava.com with a link to the material.

ARE YOU INTERESTED IN AUTHORING WITH US?

If there is a topic that you have expertise in, and you are interested in either writing or contributing to a book, please write to us at business@orangeava.com . We are on a journey to help developers and tech professionals to gain insights on the present technological advancements and innovations happening across the globe and build a community that believes Knowledge is best acquired by sharing and learning with others. Please reach out to us to learn what our audience demands and how you can be part of this educational reform. We also welcome ideas from tech experts and help them build learning and development content for their domains.

REVIEWS

Please leave a review. Once you have read and used this book, why not leave a review on the site that you purchased it from? Potential readers can then see and use your unbiased opinion to make purchase decisions. We at Orange Education would love to know what you think about our products, and our authors can learn from your feedback. Thank you!

For more information about Orange Education, please visit www.orangeava.com .

C HAPTER 1

Introduction to IT Service Management

Introduction

Welcome to the world of IT Service Management!

This chapter will help us to understand how IT services are managed to support business needs. Whether you are new to IT, or simply curious about how organizations deliver tech services efficiently, this chapter breaks down the essentials in plain language.

Imagine a world where every time you needed help with technology. Hence, whether it is a crashed computer, a slow network, or a broken app—someone fixed it quickly and efficiently. That is IT Service Management.

Have you ever wondered how businesses keep their technology running smoothly? That is where IT Service Management comes in, IT Service Management is the backbone of efficient IT operations. IT operations are the tasks and services handled by a company’s IT team to keep its technology systems running smoothly, supported, and well-managed. ITSM ensures that technology supports business goals, not the other way around. Think of ITSM as a playbook for delivering, managing, and improving IT services.

Businesses rely on IT to serve customers, consumers, employees, suppliers and partners. Let us consider a simple example of IT Service Management in Real Life:

Imagine you work at “ Sweet Tooth’s Bakery ,” a small business that sells cakes online. The bakery uses online portal for order acceptance and payment gateway, and hence, relies on technology for orders, payments, deliveries and Maintenance. Here is how IT Service Management helps them run smoothly, just like it does for big companies.

The Problem: Website Crashes During Peak Hours

Scenario : Every Friday at 3 PM, Sweet Tooth’s online ordering system slows down or crashes. Customers get frustrated, orders are lost, and sales drop.

How ITSM Practices Guide the Resolution: ITSM does not directly fix the issue, instead, it provides a structured framework and processes that guide how the issue will be identified, managed, and resolved effectively. In the case of Sweet Tooth’s online ordering system crashing every Friday at 3 PM, ITSM defines how to manage and fix the problem through the following steps.

1. Reporting the Issue (Service Desk – First Point of Contact)

What Happens? Customers or internal staff report that the website is down or slow.

ITSM Action: The Service Desk logs the issue as an incident, categorizes it, assigns priority, and escalates, if needed.

2. Restore Service Quickly (Incident Management)

Goal: Minimize disruption by getting the website back up as soon as possible. If not a permanent solution, the issue can also be fixed by a temporary fix.

What Happens? A high-priority incident is raised. Teams work to restore service, and communicates updates to stakeholders as well as escalates to support teams for resolution.

3. Identify the Root Cause (Problem Management)

Goal: Investigate and eliminate the underlying cause of the recurring crash.

What Happens? Since this happens every Friday, a Problem Ticket (record) is created to find the root cause of the issue. Technical teams conduct a Root Cause Analysis (RCA). Once discovered, they implement the resolution. If no root cause is discovered, the issue might be categorised as Risk.

4. Deploy the Fix Safely (Change Enablement)

Goal: Implement a permanent solution with minimal risk .

What Happens? A fix is proposed to permanently resolve the Issue. The fix needs to be applied without introducing new issues. A ticket ( Change Request ) is raised, reviewed for risk and impact, approved by a dedicated team (Change Advisory Board), tested, and deployed in a planned window.

5. Supporting Related User Needs (Request Management)

Goal: Handle standard user requests that may arise from the incident.

What Happens? After the crash, users might raise requests for refunds, access logs, performance reports, or status updates. These requests are handled separately from incidents via predefined workflows.

6. Learn and Prevent (Knowledge Management)

Goal: Capture lessons learned, and share solutions.

What Happens? Once the root cause and resolution are confirmed, an article or a document is created known as Knowledge Article. This includes the problem summary, fix steps, impact, and future prevention measures.

Action: Help the Service Desk and support teams respond faster to similar issues in the future.

How ITSM Provides a Structured Framework:

Issues are not ignored or patched haphazardly, they are logged, analyzed, and resolved methodically.

Roles and responsibilities are clearly defined (service desks, support teams, change managers, and so on).

Communication is structured, users and stakeholders are kept informed.

Improvements are continuous as learning from incidents ensures better service in the future.

ITSM Matters for Any Business:

Whether it is a bakery, a hospital, or a bank, ITSM works the same way:

Fixes immediate issues (incident management).

Finds the root cause, workarounds and permanent solutions (problem management).

Manages and deploys changes safely (change management).

Handles requests efficiently (service request management).

Structure

In this chapter, the following topics will be covered:

Service and Service Management

IT Service Management

History of IT Service Management

Framework of IT Service Management

Benefits of using ITSM

Difference between Traditional Management and Service Management

Service Management Stakeholders – Roles and Responsibilities

Trends and Future of Service Management

Introduction to ITIL: A Framework of ITSM

Service and Service Management

How often do you hear and use the word, “ Service ”? If you are an IT Professional, you might be hearing a lot. But what about people who are not familiar with IT, how would they define Services? In the simplest way, we can define Services as an act of aiding or helping by providing solutions to customers’ problems. By ITIL4 definition, “Services are a means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks” . Here, the customer can be anyone who receives the services which we are offering. Customers can be either Internal Users or External Clients.

Services refer to intangible offerings or capabilities provided by IT systems, infrastructure, and personnel to meet the needs of users, stakeholders, and business processes. These services are designed, delivered, and managed to deliver value, support organizational objectives, and facilitate efficient operations.

Before we go in Depth to understand the difference between Value Creation and Value Co-creation , let us first understand the concept of Value is Service Management.

Value is the essence of products, services, and everything in between. So, what is value? It is a simple English word that means something that is useful. In Information Technology Infrastructure Library (ITIL), the end user is all-powerful. End users are someone who uses the Services. Value is defined through the user’s eyes. So, as a service provider, you can claim to create value for your end user, but the ultimate judge would be the end user. Many products and services that are well intentioned because it was created to deliver value, but the end user felt that its value did not meet the expectations against the price paid for it. Hence, Value is subjective. Value to one user may not be valuable to another.

Scenario : Sweet Tooth’s Bakery introduces an online ordering system that allows customers to:

Pre-order cakes and pastries.

Choose delivery slots.

Pay online securely.

From the user’s perspective:

It saves time.

It avoids waiting in line.

It offers convenience.

Result: Customers use it regularly, and love the ease. For them, this service creates value because it meets their needs for convenience and reliability.

Value Delivered: The bakery’s investment in technology is successful because the end users recognize and appreciate the benefits.

Another scenario would of Mobile app with Loyalty Points. Sweet Tooth’s Bakery launches a mobile app that:

Tracks purchases.

Rewards customers with loyalty points for every order.

Offers free pastries after a certain number of points.

From the user’s perspective:

Regular customers love it as they earn rewards, save money, and feel appreciated.

One-time or occasional buyers do not see much benefits because they rarely accumulate enough points to redeem anything.

Result: The service creates high value for loyal and frequent users but low or no value for casual customers.

Value is Subjective: This highlights how value depends on the user. What is valuable for one segment, might not be for another.

Thus, Value is what the user experiences and perceives, not what the provider claims.

So, in ITIL, delivering value means understanding user needs, designing services accordingly, and continuously checking whether the users feel that they are getting something useful and worth their time or money.

Value creation is the process of producing something which is more valuable than the inputs. Usually, the valuable thing can be classified as a product or service. Value creation is important for many reasons as it determines whether a business will be profitable because both sales and costs are based on the value created. As per Axelos, the relationship between a service provider and consumer is a unidirectional delivery of value. If IT does not partner with consumers, it defines value in isolation, leading to misalignment, and even dysfunctionality.

Examples can be the process of the Online Banking System provided by your bank. They would share the list of services that can be provided online to make banking easier for the customers.

Value Co-creation involves collaborative process, and establishing a symbiotic partnership with consumers that benefits both parties.

Scenario : Sweet Tooth’s Bakery wants to improve its online ordering system after getting feedback about frequent crashes and customer frustration on busy weekends.

How Value Co-Creation Happens

Customer Feedback (Consumer Role) : Customers report issues such as delays, crashes, and poor mobile experience. They suggest features like, Live order tracking, Custom cake designs with upload options.

Bakery’s IT and Business Teams (Provider Role) : The IT Team analyses the feedback. Engage with a few loyal customers to understand the use cases, and redesign the ordering app, based on real customer input.

Outcome : It is a better, user-friendly app that aligns with real customer needs. Customers feel involved and valued. The bakery sees increased orders, and fewer complaints. Value is Co-Created, because the end users actively participated in shaping the solution as the final service is more relevant, valuable, and successful.

Thus, Value is essentially driven by three aspects. They are:

Outcomes

Costs

Risks

Figure 1.1: Value and Its Aspect in ITIL

Consider yourself as a customer, and if you are purchasing a service or a product, you want it to achieve the outcome it promises, the costs must be reasonable, and the risks associated with it must not be owned by the end user, but rather with the company.

By focusing on delivering value, achieving the desired outcomes, managing costs efficiently, and mitigating risks effectively, organizations can maximize the success and impact of their investments and efforts. Thus, a service provider produces outputs that help its consumers to achieve certain outcomes.

Output: Output refers to the tangible or measurable results of activities, processes, or deliverables produced during the execution of a service or project. Outputs are typically quantitative, observable, and directly related to the tasks or activities performed. They represent the immediate results of efforts expended.

Examples : In an IT context, outputs may include the deployment of new software, the installation of hardware components, the completion of system upgrades, the resolution of incidents, or the delivery of training sessions.

Sweet Tooth Example: Sweet Tooth’s Bakery launches a new mobile app for online ordering.

Other outputs include:

Deployment of the app on iOS and Android stores.

Integration of payment gateway.

Installation of a notification system.

Delivery of training to the bakery staff on how to manage app orders.

These are all the visible deliverables; things the bakery can show were completed.

Outcome: Outcome refers to the broader, intended impacts or results that stakeholders expect from the outputs delivered by a service or project. Outcomes are qualitative, strategic, and focused on the long-term benefits or value realized by stakeholders. They represent the ultimate goals or objectives that the outputs are intended to achieve.

Examples : In ITIL and project management, outcomes may include increased productivity, improved user satisfaction, enhanced operational efficiency, reduced downtime, cost savings, or better alignment with business objectives.

Sweet Tooth Example: As a result of the new mobile app, the bakery sees:

A 30% increase in weekend orders.

Higher customer satisfaction due to easy ordering and timely delivery.

Reduced workload on in-store staff.

Improved customer retention due to the loyalty program in the app.

These are the real-world benefits that make the efforts worthwhile, how the output helps the business and customers.

Summary : It is important to understand the difference between outputs and outcomes. For example, the output of a training service is a Course Presentation which the trainers can use to deliver the training. The outcome of the service is the ability of the participants to pass the related certification exam, after attending the training.

The following are the key characteristics of services in IT:

Figure 1.2: Key Characteristics of IT Services

In the realm of IT, services are diverse and customized to address the unique needs of organizations, users, and stakeholders.

The following are common examples of IT services across various domains:

Email Services : Email services enable users to send, receive, and manage electronic messages over a network. These services typically include features such as email hosting, inbox management, spam filtering, and collaboration tools.

Cloud Computing Services : Cloud computing services offer on-demand access to computing resources, including servers, storage, databases, networking, and software applications, over the internet. Examples of cloud services include Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).

Network Services : Network services encompass a range of functionalities related to networking, such as network infrastructure management, network monitoring, configuration management, and Virtual Private Networking (VPN) services.

Security Services : Security services focus on protecting IT assets, data, and systems from unauthorized access, cyber threats, and malicious activities. Examples include firewall management, intrusion detection and prevention, antivirus software, encryption services, and security incident response.

Data Backup and Recovery Services : Data backup and recovery services involve the regular backup of critical data, and the implementation of strategies to recover data in the event of data loss, corruption, or system failure. These services ensure data integrity, business continuity, and disaster recovery preparedness.

Software Development and Maintenance Services : Software development services encompass the design, development, testing, deployment, and maintenance of custom software applications tailored to meet the specific business requirements. This includes services related to application lifecycle management, version control, and software configuration management.

IT Help Desk and Technical Support Services : IT help desk and technical support services provide end-users with assistance, troubleshooting, and resolution of IT-related issues and inquiries. This includes support for hardware, software, network connectivity, and system configurations.

Enterprise Resource Planning (ERP) Services : ERP services involve the implementation, customization, integration, and support of enterprise-wide software solutions designed to streamline business processes, improve efficiency, and facilitate data-driven decision-making across various functional areas.

Collaboration and Communication Services : Collaboration and communication services facilitate real-time communication, document sharing, and collaboration among individuals and teams within an organization. Examples include instant messaging, video conferencing, document management, and project collaboration tools.

Mobile Device Management (MDM) Services : MDM services enable organizations to manage and secure mobile devices, such as smartphones and tablets, used by employees to access corporate resources and data. This includes mobile device provisioning, configuration management, security policy enforcement, and remote device wipe capabilities.

These examples illustrate the diverse range of IT services available to organizations, each playing a critical role in supporting business operations, enhancing productivity, and driving innovation in today’s digital landscape.

Understanding IT Service Management

In today’s digital age, Information Technology (IT) plays a pivotal role in the success of organizations across various industries. IT Service Management emerges as a critical discipline that ensures the effective delivery and management of IT services to meet the evolving needs of businesses and their customers.

At its core, ITSM is a set of practices, processes, and frameworks designed to align IT services with the strategic objectives of the organization, enhance operational efficiency, and deliver value to stakeholders. It encompasses a holistic approach to managing IT services throughout their lifecycle, from design and implementation to operation and continual improvement.

Let us understand what exactly Processes and Practices are:

Processes: Processes in ITSM refer to the structured set of activities designed to achieve a specific objective. These activities are often sequential and interrelated, aiming to deliver a particular service or outcome efficiently and effectively. These define how things should be done within an organization to ensure consistency, quality, and compliance with standards or best practices.

Practices: Practices in ITSM encompass a broader range of activities, including processes, policies, procedures, guidelines, and cultural aspects that guide the organization in managing its IT services. These provide a framework for implementing and improving processes within the organization. They often include a combination of formalized methods and informal techniques, based on industry standards, organizational goals, and specific needs. Practices are more holistic and flexible compared to processes, and can adapt to changes in technology, business requirements, and organizational culture.

Effective ITSM practices are essential for organizations to thrive in today’s competitive landscape. Here are some key reasons why ITSM is crucial:

Alignment with Business Goals : ITSM helps align IT services with the overarching goals and objectives of the business, ensuring that technology investments contribute to organizational success.

Enhanced Service Quality : By implementing standardized processes and best practices, ITSM improves the quality, reliability, and consistency of IT services, leading to enhanced user satisfaction and loyalty.

Efficient Resource Utilization : ITSM frameworks enable organizations to optimize resource allocation, streamline workflows, and minimize downtime, ultimately leading to cost savings, and improved operational efficiency.

Risk Mitigation : Through proactive monitoring, incident management, and risk assessment, ITSM helps identify and address potential issues before they escalate, reducing the impact of disruptions on business operations.

Continuous Improvement : A core principle of ITSM is continual service improvement, which fosters a culture of innovation, learning, and adaptation within the organization, driving ongoing enhancements to IT services and processes.

Evolution of IT Service Management

The field of ITSM has evolved significantly over the years in response to the changing business dynamics, technological advancements, and industry trends. Early approaches to IT service management were often ad-hoc and reactive, focusing primarily on resolving technical issues as they arose.

However, with the growing complexity of IT environments, and the increasing reliance on digital technologies, there arose a need for more structured and systematic approaches to managing IT services. This gave rise to formal ITSM frameworks, and other methodologies, such as the ITIL, COBIT, and ISO/IEC 20000.

These frameworks provide organizations with a structured set of best practices, processes, and guidelines for managing IT services effectively. They emphasize the importance of a service-oriented mindset, customer-centricity, and continual improvement, laying the foundation for a mature and proactive approach to ITSM.

In the digital era, ITSM continues to evolve in response to emerging technologies, changing customer expectations, and evolving business models. Concepts such as automation, artificial intelligence, Generative Artificial Intelligence (Gen AI) and DevOps are reshaping traditional ITSM practices, enabling organizations to deliver services more efficiently, rapidly, and flexibly than ever before.

Introduction to IT Service Management

The history of IT Service Management traces back to the evolution of information technology, and its increasing integration into business operations. Here is a brief overview:

Early IT Management : In the early days of computing, IT management primarily focused on managing hardware, and ensuring its availability. There was limited emphasis on service delivery or aligning IT with business objectives.

Emergence of ITIL : In the 1980s, the UK government’s Central Computer and Telecommunications Agency (CCTA) developed the ITIL as a set of best practices for IT service management. ITIL provided guidelines for managing IT services, processes, and operations more effectively.

Adoption of ITIL : ITIL gained popularity in the 1990s as organizations recognized the need for structured approaches to IT service management. The framework underwent several revisions, with ITIL v2 being widely adopted globally.

Expansion and Standardization : During the early 2000s, ITSM frameworks and standards continued to evolve. Organizations sought to standardize their IT service management practices to improve efficiency, quality, and alignment with business goals.

ITSM Frameworks and Standards : Alongside ITIL, other frameworks and standards emerged, such as COBIT (Control Objectives for Information and Related Technologies), ISO/IEC 20000 (International Standard for IT Service Management), and ISO/IEC 27001 (Information Security Management System). These provided additional guidance and requirements for IT service management, governance, and security.

Shift towards Service-Oriented Approach : In the late 2000s and early 2010s, there was a significant shift towards a more service-oriented approach to ITSM. This involved focusing on delivering value to customers through IT services, rather than just managing technology components. Frameworks such as DevOps and Agile gained prominence, emphasizing collaboration, automation, and continuous improvement.

Digital Transformation and Cloud Computing : The rise of digital transformation initiatives and the widespread adoption of cloud computing further influenced ITSM practices. Organizations had to adapt their ITSM processes to accommodate new technologies, service delivery models, and changing customer expectations.

ITIL 4 and Beyond : ITIL underwent a major update with the release of ITIL 4 in 2019, reflecting changes in the IT landscape, and incorporating modern practices such as Agile, DevOps, and digital transformation. ITSM continues to evolve in response to emerging technologies, industry trends, and the evolving needs of organizations and their customers.

Throughout its history, ITSM has evolved from a technical discipline focused on managing IT infrastructure to a strategic capability for delivering business value through IT services. It remains an essential aspect of modern organizations’ operations, enabling them to effectively leverage technology to achieve their objectives.

Frameworks of IT Service Management

Several frameworks and standards exist within the realm of IT Service Management, each offering guidelines, best practices, and methodologies for managing IT services effectively. Here are some of the prominent frameworks:

Information Technology Infrastructure Library (ITIL) : ITIL is one of the most widely adopted IT Service Management (ITSM) frameworks globally. ITIL 4 provides a modern, flexible approach to managing IT services by aligning them with evolving business needs. It introduces the Service Value System (SVS) which integrates principles, governance, service value chain activities, and practices to co-create value. Rather than focusing on a rigid lifecycle, ITIL 4 emphasizes practices such as Incident Management, Change Enablement, and Continual Improvement, enabling organizations to deliver effective and adaptive services in dynamic environments.

Control Objectives for Information and Related Technologies (COBIT) : COBIT is a framework developed by ISACA (Information Systems Audit and Control Association) for IT governance and management. It provides guidance on aligning IT with business objectives, managing risks, and ensuring compliance with regulations. COBIT emphasizes control objectives, processes, and maturity models for effective IT governance.

ISO/IEC 20000 : ISO/IEC 20000 is an international standard for IT service management. It outlines requirements for establishing, implementing, maintaining, and continually improving an IT service management system. ISO/IEC 20000 aligns with ITIL principles, and provides a framework for organizations to achieve certification for their ITSM practices.

DevOps : DevOps is a cultural and organizational movement that promotes collaboration, automation, and continuous integration between development and operations teams. In the context of ITIL 4, DevOps complements ITSM by supporting the principles of agility, fast feedback, and continual improvement. While not an ITSM framework itself, DevOps aligns with ITIL 4’s focus on co-creating value, improving deployment frequency, reducing lead time, and enhancing the overall speed and quality of service delivery.

Agile : Agile is an iterative approach to software development that focuses on delivering value to customers through incremental, collaborative, and adaptive processes. Agile methodologies, such as Scrum and Kanban, prioritize customer feedback, continuous improvement, and flexibility in responding to changing requirements. Agile principles can be integrated into ITSM practices to enhance service delivery and responsiveness.

Lean : Lean applies Lean principles and practices to IT service management, with a focus on eliminating waste, optimizing processes, and maximizing customer value. Lean aims to streamline IT operations, improve efficiency, and enhance the quality of IT services. It emphasizes concepts such as value stream mapping, Kaizen (continuous improvement), and visual management to drive organizational excellence.

IT4IT : IT4IT is a vendor-neutral framework that provides a holistic, end-to-end model for managing the entire IT value chain—from strategy and planning to development, operations, and continuous improvement. It was developed by The Open Group, and is designed to help IT organizations deliver value more efficiently and transparently.

These frameworks and standards offer valuable guidance for organizations seeking to establish effective ITSM practices, improve service quality, and align IT with business goals. Depending on the organization’s needs, industry sector, and specific objectives, they may choose to adopt one or more of these frameworks in their ITSM initiatives.

Benefits of IT Service Management

Implementing IT Service Management can bring several benefits to organizations, including:

Alignment with Business Objectives : ITSM helps align IT services with the goals and objectives of the business. By understanding business needs and priorities, ITSM ensures that IT resources and investments are directed towards supporting key business processes and delivering value to customers.

Improved Service Quality : ITSM focuses on delivering high-quality IT services that meet or exceed customer expectations. Through standardized practices, effective incident and problem management, and proactive service monitoring, ITSM helps ensure consistent service delivery and reliability.

Enhanced Customer Satisfaction : By providing reliable and responsive IT services, organizations can improve customer satisfaction levels. ITSM emphasizes customer-centric approaches, such as service catalogs, self-service portals, and clear communication channels, to enhance the overall customer experience.

Increased Efficiency and Productivity : ITSM streamlines IT processes, reduces manual tasks, and eliminates unnecessary activities, leading to increased efficiency and productivity. Automation, workflow management, and standardized procedures help IT teams work more effectively, and focus on value-added tasks.

Better Risk Management and Compliance : ITSM frameworks such as ITIL and COBIT include guidelines for managing risks, ensuring compliance with regulations, and maintaining security standards. By implementing robust change management, configuration management, and security controls, organizations can mitigate risks and meet regulatory requirements more effectively.

Cost Optimization : ITSM helps organizations optimize IT costs by rationalizing IT investments, eliminating redundant processes, and improving resource utilization. By aligning IT spending with business priorities, and focusing on value-driven initiatives, organizations can achieve cost savings, and maximize Return on Investment (ROI).

Faster Incident Resolution and Root Cause Analysis : ITSM processes, such as incident management and problem management, enable IT teams to respond quickly to issues, minimize downtime, and restore services to normal operation. Thus, by identifying root causes and implementing preventive measures, ITSM helps reduce the recurrence of incidents, and improve overall service reliability.

Continuous Improvement : ITSM promotes a culture of continuous improvement through practices such as Continual Service Improvement (CSI). By regularly assessing performance, identifying areas for enhancement, and implementing corrective actions, organizations can adapt to changing business needs, technology trends, and customer requirements more effectively.

Difference Between Traditional Management and Service Management

In the world of IT and business operations, the way organizations manage systems and deliver services has evolved significantly over time. Traditionally, the focus was on managing technology and infrastructure, ensuring that servers were running, and networks were connected. But as businesses grew more customer-centric and digital-first, a shift began—toward managing services and user experiences, rather than just technology.

This chapter explores how Traditional Management differs from Service Management, highlighting the fundamental changes in philosophy, priorities, and outcomes.

Traditional Management: Technology-Centric

Traditional management models are often technology-focused. The core goal is to keep systems running, hardware functional, and software deployed. Success is typically measured by uptime, number of completed installations, or number of resolved hardware issues.

Characteristics of Traditional Management:

Focus on systems and infrastructure

Siloed teams (for example, networking, database, and support)

Reactive problem management

Minimal user involvement

Success = Systems working

Example: In a traditional IT team, if a server goes down, the team scrambles to get it back up. Once it is running, the job is considered done, even if the users affected are still facing issues, logging in or using the application.

Service Management: User- and Service-Centric

Service Management is a more holistic, modern approach. It focuses not just on the technology, but on how that technology delivers value to the user or business. It aligns IT services with business needs, and emphasizes delivering measurable outcomes.

Characteristics of Service Management:

Focus on services and user experience

Integrated, cross-functional teams

Proactive and preventive measures

User feedback and business alignment

Success = Value delivered to the user

Example: If a Wi-Fi issue is reported in a service-managed environment, the goal is not just to restart the router. IT will check whether users across different departments are impacted, monitor SLA timelines, send regular updates, and ensure users are fully operational post-fix. It is about ensuring productivity, not just technical resolution.

Key Differences:

Aspect

Traditional Management

Service Management

Focus

Systems, hardware, uptime

Services, users, business value

Approach

Reactive (fix it when it breaks)

Proactive (prevent and plan)

Measurement of Success

Uptime, availability, issue count

SLA compliance, user satisfaction, value

Organizational Structure

Departmental silos

Cross-functional collaboration

User Interaction

Minimal, indirect

Continuous feedback, self-service options

Tools

Monitoring, hardware management tools

Service portals, ticketing systems (for example, ServiceNow)

Table 1.1: Traditional Management vs. Service Management

Real-Life Comparison Example

Traditional IT Support Scenario: A user reports a slow laptop. IT runs a basic check, reinstalls the OS, and returns the device. The user later finds he cannot access the key applications on his laptop that he uses daily. IT considers the ticket closed, and no follow-up happens.

Service Management Scenario: A user raises a ticket via the Service Portal. The system logs the request, tracks SLA timers, and routes it to the correct team. After fixing the issue, the user receives a feedback form. If the user is not satisfied, the ticket remains open. This approach ensures full issue resolution and user satisfaction.

Ticket Logging via Service Portal

Based on the category and urgency selected, the system routes the ticket to the appropriate IT support team

Diagnosis and Resolution

User Validation and Feedback

Ticket Closure

Why the Shift Matters

Better User Experience : Users care about output and outcomes, not just system uptime.

Business Alignment : Services are mapped to business goals and processes.

Increased Efficiency : Proactive service management reduces downtime and repeat issues.

Scalability : Service-oriented models are easier to scale across departments.

Future Trends Supporting Service Management

AI-driven ticketing systems

Virtual Agent - Chatbot

Self-service portals and knowledge bases

Integrated service platforms like ServiceNow and Jira Service Management

Enterprise Service Management (ESM) expanding beyond IT (HR, Facilities, and Finance)

The move from traditional IT management to service management is a big change in how organizations support technology. Traditional management focuses on making sure “ the machine is working ,” but service management goes a step further, it makes sure “ the user is able to work smoothly on the machine .” This shift puts the user’s experience at the centre, which is key for modern businesses that want to deliver reliable, high quality services at scale.

Service Management Stakeholders: Roles and Responsibilities

In the world of Service Management, delivering consistent and high-quality services does not happen in isolation. It requires the collaboration of multiple stakeholders, each with unique responsibilities. A stakeholder is any individual, group, or organization that has an interest in, or is affected by the services provided by the IT organization. Stakeholders are key to value co-creation. ITSM practices should consider their needs, expectations, and experiences to ensure services deliver meaningful outcomes. From defining services to supporting end users, stakeholders play vital roles that ensure services are designed, delivered, supported, and continuously improved.

This chapter explores the four primary stakeholders in service management:

Service Owners

Service Managers

Users (Customers or Consumers)

Support Teams

Each of these roles contributes to the overall effectiveness of service delivery and user satisfaction.

Service Owner

The Service Owner is accountable for specific services throughout its lifecycle, from design to improvement. Service Owner ensures that the service aligns with business needs, and delivers the expected value.

Key Responsibilities:

Define the service, and its scope,

Ensure service performance meets business expectations.

Manage the service roadmap, and continuous improvements.

Coordinate with other stakeholders (for example, process owners, IT teams)

Scenario: In a bank, the Service Owner for “ Online Banking Services ” ensures that online banking is available 24/7, secure, and user-friendly. If there is a plan to introduce new features such as mobile check deposit, the service owner oversees planning, design, and rollout.

Service Manager

The Service Manager oversees the daily operations of a service. They are responsible for managing SLAs, monitoring performance, and handling escalations.

Key Responsibilities:

Ensure that the service levels are met.

Analyse and report on service performance.

Handle escalations.

Communicate with users and business leaders.

Coordinate with support teams and vendors.

Scenario: At a university, the Service Manager for the IT Help Desk tracks how quickly student issues (such as password resets or Wi-Fi problems) are resolved. If SLA targets are not being met, the Service Manager investigates, and makes operational improvements.

Users (Consumers)

Who They Are: Users are the recipients or consumers of the service. Users may be internal (employees using email or HR systems) or external (customers using a mobile app or website).

Key Responsibilities:

Use the service for its intended purpose.

Report issues, or raise service requests.

Provide feedback on service.

Follow organizational processes (using the portal to raise tickets).

Scenario: An employee at a manufacturing company uses the self-service portal to request a new laptop. The employee is the user of the “ IT Asset Request ” service, and the employee’s experience, satisfaction, and feedback help the service improve over time.

Support Teams

Support teams are the technical experts who resolve incidents, fulfil requests, and manage the backend infrastructure. They ensure that the service is running smoothly and efficiently.

Responsibilities:

Troubleshoot and resolve incidents.

Fulfil service requests.

Deploy the changes management, and problem resolution.

Monitor service health, and respond to alerts.

Scenario: If a finance team reports that its payroll application is not loading, the IT Support Team investigates the issue, checks server logs, and resolves it, keeping both the service manager and the users informed.

Collaboration Among Stakeholders

Stakeholders do not work in silos. Their collaboration ensures end-to-end service quality.

Example: End-to-End Flow

A user logs a complaint about email slowness.

The support team diagnoses a storage issue.

The service manager reviews the issue, checks the Knowledge Base for known solutions, ensures SLA timelines are tracked, and communicates status updates. If the resolution is not achieved within the expected SLA window, the issue is escalated accordingly.

The service owner observes a trend, and evaluates the long-term solution (increasing mailbox capacity) as well as plans a service improvement initiative.

Why These Roles Matter

Effective service management depends on clear ownership, accountability, and communication. Without the defined roles:

Issues fall through the cracks.

SLAs are missed.

Users lose trust in IT or business support.

With proper stakeholder collaboration:

Services are more reliable.

Continuous improvement becomes a reality.

User satisfaction increases.

Trends and Future of Service Management

Service Management is evolving rapidly in response to the changing technology, user expectations, and business needs. Traditional ticket-based support is giving way to smarter, faster, and more user-centric approaches. With the rise of AI, automation, and cross functional service models, organizations are reimagining how they deliver, and manage services.

This chapter explores the most impactful trends shaping the future of Service Management:

Shift-Left Strategies and Self-Service

AI, Machine Learning, and Predictive Analytics

Enterprise Service Management (ESM) beyond IT

Shift Left Strategies and Self-Service

“ Shift-left ” means moving support and issue resolution closer to the end user. Instead of escalating issues to higher-level technical teams, users are empowered to solve common problems themselves through self-service portals, knowledge articles, and automation.

Benefits:

Reduces ticket volume

Improves resolution time

Enhances user satisfaction

Frees the IT teams for more complex issues

Scenario: A company implements a self-service portal, using ServiceNow. Users can:

Reset their passwords automatically

Track their IT requests

Access how-to guides and FAQs

As a result, 40% of tickets are resolved without support team involvement. The IT team, now focuses on other priority incidents and improvements, instead of repetitive issues.

AI, ML, and Predictive Analytics

How AI is Transforming Service Management: Artificial Intelligence (AI) and Machine Learning (ML) are making service delivery smarter, faster, and more personalized. These technologies automate routine tasks, analyse data patterns, and provide the accurate solutions.

Key Use Cases:

Chatbots that resolve common issues 24/7

Auto-categorization and ticket routing

Predictive maintenance alerts

Sentiment analysis from user feedback

Real-Life Example: A telecom company uses AI-powered virtual agents in ServiceNow. When a customer reports internet issues, the chatbot:

Identifies the location

Checks for outages

Suggests troubleshooting steps

Creates a ticket, if needed

Meanwhile, ML algorithms detect that repeated incidents are happening in one region, and alert engineers before major complaints flood in.

Enterprise Service Management (ESM) Beyond IT

Enterprise Service Management (ESM) extends the principles of IT Service Management to other business functions such as HR, Facilities, Finance, Legal, and more. These departments manage requests, tasks, and workflows through a centralized platform—improving visibility, accountability, and user experience across the enterprise.

Why ESM Matters:

Breaks down silos between departments

Offers a consistent user experience

Tracks performance with shared metrics (for example, SLAs)

Encourages automation and transparency organization-wide

Real-Life Example: A global company uses ServiceNow not just for IT, but also:

HR : Employees use a portal to request leave, update personal info, and track onboarding tasks.

Facilities : Staff submit maintenance requests, and track room bookings.

Finance : Users request expense reimbursements and invoice status updates.

All departments use a unified platform, making service delivery faster, trackable, and more user-friendly.

The Future of Service Management: What is Next?

Upcoming Innovations:

Hyper-automation : Combining AI, RPA (Robotic Process Automation), and integration tools to automate end-to-end workflows

Conversational Interfaces : More advanced, human-like AI assistants

Experience-Level Agreements (XLAs) : Going beyond SLAs to measure actual user satisfaction

Mobile-First Service Delivery : Full functionality from smartphones and tablets

Introduction to ITIL: A Framework of ITSM

In the fast-paced world of IT, delivering reliable, consistent, and user-focused services is critical for business success. This is where ITIL comes in, a globally recognized framework for IT Service Management.

ITIL provides a set of best practices that help organizations design, deliver, manage, and continuously improve their IT services. It enables IT teams to align their activities with business goals, reduce risks, and ensure high-quality service delivery.

Understanding ITIL

ITIL is a framework (not a tool or software) that offers guidelines and best practices for delivering IT services in a structured and value-driven way. It helps organizations adopt a service-centric approach, rather than just focusing on hardware, software, or internal processes.

Developed in the 1980s by the UK Government

Owned by Axelos (a joint venture between the UK government and Capita)

The most recent version is ITIL 4

ITIL and ITSM

While ITSM refers to how IT teams manage service delivery (including processes such as incident, change, and problem management), ITIL is the framework that guides how ITSM should be implemented effectively.

ITIL provides:

A common language for service delivery

Defined roles and responsibilities

Guidance on continuous improvement

A service lifecycle approach

Scenario: ITIL in Action

Company: GlobalTech Inc.

Scenario : GlobalTech was facing constant disruptions in its customer support platform. The IT team used ad-hoc methods, and service requests were tracked via email.

Solutions with ITIL:

Adopted ITIL framework to structure support operations.

Implemented Incident Management and Service Request Management processes using ServiceNow.

Introduced Change Enablement to handle system upgrades with planning and rollback strategies.

Measured SLA compliance, and implemented Continual Improvement.

Results:

50% drop in recurring incidents.

Average resolution time improved by 35%.

User satisfaction scores increased.

Is ITIL Only for Large Enterprises? Not at all. ITIL is scalable, and works for organizations of all sizes. Start-ups and small IT teams can adopt a " light " version of ITIL—focusing on core practices such as Incident, Change, and Request Management.

The Future of ITIL and Service Management

ITIL 4 is more aligned with modern practices like:

Agile

DevOps

Lean

Cloud-native operations

It encourages organizations to be more flexible, collaborative, and value-focused, rather than being rigidly process-driven.

Benefits of Implementing ITIL Over a Basic ITSM Approach

Feature

Generic ITSM Approach

ITIL-Based ITSM

Structure and Standards

May vary

Based on proven best practices

Business Alignment

Often limited

Strong emphasis

Continuous Improvement

Ad hoc

Formalized (CSI process)

Scalability

Can be inconsistent

Highly scalable

Adoption and Recognition

Organization-specific

Globally recognized framework

Table 1.2: Generic ITSM vs. ITIL Based ITSM

ITIL is more than just a framework, it is a mindset that enables IT teams to deliver services that are efficient, customer-focused, and business-aligned. Thus, whether it is restoring service quickly, managing change safely, or improving based on feedback, ITIL provides the structure needed for success in today’s digital world.

By embracing ITIL, organizations can transform IT from a support function into a strategic enabler of value, ready to meet the growing expectations of users, and the business alike.

Conclusion

In conclusion, IT Service Management is a fundamental discipline that enables organizations to harness the power of technology to drive innovation, agility, and business value. By embracing ITSM principles and best practices, organizations can optimize their IT investments, enhance customer experiences, and stay ahead in today’s dynamic and competitive landscape. Overall, IT services play a critical role in supporting business operations, enabling innovation, driving digital transformation, and delivering value in today’s increasingly technology-driven world. By adopting a strategic and customer-centric approach to IT service management, organizations can maximize the benefits of IT services, and achieve their business objectives effectively. The next chapter will explore ServiceNow.

Multiple Choice Questions

What is the primary focus of IT Service Management?

Managing hardware and software only

Reducing IT staff costs

Delivering IT services that meet business needs

Developing new technology

Which of these is a key benefit of implementing ITSM best practices?

Increased technical complexity

Improved service quality and customer satisfaction

Higher IT costs with no ROI

Elimination of all IT incidents

How does ITSM contribute to business value?

By increasing IT staff headcount

By aligning IT services with business goals, and improving efficiency

By eliminating the need for IT governance

By focusing only on technical support

What is an “ IT Service ” in the context of ITSM?

A piece of hardware like a server or router

A software application installed on a computer

A means of delivering value to customers by facilitating outcomes, they want to achieve

A technical support call

Which of these is an example of a business-facing IT service?

A server in a data centre

An email platform used by employees

A backup power supply

A network switch

What is the primary difference between a “ Service ” and a “ Product ”?

Services are free, products are paid.

Services are intangible and consumed at the time of delivery, while products are tangible and storable.

Products are always digital, services are physical.

There is no difference.

Answers

c

b

b

c

b

b

C HAPTER 2

Introduction to ServiceNow

Introduction

ServiceNow is a cloud-based Application Software-as-a-Service (APaaS) platform designed to streamline IT Service Management (ITSM) and Enterprise Service Management (ESM) . It acts as a digital workflow platform, helping organizations manage IT operations, business processes, and customer service in a unified system.

It integrates various business functions such as operations, service management, HR, and customer service into a single system of records, thereby enhancing organizational efficiency and service delivery. The platform is highly configurable and scalable, catering to the diverse needs of enterprises of all sizes.

Structure

In this chapter, the following topics will be covered:

Overview of ServiceNow

ServiceNow History and Evolution

ServiceNow Modules

Benefits and Disadvantages of ServiceNow

How to Access and Login to ServiceNow

ServiceNow Interfaces

ServiceNow Community

Overview of ServiceNow

Purpose of ServiceNow: ServiceNow is a cloud-based platform that streamlines IT Service Management by automating workflows, and centralizing service requests, incidents, and changes. It helps organizations improve service delivery, ensure SLA compliance, and enhance visibility into operations. With integrated dashboards and reporting, it enables real-time tracking and decision-making. ServiceNow supports ITIL best practices, making processes more consistent and auditable. Effective use of ServiceNow reduces manual effort, speeds up resolution times, and improves user satisfaction.

Automation Flow and Business Processes

ServiceNow’s core strength lies in workflow automation, eliminating repetitive manual tasks across departments.

Key Aspects:

Drag-and-drop Workflow Editor : This allows non-developers to create automated processes visually.

Pre-built Automation Templates : These are used for IT issues (password resets) and business (employee onboarding) processes.

Event-driven Automation : Triggers actions based on system events (auto-creating an incident ticket when server CPU exceeds 90%). Configured ServiceNow to send automated email notifications to resolver teams, alerting them of impending SLA breaches to ensure timely action.

IT Example : When an employee submits a laptop request:

Automated approval routing, based on department budgets.

Auto-generates procurement ticket.

Triggers shipping notification.

Updates asset database upon delivery.

Notifies employee via chat, all without human intervention.

HR Example: Onboarding a New Hire

When HR initiates onboarding:

Auto-creates tasks for IT, facilities, and payroll setup.

Triggers welcome email with portal access and forms.

Assigns training modules, based on job role.

Updates employee record with completed tasks.

Sends reminders to stakeholders, all handled seamlessly through workflows.

Customer Service Example – Product Issue Reported

When a customer reports a product issue:

Auto-classifies the case, based on keywords and urgency.

Routes to the appropriate support team.

Triggers an RMA process, if replacement is needed.

Updates the customer with status via email/SMS.

Closes the case after resolution with satisfaction survey, all automated through the Customer Service Management (CSM) module.

Centralize Service Management

ServiceNow acts as a single system of records for enterprise services through:

Unified Service Model:

Common Service Data Model : All services (IT, HR, Facilities, and so on) use the same underlying framework.

Universal Request Portal : Single interface for employees to request any service.

Cross-functional Workflows : HR onboarding automatically triggers IT account creation.

Example: During a Merger:

IT integrates systems.

HR manages role changes.

Facilities and handles office moves.

All coordinated through one ServiceNow instance.

Enhance User Experience

ServiceNow revolutionizes service delivery through:

Employee Service Centre:

Conversational Virtual Agent with AI capability handles 40%–60% of common queries.

Mobile-first design with offline capabilities.

Personalized knowledge recommendations.

Customer Service Innovations:

Omnichannel routing (email/chat/social) with AI-powered categorization.

Predictive case assignment, based on agent skills.

Embedded Customer Satisfaction (CSAT) surveys.

Example: An Employee Needing Help:

Asks Virtual Agent: “ How do I reset my VPN? ”

Refer to related Knowledge Articles.

If unresolved, auto-creates ticket with all context.

Receives proactive updates via preferred channel (Teams/SMS).

ServiceNow as a PaaS Platform

ServiceNow operates as a leading Application Platform as a Service (aPaaS), offering a cloud-based environment for organizations to rapidly build, test, and deploy custom business applications and workflows. The platform provides a suite of low-code/no-code development tools, such as App Engine Studio and Flow Designer, that empower both professional developers and “ citizen developers ” to create digital workflows and automate manual processes without extensive coding knowledge.

Cloud-Hosted Architecture

Technical Advantages:

Global Availability : 20+ data centers worldwide with high uptime SLA.

Zero Downtime Upgrades : Platform upgrade, without service interruption.

Disaster Recovery : Automated failover between the availability zones.

Economic Benefits:

Eliminates capital expenditure on servers.

Reduces the need for specialized IT staff.

Scales instantly with organizational growth.

Multi-Instance Architecture

How It Works:

Single codebase serves all customers.

Each tenant’s data logically isolated.

Shared infrastructure drives cost efficiency.

Security Features:

Data Encryption : AES-256 at rest, and TLS 1.2+ in transit.

Role-Based Access Control : Granular permission models.

History and Evolution

ServiceNow was founded in 2003 by Fred Luddy, initially focusing on ITSM applications. ServiceNow has experienced significant growth and transformation, since its inception. Over the years, it has evolved into a full-fledged enterprise cloud platform that supports IT Operations Management (ITOM), Strategy portfolio management human resources, security operations, and much more. The company’s growth has been marked by a series of innovations and expansions, making it a leader in the enterprise service management space. This history outlines the key milestones and developments that have shaped the company into the influential player, it is today.

Figure 2.1: History of ServiceNow

ServiceNow’s Organizational Journey

Founded (2003): Started by Fred Luddy as a cloud-based IT Service Management (ITSM) platform.

Early Focus: IT workflow automation, and ticketing solutions.

Expansion (2010s): Broadened into enterprise workflow automation beyond IT (HR, Customer Service, Security, and so on).

IPO (2012): Went public on NYSE, signaling rapid growth.

AI and ML Integration: Incorporated AI/ML for predictive analytics and intelligent automation.

Acquisitions: Acquired companies such as Element AI, Intellibot, and Lightstep to enhance capabilities.

Now Platform: Evolved into a unified digital workflow platform for enterprises.

Cloud-First Strategy: Embraced hybrid and multi-cloud solutions.

Global Reach: Expanded to serve Fortune 500 companies and governments worldwide.

Employee Growth: Scaled from a startup to thousands of employees globally.

Innovation Focus: Continues to lead in digital transformation, AI-driven workflows, and low-code development.

ServiceNow Products

ServiceNow offers a wide range of products designed to streamline and automate various aspects of enterprise operations. These products cater to IT service management, IT operations, business management, security, HR services delivery, and customer service management, among others. Here is an overview of some of the key ServiceNow products:

IT Service Management (ITSM)

ITSM in ServiceNow refers to a suite of applications and processes that help IT teams manage the delivery of IT services to customers in a structured and efficient way, based on ITIL best practices. The following are the key components of ITSM in ServiceNow:

Incident Management : Manages the lifecycle of incidents to restore normal service operation as quickly as possible, minimizing impact on business operations.

Key Features : Incident logging, categorization, prioritization, assignment, and resolution.

Problem Management : Identifies and resolves the root causes of incidents to prevent recurrence and minimize the impact of problems.

Key Features : Problem detection, root cause analysis, workaround identification, and known error management.

Change Management

Description : Controls the lifecycle of changes to ensure changes are implemented with minimal disruption to IT services.

Key Features : Change planning, risk assessment, approval workflows, and change scheduling.

Request Management

Description : Manages service requests from users, providing a streamlined process for requesting and delivering IT services.

Key Features : Service catalogue, request fulfilment, and automation.

Knowledge Management

Description : Provides a centralized repository for knowledge articles to help users find solutions, and resolve issues via self-service.

Key Features : Knowledge base creation, article categorization, search functionality, and user feedback.

IT Operations Management (ITOM)

Event Management

Description : Monitors IT infrastructure for events that may indicate potential issues, allowing for proactive management.

Key Features : Event detection, correlation, and alerting.

Discovery

Description : Automates the process of identifying and documenting IT assets, within the organization.

Key Features : Asset identification, CMDB population, and relationship mapping.

Service Mapping

Description : Visualizes the relationships and dependencies between IT services, and underlying infrastructure components.

Key Features : Service topology mapping, impact analysis, and dependency visualization.

Operational Intelligence

Description : Uses machine learning to identify and predict IT issues, before they affect services.

Key Features : Anomaly detection, predictive analytics, and automated remediation.

Strategic Portfolio Management (SPM)

Project Portfolio Management (PPM)

Description : Manages the lifecycle of projects, programs, and portfolios to ensure alignment with business objectives.

Key Features : Project planning, resource management, portfolio tracking, and reporting.

Financial Management

Description : Tracks and manages IT spending to provide insights into cost allocation and budgeting.

Key Features : Cost tracking, budget planning, financial reporting, and chargeback/show back.

Application Portfolio Management (APM)

Description : Provides visibility into the application landscape, enabling better decision making, regarding application investments.

Key Features : Application inventory, health assessment, lifecycle management, and rationalization.

Agile Development

Description : Supports agile methodologies for software development, facilitating planning, tracking, and collaboration.

Key Features : Scrum boards, sprint planning, backlog management, and user story tracking.

Security Operations

Security Incident Response

Description : Automates the identification, prioritization, and response to security incidents, reducing response times.

Key Features : Incident logging, threat intelligence integration, automated workflows, and remediation tracking.

Vulnerability Response

Description : Manages the lifecycle of vulnerabilities, from detection to remediation, ensuring timely resolution.

Key Features : Vulnerability detection, risk assessment, remediation workflows, and reporting.

Threat Intelligence

Description : Integrates threat intelligence feeds to provide context, and prioritize threats based on relevance.

Key Features : Threat feed integration, indicator enrichment, and threat scoring.

Security Operations Center (SOC)

Description : Provides a centralized hub for managing security operations and incident response.

Key Features : SOC dashboards, incident triage, investigation tools, and collaboration.

HR Service Delivery

Case and Knowledge Management

Description : Manages employee inquiries, and provides self-service access to HR knowledge.

Key Features : Case logging, knowledge base, self-service portal, and SLA tracking.

Onboarding and Transitions

Description : Automates employee onboarding, offboarding, and other transitions, ensuring a smooth experience.

Key Features : Task automation, workflow management, and status tracking.

Employee Service Center

Description : Centralizes HR services in a single portal, providing employees with easy access to HR resources and support.

Key Features : Service catalogue, request management, and personalized content.

Employee Document Management

Description : Manages employee documents securely, providing easy access and compliance tracking.

Key Features : Document storage, access control, and audit trails.

Customer Service Management (CSM)

Case Management

Description : Manages customer cases efficiently, providing a seamless experience from issue reporting to resolution.

Key Features : Case logging, prioritization, assignment, and resolution.

Field Service Management

Description : Manages field service operations, ensuring timely and efficient service delivery.

Key Features : Work order management, scheduling, dispatching, and mobile access.

Customer SelfService

Description : Provides a SelfService portal for customers to find solutions, submit requests, and track case status.

Key Features : Knowledge base, service catalogue, and case tracking.

Service Analytics

Description : Provides insights into customer service performance, helping to identify areas for improvement.

Key Features : Reporting, dashboards, and Key Performance Indicators (KPIs).

Integrated Risk Management (IRM)

Policy and Compliance Management

Description : Manages policies and compliance activities to ensure adherence to regulatory requirements.

Key Features : Policy creation, compliance assessments, and audit management.

Risk Management

Description : Identifies, assesses, and mitigates risks across the organization.

Key Features : Risk identification, risk assessments, mitigation planning, and monitoring.

Audit Management

Description : Streamlines the audit process, from planning to execution and reporting.

Key Features : Audit planning, evidence collection, and audit reporting.

Vendor Risk Management

Description : Manages risks associated with third-party vendors, ensuring compliance, and reducing exposure.

Key Features : Vendor assessments, risk scoring, and monitoring.

Benefits of Using ServiceNow Over Other ITSM Tools

ServiceNow has established itself as a leading IT Service Management (ITSM) platform, providing numerous advantages over other ITSM tools. These benefits span across functionality, scalability, integration capabilities, user experience, and overall impact on organizational efficiency and productivity. Here are the key benefits of using ServiceNow over other ITSM tools:

Comprehensive and Integrated Platform

Unified Platform : ServiceNow offers a single, unified platform that integrates ITSM with other key business functions such as IT Operations Management (ITOM), Strategic Portfolio Management (SPM), Security Operations, and HR Service Delivery. This holistic approach eliminates the need for multiple disparate tools, and simplifies management as well as reporting.

Modular Architecture : Its modular architecture allows organizations to start with ITSM, and expand to other modules as needed, ensuring scalability and adaptability to evolving business requirements.

Advanced Automation and AI Capabilities

Automation : ServiceNow provides powerful automation capabilities, including playbooks, business rules, and orchestration. These features help automate routine tasks, reducing manual effort, and minimizing the risk of errors.

AI, ML, and Predictive Intelligence : This platform incorporates AI and machine learning to enhance various aspects of ITSM, such as predictive analytics, anomaly detection, and automated incident categorization. These capabilities improve the efficiency and accuracy of IT operations.

Superior User Experience

UserFriendly Interface : ServiceNow is known for its intuitive and user-friendly interface which is designed to enhance user productivity and satisfaction. The platform includes customizable dashboards, selfservice portals, and mobile accessibility, making it easier for users to interact with IT services.

SelfService Capabilities : The selfservice portal empowers users to resolve issues independently by accessing knowledge articles, submitting service requests, and tracking the status of their requests, leading to reduced support costs, and improved user satisfaction.

Scalability and Flexibility

Cloud-Based Solution : As a cloud-based solution, ServiceNow offers inherent scalability, allowing organizations to adjust their usage, based on changing needs without significant infrastructure investments.

Easy Configuration : ServiceNow’s flexibility allows for customization to meet the specific business requirements. Organizations can tailor workflows, forms, and applications to align with their unique processes and policies.

Robust Integration Capabilities

API and Integration Hub : ServiceNow provides robust integration capabilities through APIs and the Integration Hub, enabling seamless connectivity with other enterprise systems and tools. This ensures data consistency, and streamlines cross-functional processes.

Third-Party Integrations : The platform supports integrations with a wide range of third-party applications and services, including cloud providers, ERP systems, and collaboration tools, enhancing its functionality and interoperability.

Enhanced Collaboration and Communication

Collaboration Tools : ServiceNow includes built-in collaboration tools that facilitate communication among IT teams and stakeholders. Features such as chat, activity feeds, and notifications ensure timely and effective collaboration during incident resolution and change management.

Unified Portal : The unified service portal consolidates various service offerings, enabling users to access and interact with multiple services from a single interface. This improves the overall service experience, and enhances collaboration between different service areas.

Comprehensive Reporting and Analytics

RealTime Reporting : ServiceNow provides realtime reporting and analytics capabilities, allowing organizations to gain insights into their IT operations. Customizable dashboards and reports help track the Key Performance Indicators (KPIs), and measure service performance.

Predictive Analytics : Leveraging AI and machine learning, ServiceNow offers predictive analytics that help identify potential issues before they become critical, enabling proactive management, and reducing downtime.

Strong Community and Ecosystem

ServiceNow Community : ServiceNow boasts a vibrant community of users, developers, and partners who contribute to knowledge sharing, best practices, and continuous improvement. The community provides valuable resources, including forums, user groups, and events.

Partner Ecosystem : A robust partner ecosystem supports the implementation and customization of ServiceNow solutions, offering consulting, development, and integration services to enhance the platform’s value.

Compliance and Security

Regulatory Compliance : ServiceNow supports compliance with various regulatory standards such as GDPR, HIPAA, and ISO/IEC 27001. The platform’s security features, including data encryption, access controls, and audit logs, ensure the protection of sensitive information.

ServiceNow stands out as a leading ITSM solution due to its comprehensive and integrated platform, advanced automation and AI capabilities, superior user experience, scalability, robust integration capabilities, enhanced collaboration tools, comprehensive reporting and analytics, strong community and ecosystem, and robust compliance and security features. These benefits collectively contribute to improved efficiency, productivity, and service quality, making ServiceNow a preferred choice over other ITSM tools for many organizations.

Disadvantages of ServiceNow

ServiceNow is a powerful, highly robust, versatile and comprehensive ITSM platform with numerous benefits, but it also comes with certain disadvantages that organizations need to consider. These include high costs, complexity, resource intensity, challenges with customization, as well as potential performance issues. Evaluating these factors in the context of an organization’s specific needs and resources is crucial, when deciding whether ServiceNow is the right fit.

High Implementation Costs : The initial setup and implementation of ServiceNow can be expensive. Costs include licensing fees, customization, integration, and training. The ongoing costs for licensing, support, and additional modules can be high, particularly for smaller organizations, or those with tight IT budgets.

Complexity

Steep Learning Curve : Due to its extensive range of features and customization options, ServiceNow can have a steep learning curve. Users and administrators may require significant training to become proficient.

Complex Configuration : Customizing and configuring the platform to meet specific business needs can be complex and time consuming. This often requires skilled professionals with expertise in ServiceNow.

Resource Intensive

Requires Skilled Personnel : Effective management and customization of ServiceNow often require skilled personnel with specific knowledge of the platform. This can be challenging for organizations with limited IT staff or expertise.

Resource Intensive Implementation : Implementing ServiceNow can be resource intensive in terms of time and effort. Organizations need to allocate sufficient resources for planning, deployment, and testing.

Customization Challenges

Potential for Over Customization : While ServiceNow is highly customizable, there is a risk of over customization. Excessive customization can lead to increased complexity, making future upgrades and maintenance more difficult.

Upgrade Issues : Customizations and integrations can complicate the upgrade process. Organizations may face challenges ensuring that custom features and third party integrations remain compatible with new versions of the platform.

Performance Concerns

Performance Issues with Heavy Customization : Extensive customization and the addition of numerous applications can impact the platform’s performance, leading to slower response times, and potential downtime.

Integration Challenges

Complex Integrations : Integrating ServiceNow with other enterprise systems can be complex, and may require custom development work. This can lead to increased implementation times and costs.

API Limitations : Although ServiceNow offers robust APIs, there may be limitations in terms of functionality or performance, when integrating with certain third party systems or applications.

Guide to Logging into ServiceNow

Accessing ServiceNow is the first step in managing IT services, reporting incidents, and fulfilling requests efficiently. This topic provides a step-by-step guide to help users log into the ServiceNow platform securely, and without issues. Hence, whether you are a new user or need a refresher, the instructions outlined here will ensure a smooth and quick login experience.

Methods of Logging into ServiceNow

Logging into ServiceNow is a straightforward process, but knowing the different methods and interfaces can enhance your user experience. Thus, whether accessing through a web browser, mobile app, or leveraging advanced functionalities, ServiceNow offers a range of interfaces to meet diverse needs. Familiarity with these methods and interfaces ensures efficient use of the platform, and effective management of IT services as well as business processes.

There are several ways to log into ServiceNow, depending on the organization’s configuration, and user preferences.

Web Browser Login

The most common method to access ServiceNow is through a web browser.

Please note majority of the organization provides all its employees to create tickets. This access is limited. For a Few Employees/Teams, more than 1 role is assigned, and depending on it, access is provided. A user must have at least one active role, to maintain access.

Users can access ServiceNow via two portals:

Service Portal

Employee Portal

ServiceNow Portal: ServiceNow admins can configure a portal to be a user’s landing page, when they log into ServiceNow.

Follow these steps:

Open a Web Browser : Launch any modern web browser such as Google Chrome, Mozilla Firefox, Microsoft Edge, or Safari.

Enter the URL : https://yourdomain.service-now.com/sp .

For example, If you are an IBM Employee, you can log into the ServiceNow portal with the link, https://ibm.service-now.com/sp .

Press the " Log in " button to access the ServiceNow dashboard.

Enter Credentials, and Click ' Login ':

Figure 2.2: ServiceNow Login via Web Browser

Single SignOn (SSO): Many organizations integrate ServiceNow with Single SignOn (SSO) systems to streamline the login process.

Figure 2.3: ServiceNow Login via Web Browser

Employee Portal

Open a Web Browser : Launch any modern web browser such as Google Chrome, Mozilla Firefox, Microsoft Edge, or Safari.

Enter the URL: https://yourdomain.service-now.com .

For example, If you are an IBM Employee, you can log in to the ServiceNow portal with the link, https://ibm.service-now.com .

Enter credentials, and click ' Login ':

Mobile App Login

ServiceNow provides mobile applications for both Android and iOS devices, allowing users to access the platform on the go.

Download the App : Install the ServiceNow mobile app from the Google Play Store or Apple App Store .

Figure 2.4: ServiceNow App Installations

Open the App : Launch the ServiceNow app on your mobile device.

Enter Instance URL : Provide the instance URL, like the web browser method (for example, ` https://microsoft.servicenow.com `).

Figure 2.5: ServiceNow Login via Instance URL

Enter Credentials : Input your username and password , or use SSO, if configured.

Figure 2.6: ServiceNow Login via Mobile App

Tap ' Login ': Access your ServiceNow environment through the mobile interface.

ServiceNow Interfaces

ServiceNow offers various interfaces to cater to different user needs and roles. Here are the primary interfaces, you may encounter:

Classic Interface : The Classic Interface is the original user interface of ServiceNow, and provides a traditional layout with a straightforward navigation panel.

Navigation Panel : Located on the left side, it contains a menu of modules and applications.

Content Area : Displays the details of the selected module or application.

Application Navigator : Allows users to search for, and access different applications as well as modules.

Figure 2.7: ServiceNow Nextgen UI Experience

Employee Centre Portal : The Employee Portal is a modern, user friendly interface designed for end users, and provides a customized and responsive layout.

Home Page : Often features widgets and dashboards tailored to the user’s role or preferences.

Catalog : Users can access service catalogues, request items, and submit incidents or requests.

Search Functionality : Enhanced search capabilities to find information quickly.

Figure 2.8: ServiceNow Employee Centre Portal

How Can We Help : The " How Can We Help " section in a ServiceNow portal acts as a gateway for users to access a variety of services, resources, and tools. It is a customizable feature designed to streamline user interactions, and improve self-service experiences. The following are the key functionalities and capabilities often associated with this section:

Request Something

Users can initiate various requests, such as:

IT support for hardware or software issues.

HR services such as leave applications or benefits inquiries.

Facilities requests such as office maintenance or workspace reservations.

Guided forms simplify the process, ensuring that the users provide the necessary information upfront.

Knowledge Base : Users can search for articles, guides, and FAQs to find solutions to common issues. Provides instant answers without the need to submit a request, or raise a ticket.

Get Help : The " Get Help " functionality in ServiceNow provides users with a quick and easy way to seek assistance for various issues or inquiries. It is often a core feature in ServiceNow portals, and is designed to guide users to the right resources or support channels. Here is what " Get Help " typically does:

Streamlines Support : Directs users to the appropriate assistance quickly.

Empowers Self-Service : Encourages users to resolve common issues independently with helpful resources.

Improves Resolution Times : Automates ticket routing and prioritization for faster response.

Enhances User Experience : Simplifies the process of getting help, reducing frustration.

Service Operation Workspace : The Agent Workspace is designed for IT support and customer service agents to manage their tasks efficiently. It is a Modern User Interface offering a multi tab, multi panel experience optimized for larger screens. This also introduces concepts like interaction management, advanced work assignment, agent intelligence, case types, and playbooks.

Worklists : Provides a consolidated view of tasks, incidents, and requests assigned to the agent.

Interactive Interface : Features tools and functionalities for managing and resolving cases, incidents, and requests.

Performance Analytics : Includes dashboards and reports to monitor performance and metrics.

Figure 2.9: Service Operations Workspace

Developer Interface : The Developer Interface is used by administrators and developers for customizing and extending ServiceNow functionalities.

Studio : This is the primary environment for application development, including creating and managing applications, tables, forms, and scripts.

Script Editor : Allows for writing and editing scripts to customize the behavior of applications.

Debugging Tools : Provides tools for testing and debugging custom code.

ServiceNow Community

The Now Community (community.servicenow.com) is ServiceNow’s official online forum where users, developers, admins, and experts collaborate to solve problems, share best practices, and drive innovation on the platform. It is a global knowledge-sharing platform where:

Any users ask questions, and get answers.

ServiceNow MVPs and Experts provide guidance.

Learning About ServiceNow

ServiceNow Resources:

ServiceNow Learning Platform : Explore official training, certifications, and guided learning paths.

ServiceNow YouTube Channel : Watch tutorials, webinars, and expert-led sessions for practical insights and tips.

Figure 2.10: ServiceNow Community

How Users Benefit from Now Community

Get Instant Guidance and Path to Problems

Search the existing threads: 90% of common issues already solved.

Post questions: Get responses from experts.

Access troubleshooting guides: Step-by-step fixes for errors.

Example : “ How to auto-assign tickets based on location? ”→ Multiple solutions with sample workflows

Network with Peers and Experts

Join user groups: Local/regional meetups.

Connect with MVPs: 1:1 messaging with top contributors.

Find mentors: For career growth in ServiceNow ecosystem.

Accelerate Projects with Ready-to-Use Code

Script snippets: JavaScript, Flow Designer examples.

Shareable Update Sets: Import configurations.

GitHub Integrations: Community-developed plugins.

Example : “ Free HR onboarding workflow shared by a partner ”

Conclusion

ServiceNow has emerged as a transformative force in IT Service Management (ITSM) and Enterprise Service Management (ESM), evolving from a simple IT ticketing tool into a comprehensive cloud-based workflow automation platform. Its ability to centralize, automate, and optimize business processes across IT, HR, customer service, security, and more makes it indispensable for modern enterprises.

This chapter provided a comprehensive introduction to ServiceNow, a powerful cloud-based platform designed to streamline and automate IT and business processes. We began with an overview of ServiceNow, understanding how it supports IT Service Management (ITSM), operations, and enterprise workflows on a unified platform. We then explored the history and evolution of ServiceNow, tracing its growth from a simple ticketing system to a global enterprise solution used across industries.

Delving into ServiceNow modules, we learned about the key components such as Incident Management, Change Management, Problem Management, and more, each tailored to optimize the specific business functions. The chapter also presented the benefits of using ServiceNow—such as increased efficiency, automation, and centralized management—while acknowledging some of its disadvantages, including cost and complexity for new users.

Practical aspects such as how to access and log into ServiceNow, the different interfaces available (such as the Agent Workspace and Service Portal), and the role of the ServiceNow Community were also discussed. The community serves as a valuable resource for learning, collaboration, and solving real-world issues through peer and expert support.

In conclusion, this chapter equips readers with foundational knowledge of what ServiceNow is, how it works, and why it is a leading platform in the digital workflow, spacepreparing users to explore and navigate it confidently in real-world scenarios.

In the next chapter, we will dive deeper into ServiceNow’s Service Desk functionality, and explore how it revolutionizes IT support operations. This upcoming chapter will provide practical insights into how ServiceNow transforms traditional service desk operations into efficient, data-driven, and user-friendly experiences for both agents and end-users.

Multiple Choice Questions

What is ServiceNow primarily used for?

Web design

Automating and managing IT and business workflows

Online shopping

Video conferencing

Who founded ServiceNow?

Jeff Bezos

Elon Musk

Fred Luddy

Bill Gates

Which ServiceNow application helps organizations manage the entire lifecycle of their hardware and software assets, from procurement to retirement?

Strategic Portfolio Management (SPM)

IT Asset Management (ITAM)

Governance, Risk, and Compliance (GRC)

Field Service Management (FSM)

What type of platform is ServiceNow?

On-premise software only

Cloud-based platform

Desktop-only application

Standalone CRM tool

What is the one key benefit of using ServiceNow?

Manual data entry is required

Disconnected data systems

Centralized, automated workflow management

Limited scalability

How can users typically access ServiceNow?

Through a downloadable mobile game

By visiting a web browser, and entering the instance URL

Only via desktop software

Through voice-only assistants

Which interface is designed in ServiceNow for end users to submit requests and incidents?

Developer Portal

Admin Console

Service Portal

Task Manager

Which of the following is a disadvantage of ServiceNow?

Fully cloud-based

High cost and steep learning curve for beginners

Real-time tracking of SLAs

User-friendly interface

What is the purpose of the ServiceNow Community?

Playing online games

Sharing music playlists

Providing a platform for users to ask questions, share ideas, and learn

Streaming ServiceNow tutorials only

Which feature of ServiceNow helps in visualizing and automating workflows across departments?

Incident List View

Flow Designer

Notification Settings

Theme Manager

Answers

b

c

b

b

c

b

c

b

c

b

C HAPTER 3

Introduction to Service Desk

Introduction

A Service Desk is a centralized IT support function that acts as the Single Point of Contact (SPOC) for resolving technical issues, fulfilling service requests, and ensuring smooth business operations. Unlike traditional help desks (which focus on break-fix support), a modern Service Desk follows ITIL best practices to deliver proactive, efficient, and user-centric IT services.

In this chapter, we will discuss the functionality of Service Desk, provide foundational knowledge of Service Desk, its purpose in IT Service Management, and how it operates in ServiceNow.

Structure

In this chapter, we will cover the following topics:

Overview of Service Desk

Key Terminologies Used in the Service Desk

Difference between Help Desk, Call Center, and Service Desk

Goals, Objectives, and Benefits of Service Desk

Type of Service Desk

SLAs in Service Desk

Common SLA Metrics and SLA Best Practices

Service Desk Functionality in ServiceNow

Overview of Service Desk

Consider a scenario where you encounter an issue that must be resolved urgently to prevent a significant impact on the organization or business. However, you are unsure of which user/team is responsible for addressing the problem. This is where the Service Desk plays a crucial role. In this situation, you would contact a dedicated Service Desk team, who will log on to your issue by creating a ticket, and ensure that it is assigned to the appropriate technical team for resolution. In simple terms, the Service Desk functions as an intermediary between the service consumer and the service provider.

It is important to note that the service consumer could be either an internal or external user, utilizing services provided by the organization. These users may be technical or nontechnical, depending on the nature of the service. The Service Desk is a cornerstone of modern IT service management. As organizations continue to rely on technology for their operations, the role of the service desk will only become more critical. As organizations grow and become more complex, managing and supporting IT infrastructure becomes more challenging. This is where the IT service desk plays a pivotal role. The IT service desk serves as a bridge between the users (employees, customers, or stakeholders) and the IT department, offering support, resolving issues, and facilitating communication.

An IT service desk is a single point of contact designed to address technical issues, manage service requests, and facilitate communication between IT staff and users. It is responsible for ensuring that IT services are delivered efficiently, that issues are resolved in a timely manner, and that users can get the help, they need with minimal disruption to their work. As a critical component of IT Service Management, the service desk’s goal is to improve the quality of IT services, enhance user satisfaction, and ensure seamless business operations. By implementing the best practices, leveraging technology, and maintaining a focus on customer satisfaction, the IT service desk helps organizations meet their business goals, while maintaining a stable and responsive IT environment.

Key Terminologies Used in Service Desk

Incident : Formally defined by ITIL 4, an Incident represents: “ An unplanned interruption to an IT service or reduction in the quality of an IT service .”

When experiencing service disruptions or dissatisfaction with a subscribed service, the standard protocol involves contacting the service provider to formally report the issue. Customers, typically initiate this process through multiple channels, including phone support, email communication, or live chat systems. The service provider then generates a service ticket to document and track the reported concern.

This ticket is classified as an Incident, when it pertains to:

An active service disruption

Degraded service performance

Failure to meet the expected service levels

Service Request: When requiring new services, access, or resources as part of an existing subscription, customers engage the service provider through standardized channels. This interaction differs fundamentally from incident reporting, as it involves pre-defined fulfilment, rather than problem resolution.

Formal Definition (ITIL 4): A Service Request is defined as:

“A formal user request for a pre-approved service, resource, or information that is a part of standard service delivery.”

Key Characteristics of Service Request(s):

Pre-approved Nature : Fulfils routine needs documented in service catalogs.

Standardized Fulfilment : Follows established workflows (often automated).

Non-Urgent : Typically bound by fulfilment timelines, or with due dates rather than resolution SLAs.

Proactive Engagement : User-initiated capacity expansion or capability enablement.

Classification as a Service Request When:

Requesting additional licensed software.

Ordering approved hardware replacements.

Seeking access to pre-authorized systems.

Requesting documented how-to information.

Problem

Formal Definition (ITIL 4):

A Problem is defined as:

“A cause, or potential cause, of one or more incidents.”

“A Known Error is a problem that has been analyzed but has not yet been resolved.”

When recurring service disruptions or underlying issues are identified, organizations initiate Problem Management processes to investigate the root causes, rather than just restore service. This proactive approach differs from Incident Management by focusing on permanent solutions or workarounds, rather than immediate fixes.

Key Characteristics of Problem Management:

Root Cause Focus : Investigates why incidents occur, rather than just restoring service.

Preventive Orientation : Aims to eliminate recurring issues through permanent solutions or providing workarounds.

Strategic Value : Reduces future incident volume, and improves service stability.

Cross-Functional Collaboration : Often involves multiple technical teams for analysis.

Classification as a Problem When:

Multiple similar nature incidents or symptoms occur over time.

Major incidents reveal systemic weaknesses.

Incident analysis suggests deeper underlying causes.

Known errors require permanent resolutions.

Difference Between a Call Center, Helpdesk and Service Desk

Call Center, Help Desks, and Service Desks are all forms of customer or user support, but they differ significantly in their scope, function, and approach.

Call Center : Provides general customer service or handles sales inquiries, typically by phone. It focuses on nontechnical issues, and high-volume transactions.

Help Desk : A specialized IT function that handles technical issues such as troubleshooting and resolving user problem(s). The scope is primarily incident resolution.

Service Desk : A more comprehensive IT function, encompassing not only incident resolution, but also managing IT services in alignment with business processes, including change management, service request fulfilment, and continuous improvement.

Call Center

A Call Center is a centralized department designed primarily for handling large volumes of inbound and outbound phone calls. It focuses on customer service or telemarketing, typically serving as the first point of contact for customers seeking assistance.

Key Features:

Primary Function: Handles telephone-based interactions. The focus is often on customer service, sales, or inquiries, rather than technical support.

Channels: Primarily phone-based, though some modern Call Centers might include chat or email support.

Focus : Customer service, resolving general inquiries, order processing, troubleshooting nontechnical issues, or providing information.

Scope: Repetitive tasks (for example, taking orders, answering questions, billing inquiries, and so on).

Agents: Often nontechnical, and trained to handle specific types of queries based on scripts or preset responses.

Tools Used: Call routing software, Customer Relationship Management (CRM) systems, and telephony systems.

Example: Customer Service Call Center: A customer calls to inquire about a bill, a product return, or an order status. The agent provides information or assists with the basic transactional tasks.

Help Desk

A Help Desk is a more specialized support function, typically focused on providing technical assistance to users, whether internal (employees) or external (customers). Help desks are usually the first point of contact for IT-related issues, offering basic troubleshooting and support.

Key Features:

Primary Function: Provides technical support to users. It helps resolve technical issues such as software problems, network outages, password resets, and other IT-related concerns.

Channels: Phones, emails, chats, ticketing systems, or even walk-ins in some cases.

Focus: Primarily reactive support, focusing on resolving immediate user issues.

Scope: Limited to incident resolution and break/fix problems.

Agents: Technical agents with the knowledge of basic troubleshooting and issue resolution.

Tools Used: Ticketing systems, remote desktop tools, knowledge bases, and monitoring tools.

Example: IT Help Desk: An employee reports his or her computer has crashed or that they are unable to log into the system. The help desk technician diagnoses and resolves the issue, or escalates it to a higher level of support, if needed.

Service Desk

A Service Desk is a broader and more comprehensive IT support function, covering all the aspects of IT Service Management. Unlike the help desk, which focuses on fixing immediate issues, the service desk is responsible for ensuring that IT services align with business goals, managing incidents, service requests, and changes, and ensuring continual service improvement.

Key Features:

Primary Function: Manages the entire IT service lifecycle, including incident management, request fulfilment, problem management, change management, case management, and maintaining Service Level Agreements (SLAs).

Channels : Multichannel, including phones, emails, self-service portals, and chats.

Focus: Both proactive and reactive. It aims to prevent incidents through problem management, manage IT changes effectively, and improve service quality.

Scope: Broad, encompassing not just issue resolution, but also service management, user satisfaction, and aligning IT services with business needs.

Agents: IT professionals skilled in not just troubleshooting, but also in managing service delivery, SLAs, and IT processes.

Tools Used : ITSM platforms (for example, ServiceNow, Jira Service Desk), knowledge bases, automation tools, and advanced reporting systems.

Example: IT Service Desk: An organization needs to implement a system wide software upgrade. The service desk coordinates with different teams, ensures that the change is managed with minimal disruption, and communicates with users about the schedule. It also tracks incidents and manages user requests during the process.

Aspect

Call Center

Help Desk

Service Desk

Primary Focus

Handling large volumes of calls and inquiries

Technical support for immediate IT issues

Comprehensive IT service management.

Channels

Primarily phone (sometimes chat or email)

Phone, email, chat, ticketing systems

Multichannel: phone, email, self-service portals, chat

Scope

General customer service, order processing, basic inquiries

Technical troubleshooting and incident resolution

Incident management, request fulfilment, problem and change management.

Nature of Support

Nontechnical, customer service oriented

Technical, focused on resolving IT issues

Technical, aligned with business goals and service delivery.

Tools Used

CRM systems, call routing, telephony systems

Ticketing systems, remote support tools

ITSM platforms (ServiceNow, Jira), advanced reporting and automation tools.

Proactive/Reactive

Reactive (respond to customer inquiries)

Primarily reactive (responds to IT issues)

Both reactive (incident resolution) and proactive (service improvement).

Agents

Nontechnical, trained in specific products or services

Technical agents focused on IT troubleshooting

IT professionals skilled in IT service management and continuous improvement.

Goal

Handle high-volume customer interactions efficiently

Restore normal operations quickly by resolving IT issues

Ensure that IT services align with business objectives, and improve service delivery.

Table 3.1: Different Forms of Customer Support

Goals, Objectives, and Benefits of Service Desk

Goals, Objectives, and Benefits of Service Desk are discussed in this section.

Goals of a Service Desk

Provide Centralized Support: Act as a single point of contact for all IT-related issues, requests, and incidents, ensuring that users have a clear and straightforward path for getting help.

Enhance User Satisfaction: Ensure timely resolution of issues to keep the users productive and satisfied with IT services.

Minimize Downtime: Quickly resolve incidents, and restore normal operations to reduce the impact of IT issues on business operations.

Improve Efficiency: Streamline support processes to enhance response times, and minimize repetitive work.

Facilitate Communication: Serve as a communication bridge between IT and users, ensuring smooth information flow about outages, changes, or service disruptions.

Support Continual Service Improvement (CSI): Monitor performance and feedback to identify opportunities for improving service quality and efficiency.

Benefits of a Service Desk

Increased Productivity: By resolving issues quickly, users spend less time waiting for support, enabling them to focus on their core tasks.

Cost Savings: Efficient handling of IT incidents reduces operational costs by minimizing system downtimes, and streamlining IT operations.

Enhanced IT User Relationship: A well-functioning service desk fosters trust between IT departments and users through reliable, transparent communication, and issue resolution.

Centralized Issue Management: All incidents, service requests, and queries are handled in one place, providing clear oversight, and tracking of issues.

Better Resource Allocation: By analyzing ticket trends, the service desk can help IT departments prioritize resources for resolving high-impact issues.

Proactive Problem Management: Historical data allows the service desk to identify recurring issues, and suggest preventive measures, reducing future incidents.

Objectives of a Service Desk

Timely Resolution of Incidents: Ensure that all the reported incidents and requests are resolved and fulfilled respectively within agreed-upon Service Level Agreements (SLAs).

Effective Incident Management: Efficiently manage the lifecycle of incidents, from logging to resolution, ensuring transparency and accountability.

Service Request Fulfilment: Handle and fulfil user service requests such as software installations, access permissions, and so on.

Communication and Escalation: Keep the users informed about the status of their requests, and escalate incidents as necessary to avoid prolonged downtimes.

Monitor and Improve Performance: Regularly track performance metrics (for example, response times, resolution times, and user satisfaction) to identify areas for improvement.

By aligning its goals, benefits, and objectives, a service desk can significantly improve the efficiency and satisfaction of both the IT teams and end users.

Types of Service Desks

As discussed earlier, the Service Desk is a central hub for managing incidents, requests, and communications between an organization and its users. Service Desks can be categorized into various types based on their structure, functionality, and scope of operation. These Service Desk types can be implemented individually or combined, depending on an organization’s specific requirements and operational scope.

Local Service Desk

Definition : A Service Desk located within the same premises or region as the user base it serves.

Characteristics :

Serves a specific geographical area or office.

Provides direct, face-to-face support in addition to remote help.

Common in small-to-medium-sized organizations.

Example : Ideal for organizations with a single office or regional presence.

An example of a Local Service Desk is a municipal government office that supports employees and residents within a specific city or town. For instance, the IT support team is located within the city hall building, and assists staff members with technical issues related to their workstations, printers, and software. Since the service desk operates on-site, employees can walk into and report problems, or seek assistance directly. This proximity allows for quick response times, and face-to-face interactions, making it an ideal solution for a small, localized organization.

Centralized Service Desk

Definition : A single Service Desk that serves users across multiple locations.

Characteristics:

Centralized resources and teams manage support.

Increased efficiency and cost-effectiveness due to reduced redundancy.

Example : Suitable for organizations with multiple branches looking to streamline operations.

An example of a Centralized Service Desk is a national bank with multiple branches across the country. Instead of having separate support teams at each branch, the bank maintains a single, centralized service desk located at its headquarters, or a dedicated Operations Center. This centralized team handles all user requests, whether they come from employees at branches, ATM maintenance teams, or customers needing assistance with online banking. Support is provided through phones, emails, chats, or a ticketing system, ensuring consistent service and efficient resource utilization across all locations.

Virtual Service Desk

Definition : A Service Desk model that operates remotely, connecting agents and users via digital platforms.

Characteristics:

Use technologies like cloud-based software, AI, and remote desktop tools.

Enables support across time zones and geographical barriers.

Highly scalable and flexible.

Example : Perfect for global organizations, or remote-first companies.

An example of a Virtual Service Desk is an e-commerce company with remote employees and customers across different regions. The company’s service desk operates entirely online, with support agents working from various locations. Using a cloud-based help desk platform, customers and employees submit tickets through email, chat, or a self-service portal. Virtual tools such as remote desktop software allow agents to troubleshoot technical issues without being physically present. This setup ensures flexibility, scalability, and round-the-clock support across multiple time zones, making it suitable for a dispersed or remote-first workforce.

Follow-the-Sun Service Desk

Definition : A globally distributed Service Desk model that provides continuous support by utilizing teams in different time zones.

Characteristics :

Ensures 24/7 support coverage.

Shifts are handed over to teams in different regions as the workday ends in one location.

Example : Ideal for multinational organizations needing round-the-clock service.

An example of a Follow-the-Sun Service Desk is a global IT services company that provides 24/7 technical support to its clients worldwide. The company has support teams located in different regions such as the United States, Europe, and Asia. When the workday ends in the U.S., unresolved tickets are seamlessly handed over to the team in Europe. Similarly, as Europe closes for the day, any pending issues are passed to the team in Asia. This ensures that users receive uninterrupted support, regardless of their time zone, leveraging the geographical distribution of teams to provide round-the-clock assistance.

Specialized Service Desk

Definition : A Service Desk focused on specific types of issues or departments.

Characteristics :

Handles specialized tasks such as IT support, HR inquiries, or customer service.

Staffed by agents with expertise in the specific domain.

Example : Effective for large organizations with complex operational needs.

An example of a Specialized Service Desk is the HR Service Desk within a large corporation. This service desk is dedicated to handling HR-related queries and tasks such as:

Assisting employees with payroll or benefits issues.

Answering questions about company policies or leave applications.

Managing recruitment inquiries, or onboarding processes.

The service desk is staffed by HR professionals who have the expertise to address these specific types of issues efficiently. This specialization ensures that employees receive accurate and focused support tailored to HR matters.

Self-Service Desk

Definition : A Service Desk that enables users to resolve issues independently through self-help tools.

Characteristics :

Features knowledge bases, FAQs, chatbots, and automated ticketing.

Reduces the burden on human agents by empowering users.

Provides quick solutions to repetitive or simple queries.

Example : Organizations looking to minimize support costs, and improve user autonomy.

An example of a Self-Service Desk is a university’s IT department providing an online self-service portal for students and staff.

Through this portal, users can:

Reset their passwords.

Access a knowledge base with step-by-step guides for resolving common technical issues such as connecting to campus Wi-Fi, or setting up email accounts.

Submit and track support tickets for more complex problems.

Use chatbots to get instant answers to the Frequently Asked Questions (FAQs).

This self-service model empowers users to resolve simple issues independently, reducing the workload on IT staff, and improving response times for more critical problems.

Outsourced Service Desk

Definition: A Service Desk operated by an external provider, rather than the organization itself.

Characteristics:

Cost-effective for organizations without the resources to manage in-house support.

May face challenges like reduced control or slower response times due to dependency on third parties.

Example : Organizations seeking to focus on core activities, while outsourcing non-core operations.

An example of an Outsourced Service Desk is a small retail chain contracting a third-party IT support company to handle all technical issues for its stores. Instead of maintaining an in-house IT team, the retail chain relies on the external provider to:

Manage hardware and software troubleshooting.

Provide help-desk services for employees across all store locations.

Monitor and maintain network systems remotely.

Offer 24/7 support for critical issues.

This approach allows the retail chain to focus on its core business operations, while benefiting from expert technical support at a lower cost.

Multi-Level Service Desk

Definition: A Service Desk structured in levels, with each level addressing increasingly the complex issues.

Levels:

Tier 0 : Self-service

Tier 1 : Basic troubleshooting and ticketing

Example : Suitable for large organizations with diverse and complex service needs.

An example of a Multi-level (Tiered) Service Desk is the IT support structure in a large healthcare organization such as a hospital network.

Tier 0 : A self-service portal with a knowledge base, FAQs, and automated tools for common issues such as password resets or printer setup.

Tier 1 : Frontline support staff who handle basic user issues such as login problems or software installation requests. If they cannot resolve the issue, it is escalated.

This tiered approach ensures efficient resolution of issues by routing them to the appropriate level based on complexity.

SLA of Service Desk

An SLA is like an agreement between the Service Desk (IT support team) and Service Providers about:

How fast they can or will respond to your ticket.

How quickly they can or will fix your issue.

It is like ordering pizza with a delivery guarantee (for example, “ 30 minutes or it is free! ”).

Service Level Agreements (SLAs) for a Service Desk are formalized agreed commitments outlining the expected performance standards, response times, and resolution times for handling support incidents and requests. They serve to manage expectations between the service provider and its users, ensuring a clear understanding of service quality and timelines.

How SLA Works in ServiceNow

When a user reports an Issue (for instance, “ Email not working ”):

A ticket is created in ServiceNow.

An SLA clock is triggered.

Tracking Deadlines :

Response SLA : Time to first reply (for example, “ Acknowledge ticket in 30 mins ”).

Resolution SLA : Time to fix (for example, “ Fix critical issues in 4 hours ”).

If the SLA is breached :

It can trigger escalation, and penalties can occur as agreed in the contract.

Why SLAs Matter:

Users : Know the maximum time in which the issue will get resolved.

IT Team : Clear goals to work toward.

Company : Measures performance (for instance, “ We fix 95% of tickets on time ”).

SLA Automation in ITSM Tools

SLA automation in IT Service Management tools such as ServiceNow, BMC Remedy, or Jira Service Management helps organizations to enforce and monitor service level objectives by automatically tracking response and resolution times for incidents or service requests. When a ticket is raised, the tool automatically applies to the appropriate SLA policy based on priority, urgency, or category. For example, if a Priority 1 (P1) incident is created, the system may define a 15-minute response SLA, and a 4-hour resolution SLA. The tool starts with an SLA timer as soon as the ticket is logged, and monitors its progress. If the response time reaches a predefined threshold (for example, 80% of the SLA time), the system triggers the automated alerts to the assigned engineer and their manager.

Similarly, for resolution, the tool continuously evaluates ticket progress. If the issue is not resolved within the expected timeframe, the ticket is marked as “ SLA Breached ,” and a notification is sent to relevant stakeholders. These tools also provide scheduled or on-demand SLA performance reports, highlighting metrics such as the percentage of tickets that met or breached SLA, average resolution times, and trends over time. These reports help IT leaders track compliance, identify gaps, and drive process improvements. Overall, SLA automation ensures the timely incident handling, proactive communication through alerts, and complete visibility via reporting, leading to improved service delivery and customer satisfaction.

Scenario: Priority 1 Incident in a Banking Application

A major Indian bank uses ServiceNow for incident management, and has defined the following SLA for P1:

Response SLA: 15 minutes

Resolution SLA: 4 hours

Flow with SLA Automation:

Incident Raised (10:00 AM): A user from the bank’s operations team reports that the Net-Banking platform is down for all customers. This triggers a P1 incident in ServiceNow.

SLA Timers Start Automatically: ServiceNow detects the ticket as P1 based on impact/urgency, and automatically starts the SLA timers for both response and resolution.

Response SLA Automation:

10:10 AM: No response yet. ServiceNow sends an automated email alert to the assigned support group:

“ P1 Incident INC123456 is approaching response SLA breach (80% threshold). Please acknowledge immediately .”

10:15 AM: No one has updated or accepted the ticket. SLA is now breached.

Resolution SLA Automation:

1:30 PM: ServiceNow checks the SLA clock, and sees the ticket is unresolved.

It triggers another pre-breach alert: “ Resolution SLA for P1 INC123456 will breach in 30 minutes. Please take the necessary action or escalate .”

1:45 PM: The fix is deployed, and Net-Banking services are restored. The engineer updates the incident with the resolution.

ServiceNow stops the SLA timer, and marks “ Resolution SLA Met .”

SLA Reporting and Audit:

We can trigger an SLA report generated by ServiceNow, which includes:

Incident INC123456 : Response SLA breached; Resolution SLA met

Time to respond : 18 mins (3 mins breach), Time to resolve: 3 hrs. 45 mins

This example shows how SLA automation improves incident handling speed, keeps stakeholders informed in real time, and supports data-driven process improvements.

How to Review SLA for Service Desk in ServiceNow

In ServiceNow , you can view SLA in several places, depending on your role, and what you are trying to track. Here is where you can see SLA details:

IT Support View:

Open the Incident record.

Scroll down to the " SLA " or " Task SLAs " related list.

You will see:

SLA name (for example, Response SLA, Resolution SLA)

Start time, Breach time

Stage (In Progress, Paused, Completed)

Whether it is met or breached

Figure 3.1: SLA Status in Incident

Monitoring SLA Performance via Dashboards

ServiceNow offers dashboards that provide a visual overview of the SLA performance:

SLA Dashboard:

Navigate to Service Level Management > SLA > SLA Dashboard .

This dashboard displays the:

Overall SLA compliance rate

Number of breached SLAs

SLA performance trends over time

SLA Performance Analytics:

For more detailed insights, go to Performance Analytics > SLA Performance .

Here, you can view the :

Average SLA resolution times

Compliance rates by priority or department

Historical SLA trends

Common SLA Metrics for a Service Desk

Response Time:

The time taken to acknowledge a ticket, after it is logged.

Response Time Definition: The time elapsed between the logging of an incident, and the initial acknowledgment by the Service Desk, including confirmation of receipt, and assignment to a technician.

Example :

Priority Level

Response Time SLA

Critical Priority

Within 15 minutes

High Priority

Within 1 hour

Medium Priority

Within 4 hours

Low Priority

Within 8 hours

Table 3.2: Response SLA Matrix

Resolution Time: The time within which an issue is resolved, or a workaround is provided.

Example :

Priority Level

Resolved Time SLA

Critical Priority

Within 4 hours

High Priority

Within 8 hours

Medium Priority

Within 3 business days

Low Priority

Within 5 business days

Table 3.3: Resolution SLA Matrix

First Contact Resolution Rate (FCR):

The percentage of tickets resolved during the first interaction with the user.

Example Target : 75%–85%.

Escalation Time:

The time at which an unresolved ticket is escalated to the next support level, either due to user dissatisfaction with the resolution, or because the resolution SLA is approaching its breach threshold.

Example :

Critical Priority: Escalate within 1 hour.

High Priority: Escalate within 4 hours.

Medium Priority: Escalate within 1 day

Low Priority: Escalate within 3 days

PS : The escalation time can vary from organization to organization, and it can be done as per the business need.

Uptime and Availability:

Ensures systems are operational within the agreed parameters.

Example : 99.9% uptime for critical systems.

Customer Satisfaction (CSAT):

Measured through surveys post-resolution.

Example Target : Maintain a score of 90% or above.

Call Abandonment Rate:

Percentage of calls abandoned by users, before connecting with an agent.

Example Target : <5%.

Call Pick Rate:

It indicates how promptly support agents or service desk staff are answering the incoming calls. A high call pick rate means calls are being answered quickly which contributes to a better user experience.

Measures responsiveness and customer service efficiency. Helps assess staffing adequacy and training needs.

SLA Best Practices

Categorization: Define clear priority levels, based on impact and urgency.

Monitoring and Reporting: Use tools to track SLA adherence in real-time.

Regular Reviews: Periodically evaluate SLA effectiveness, and adjust as necessary.

Transparency: Ensure that the users are aware of SLA terms.

Alignment: Align SLAs with business objectives to reflect criticality.

Step-by-Step Procedure for Service Desk in ServiceNow

The Service Desk team can use ServiceNow effectively for better ticket management by leveraging its robust features and best practices to streamline processes, enhance collaboration, and improve resolution times. Here is how they can make the most of the platform:

Accessing the Service Desk

Service Desk Agents/Technicians log in to the ServiceNow Agent Workspace ( https://<instance>.service-now.com/nav_to.do ).

Submitting a New Incident or Request

In the Agent Workspace , go to Incidents or Service Catalog .

Click New .

Fill in the ticket details, and assign it to the appropriate group/individual.

Figure 3.2: Incident creation in ServiceNow

Ticket Workflow and Resolution

Agent Receives Notification (email/ServiceNow alert).

Agent Reviews Ticket:

Checks description, priority, and related records (for example, past incidents and known errors).

Consults Knowledge Base for solutions.

Agent Acts :

Resolves immediately (if simple issue).

Escalates to a specialist (if complex).

Requests more info from the user (via comments/emails).

Updates Ticket/s:

Adds work notes (internal updates).

Changes state (for instance, " In Progress ," " Awaiting User response ").

Resolution and Closure:

Once fixed, the agent marks the ticket as " Resolved ."

The user gets a confirmation email.

If the user confirms resolution, the ticket closes.

Figure 3.3: Incident Lifecycle Flowchart

Effective ServiceNow Utilization for Service Desk Teams

The Service Desk team can use ServiceNow effectively for better ticket management by leveraging its robust features and best practices to streamline processes, enhance collaboration, and improve resolution times. Here is how they can make the most of the platform:

Centralize Ticket Management

Single Platform : Use ServiceNow as a unified platform to log, manage, and resolve tickets across IT, HR, and other departments.

Categorization and Prioritization : Ensure that tickets are appropriately categorized, prioritized, and assigned to the correct teams or individuals.

Automate Ticket Routing

Assignment Rules : Configure automated routing based on ticket categories, urgency, or business rules to assign tickets to the right team or agent.

Escalation Policies : Set up escalation workflows to ensure that critical tickets are addressed promptly, if unresolved within the defined timeframes.

Leverage Knowledge Base

Knowledge Articles : Create and maintain an up-to-date knowledge base with solutions to common issues.

Deflection : Use the knowledge base to empower end-users and service desk agents to resolve issues faster.

Auto-Suggestions : Configure ServiceNow to suggest the relevant knowledge articles, when users log tickets.

Use Self-Service and Automation

Self-Service Portals : Encourage users to submit and track their tickets through self-service portals.

Virtual Agents : Deploy ServiceNow’s chatbot to handle the routine queries, or guide users to the correct resources.

Automated Workflows : Use automation to handle repetitive tasks such as password resets, or provisioning requests.

Monitor and Manage SLAs

Service Level Agreements (SLAs) : Define SLAs to ensure that tickets are resolved within the acceptable timeframes.

Real-Time Monitoring : Use dashboards to monitor the SLA compliance, and address potential breaches proactively.

Enhance Collaboration

Collaboration Tools : Use built-in collaboration features such as comments, tags, and work notes to share updates, and coordinate efforts among team members.

Integrated Communication : Integrate communication tools such as Microsoft Teams or Slack for real-time updates and discussions.

Utilize Reporting and Analytics

Dashboards and Reports : Leverage prebuilt and customizable dashboards to track ticket volumes, resolution times, and team performance.

Trend Analysis : Identify recurring issues and bottlenecks through analytics, and take corrective actions.

KPIs : Monitor the Key Performance Indicators (KPIs) such as first-call resolution, average response time, and customer satisfaction scores.

Standardization and Follow ITIL Practices

Incident Management : Follow ITIL principles for incident resolution and problem management.

Change Management : Use ServiceNow to manage changes effectively, ensuring that tickets related to changes are tracked and implemented smoothly.

Empower Agents

Agent Workspace : Provide agents with a unified view of tickets, tasks, and customer information for improved productivity.

Training : Regularly train service desk teams on ServiceNow features, best practices, and new updates.

Gather User Feedback

Surveys : Use ServiceNow’s feedback tools to collect customer satisfaction (CSAT) scores after ticket resolution.

Continuous Improvement : Analyze feedback to identify areas for improvement, and enhance service quality.

Integrate with Other Systems

Third-Party Tools : Integrate ServiceNow with tools such as monitoring systems, email platforms, and collaboration apps to streamline ticket creation and updates.

Configuration Management Database (CMDB) : Use CMDB to link incidents and problems with assets or services, providing context for troubleshooting.

Regular Maintenance and Optimization

Audit Workflows : Periodically review and optimize workflows to ensure efficiency.

Update Knowledge Base : Continuously update knowledge articles, and remove the obsolete ones.

Platform Upgrades : Keep the ServiceNow platform updated to leverage new features and improvements.

Benefits of Effective Ticket Management with ServiceNow:

Improved Resolution Times : Faster resolution with automated routing and clear workflows.

Enhanced Customer Satisfaction : Streamlined processes and self-service options improve the user’s experience.

Reduced Workload : Automation and deflection reduce the workload on service desk agents.

Data-Driven Decisions : Insights from reports and analytics guide continuous improvement efforts.

By applying these strategies, the Service Desk team can maximize ServiceNow’s capabilities, and deliver better, faster, and more efficient support.

Conclusion

In this chapter, we explored the essential aspects of a Service Desk, and its critical role in IT Service Management (ITSM). We began with an overview of what a Service Desk is serving as the central point of contact between users and IT, as well as discussed the key terminologies that form the foundation for understanding its operations. We clarified the differences between a Help Desk, Call Center, and Service Desk, highlighting how the Service Desk offers a broader and more strategic scope.

We also looked into the goals and objectives of a Service Desk such as improving user satisfaction, ensuring service continuity, and streamlining issue resolution, along with the tangible benefits it brings to an organization. The different types of Service Desks, centralized, local, virtual, and follow the sun, showcase how organizations can tailor their support structures to fit global or regional needs.

A crucial part of service delivery, Service Level Agreements (SLAs), was also covered, emphasizing how SLAs set clear expectations for performance and response times. Finally, we examined how ServiceNow enhances Service Desk functionality through automation, real-time tracking, and efficient incident and request management.

Altogether, this chapter provides a solid foundation for understanding how a well-structured Service Desk, supported by platforms such as ServiceNow, contributes to delivering high-quality, efficient, and user-focused IT services.

In this chapter, we’ll explore the fundamental Service Request and Request Fulfillment processes in ServiceNow. We will define what are Service Requests and we will then examine the structured and automated Request Fulfillment lifecycle. Our discussion will highlight how ServiceNow’s Service Catalog and workflow automation tools are used to streamline the process, from initial submission and approval to task assignment and final delivery. This ensures a consistent, efficient, and user-friendly experience for everyone.

Multiple Choice Questions

What is the primary role of a Service Desk in IT Service Management?

Develop software applications

Monitor network traffic

Act as a single point of contact between users and IT

Manage hardware installation

Which of the following best describes an SLA?

A software license agreement

A contract for purchasing IT equipment

A documented agreement on service expectations between IT and users

A list of software applications used by IT

What is a key difference between a Help Desk and a Service Desk?

Help Desk is more strategic than Service Desk.

Service Desk supports only hardware issues.

Help Desk focuses on break-fix, while Service Desk supports broader ITSM practices.

There is no difference between them.

Which of the following is NOT a type of Service Desk?

Centralized

Virtual

Distributed

Remote Support

In ServiceNow, where can you typically view SLA progress on an Incident record?

Header section

Notification Center

Task SLAs related list

User Preferences

Which term refers to the time within which IT must respond to a reported issue?

Fix Time

Response Time

Downtime

Breach Timer

What is one of the primary goals of the Service Desk?

Reducing company expenses

Managing employee salaries

Improving user satisfaction, and resolving IT issues efficiently

Designing the company website

What does " Breach " mean in the context of an SLA?

Meeting the SLA successfully

Exceeding the allowed time to respond, or resolve an issue

Upgrading the SLA contract

Logging out of the system

Which of the following is the benefit of having a well-structured Service Desk?

Increased software development time

Improved call center metrics only

Faster issue resolution, and better communication

More frequent IT outages

What functionality does ServiceNow offer for Service Desk operations?

Only hardware troubleshooting

Automation of tasks, SLA tracking, and incident management

Hiring new employees

Training IT staff in programming languages

Answers

c

c

c

d

c

b

c

b

c

b

C HAPTER 4

Introduction to Service Request Management

Introduction

In today’s fast-paced digital world, delivering consistent, efficient, and user-centric IT services is essential for business success. Organizations rely on structured frameworks such as ITIL and platforms such as ServiceNow to streamline service delivery, manage user requests, and ensure value creation through IT services. This chapter explores fundamental concepts central to effective Service Management, including the nature of services, how they deliver value, and how value streams guide the delivery and improvement of those services. You will be introduced to Service Requests, which are formal requests from users for access to IT services, hardware, software, or information.

The chapter also delves into Request Fulfillment, the process by which service requests are handled from initiation to completion/fulfillment. Understanding the Request Fulfillment Lifecycle within ServiceNow provides insight into how automation, approvals, and workflows collaborate to ensure timely and accurate delivery of services.

Finally, we distinguish between Service Catalogs and Request Fulfillment, two closely linked yet distinct elements of service management, to clarify their individual roles and interactions in the broader IT service ecosystem. By the end of this chapter, you will understand how these components work together to enhance operational efficiency, improve user experience, and streamline service delivery in IT and business environments.

Structure

In this chapter, we will cover the following topics:

Service, Value, and Value Streams

Introduction to Service Request

Introduction to Service Catalogs

Navigating Service Catalogs in ServiceNow

Managing Service Catalogs in ServiceNow

Introduction to Request Fulfillment

Request Fulfillment Lifecycle in ServiceNow

Difference between Service Catalogs and Request Fulfillment

Service, Value, and Value Streams

Service: A service is an act of helpful activity, aid, or help. A coffee shop provides services in the form of delivering coffee to its customers. In ITIL 4, a service is defined as a way to co-create/co-deliver value to customers by facilitating outcomes they want to achieve, without the customer having to manage specific costs and risks. It involves a combination of people, processes, and technology designed to meet a business need or fulfill a user requirement.

Value: In ITIL, value is the perceived usefulness, importance, and benefits of something. It is a multifaceted concept that goes beyond financial metrics, and includes:

Utility

Warranty

Alignment with business objectives

Customer and user perspectives

Outcomes

Cost-effectiveness

Continual improvement

Value is subjective, and can vary from person to person, depending on their reason or emotion. For example, a person might value home insurance for the peace of mind it provides, while another might value it for the logical reason that it replaces stolen or destroyed possessions.

Scenario: An employee requests access to Microsoft Teams. User submits a service request through ServiceNow.

Process:

The request is auto routed to the appropriate fulfillment group, based on the user’s department.

Approval is auto triggered for the line manager.

Once approved, access is provisioned via automation or assigned to IT for manual fulfillment.

The user receives confirmation, and the request is marked as completed.

Value delivered:

Type of Value

Explanation

Operational Efficiency

Automation reduces manual effort, and speeds up fulfillment.

User Satisfaction

Fast, predictable response enhances the user experience.

Compliance

Approval workflow ensures proper authorization and audit trail.

Table 4.1: Value Delivered in Service Request

In ITIL, value is only perceived when a product or service is used and appreciated. To determine a product or service’s worth, organizations should engage with consumers, both internal and external. Service Request Management adds value by delivering standardized, efficient, and user-friendly access to commonly requested services, helping IT align closely with business needs, while ensuring governance and responsiveness.

Value Streams: Value streams are a way to visualize how a business creates value for customers.

The concept of value streams in ITIL 4 can be used to explain how the overall value of a service is made up of subcomponents. For example, when visiting a coffee shop, the overall value is getting a great coffee, but the subcomponents are: Getting service with a smile, having a comfortable seat, and having a clean table.

Each subcomponent contributes to the overall value of having a coffee, but they have their own specifics. For example, one person may get the coffee from the counter, while another person is responsible for cleaning up the tables.

Value streams represent the end-to-end flow of activities, from demand (user request) to value (fulfilled outcome), ensuring each step contributes meaningfully to service delivery, and aligns with business goals.

Value Stream in Service Request Management

In Service Request Management, value streams are used to visualize and optimize how user requests (like access, installations, or information) are efficiently fulfilled to deliver value to the customer. Each step in the process such as logging, approval, fulfillment, and closure, contributes to the overall value.

Scenario: A new employee submits a laptop request via the IT service portal.

Service Request Value Stream Breakdown

Step in Value Stream

Value Contributed

User Submits Request

Self-service portal ensures easy, 24/7 access to standardized offerings.

Auto-Categorization and Routing

Reduces manual triage time; request goes to the correct support team instantly.

Manager Approval Workflow

Ensures governance, and prevents unauthorized access to resources.

IT Fulfillment (Provisioning)

Hardware is allocated, imaged, and delivered; this is the core product value.

Confirmation and Closure

The User is informed, ticket closed, and satisfaction can be measured via survey.

Post-Request Analysis

Data collected for continuous improvement (for example, delays and bottlenecks).

Table 4.2: Service Request Value Stream Breakdown

In ITIL 4, a value stream helps map and improve every activity that contributes to fulfilling a service request. It ensures that each step adds measurable value, enabling IT to deliver services that are efficient, reliable, and aligned with business and user needs.

Introduction to Service Request

A Service Request is a formal way to ask for something you need to do your job, whether it is equipment, software, access to a system, or help setting something up. It is like putting in a work-related order, or asking for assistance that does not involve something being broken.

Think of it as raising your hand and saying, “Hey, I need something to work better!” But in a structured, trackable way through your company’s service portal.

In ITIL 4, a Service Request is a formal request from a user, or a customer for something to be provided such as information, advice, a standard change, or access to a service by the IT service provider. Service Request Management is one of the 17 Service Management Practices in ITIL 4, placing SRM as a core operational function that supports user satisfaction, efficiency, and value delivery.

Service Requests are typically standard and predefined, repeatable, and low-risk actions that are part of the normal service delivery process. They are often initiated by or on behalf of users through a self-service portal, or by contacting the service desk. Service requests follow defined workflows, and do not require additional approval.

Examples of Service Requests:

Requesting access to a specific application or system

Requesting a new laptop or other hardware

Requesting software installation or updates

Requesting a password reset

Requesting information or documentation

Requesting a new email account or mailbox

Key Characteristics of a Service Request in ITIL 4

Standardized and Predefined : Service Requests are for well-documented, routine services or actions, such as password resets, access to software, or provisioning of equipment. Service Requests follow predefined workflows and approval processes.

User Initiated : Service Requests are initiated by users (employees or customers) who need something from the IT service provider.

Why Are Service Requests Important?

Service requests might seem like a small part of your workday, just a quick form you fill out, when you need something, but they actually play a big role in keeping your organization running smoothly. Service requests ensure that needs are met systematically, reducing chaos and improving service delivery. Without Service requests, organizations risk inefficiency, poor communication, and dissatisfied users.

Service requests are one of the main building blocks of ITSM. They are handled through a defined process which ensures that:

Your request goes to the right team.

It gets fulfilled in a consistent way.

Progress can be tracked and measured.

The whole experience is smooth for the user.

Without service requests, you would probably have to follow a manual process to request something… The service desk then forwards your request… who asks someone else… and so on. Things get lost, delayed, or forgotten.

With a central request system like ServiceNow, the process can be automated and streamlined. You can search and select exactly what you need (like shopping online).

The system knows where to send your request.

Approval flows (like manager sign-off) trigger automatically.

You get updates without having to chase people.

This saves time for both the requester and the fulfillment teams, and it ensures that important tasks do not fall through the cracks.

Improving User Experience and Productivity

When service requests work well, they make life easier for everyone:

Employees get what they need faster (hardware, access, support).

Managers can approve requests with one click.

IT teams spend less time figuring out what people need.

The business runs more efficiently.

Introduction to Service Catalog

Imagine walking into a store where everything is organized into neat shelves, one section for electronics, another for office supplies, and another for services like printing or repairs. You browse, pick what you need, and check out. Now imagine that store exists online, inside your company and instead of buying things with money, you are submitting requests for tools, access, or support to help you do your job.

A Service Catalog is a centralized, organized list of IT services provided by an organization’s IT department. Service Catalog is a digital, user-friendly interface that allows employees or customers to browse and request IT services, and other business services.

Catalog

ServiceNow’s Service Catalog is a core feature that helps organizations streamline service delivery, improve user experience, and enhance operational efficiency.

Key Features of a Service Catalog in ServiceNow:

User-friendly Interface:

The Service Catalog is accessible via a web-based portal, often customized to match the organization’s branding.

Users can browse services by category, search for specific services, or view popular services.

Service Categories:

Services are organized into logical categories (for example, Software, Hardware, Services, Facilities) for easy navigation.

Service Items:

Each service item includes a description, eligibility criteria, request process, and any associated costs.

Users can submit requests directly from the Catalog.

Request Workflows:

ServiceNow automates the request process with predefined workflows, ensuring requests are routed to the right teams, and fulfilled efficiently.

Self-service Capabilities :

Users can see how to raise a new request, how to track the status of their requests, and access knowledge articles directly from the Catalog.

Integration with Other Modules:

The Service Catalog integrates with other ServiceNow modules such as Incident Management , Change Management , and Asset Management for end-to-end service delivery.

Navigating the Service Catalog in ServiceNow

Types of Catalog Items: The catalog is usually divided into categories, and so it is easy to find what you need. Here are the most common types of service catalog items:

Figure 4.1: Accessing Service Catalog in ServiceNow

Steps to Access Service Catalog in ServiceNow

Visit the Service Portal page of your organization.

Navigate to the Service Catalog:

On the Service Portal homepage, locate and click " Service Catalog " or " Request Something " tile or menu option.

Figure 4.2: Accessing Service Catalog via Service Portal

Browse Categories: The catalog is organized into categories like Hardware, Software, Access, and so on. Click a category to view the related services.

Select a Catalog Item: Click the desired service or item (for example, " Request Laptop " or " Request Folder Access ").

Figure 4.3: Browsing Service Catalog Items in ServiceNow

Fill Out the Request Form: Complete all required fields, and provide the necessary details.

Submit the Request:

Click the " Submit " button.

You will receive a confirmation and tracking number (RITM/REQ).

Track Your Request: Use the " My Requests " or " My Approvals " section in the portal to monitor the status, or take action if required.

Roles in Service Catalog

In the ServiceNow Service Catalog , several key roles work together to ensure the catalog is well-designed, maintained, and aligned with business needs. Following are the main roles involved, along with their responsibilities:

Requestor (End User)

Primary Role: Submits service requests via the Service Catalog.

Responsibilities:

Accesses and browses catalog items.

Fills out forms and submits service requests.

Tracks the status of their requests.

Approver (Line Manager)

Primary Role : Reviews and approves or rejects requests based on policies or business needs.

Responsibilities:

Receives approval notifications.

Reviews request details and justifications.

Approves or denies requests in a timely manner.

Fulfiller

Primary Role : The individual or team member who performs the work to complete a service request task.

Responsibilities :

Receives and accepts assigned catalog tasks (SCTASKs).

Performs the actions required to deliver the requested item or service.

Updates the status of tasks in ServiceNow.

Communicates with the requestor, if additional information is needed.

Service Owner

Primary Role : A strategic role accountable for the overall delivery and lifecycle of a specific IT service.

Responsibilities :

Accountable for the service, from strategy and design to retirement.

Ensures that the service provides value, and meets the business requirements.

Negotiates and agrees upon Service Level Agreements (SLAs) with stakeholders.

Acts as the primary point of contact and escalation for the service.

Service Manager

Primary Role : A tactical role responsible for the day-to-day operational management of one or more services.

Responsibilities :

Manages the day-to-day delivery of the service, according to the agreed SLAs.

Oversees the fulfillment process, and manages the teams involved.

Monitors service performance, and reports to the Service Owner.

Handles operational escalations, and contributes to service improvement.

Catalog Managers

Primary Role: Catalog Managers are responsible for overseeing the design, structure, and usability of the ServiceNow Service Catalog, ensuring it meets business requirements and delivers a seamless user experience.

Responsibilities:

Defining and maintaining the overall structure and taxonomy of the Service Catalog.

Collaborating with stakeholders to identify and prioritize catalog offerings, based on business needs.

Ensuring consistency, accuracy, and clarity of catalog items and descriptions.

Reviewing and approving new catalog items and changes, before they are published.

Coordinating with ServiceNow Administrators to implement catalog configurations and workflows.

ServiceNow Administrators

Primary Role : ServiceNow administrators are responsible for the overall configuration, maintenance, and management of the ServiceNow platform, including the Service Catalog.

Responsibilities:

Creating and updating Catalog items.

Configuring workflows and approval processes for Catalog items.

Managing categories and subcategories in the Service Catalog.

Ensuring that the Catalog aligns with the organizational needs and policies.

Fulfillment Team

Primary Role : The fulfillment team (or IT support team) often works closely with the ServiceNow administrators to define the services and Catalog items that should be available to the users.

Responsibilities :

Identifying and documenting services to be included in the Catalog.

Defining Service Level Agreements (SLAs) and workflows for Catalog items.

Ensuring that the Catalog meets the user needs and organizational goals.

Business Stakeholders

Primary Role : Business units or departments (for example, HR, Facilities, Finance) often own specific services or Catalog items related to their functions.

Responsibilities : Providing input on the services they offer and how they should be presented in the Catalog.

Approving the content and workflows for their respective Catalog items.

Ensuring their services are up-to-date and relevant.

Process Owners

Primary Role : Process owners are responsible for specific processes or services within the organization.

Responsibilities :

Defining the requirements for Catalog items related to their processes.

Ensuring that the Catalog items align with business processes and policies.

Reviewing and approving changes to Catalog items.

Requesting Changes to the Service Catalog

If you need to add, modify, or remove a Catalog item, you typically need to:

Submit a request to the ServiceNow administrators or ITSM team.

Work with the relevant business stakeholders to define the requirements.

Test and approve the changes before they go live.

Introduction to Request Fulfilment

Request Fulfillment is a key process in ITSM that focuses on handling service requests from users. It is one of the core processes in the ITIL framework. Request Fulfillment is the process responsible for managing the lifecycle of service requests, from submission to fulfilment. The goal is to provide users with quick and efficient access to the services they need, while maintaining consistency and control.

Request Fulfillment Lifecycle in ServiceNow

The Request Fulfillment Lifecycle in ServiceNow is a structured, often automated, process for managing and delivering services that users request from the Service Catalog.

Figure 4.4: Request Fulfillment Lifecycle in ServiceNow

Request Intake/Submissions:

Users submit requests through self-service portal.

Requests are logged.

Validation and Approval:

The request is reviewed to ensure that it is valid and complete.

Certain requests require approval from the requestor’s line manager, before they can proceed. In such cases, the request will be automatically routed to the appropriate manager for approval.

Fulfillment:

The request is processed by the appropriate team or automated workflow.

This may involve provisioning resources, providing information, or performing a task. In Request Fulfillment, tasks are the building blocks that structure, assign, and track the work required to deliver a requested service.

Each task is tracked separately, and may be handled by different fulfillment groups.

Tasks can be automated or manual.

Tasks can run in parallel or sequentially, depending on the workflow design.

Task completion contributes to the overall SLA compliance and customer satisfaction.

Closure:

Once the request is fulfilled, it gets closed on its own.

The user is notified, a survey is triggered, and feedback can be collected.

Role of Tasks in Request Fulfillment

In ServiceNow’s Request Fulfillment process, tasks are individual units of work that need to be completed in order to fulfill a user’s service request. These tasks ensure that the request is broken down into manageable steps, assigned to the right teams, and tracked through completion.

Figure 4.5: Task Fulfillment Lifecycle

Benefits of Request Fulfillment

Improved User Experience : Users can conveniently submit and manage requests through a self-service portal, enhancing satisfaction and ease of access.

Operational Efficiency : Automated and standardized workflows reduce manual intervention, accelerating fulfilment and minimizing errors.

Enhanced Visibility : Real-time tracking and reporting offer transparency into request status, enabling better communication and oversight.

Process Consistency : Predefined procedures ensure uniform handling of requests, supporting compliance with organizational policies and standards.

Reduced Workload for IT Teams : Automation and clear categorization of service requests help reduce the volume of repetitive queries and manual tasks.

Faster Time to Resolution : Standard service requests are fulfilled quickly, improving the overall service delivery timelines.

Improved Resource Allocation : Categorizing and tracking requests allow better planning and utilization of IT resources.

Increased Policy Compliance : Automated routing and approval workflows ensure that only authorized requests are fulfilled.

Data-Driven Insights : Request data can be analyzed to identify trends, recurring needs, and areas for service improvement.

Scalability : As the organization grows, the request fulfillment process can be scaled efficiently, without increasing the overhead.

Request Fulfillment and Service Catalog

Request Fulfillment and Service Catalog are closely related concepts in IT Service Management, but they serve different purposes and functions. The Service Catalog is about what users can request. Request Fulfillment is about how those requests are handled and fulfilled. Both are essential components of ITSM, and work together to provide a seamless experience for users, while ensuring efficient service delivery.

Service Catalog

The Service Catalog is a user-facing interface that provides a menu of available services and items that users can request. It acts as a " storefront " for IT and business services.

Key Characteristics of the Service Catalog

Purpose : To present a list of standardized, preapproved services and items that users can request.

Content : Includes Catalog items such as software requests, hardware provisioning, access requests, and other services.

User Interaction : Users browse or search the Catalog, select an item, and fill out a form to submit a request.

Focus : On presentation and accessibility of services.

Example: A user visits the Service Catalog to request a new laptop. They search for the " Laptop " in the Catalog item, select the required laptop, fill out the required details, and submit the request.

Figure 4.6: Overview of Service Catalog to Request a New Laptop

Figure 4.7: Submitting a Request for a New Laptop

Request Fulfillment

Request Fulfillment is the process responsible for handling and fulfilling service requests submitted through the Service Catalog. It focuses on the end-to-end lifecycle of a request, from submission to delivery.

Key Characteristics of Request Fulfillment

Purpose : To manage and fulfill user requests efficiently and consistently.

Process : Includes steps such as request intake, validation, approval, fulfillment, and closure.

Automation : Uses workflows to automate tasks, approvals, and notifications.

Focus : On execution and delivery of services.

Example: After the user submits a laptop request through the Service Catalog, the Request Fulfillment process kicks in. The request is routed to the procurement team for approval, and the laptop is ordered, configured, and delivered to the user. The process ends with the request being closed, and the user being notified.

How They Work Together

The Service Catalog is the entry point for users to submit requests.

Once a request is submitted, the Request Fulfillment process takes over to ensure the request is fulfilled.

Example Workflow:

A user visits the Service Catalog, and selects " Request Access to a System ."

They fill out the form, and submit the request.

The Request Fulfillment process begins:

The service request is initially validated by a designated fulfillment team.

_ If request are to be approved, the ticket will be routed for managerial approval.

Once approved, the IT team grants access.

The request is closed, and the user is notified.

Example of an E-commerce Company: Service Catalog and Request Fulfillment

The Service Catalog is like the product listing page where users select what they need. Request Fulfillment is like the order processing and delivery system that ensures the request is fulfilled.

Consider an e-commerce company named “Zento” where users can buy electronic gadgets online.

Service Catalog (Zento’s Product Listing Page)

What it is: The Service Catalog is like Zento’s product listing page, where users can browse and select items to purchase.

How it works:

Zento displays a Catalog of products (for example, laptops, smartphones, and headphones) with details such as price, specifications, and availability.

Users can search, filter, and select the products they want to buy.

Once a product is selected, the user adds it to their cart, and proceeds to checkout (similar to submitting a request in ServiceNow).

Request Fulfillment (Zento’s Order Processing and Delivery)

What it is: The Request Fulfillment process is like Zento’s order processing and delivery system which handles the request (order) from the time, it is placed until it is delivered to the customer.

How it works:

Once the user places an order, Zento’s system processes the request:

Validation: The system checks if the item is in stock, and if the payment is successful.

Approval: If the payment is approved, the order is confirmed.

Fulfillment: The item is then picked from the warehouse, packed, and handed over to the delivery partner.

Delivery: The item is shipped and delivered to the user.

Closure: Once the user receives the item, the order is marked as complete.

Analogy to ServiceNow: In ServiceNow, Request Fulfillment is the behind-the-scenes process that handles the user’s request (example, " Request a Laptop ") from submission to delivery. It includes steps such as approval, procurement, configuration, and delivery.

Process Similarity with ServiceNow

Step

Zento

ServiceNow

1. User Interaction

The user browses the product Catalog and selects an item.

The user browses the Service Catalog and selects a service (for example, " #1Request a Laptop ").

2. Submission

The user adds the item to the cart and checks out.

The user fills out a form and submits the request.

3. Validation

Zento checks stock availability and payment.

ServiceNow validates the request (for example, checks budget or approvals).

4. Approval

Payment is approved, and the order is confirmed.

The request is routed for approval (for example, manager approval).

5. Fulfillment

Item is picked, packed, and shipped.

IT team procures, configures, and delivers the requested item.

6. Delivery

Item is delivered to the user.

The requested service or item is provided to the user.

7. Closure

Order is marked as complete after delivery.

The request is closed, and the user is notified.

Table 4.3: Process Similarity with ServiceNow

Conclusion

In ITIL 4, Service Request contributes to the overall value creation by enabling users to access the resources and services they need to perform their tasks effectively.

It is a critical component of IT service delivery, enabling organizations to provide efficient, consistent, and user-friendly support. By managing Service Requests effectively, IT teams can enhance user satisfaction, optimize resources, and contribute to the overall value-creation process. In this chapter, we have laid the foundation for understanding how modern service management works through the lens of ServiceNow and ITSM principles. By exploring the key concepts such as services, value, value streams, service catalogs, and request fulfillment, we have gained a comprehensive view of how organizations efficiently deliver support and resources to the employees.

The discussion progressed to Service Catalogs, which act as a centralized, user-friendly interface for browsing and requesting services. We examined how to navigate and manage Service Catalogs in ServiceNow, ensuring efficient service delivery through organized listings, categories, and workflows.

Next, we introduced Request Fulfillment, the process of handling and resolving service requests, and analyzed its lifecycle in ServiceNow, from submission to closure. Finally, we distinguished between Service Catalogs and Request Fulfillment, clarifying that while catalogs provide the front-end interface for users, request fulfillment encompasses the back-end processes that ensure timely and effective service delivery.

By mastering these concepts, organizations can enhance service efficiency, improve user satisfaction, and streamline IT and business operations. The next step is applying these principles in real-world scenarios to optimize service management workflows.

Key Takeaways

Service, Value, and Value Stream define how services create business outcomes.

Service Requests standardize user needs for better tracking.

Service Catalogs provide a user-friendly portal for service discovery.

Request Fulfillment ensures end-to-end processing of requests.

ServiceNow integrates both catalogs and fulfillment for seamless service management.

Multiple Choice Questions

What is the primary goal of a service in ITIL?

To provide value to customers and facilitate outcomes

To reduce cost of hardware

To replace outdated software

To manage vendor contracts

Which of the following best defines “Value” in the context of IT services?

The price paid for a service.

The number of services offered.

The perceived benefits minus the cost and risks.

The amount of data processed.

What are Value Streams in ITIL 4?

A method of streaming service videos to customers.

A cost-saving mechanism in IT services.

A storage method in cloud computing.

A series of steps, an organization uses to create and deliver services.

What is a Service Request in ServiceNow?

A warning about a critical system error.

A ticket raised for unauthorized access.

A user-initiated request for something to be provided.

A policy violation alert.

Which of the following is typically included in a Service Catalog?

Only incidents and problems.

A list of available hardware only.

Standard services and items, users can request.

Confidential IT audit logs.

In ServiceNow, how do users typically navigate a Service Catalog?

Through the Service Portal or Self-Service interface

Through writing SQL queries

By contacting IT via phone only

Through Windows Command Prompt

Who is primarily responsible for managing and maintaining the Service Catalog in ServiceNow?

End users

Finance department

Service Catalog Administrator or Service Owner

External vendors

What is the first step in the Request Fulfillment lifecycle?

Authorization

Request Logging

Request Closure

Request Approval

During the request fulfillment lifecycle, which step ensures the user has received what was requested?

Logging

Categorization

Request Closure

Fulfillment

What is a key difference between a Service Catalog and Request Fulfillment?

Service Catalog is about ticket closure only; Request Fulfillment is about service listing.

Service Catalog lists the available services, Request Fulfillment handles delivery of requested services.

They are the same process with different names.

Request Fulfillment only applies to software, not services.

Answers

a

c

d

c

c

a

c

b

c

b

C HAPTER 5

Incident Management

Introduction

In today’s fast-paced digital environment, organizations rely heavily on their IT infrastructure to deliver seamless services to customers, and maintain internal operations. However, disruptions are inevitable, whether due to technical glitches, security breaches, system overloads, or unforeseen failures. When such disruptions occur, the ability to respond swiftly and efficiently can make the difference between minimal impact and significant operational downtime. This is where Incident Management plays a crucial role.

This chapter provides a foundational understanding of Incident Management, an essential practice within IT Service Management frameworks such as ITIL. We begin with a broad overview of what Incident Management entails, followed by a clear definition of incidents, and the more severe major incidents, exploring how they differ in scope, impact, and urgency. You will learn to identify the key characteristics of incidents, understand what qualifies as a major incident, and why their handling requires a distinct and escalated approach.

We also introduce the role of the Incident Manager, a central figure responsible for coordinating the resolution process, minimizing service disruption, and ensuring that appropriate communication flows between stakeholders.

A comprehensive breakdown of the Incident Lifecycle will illustrate the typical stages an incident goes through, from detection and logging to resolution and closure, highlighting how structured processes ensure efficiency and accountability. Furthermore, we will explore the concept of incident states such as " New ," " In Progress ," and " Resolved ," and how each state is governed by the specific Service Level Agreements (SLAs) that define response and resolution timeframes.

So, whether you are aspiring to work in a service desk, manage IT operations, or simply build a foundational knowledge in ITSM, this chapter sets the stage for mastering the principles and practices of effective Incident Management.

Structure

In this chapter, we will cover the following topics:

Incident Management: An Overview

Understanding Incidents: Characteristics, Scope, and Impact

Difference between an Incident and Service Request

Understanding Major Incidents: Characteristics, Scope, and Impact

Difference between Incidents and Major Incidents

Defining Priority in IT Service Management

Core Principles of Incident Management

The Role of the Incident Manager

The Incident Lifecycle: From Detection to Resolution

Incident States and SLAs

Incident Management: An Overview

Consider a scenario where a network outage impacts all users at the organization’s head office. With the network down, day-to-day operations are completely stalled, resulting in significant operational and financial losses. In such critical situations, swift action is imperative to resolve the issue at the earliest opportunity.

While it is evident that the Issue is network-related, the key questions that arise are:

Who will take the responsibility for engaging and informing the network team?

What happens if the network engineers are occupied with other high-priority tasks, and are unable or unwilling to address the issue immediately?

Delays in resolving incidents like these can have severe consequences, including operational downtime, financial losses, SLA (Service Level Agreement) penalties, and damage to the organization’s reputation.

Once the issue is resolved, proper documentation becomes equally important. The key details that should be recorded include:

The time of occurrence, and when the issue was reported to technical teams.

When a ticket was created in systems like ServiceNow.

The time taken to resolve the issue.

Teams involved in resolving the incident.

The actions, implementations, or changes made to rectify the issue.

Without a structured approach, managing such incidents can quickly become chaotic, especially if a dedicated person must be identified each time an issue arises. This is where the practice of Incident Management comes into play.

Understanding Incident

Before delving into the Incident Management process, it is essential to clearly define what constitutes an incident.

Incident

According to ITIL 4, an incident is an unplanned interruption to a service, or reduction in the quality of a service.

Example of an Incident: Coffee Machine Malfunction

Consider the scenario where a coffee machine suddenly stops functioning, disrupting coffee-making services. This unplanned interruption leads to an operational and financial loss for the business owner, as it directly affects service delivery to customers. Such an unplanned disruption is classified as an Incident .

Even if the coffee machine remains partially functional, any degradation in its performance is also considered an Incident . For example, if the heating function of the coffee machine malfunctions and the coffee is served semi-hot, the quality of service is compromised. From the customer’s perspective, they are paying the full price but receiving a substandard product in terms of temperature. This reduction in quality still qualifies as an Incident , as it impacts the expected service level.

Another example would be of Wi-Fi services at home. If the Internet is completely down, or there is reduction in the speed of the Internet, both qualify as Incident.

Difference Between Incident and Service Request

This is a very silly mistake, most of the users do across the IT organization. At this stage, we have already learnt about Service Request and Incident, their definitions, their characteristics, and so on. Now, we will talk about how we can distinguish between an Incident and a Service Request.

Impact : This is directly proportional to the Incidents. Higher the Impact, higher is the Incident Priority. If a user is saying something is not working for them causing an impact, then it should be an Incident.

Service Requests are always non-impacting.

Purpose : The Purpose of an Incident is to restore the normal service operation minimizing the Impact, whereas Service Request tends to provide a Service or fulfil a request.

Response Time : The time taken to acknowledge an Incident is higher than Service Higher as lesser the time, the lesser will be the Impact.

Example:

If a user is experiencing issues with their laptop keyboard that are affecting their ability to perform their work, they would raise an Incident, as it represents an unplanned disruption to a service. However, if IT technicians are unable to resolve the issue through troubleshooting, a Service Request may then be raised to facilitate the replacement of the keyboard. This transition reflects the shift from an attempt to restore service (Incident) to a standard, approved change, or fulfilment (Service Request).

Another common example is related to password resets. If a user wishes to reset their password, before it expires, this is considered a Service Request, as it is a standard, non-impacting action—the user can still access their account. However, if the password has already expired, and the user is unable to log in, this becomes an Incident, as it disrupts the user’s ability to access systems and perform work.

Key Characteristics of Incidents

Every incident possesses certain features that help IT teams quickly assess, prioritize, and manage the issue effectively. These characteristics include:

Urgency : How quickly the incident must be resolved to avoid serious consequences.

Impact : The extent to which the incident affects business operations, users, or customers.

Priority : A combination of impact and urgency that determines how resources are allocated.

Category and Subcategory : Classification of the incident into logical groupings to aid in accurate routing and reporting. This structure helps streamline triaging, assign to the correct support group, and enable meaningful analytics.

Category: Network Issue

Subcategory: VPN Connectivity, Wi-Fi Outage, Switch Failure

Category: Software Bug

Subcategory: Application Crash, Login Failure, Data Sync Issue

Category: Hardware Failure

Subcategory: Hard Drive Failure, Printer Malfunction, Monitor Issue

Affected Services or Users : The specific services, systems, or end-users impacted by the incident.

Scope of an Incident

The scope of an incident refers to the breadth of its impact across the organization, or its customers or users. The broader the scope, the higher the attention and resources required to resolve the incident. Additionally, incidents with wider scopes often demand better coordination, communication, and sometimes, public relations management.

It involves factors such as:

Number of users affected : Is it isolated to a single user, a team, a department, or the entire organization?

Number of systems or services involved : Is only one application affected, or is there a cascading impact on multiple integrated systems?

Geographical spread : Is the incident localized to a specific site, or is it affecting multiple offices, regions, or countries?

Impact of Incidents

The impact of an incident measures the degree to which it affects business operations, financial performance, regulatory compliance, or reputation. Impact is a key determinant in setting incident priority, and allocating the necessary response effort. Identifying the impact early in the incident lifecycle helps Incident Managers escalate the issue appropriately, involve necessary stakeholders, and initiate disaster recovery plans, if needed.

Different types of impacts include:

Operational Impact : Loss of productivity due to service unavailability (for example, employees unable to access a CRM system).

Financial Impact : Direct or indirect monetary losses (for instance, lost sales during an e-commerce site outage).

Customer Impact : Dissatisfaction or loss of customers due to poor service availability.

Compliance and Legal Impact : Violations of industry regulations or contractual Service-Level Agreements (SLAs).

Reputational Impact : Negative public perception, or damage to brand image resulting from prolonged or poorly handled incidents.

Examples of Incidents:

A single user reports being unable to access the application due to a login error.

Wi-Fi is temporarily down in a meeting room due to router misconfiguration.

Product images are not loading correctly for some users on the mobile version.

Major Incident

A Major Incident is a type of incident in IT Service Management that has a significant and widespread impact on business operations or poses a critical risk to the organization. It differs from regular incidents in terms of severity, urgency, and the level of response required. A Major Incident is a critical incident that has a significant impact on the organization, its customers, or key business processes.

Impact is severe, often causing major business disruption, revenue loss, or critical service downtime.

It requires an immediate and coordinated response with a special escalation process with dedicated resources, including a Major Incident Manager (MIM).

Example: A company-wide network outage, critical server failure, entire website down, or data breach affecting customers.

Key Characteristics of a Major Incident

High Impact : Affects critical business functions or services, often leading to operational disruptions.

Widespread Scope : Impacts multiple users, systems, or locations.

Urgency : Requires immediate attention to minimize damage.

Priority : Typically treated as the highest priority, overriding normal incident workflows.

Special Handling : Often requires a dedicated Major Incident Management Team (MIM) and predefined processes to address the issue.

Escalation : Involves senior management, key stakeholders, and potentially external vendors.

Public or Reputational Risk : May attract significant attention from external parties or the media.

Impact of a Major Incident

The impact of major incidents is typically widespread and critical, often affecting core business operations, customers, compliance, and even the organization’s reputation. Following are key areas where major incidents can have a significant impact:

Business Operations Disruption

Issue: Key services or applications become unavailable, halting workflows across departments.

Example: A CRM outage prevents sales teams from accessing customer data, delaying deals and client communication.

Impact: Loss of productivity, missed deadlines, and operational delays.

Financial Loss

Issue: Downtime leads to lost revenue, SLA penalties, overtime costs, or remediation expenses.

Example: An e-commerce outage during Black Friday results in hundreds of thousands in lost sales.

Impact: Direct financial loss and increased recovery costs.

Customer Experience and Satisfaction

Issue: Customers are unable to access services or experience degraded performance.

Example: A mobile banking app crash prevents users from making urgent transactions.

Impact: Customer frustration, churn, and damage to brand loyalty.

Legal and Compliance Risks

Issue: The incident causes a breach of regulations or contractual obligations.

Example: A data breach exposes Personally Identifiable Information (PII), violating GDPR or HIPAA.

Impact: Regulatory fines, legal action, mandatory disclosures, and audits.

Reputational Damage

Issue: News of the incident spreads internally or externally, affecting public trust.

Example: A social media storm erupts after a prolonged outage in a high-profile service.

Impact: Negative press, reduced customer confidence, investor concerns.

Figure 5.1: Impact of Major Incidents

Examples of Major Incidents

A critical application outage affecting thousands of users.

A cyberattack or security breach.

Data centre power failure.

Widespread network outage across multiple offices or regions.

Disruption to an e-commerce platform during peak sales hours.

Why Major Incident Management is Different

Major incidents necessitate:

Predefined Playbooks : Specific steps to be followed for handling high-impact events.

Rapid Decision-Making : Speed is critical, and decision-making may bypass usual hierarchies.

Enhanced Collaboration : Involves multiple teams and departments working together.

Post-Incident Reviews (PIRs) : To analyse root causes, learn lessons, and prevent recurrence.

By distinguishing between major incidents and regular incidents, organizations can ensure an appropriate level of urgency, and resources are applied to minimize business impact.

Differences Between Incidents and Major Incidents

Aspect

Incident

Major Incident

Impact

Limited to a specific user or group; localized.

Widespread, affecting critical services or many users.

Priority

Varies based on SLAs and impact.

Always the highest priority.

(P1/P2)

Response and Resolution Time

Managed based on SLAs; resolution might take longer.

Requires immediate response and resolution efforts.

Escalation

Handled within the normal support tiers.

Escalates to senior leadership and dedicated fulfilment teams.

Resources Required

Typically involves standard support teams.

May require cross-functional teams and external resources.

Communication

Standard updates to affected users.

Frequent, structured communication to stakeholders and Impacted users.

Management Process

Managed through standard incident management workflows.

Governed by a Major Incident Management process.

Visibility

Internal and limited to specific teams or users.

High visibility across the organization, sometimes external.

Documentation

Normal incident records.

Detailed Post-Incident Review (PIR) or root cause analysis.

Table 5.1: Differences between Incidents and Major Incidents

Priority

The priority assigned to an incident determines how quickly the incident is handled by the support staff and the ServiceNow tool. It is important to assign the correct priority to an incident to ensure SLAs, response times, and service restorations are met.

Priority Levels: Priority in IT Service Management refers to the order in which an incident, service request, or change should be addressed and resolved, based on its impact on the business, and the urgency with which it needs to be resolved.

P1 - Critical : A “ drop everything ” task that has a severe and immediate impact on core business operations.

P2 - High : An important task that has high impact, but not immediately urgent.

P3 - Medium : A task that is urgent, but less important.

P4 - Low : A task that is neither urgent nor highly important.

How to Calculate the Priority:

As per ITIL, an incident’s priority is determined by its impact and urgency:

Impact : The potential damage to the business such as financial, brand, or security damage, before the incident is resolved.

Impact is calculated by the number of users that are affected by the Issue.

Impact 1: All users are Impacted.

Impact 2: Some users are Impacted.

Impact 3: Single user is Impacted.

Urgency : How quickly the incident needs to be resolved.

Urgency is calculated by how soon the issue must be fixed.

Urgency 1: If Services/Applications/Component is completely down (Interruption in the service).

Urgency 2: If Services/Applications/Component is partially down (Reduction in the Quality of Service).

Urgency 3: If Services/Applications/Component is showing errors, but not impacting businesses or end users.

Priority Matrix in ServiceNow

The Priority Matrix is a decision tool in ServiceNow that determines the priority level of an incident or request, based on two input values: Impact and Urgency.

In ServiceNow, assigning a priority to an incident is not a manual or arbitrary action; it must adhere to the structured approach defined by ITIL best practices. The system is intentionally configured to automatically determine the priority, based on two key parameters: Impact and Urgency. This ensures a standardized and objective method for incident classification, promoting fairness and consistency across the organization.

For example, if a user reports that “ a business-critical application is down ,” it may seem urgent, but the priority cannot be set directly to P1, without proper evaluation. Instead, the service desk must gather the detailed information such as:

Impact : Is this issue affecting all users, a specific department, or just a single user?

Urgency : Is the service completely unavailable, or is it partially functioning with workarounds?

Only after both these factors are assessed can ServiceNow calculate and assign the correct priority level, using the predefined Priority Matrix . This Matrix is built on the formula, Priority = Impact X Urgency.

This process prevents over-prioritization of issues, and ensures that truly critical incidents—such as a company-wide outage or a major cybersecurity breach—are appropriately escalated and resolved with the highest urgency.

Figure 5.2: Priority Matrix in ServiceNow

P1 (Critical) = Impact 1 * Urgency 1.

Consider an example where ALL THE USERS (Impact 1) are reporting, and the Internet is COMPLETELY DOWN (Urgency1), as per ITIL definition, this would qualify as P1.

P2 (High) = Impact 1 * Urgency 2.

Consider an example where ALL THE USERS (Impact 1) are reporting INTERMITTENT ISSUES with the Internet (Urgency 2), as per ITIL definition, this would qualify as P2.

P2 (High) = Impact 2 * Urgency 1.

Consider an example where SOME USERS (Impact 2) are reporting, the Internet is COMPLETELY DOWN (Urgency 1), as per ITIL definition, this would qualify as P2.

P3 (Moderate) = Impact 3 * Urgency 1.

Consider an example where a SINGLE USER (Impact 3) is reporting, the Internet is COMPLETELY DOWN (Urgency 1), as per ITIL definition, this would qualify as P3.

Benefits of the Priority Matrix

Consistency in ticket triage and response.

Automation of SLA triggers and escalations.

Improved visibility into critical issues.

Optimized resource allocation to fix high-impact problems, first.

Understanding Incident Management

Now that we have a clear understanding of Incidents and their associated priorities, let us delve into the concept of Incident Management .

Defining Incident Management

In its simplest form, Incident Management refers to a structure for managing incidents. This involves accurately prioritizing incidents, assigning them to the appropriate teams, escalating when necessary, and meticulously documenting timelines and actions taken.

According to ITIL 4, Incident Management is defined as the practice of restoring normal service operations as quickly as possible to minimize the negative impact of an unplanned disruption or reduction in service quality.

Role of the Incident Management Team

When an incident is reported in an organization that may cause significant operational or financial impact, the Incident Management Team is engaged to mitigate the issue swiftly. This can involve:

Implementing a temporary workaround to restore service quickly.

Facilitating a permanent solution through technical teams.

It is important to note that the Incident Management Team is not typically a technical team responsible for directly resolving the issue. Instead, their roles include:

Delegation: Assigning incidents to the appropriate technical teams.

Escalation: Ensuring higher-level intervention, if required to expedite resolution.

Documentation: Recording all the relevant details, including timelines, actions taken, and teams involved.

Prioritization: A Key Responsibility

One of the primary responsibilities of the Incident Management Team is to accurately determine the priority of incidents. This ensures that technical teams are engaged promptly and proportionately, aligning resource allocation with the impact and urgency of the issue.

By following a structured approach, Incident Management helps organizations reduce downtime, improve service reliability, and enhance overall operational efficiency.

Categorization: A Foundational Step

Accurate categorization is a crucial responsibility of the Incident Management Team. It involves classifying incidents, based on predefined categories and subcategories (for example, hardware, software, and network). This enables effective routing, streamlined triage, and meaningful reporting as well as trend analysis.

By ensuring incidents are consistently categorized, organizations can accelerate resolution, identify recurring issues, and support continuous service improvement.

Goals of Incident Management

Minimize Service Disruptions : Reduce the impact of incidents on business operations.

Restore Service Promptly : Quickly restore normal service levels to meet the Service Level Agreements (SLAs).

Enhance User Satisfaction : Provide a reliable and efficient response to disruptions to build trust with users.

Prevent Future Incidents : Identify trends and recurring issues to prevent future disruptions.

Ensure Accurate Communication : Provide stakeholders with the timely updates during incidents.

Benefits of Incident Management

Improved Operational Efficiency : Structured workflows and escalation procedures lead to faster resolution.

Enhanced Customer Satisfaction : Faster and consistent resolution of issues foster confidence and trust.

Reduced Downtime Costs : Minimizing service downtime reduces financial losses and productivity impacts.

Better Resource Utilization : Ensures that IT resources are focused on high-priority issues.

Increased Visibility : Provides detailed insights into the frequency, causes, and impacts of incidents.

Compliance with SLAs : Helps organizations meet service-level commitments.

Objectives of Incident Management

Timely Resolution : Ensure incidents are identified, logged, and resolved within defined timelines.

Categorization and Prioritization : Classify incidents based on urgency and impact to allocate resources effectively.

Documentation : Maintain detailed records of incidents for analysis, reporting, and future reference.

Efficient Communication : Keep users and stakeholders informed throughout the incident lifecycle.

Continuous Improvement : Use insights from incident data to enhance processes, and prevent recurrences.

Incident Managers

An Incident Manager plays a critical role in IT Service Management by overseeing the end-to-end handling of high-priority incidents to ensure timely resolution. Incident Managers follow the Incident Management Practice, and make sure that Services are getting restored as soon as possible to have a minimal impact on the organization.

Incident Managers as the central point of contact for updating the key stakeholders, like IT leadership team, Senior management and other relevant parties coordinate communication, resources, and resolution efforts across multiple support teams. They usually work in a 24X7 environment with at least one Incident Manager available at any given time.

Primary Responsibilities

Incident Oversight : Monitor the lifecycle of all incidents, ensuring that they are promptly acknowledged, escalated, and resolved within agreed service levels.

Coordination and Communication : Lead high priority and major incident bridge calls. A bridge call enabling faster decision-making, brings together key support teams, vendors, and stakeholders to coordinate efforts, share updates, and drive quick resolution.

Stakeholder Updates : Ensure regular and clear communication with the key stakeholders, providing status updates, action plans, and expected resolution timelines.

Root Cause Documentation : Oversee documentation of the root cause, workaround, and a permanent fix for recurring or major incidents.

Process Compliance : Ensure that all incident management processes and SLAs are adhered to, and drive continual improvement, based on post-incident reviews.

Escalation Handling : Act as the escalation point for unresolved or reopened incidents ensuring appropriate attention, and resources are allocated.

Incident Lifecycle

A Process refers to a set of steps or activities that are designed to achieve a specific outcome. When an Incident is reported, Organizations will always have a planned process in place to respond and resolve the Incident. This process is well defined, and is known as Incident Management Process.

A distinguished quality of a Process is that it tends to finish, once the outcome is achieved. Example, the outcome of Incident management process is to quickly resolve the issue to minimize the impact. Once the Incident is resolved, and the Outcome is achieved, a Process is over, till a new incident is reported.

In ITIL 4, the concept of Incident Management is no longer defined strictly as a " process " but as a Practice. A Practice in ITIL 4 is a set of organizational resources, including people, processes, tools, and information that are designed to perform a specific function or deliver value. Therefore, while the Incident Management practice includes a series of structured steps (which resemble a process), it also encompasses supporting capabilities such as skills, governance, technology, and cultural alignment.

So, while in earlier ITIL versions, Incident Management was seen primarily as a process that begins with the logging of an incident and ends with its resolution and closure, ITIL 4 emphasizes that Incident Management as a practice, is broader. It is about ensuring that incidents are managed in a way that minimizes the negative impact on the business, and maintains agreed service levels.

For example, when an incident is reported, say, a user cannot access the email system, it is not just about following a linear set of steps to resolve it. The Incident Management practice ensures that:

The right people with the right skills are engaged.

The tools like ServiceNow are used to record, track, and communicate effectively.

SLAs are enforced and monitored.

Continuous improvement is encouraged (post-incident reviews, trend analysis, and so on.).

In this context, while the incident lifecycle (from logging to closure) remains a part of the practice, ITIL 4 encourages viewing Incident Management as an ongoing capability that contributes to delivering consistent value through effective service restoration.

Figure 5.3: Incident Lifecycle

Let us understand the Incident Lifecycle Process.

The Incident Lifecycle refers to the sequence of states that an incident goes through, from the moment it is reported until it is closed. The goal of this lifecycle is to restore normal service operations as quickly as possible, while minimizing the negative impact on the business. The following are the key stages of the Incident Lifecycle:

Incident Identification: The first and most crucial step is to identify whether the reported issue is an Incident, Service Request, Feedback or a Complaint. If it does not qualify as an incident, the process will be stopped here, and users will be notified to create a Service Request.

Example : A new joiner wants to order a new Headset. As this would be a first-time requirement, a Service Request ticket needs to be raised. The Incident Lifecycle would not get Initiated as No Incident was created.

Incident Logging: Consider an example, where few users are facing Internet issues at the office, and this needs to get fixed ASAP. The Process of creating an Incident in ServiceNow is known as Incident Logging. In ServiceNow, incidents can be logged through multiple channels, depending on how users prefer to report issues, or how the organization has configured its IT service desk.

Self-Service Portal (ServiceNow Portal): Users can log incidents directly through the self-service portal.

Best For : End-users who are not technically inclined, or need quick access to report common IT issues.

Service Desk (Phone or Email): Service desk agents can log incidents on behalf of users who report issues via phone or email.

Best For : Complex or high-priority incidents where users need immediate help, or cannot access the portal.

Email to Inbound Actions: Some ServiceNow instances are configured to convert the incoming emails into incidents automatically. For example, an email sent to servicedesk@yourcompany.com can trigger a new incident.

Best For : Users or systems not able to access the portal, but need a way to log incidents quickly.

Virtual Agent (Chatbot): The ServiceNow Virtual Agent allows users to log incidents, using a chatbot interface.

Best For : Streamlining frequent or simple requests (for example, password resets, access issues).

Incident Categorization: This is the process of arranging incidents into classes or categories. The main objective is to understand what type of incident has occurred. Over time, if incidents are categorized similarly, the data is then used to identify trends, and focus efforts on improving proactively.

Incidents can be categorized by type, such as software, hardware, equipment, facilities, and network. They are further sub-categorized, according to their categories. Router, switch, and firewall can be added into the Network Category. Keyboards, laptops, and printers can also be added in hardware category, and so on.

Figure 5.4: Incident Categorization.png

Incident Prioritization: Once Incidents are Categories, they need to have a priority so that a timeline needs to be set for resolving them. The higher the priority, the less the time to fix them. We have already learnt how to prioritize the Incidents, according to the Impact and the Urgency.

Figure 5.5: Incident Prioritization.png

Incident Response: Once appropriate Category and Priority is assigned to an Incident, it is submitted in the ServiceNow portal, and an Incident Ticket is generated.

The response time is the maximum time to acknowledge the newly created ticket. This is handled by the Service Desk team. Response time is less, when Priority is high. The following is the response table:

Priority

Standard Response Time SLA

1 - Critical

15 mins

2 - High

30 mins

3 - Medium

4 hours

4 - Low

8 hours

Table 5.2: The Response Table

Consider a real-life example where you have ordered food online. It will take a couple of minutes for the Restaurant to accept your order, and confirm that they are preparing the dish. In the same way, when an Incident is created, it needs to be acknowledged by the Service Desk team that they are looking into it.

Incident Diagnosis and Investigation: Once the Incident is acknowledged by the Service Desk team, they will start the Initial Investigation Process. In some Organizations, Service Desk can also perform L1 level tasks which helps in resolving the Issue. The diagnosis part is digging a little deeper into the Issue to determine the probable cause, same as if you had been to a doctor for a headache, and he would ask you several questions to find out the cause for the headache.

Incident Escalation: Incident escalation is the process of raising the priority or responsibility level of an incident, when it cannot be resolved within a defined time frame or service level, or when additional expertise or authority is required to restore service.

Escalation ensures that critical incidents receive appropriate attention, are resolved quickly, and are handled by the right people with the right level of authority or technical skills.

There are two types of Escalations:

Functional Escalation: Also known as technical escalation, this type of escalation occurs, when a technician needs help with an Incident that is outside of their scope. The issue may be passed to a team or individual with more relevant expertise.

Example : L1 to L2, L3 and so on. A service desk agent cannot resolve a server crash, so the ticket is escalated to the infrastructure team.

Hierarchical Escalation: This type of escalation involves passing an incident to a team or person, based on their seniority or experience level within the organization. This involves notifying or involving higher management or decision-makers due to: Breach of SLA or High Business Impact.

Example : A P1 outage affecting online sales for hours is escalated to senior IT leadership, or even business executives for visibility and decision-making.

It is important to note that not every incident requires escalation. In fact, the majority of incidents are resolved by the teams to which they are initially assigned, without the need for further escalation.

Incident Resolution : Once the Issue is resolved by the technical teams, the incident is deemed to be resolved. The technical teams need to update what steps were taken to fix the issue.

The resolved state of incidents can always be re-opened, if the issue reoccurs. An Incident can remain in a particular state, until a timeline is set by an organization. Once that timeline is crossed, the incident will automatically move into the closed state. The timeline differs from organization to organization, and it can range from 1 to 2 weeks.

Incident Closure: Once the Incident is closed, we cannot reopen the incident. This is the last step in the Incident Management Process where the process will end as the Incident cannot be reopened.

Figure 5.6: Reclassification of an Incident as a Service Request (During Categorization).jpg
https://www.acte.in/what-is-itil-incident-management-and-its-importance-article

Reclassification of an Incident as a Service Request (During Categorization)

Users may sometimes be unsure whether to raise an incident or a service request, especially when reporting an issue, or requesting something new. This confusion is common, and can be clarified during the categorization step of the incident lifecycle, where the service desk reviews the details, and ensures that the ticket is correctly classified, according to ITIL guidelines.

During the Categorization step of the Incident Lifecycle, the service desk reviews the information provided, when an issue is first reported. The purpose of this step is to accurately determine the type of issue, whether it is truly an incident (unplanned disruption or reduction in service quality) or a service request (a planned, standard request for service or information).

Sometimes, a user might log something as an incident, but upon review, it is found to be a routine or predefined request that should be handled as a service request, instead.

Incident States and SLA

The Incident Management process has many states, and each is vitally important to the success of the process, and the quality of service delivered. The different states can be represented in a diagram as follows:

Figure 5.7: Incident States in ServiceNow

An incident in ServiceNow moves through a series of defined states as it progresses through its lifecycle. Each state represents a specific stage in handling and resolution, and the SLAs are often triggered, paused, or stopped, based on these states.

SLAs

Response SLA : It refers to the maximum allowable time to acknowledge or start working on an incident, after it has been reported.

Meeting the response SLA ensures that incidents are promptly attended or acknowledged.

Resolution SLA : This refers to the maximum allowable time to resolve an incident.

Meeting the resolution SLA ensures that incidents are resolved within an acceptable timeframe, minimizing impact on business operations.

Incident States

Incidents go through various states, from the time they are reported, until they are resolved and closed.

New

In Progress

On Hold

Resolved

Closed

Cancelled

Each state represents a specific phase in the incident lifecycle, and helps in tracking the progress and actions required. By adhering to these states, teams can ensure a structured approach to incident management, leading to better communication, faster resolution, and improved user satisfaction. The ServiceNow platform supports this lifecycle through a series of predefined states and associated SLAs, specifically known as Task SLAs.

Understanding Task SLA in ServiceNow

ServiceNow tracks SLA compliance, using a special record type called Task SLA. Each SLA associated with an incident (such as Response or Resolution) has its own record.

Key SLAs

Response SLA: Time to acknowledge the incident.

Resolution SLA : Time to fully resolve the issue.

Priority

Response SLA

Resolution SLA

P1

15 minutes

4 hours

P2

30 minutes

8 hours

P3

4 hours

24 hours

P4

8 hours

2 days

Table 5.3: Task SLA ServiceNow

P.S: The above-mentioned SLA timelines are just for the reference purpose. The SLAs differ from organization to organization.

In ServiceNow, Task SLAs are used to measure the performance of a task (such as an incident) against defined timelines. Each Task SLA has a Stage field that represents its current status within the SLA lifecycle. These stages help track SLA compliance, and take appropriate action, if service targets are at risk.

Stage

Meaning

In Progress

The SLA timer is actively counting down. This is the default state when the task is ongoing, and has not met any pause or completion conditions.

Paused

The SLA timer is temporarily halted. This typically occurs when a task enters a state that matches a defined " pause condition ." For example, when an incident is placed " On Hold ," the SLA timer resumes, once the task exits the paused condition, or an Incident has been resolved.

Completed

The SLA objective was achieved successfully before breaching the deadline. This typically occurs, when the incident is closed within the allowed time.

Breached

The SLA goal was not met in time. The task exceeded its defined duration (for example, resolution within 8 hours), triggering this status. This may require follow-up or review.

Cancelled

The SLA was manually or automatically cancelled, often due to changes in task categorization or workflow logic (example, reassigned to a different SLA policy). For instance, if an incident was initially classified as “P1” and later reassessed as a “P3”, the original SLA would be automatically cancelled.

Table 5.4: Task SLA Stages

Example: Let us consider an example of a Response SLA with a 30-minute target:

Incident Created.

SLA starts tracking → Stage: In Progress

Incident Placed On Hold Due to User Response Delay.

SLA timer pauses → Stage: Paused

User Provides Input, Work Resumes.

SLA resumes → Stage: In Progress

Incident Resolved in 25 minutes.

SLA goal met → Stage: Paused (Resolved incidents can be reopened)

If Resolution Took 35 minutes.

SLA missed → Stage: Breached

Incident States

New

Description : When an incident is first reported, it enters the " New " state. This state indicates that the incident has been logged, but not yet reviewed or assigned.

SLA Behavior : The countdown for the response SLA begins ( In Progress ) as soon as the incident is logged into the ServiceNow tool.

Actions: Acknowledge the Incident. This task is usually performed by the ServiceDesk team as all the new incidents are first routed to the Service desk team. They will also perform an initial assessment.

In Progress

Description : The incident moves to the " In Progress " state, when work commenced to investigate and resolve the issue.

SLA Behavior : The resolution SLA continues ( In Progress ), until the incident is placed ON HOLD / RESOLVED or CLOSED .

Actions : The Engineer who has assigned the incident to himself/herself will perform a detailed analysis and troubleshooting. Implement necessary corrective actions, and update incident notes with progress and findings.

On-Hold

Description : If the incident cannot be resolved immediately due to pending actions, dependencies, or external factors, it may be placed " On-Hold ."

SLA Behavior : The resolution SLA countdown pauses, when an incident is placed on hold, and resumes once it is taken off hold.

In general, Organizations have four types of On-hold conditions for an Incident in ServiceNow.

On Hold - Awaiting Caller : An incident should be placed in the " Awaiting Caller " status under the following conditions:

Additional Information Required: The user has not shared enough information to start troubleshooting, or to fix it.

User Confirmation Needed: The issue has been fixed, but we are waiting for confirmation from the user.

Scheduling and Coordination: If the user is unavailable for troubleshooting, and he has requested to schedule a meeting later.

On Hold - Awaiting Problem: An incident should be placed in the " Awaiting Problem " status under the following conditions:

Root Cause Analysis required.

Permanent Solution for a workaround required.

On Hold - Awaiting Change: An incident should be placed in the " Awaiting Change " status under the following conditions:

A change (Normal, Emergency, and Standard) to the IT infrastructure, application, or service is necessary to resolve the incident.

On Hold - Awaiting Vendor: An incident should be placed in the " Awaiting Vendor " status under the following conditions:

Vendor Engagement Required.

Parts or Services are awaited from the Vendor.

Resolved

Description : Once the corrective actions have been implemented, the incident is considered fixed by the technical teams. Post user confirmation, the incident state will be changed to " Resolved ." Resolved state incidents can be REOPENED in 5–10 working days, if the issue reoccurs. The reopening time varies from organization to organization.

SLA Behavior : The Resolution SLA will be paused, until the Incident is moved to the Closed state.

Actions : The Engineer will verify that the issue has been fixed, and he will update the incident with resolution details.

Closed

Description : The final state, " Closed ," indicates the incident is formally closed in the tracking system, indicating the end of the incident management lifecycle for this specific issue. If no one reopens the Incident in 7 working days, the Service Now tool will automatically move the RESOLVED state incident to CLOSED . Closed state Incidents cannot be reopened.

P.S : The 7 working days is a standard timeline as per ServiceNow. Organizations can make changes, according to their internal policies.

SLA Behavior : The Resolution SLA will be MET / COMPLETED , once the Incident is in Closed state.

Actions : if no root cause is determined, a Problem ticket will be opened to conduct a post-incident review, if necessary. Incident Managers will prepare a Post Incident report to Document any lessons learned or follow-up actions.

Cancelled

Description : The Cancelled state is used, when an incident is no longer valid, and will not be pursued further. This may happen if the incident was created in error, is a duplicate of another record, or the reported issue has been resolved outside of formal support processes.

SLA Behavior : All associated SLAs are stopped and marked as Cancelled . The task is no longer tracked for SLA compliance.

Actions : The engineer confirms that the incident is indeed invalid or no longer necessary, and provides an apparent reason for cancellation in the incident notes.

Conclusion

This chapter provided a comprehensive overview of Incident Management within the ServiceNow platform, a core practice in IT Service Management (ITSM). Through an in-depth look at the Incident Lifecycle, we learned how incidents progress through structured states—from detection to closure—ensuring transparency, accountability, and streamlined resolution processes.

We examined how Response and Resolution SLAs play a vital role in defining expectations for incident handling times, and how these are monitored through Task SLA Stages like In Progress, Paused, Completed, Breached, and Cancelled. This lifecycle-based approach empowers support teams to work efficiently, while keeping service levels aligned with organizational objectives.

By mastering these elements, IT professionals can ensure high levels of service availability and user satisfaction, while also laying the groundwork for more proactive IT operations.

In the next chapters, we will discuss the Problem Management. While Incident Management is focused on restoring service as quickly as possible, Problem Management takes a longer-term view. It aims to identify the root causes behind incidents, and eliminate them to prevent future recurrences.

Key Takeaways

Understanding what constitutes an Incident versus a Service Request.

Differentiating between Incidents and Major Incidents, and why that distinction matters.

The critical function of Incident Prioritization in managing workload and impact.

Roles and responsibilities of Incident Managers, and the skills needed to succeed in that position.

A walkthrough of incident states, and how Task SLAs help maintain service quality.

Multiple Choice Questions

What is the primary goal of Incident Management?

To perform Root Cause Analysis of recurring issues

To restore normal service operation as quickly as possible

To manage hardware procurement

To create change records

Which of the following best describes an " Incident "?

A planned request for a new laptop.

A scheduled software upgrade.

An unplanned interruption or reduction in the quality of an IT service.

A recurring issue tracked in Problem Management.

How does a Service Request differ from an Incident ?

Service Requests are only handled by vendors.

Service Requests are unplanned outages.

Service Requests require a Major Incident review.

Service Requests are pre-approved requests for standard services.

What makes an incident a " Major Incident "?

It impacts multiple users or business-critical services.

It can be resolved within the SLA.

It only affects a single user.

It requires password reset.

What is the purpose of assigning a " Priority " to an incident?

To identify the team that logged the ticket

To track the hardware being used

To determine the order and speed of response and resolution

To categorize the assets involved

Which two parameters determine the Priority of an Incident in ITIL-based systems like ServiceNow?

Impact and Status

Urgency and Category

Impact and Urgency

Category and Configuration

What is the role of a Major Incident Manager during a Major Incident?

Approving new hardware requests.

Investigating and resolving security vulnerabilities.

Scheduling team shifts.

Coordinating response teams, and ensuring timely resolution.

What is the first state of an Incident in ServiceNow, once it is logged?

Assigned

In Progress

New

On Hold

What does an SLA (Service Level Agreement) define in Incident Management?

User training schedules

Timeframes for response and resolution

Configuration management guidelines

Asset depreciation rates

In which scenario would an incident move to the " On Hold " state?

When it is resolved and closed.

When assigned to a resolver group.

When created by a user via email.

When waiting for user input, or external dependency.

Answers

b

c

d

a

c

c

d

c

b

d

C HAPTER 6

Problem Management

Introduction

In ITIL, distinguishing between Incident Management and Problem Management is critical, particularly when addressing recurring issues. Consider a scenario where a specific issue reoccurs consistently over a period of time. While incidents related to this issue may be temporarily resolved, their recurrence signals the need for a different approach. Incident Management focuses on restoring service as quickly as possible; once an incident is resolved, the Incident Management team’s involvement typically concludes.

However, resolving incidents without addressing their underlying cause often leads to recurring disruptions, impacting service quality, and customer satisfaction. This highlights the importance of Problem Management, which takes a proactive and analytical approach to identifying and eliminating the root causes of incidents, rather than merely treating their symptoms. Effective Problem Management not only reduces the number and impact of incidents, but also improves the overall resilience and stability of IT services.

For example, imagine that the electricity in your home consistently fails at 10:00 AM each day, and returns after an hour. This pattern has persisted for the past three days. Although an electrician can restore power each time, the repetitive nature of the outage indicates the need for a deeper investigation to identify and resolve the underlying cause. This is where Problem Management becomes essential.

According to ITIL 4, a problem is defined as the underlying cause or potential cause of one or more incidents. In simple terms, a series of recurring incidents where cause in unknown is classified as a problem. The primary objective of Problem Management is to determine the root cause of these incidents, and implement a permanent solution to prevent recurrence. Additionally, Problem Management may also involve proactive measures such as identifying and addressing potential issues, before they result in incidents.

In the preceding example, the daily power outage at 10:00 AM would be escalated from a set of incidents to a recognized problem due to its repetitive nature. A problem record would be created to initiate a thorough investigation into the root cause. Once identified, corrective actions would be implemented to eliminate the issue, thereby enhancing the overall stability and reliability of the service.

Structure

In this chapter, the following topics will be covered:

Understanding Problem Management Concepts

Problem Management: Roles, Benefits, and Performance Metrics

Key Stages in Problem Management

Problem Management in ServiceNow

Problem Ticket Lifecycle in ServiceNow

Problem Techniques

Understanding Problem Management

Problem Management is a systematic and proactive process aimed at identifying, analysing, and resolving the root causes of incidents within an organization. It is a crucial component of IT Service Management that ensures the stability and reliability of IT services. Unlike Incident Management, which focuses on restoring services as quickly as possible after an outage or disruption, Problem Management delves deeper to uncover the underlying issues that cause incidents in the first place. By addressing these root causes, organizations can prevent the recurrence of incidents, reduce downtime, and improve overall service quality.

The primary goal of Problem Management is to minimize the adverse impact of incidents on business operations. This is achieved by not only resolving the existing problems, but also by identifying the potential issues, before they escalate into incidents. In doing so, Problem Management contributes to the long-term improvement of IT services and infrastructure, ensuring that businesses can operate smoothly and efficiently.

In simple terms:

Incident Management fixes the immediate issue.

Problem Management fixes the real reason why the issue happened.

ITIL 4 defines a problem as the cause or potential cause of one or more incidents.

Example:

Incident: Users cannot log into the email system.

Problem: The authentication server is overloaded every morning at peak login times.

Problem Management would investigate why the server is overloaded, and find a solution such as upgrading the server or balancing the load.

While both Incident Management and Problem Management are essential components of ITSM, they serve different purposes and focus on different aspects of service management.

Incident Management is primarily concerned with restoring normal service operations as quickly as possible following an incident. The focus is on minimizing downtime and ensuring that business operations can continue with minimal disruption. Incident Management is reactive in nature, responding to issues as they arise.

Problem Management, on the other hand, is proactive and preventive. It seeks to identify and resolve the root causes of incidents to prevent them from recurring. Problem Management addresses the underlying cause.

Aspect

Incident Management

Problem Management

Goal

Restore normal service quickly

Find and eliminate the root cause

Focus

Symptom

Underlying cause

Action

Quick fix (temporary workaround or resolution)

Permanent solution

Example

Restarting a crashed server

Investigating why the server crashes regularly

Table 6.1: Differences between Incident and Problem Management

For instance, if a server crashes and causes an outage, Incident Management would focus on getting the server back online as quickly as possible. Problem Management would investigate why the server crashed in the first place. It might find that the server was running outdated software that was incompatible with the recent updates. By updating the software, Problem Management can prevent future crashes, thereby reducing the number of incidents that Incident Management needs to handle.

Core Concepts of Problem Management

Problem Management

Definition: The process responsible for identifying, analysing, and eliminating problems as well as their root causes to prevent future incidents.

Two modes:

Reactive Problem Management (post-incident).

Proactive Problem Management (pre-incident).

Problem Record: A record containing details of a problem, its analysis, and resolution progress. The Problem Record serves as the central hub, documenting all details such as root cause, priority, and workarounds, to ensure accountability and traceability throughout the problem lifecycle.

Problem Tasks: The problem tasks break down the root cause analysis into actionable sub-tasks, enabling parallel work across teams (for example, investigation and vendor coordination) while maintaining clear audit trails and SLA adherence.

Known Error: A problem that has been analysed but not yet resolved, with a documented root cause and workaround.

Recorded in the Known Error Database (KEDB) .

Helps speed up incident resolution via pre-defined workarounds.

Example : A software bug causing login failures (workaround: Clear browser cache).

Known Error Database (KEDB): A repository of known errors, workarounds, and their statuses. This is used by technical teams for faster resolution.

Error Control: The sub-process of Problem Management that manages the known errors, until a permanent fix is deployed.

Workaround: A temporary solution to reduce the impact of an incident, until a permanent fix is implemented.

Does not resolve the root cause.

Critical for minimizing downtime, while a problem is being resolved.

Example : Restarting a service to restore functionality, while engineers investigate.

Root Cause Analysis (RCA): A structured method to identify the underlying cause of a problem.

Common techniques: 5 Whys, Fishbone Diagram (Ishikawa), Fault Tree Analysis.

Focuses on preventing recurrence, rather than just fixing symptoms.

Example : Why did the server crash? → Overloaded CPU → Why? → Inefficient code

Permanent Fix (Solution): A change that eliminates the root cause of a problem.

Implemented via Change Management to avoid risks.

Requires testing before deployment.

Example : Patching a security vulnerability causing system crashes.

The Role of Problem Management in Minimizing Business Impact

Incidents, whether they are system outages, software bugs, or hardware failures, can have a significant impact on business operations. They can lead to lost productivity, dissatisfied customers, and financial losses. Problem Management plays a crucial role in mitigating these impacts by addressing the root causes of incidents. By doing so, it reduces the frequency and severity of incidents, leading to more stable and reliable IT services.

Proactive Incident Prevention

Investigates the underlying causes of incidents, rather than just treating symptoms.

Implements permanent fixes (workarounds or permanent solutions) to prevent recurrence.

Reduces the frequency and severity of service disruptions.

Minimizing Downtime and Service Disruptions

Reduces the Mean Time to Repair (MTTR) by leveraging known errors and workarounds.

Ensures faster resolution when similar incidents occur.

Enhances the overall service availability and performance.

Improving Operational Efficiency

Eliminates repetitive firefighting by addressing the root causes.

Frees up IT resources to focus on strategic initiatives, rather than reactive incident handling.

Reduces operational costs associated with recurring incidents.

Enhancing Customer and User Experience

Fewer disruptions lead to higher user satisfaction and trust in IT services.

Maintains business continuity by preventing major outages.

Supports compliance with SLAs.

Knowledge Management and Continuous Improvement

Documents known errors, workarounds, and resolutions in a Knowledge Base.

Facilitates better decision-making for future incidents.

Enables continuous service improvement through trend analysis.

Risk Mitigation and Compliance

Identifies vulnerabilities, before they escalate into major incidents.

Supports regulatory compliance by maintaining stable and secure IT services.

Reduces the likelihood of security breaches stemming from unresolved problems.

For example, consider a scenario where a company experiences frequent network outages. Incident Management would focus on restoring the network as quickly as possible, each time an outage occurs. However, Problem Management would investigate why the outages are happening in the first place. It might discover that the outages are caused by an outdated network infrastructure that cannot handle the current volume of traffic. By upgrading the infrastructure, Problem Management can prevent future outages, thereby minimizing the impact on business operations.

Types of Problem Management

Problem Management in IT Service Management operates in two key modes: Reactive and Proactive. Both approaches aim to minimize business impact but differ in timing, methodology, and strategic value.

Reactive Problem Management

Definition: Reactive Problem Management focuses on identifying and resolving the root causes of problems after they have already resulted in one or more incidents. It is triggered by incidents that disrupt services, and aims to prevent recurrence.

Key Characteristics:

Incident-Driven: Initiated in response to reported issues.

Corrective Action: Focuses on diagnosing and fixing problems that have already caused disruptions.

Short-Term Resolution: Often involves temporary workarounds, before a permanent fix is implemented.

Post-Incident Analysis: Uses incident data to investigate the underlying causes.

Process Flow:

Incident Occurs → Incident Resolution → Problem Identification → Root Cause Analysis (RCA) → Solution Implementation .

Example Scenario:

Incident: Employees report frequent VPN disconnections.

Reactive Response:

Temporary Fix : Restarting the VPN server.

Investigation : Logs reveal an outdated firmware bug.

Permanent Fix : Upgrading the firmware to prevent future disconnections.

Advantages:

Resolves known issues efficiently.

Reduces recurrence of incidents.

Improves future incident response through documented solutions.

Limitations:

Business Impact First: Issues must cause disruptions, before being addressed.

Firefighting Mode: Can lead to repetitive fixes, without long-term prevention.

Proactive Problem Management

Definition: Proactive Problem Management seeks to identify and eliminate the potential problems before they cause incidents. It relies on trend analysis, monitoring, and risk assessments to prevent future disruptions.

Key Characteristics:

Preventive Approach: Aims to stop incidents before they affect services.

Data-Driven: Uses logs, performance metrics, and incident trends.

Continuous Improvement: Part of the ongoing IT service optimization.

Risk Mitigation: Addresses vulnerabilities before they become critical, reducing the impact of business disruptions, and preventing Operational, Financial, as well as Reputational losses to the organization.

Process Flow:

Trend Analysis → Risk Identification → Preventive Action → Monitoring and Validation .

Example Scenario:

Observation: IT team notices database response times are slowing every Friday.

Proactive Response:

Analysis : Identifies an unoptimized weekly backup process.

Solution : Adjusts backup schedule, and optimizes queries before performance degrades further.

Advantages:

Prevents Outages: Reduces the unexpected downtime.

Cost-Effective: Fixing issues early is cheaper than post-incident recovery.

Enhances Reliability: Improves the overall IT service stability.

Limitations:

Resource-Intensive: Requires monitoring tools and skilled analysts.

False Positives: Not all detected risks may lead to actual incidents.

Aspect

Reactive Problem Management

Proactive Problem Management

Trigger

After incidents occur.

Before incidents happen.

Focus

Fixing known problems.

Preventing potential problems.

Approach

Corrective.

Preventive.

Data Used

Incident reports.

Logs, trends, risk analysis.

Business Impact

Reduces recurrence.

Minimizes future disruptions.

Cost Efficiency

Higher recovery costs.

Lower long-term costs.

Table 6.2: Key Differences between Reactive and Proactive Problem Management

Problem Management: Roles, Benefits, and Performance Metrics

Successful Problem Management requires collaboration across various roles, each contributing unique expertise to ensure that problems are identified, diagnosed, and permanently resolved. Clearly defining these roles helps streamline the process, avoid confusion, and promote accountability.

Roles

Process Owner: The Problem Management Process Owner’s primary objective is to own and maintain the Problem Management process. The role of the Process Owner is usually a senior manager with the ability and authority to ensure the process is rolled out and used by all the stakeholders.

Their key responsibilities include:

Defining the overall mission of the process.

Establishing and communicating the process mission, goals, and objectives to all the stakeholders.

Documenting and maintaining the process and procedures.

Resolving any cross-functional (departmental) issues.

Ensuring proper staffing and training for execution.

Ensuring consistent execution of the process across the organization.

Monitoring, measuring, and reporting on the effectiveness of the process to the senior management.

Continually improving the process.

Problem Manager: The Problem Manager is responsible for the overall Problem Management process, and can configure Problem Management settings as well as act as a Problem Coordinator.

Their key responsibilities include:

Can configure whether a problem or problem task can be re-opened, and if so, by which roles.

Can configure whether accepting the risk of not fixing this problem moves the problem to resolved (still active) or closed.

Problem Coordinator: The Problem Coordinator is the responsible owner for getting a problem permanently resolved or prevented as soon as possible. They must also manage and co-ordinate all problems through the process.

Their primary duties are:

Assessing problems to ensure that they are genuine.

Monitoring and controlling the detection, recording, assignment, escalation, and resolution of problems.

Coordinating with the technical and service Subject Matter Experts (SMEs).

Documenting problem information.

Publishing workarounds.

Publishing known error articles.

Coordinating decisions on whether to apply a fix.

Deciding whether to accept the risk of not applying a fix.

Reviewing problems to check for quality and completeness.

Driving the efficiency and effectiveness of the problem management process.

Example: A Problem Coordinator at an IT service provider notices frequent login failures across multiple client environments. They identify that a recently updated authentication service has a memory leak, allowing the issue to be fixed across all affected systems.

Technical Support Teams (Third-Line Support)

The Third-Line Support teams consist of specialists and technical experts who are called in for complex problems. Their responsibilities include:

In-depth Technical Diagnosis : Performs technical investigations into the issues escalated as problems.

Developing and Testing Permanent Solutions : Designs, tests, and recommends fixes that address the root cause.

Implementing Changes : Applies fixes according to the Change Management processes, ensuring minimal disruption.

Benefits

Implementing a strong and systematic Problem Management process brings significant advantages to both IT operations and the broader business. Instead of constantly reacting to incidents, organizations can focus on preventing issues at their source, leading to a more stable, efficient, and cost-effective IT environment.

Following are the key benefits of effective Problem Management:

Reduced Recurrence of Incidents: By identifying and eliminating the root causes of incidents, Problem Management prevents similar issues from happening repeatedly.

This reduces the workload on the Service Desk, frees up technical resources, and improves the overall reliability of IT services.

Example: If a network switch causes regular disconnections, identifying and replacing the faulty hardware stops a series of related incidents from occurring.

Faster Incident Resolution: Problem Management often identifies workarounds that can be used immediately when similar incidents occur.

Having documented workarounds in a Known Error Database (KEDB) allows Service Desk agents to resolve incidents quickly, without needing to escalate.

Example: If a known error causes an application to crash under certain conditions, a workaround to restart the app’s services can be applied immediately, without investigation.

Improved Service Quality and User Satisfaction: A reduction in the number and frequency of incidents naturally improves service uptime and performance. When IT services are more reliable, customer trust and satisfaction increase significantly.

Example: In an e-commerce platform, preventing checkout failures ensures customers can complete purchases smoothly, leading to better reviews and repeat business.

Cost Savings: Fewer incidents mean reduced support costs, less unplanned downtime, and lower operational disruptions.

Additionally, permanent fixes avoid repeated resource drain on incident resolution efforts.

Example: A telecom provider saves hundreds of hours in technician labour by fixing a recurring network configuration issue once and for all, instead of constantly troubleshooting similar complaints.

Proactive Risk Management: Effective Problem Management includes proactive identification of potential problems, before they cause major incidents.

This helps organizations avoid serious outages, regulatory penalties, and reputational damage.

Example: Through trend analysis, a bank identifies increasing errors in its online payment system, and fixes them before customers even notice any disruption.

Better Use of Technical Resources: When problems are permanently solved, technical teams can shift their focus from firefighting to innovation and system improvements.

This strategic use of time and expertise helps IT deliver greater value to the business.

Example: After stabilizing its server environment, an IT team in a hospital can work on improving the patient data systems, instead of constantly responding to server crashes.

Key Metrics and KPIs for Problem Management

In Problem Management, simply solving problems is not enough, you must also measure how effectively and efficiently problems are being handled.

This is where Key Metrics and Key Performance Indicators (KPIs) come into play.

They allow organizations to:

Track the health of their Problem Management process.

Identify areas for improvement.

Justify the value Problem Management brings to the business.

Drive Continuous Service Improvement (CSI) efforts.

Without measurement, management is guesswork. Metrics and KPIs turn the Problem Management process into a structured, data-driven discipline.

What are Metrics and KPIs?

Metrics are quantitative data points collected during the execution of processes. (For example, number of problems logged, and time taken to resolve a problem.)

KPIs (Key Performance Indicators) are specific metrics chosen to measure the success of a process in meeting its goals. (For instance, percentage of problems resolved within SLA.)

Example:

Metric = 50 problems logged last month.

KPI = 90% of problems resolved within agreed timelines.

KPIs usually have a target (example, “Resolve 80% of problems within 30 days”) that teams aim to achieve.

Common KPIs and Metrics in Problem Management:

KPI/Metric

What It Measures

Why It Matters

Number of Problems Identified

Total problems logged over a period.

Shows proactive problem identification.

Number of Problems Resolved

Problems closed after root cause fix.

Indicates efficiency of Problem Management.

Mean Time to Resolve (MTTR)

Average time taken to resolve problems.

Measures speed of problem resolution.

% Problems with Workarounds

Number of problems with documented temporary solutions.

Ensures incidents can be quickly mitigated.

Recurring Incidents Rate

Incidents linked to existing problems that repeat.

Lower numbers indicate successful root cause fixes.

Proactive Problems vs Reactive Problems

Problems identified before incidents occur vs after.

Shows maturity in proactive Problem Management.

Reduction in High-Impact Incidents

Fewer major incidents caused by known problems.

Demonstrates business value to stakeholders.

Table 6.3: Common KPIs and Metrics in Problem Management

Why Metrics and KPIs are Important for Problem Management

Metrics and KPIs are important in Problem Management as it help teams measure how well they are finding and fixing problems. Without tracking numbers, it is hard to know if the process is really working. Metrics give clear data like how many problems were found, how fast they were solved, and how many needed workarounds. KPIs help set goals, such as “ solve 90% of problems within 30 days ,” so that everyone knows what success looks like.

Problem Lifecycle

The key components of Problem Management work together to form a comprehensive process for addressing the root causes of incidents. Each component plays a vital role in ensuring that problems are managed effectively and efficiently. From detecting issues early to implementing permanent fixes, Problem Management is a proactive and preventive approach that aligns with ITIL best practices, and supports the long-term success of IT service management.

By mastering these components, organizations can enhance their ability to deliver reliable and high-quality IT services, ultimately contributing to better business outcomes.

Problem Identification/Detection

Problem Identification is the first step in the Problem Management process. It involves detecting recurring incidents or potential issues that could lead to service disruptions or high impacting P1 incidents. This is achieved through various methods, including:

Monitoring Tools : Automated monitoring systems can detect anomalies, performance degradation, or failures in IT infrastructure, applications, or services. These tools provide early warnings of potential problems.

Incident Analysis : By analysing incident data, organizations can identify patterns or trends that indicate underlying problems. For example, if the same type of incident occurs repeatedly, it may point to a deeper issue.

User Reports : Feedback from users or customers can also help identify problems, especially those that may not be immediately apparent through automated monitoring.

The goal of Problem Identification is to proactively detect issues, before they escalate into major incidents, or to recognize recurring incidents that require deeper investigation.

Problem Logging

Once a problem is identified, it must be formally documented in a problem record. Problem Logging involves capturing all relevant details about the problem, including Description, Impact, Affected Services, Timeline, and related Incidents.

Proper logging ensures that all stakeholders have a clear understanding of the problem, and provides a foundation for further analysis and resolution.

Figure 6.1: Process Flow of Problem Lifecycle

Problem Categorization

Categorization involves classifying the problem, based on the specific criteria to facilitate easier management and resolution. In ServiceNow, Problem tickets are usually categorized by their types such as hardware failure, software bug, network issue, or configuration error.

Problem Prioritization

Not all problems are equal in terms of their impact on the business. Problem prioritization involves assigning priority levels to problems, based on their urgency and impact. This ensures that resources are allocated effectively, and that the most critical problems are addressed first. The key factors considered during prioritization include Business Impact, Urgency and Risk.

Problem Investigation

Problem Investigation is the core of the Problem Management process. It involves a thorough analysis of the problem to identify its root cause. This step typically includes:

Data Collection : Gathering all relevant information, such as logs, error reports, and configuration details.

Root Cause Analysis (RCA) : Using techniques like the 5 Whys, Fishbone Diagram (Ishikawa), or Fault Tree Analysis to trace the problem back to its origin.

The goal of Problem Investigation is to move beyond the symptoms of the problem, and uncover the underlying issue that needs to be addressed to prevent recurrence.

Problem Resolution

Once the root cause of the problem has been identified, the next step is to implement a workaround (if not found yet) or permanent fix. Problem Resolution involves:

Developing a Workaround or Permanent Solution : Creating a plan to address the root cause, which may involve changes to hardware, software, configurations, or processes.

Implementing the Fix : Applying the solution in a controlled manner, often through the Change Management process to minimize risks.

Testing and Validation : Conducting tests or simulations to confirm the root cause, and ensure that the analysis is accurate.

Verification : Testing the solution to ensure that it effectively resolves the problem and does not introduce new issues.

Documentation : Updating the problem record with details of the resolution, including the steps taken, and any lessons learned.

Problem Management in ServiceNow

ServiceNow provides a dedicated Problem Management application that helps organizations manage problems efficiently, using structured workflows, automation, and reporting.

It supports both reactive (fixing recurring issues) and proactive (preventing issues) problem management activities, aligning closely with ITIL 4 best practices.

In ServiceNow:

Problems are logged and tracked as Problem Records.

Root Cause Analysis (RCA) is performed systematically.

Known Error Articles can be created, and linked to the Knowledge Base.

Related Incidents and Change Requests can be connected directly to Problems for full traceability.

Inputs into the Problem Process

Incidents: When incidents occur repeatedly or have a significant impact due to its severe effect on business operations, they may indicate an underlying problem. These incidents are analysed to identify patterns or trends that could point to a root cause.

Example : A network outage affecting an entire organization would likely lead to a problem investigation, or a server crashing repeatedly could indicate a deeper problem.

Change Process : Sometimes, changes can introduce new Issues or reveal underlying issues. An incident will be raised for the fix. Indirectly, Problem Management practice may be initiated, if a change leads to unexpected incidents, or if a change is identified as a potential cause of recurring issues.

Example : A software update that causes compatibility issues with the existing systems could trigger a problem investigation.

Outputs from the Problem Process

Request for Change (RFC): Once the root cause of a problem is identified, an RFC may be raised to implement a workaround or permanent fix.

The RFC outlines the necessary changes to resolve the problem, and prevents recurrence. It is submitted to the Change Management process for approval and implementation.

Example : If a faulty hardware component is identified as the root cause, an RFC might be raised to replace the component.

Known Errors: These are documented in the Known Error Database (KEDB), and often come with workarounds to minimize the impact on users, while a permanent solution is being developed.

Example : A software bug causing application crashes might be documented as a known error, with instructions for users to restart the application as a temporary workaround.

Permanent Fix: This fix is typically implemented through the Change Management process, and may involve updates, patches, or replacements.

Example : Patching a software vulnerability to prevent future security incidents.

Acknowledge or Accept Risk/Input to Risk Register: In some cases, it may not be feasible to implement a permanent fix immediately due to cost, complexity, or other constraints. In such situations, the risk associated with the problem is acknowledged and documented.

The risk is added to the Risk Register, which is a tool used to track and manage risks within the organization. This ensures that the risk is monitored and addressed in the future.

Example : A legacy system that is prone to failures but cannot be replaced immediately due to budget constraints might be documented as a risk in the Risk Register.

Logging Problem Tickets in ServiceNow

Raising Problem Tickets in ServiceNow can be done in two primary ways: without an incident (proactively), or directly from an incident (reactively).

Logging a Problem Ticket without an Incident

This method is used when an IT user or backend team identifies an underlying issue that warrants investigate, even if no specific incident has been reported.

In ServiceNow homepage, on the left-hand navigation pane, click “ All ” tab to view all available modules and applications.

In the filter search bar, type “ Problem ” to quickly locate the Problem Management module.

Once you are in the Problem Management module, click “ New ” to create a new problem record.

Provide the necessary information in the problem form, such as Problem statement, Description, and Priority, and then submit the ticket Save / Submit the record, once all the details are filled in.

Figure 6.2: Creating a New Problem Ticket

Logging a Problem Ticket Directly from an Incident

This method is used, when an IT support staff member identifies a recurring issue, or a major incident that indicates an underlying problem. Here is how to raise a problem directly from an incident:

Figure 6.3: Creating a Problem Ticket from Incident

Navigate to the incident that you believe indicates an underlying problem. This could be a recurring incident, or a major incident with significant impact.

Within the incident record, look for the “ Create Problem ” option. This is typically available in the incident form’s action menu, or as a related link.

When you click “ Create Problem ,” ServiceNow will automatically link the incident to the new problem record. This ensures that all the related incidents are associated with the problem for easier analysis.

Similar to creating a problem without an incident, provide the necessary details in the problem form, and save the problem record.

Problem Ticket Lifecycle in ServiceNow

Figure 6.4 depicts the problem ticket lifecycle in ServiceNow:

Figure 6.4: Problem Lifecycle in ServiceNow

New

It is the initial state, when a Problem ticket is created. This indicates that the Problem has been identified, but not yet assessed.

Figure 6.5: Creating New Problem Ticket

Assess

At the Assess state, the Problem Coordinator who has assigned the ticket to his/her team is primarily assessing the problem to determine whether it is genuine or not. He is expected to click the Assess button. This will move the problem into the lifecycle where it is considered ‘ live ’, and something that requires attention.

If the Problem Coordinator determines that this is a duplicate problem, the problem coordinator will click Mark Duplicate, and select the problem, this is a duplicate of.

If the Problem Coordinator recognizes it is not a genuine problem, the problem coordinator will click Cancel, and populate a Cancelled reason field to explain why the problem is not considered to be genuine. He/she will also explain why no further investigation is required.

If the Problem Coordinator is comfortable to proceed with the investigation, he may need to update the Priority, and click Confirm .

Figure 6.6: Assessment of the Problem Record

Figure 6.7: Assess State Workflow

Root Cause Analysis

If the Problem Coordinator is confirmed that it is a Valid Problem, he may now need to engage one or more technical support teams to investigate, and potentially help to fix the problem. This is achieved using Problem Tasks.

Problem Tasks: The parent problem record remains assigned to the Problem Coordinator throughout the entire process. The Problem Coordinator creates and assigns individual tasks to the various technical support teams to aid in the investigation and diagnosis. Each team will capture their own investigation and discoveries in their individual tasks, and the Problem Coordinator will review and coordinate them all. There are two types of problem tasks. Root Cause Analysis (RCA) and General. The RCA type should be selected for specific tasks required to investigate the root cause, and should be created by the Problem Coordinator at this point.

Root Cause Analysis Tasks: The primary purpose of an RCA task is investigation and diagnosis. It is a formal assignment to a specialist or team to dig deep into the technical evidence, and find the single, underlying trigger for the problem.

Example:

Problem Title : Intermittent “ 503 Service Unavailable ” errors on the E-commerce Website during checkout.

RCA Task 1 : Analyze Web Server Performance Logs to determine if the web server infrastructure is the bottleneck.

RCA Task 2 : Review Application Error Logs to see if a bug in the application code is the trigger.

RCA Task 3 : Diagnose Database Query Performance to find out if the database is failing under load.

General Tasks: The primary purpose of a General Task is action and coordination. These are all the other activities required to manage the problem lifecycle, from implementing workarounds to coordinating the final fix. It answers the questions, “ What do we need to do? ” and “ How will we get it done? ”.

Example:

Problem Title: Intermittent “ 503 Service Unavailable ” errors on the E-commerce Website during checkout.

General Task 1 : Implement Temporary Workaround to reduce the immediate business impact, while the investigation proceeds.

General Task 2 : Communicate with Stakeholders to manage business expectations.

General Task 3 : Create a Change Request to follow the formal process for deploying a fix.

General Task 4 : Monitor and Verify Solution to ensure the fix worked before closing the parent problem record.

Think of it like a detective story. The RCA Task is the forensic investigation to figure out who committed the crime and how. The General Tasks are all the other actions needed to manage the crime scene, talk to witnesses, and eventually, make the arrest.

During the Root Cause Analysis state, three main activities are intended to occur: These activities can all happen in parallel, and may be discovered at different times through Root Cause Analysis. It is possible that none of these are discovered, some, or all three are as follows:

Figure 6.8: Activities of RCA State

Discover a workaround (if possible): The Problem Coordinator /Technical Team should enter the Workaround field, and communicate it to all open related incidents, using the Communicate Workaround related link.

This populates the text from the Workaround Field into the Activity Log of all related open incidents, explaining that it is a workaround from the problem record.

Figure 6.9: Updating Workaround Details in Problem Ticket

Discover the root cause: The Cause Notes tab in a Problem record is a critical section used to document the investigation process, findings, and root cause analysis. It serves as a centralized place for teams to collaborate, share insights, and record the steps taken to diagnose and resolve the problem.

Figure 6.10: Updating the Root Cause Details in the Problem Ticket

Discover a permanent fix: The Fix Notes tab in a Problem record is a dedicated section for documenting the steps taken to resolve the problem, including the implementation of permanent fixe(s), workaround (s), and any related change(s). This section ensures that all the actions taken to address the problem are well-documented, providing a clear record for future reference and compliance purposes.

Figure 6.11: Updating the Fix Details in the Problem Ticket

Fix in Progress

The fix in progress state represents a problem that has been investigated, and is now needing a fix. Once fix notes are updated, communicate it to all the related incidents. If a fix cannot be discovered, or the fix cannot be implemented, the Problem Coordinator can use the Accept Risk button, and provide the reason they are accepting the risk of not fixing this problem for now.

Risk Accepted: From the Root Cause Analysis or Fix in Progress states, the Problem Coordinator along with Business/Management will discuss, and can accept the risk of not fixing the problem for now:

Due to cost implications, the business may determine it is not worth the cost of fixing.

Due to any business reason provided by the organization.

A fix cannot be determined, or not required at the moment.

Vendor dependency.

A Problem record which has been accepted as risk can be reviewed by the Problem Coordinator, along with the business, at appropriate intervals in the above situations. The coordinator establishes whether the impact has increased, or the situation has changed to the point where either the problem will be fixed, or is no longer required due to some other change that has occurred and resolved it. The Problem Coordinator can then choose to re-analyse the problem, so that the problem process can then be worked through to find the solution.

The OOTB behavior (the standard, pre-configured functionality) is that Risk Accepted problems should be set to Resolved, and can remain in Resolved indefinitely. Problem Management is concerned with permanently resolving the issue, and ensuring it will not reoccur — therefore, it is acceptable for this to take as much time as is required.

Resolved State

This state indicates that the problem has been addressed, and a solution (either a permanent fix or a workaround) has been implemented. However, the ticket is not yet closed, allowing for a final review and verification to ensure that the resolution is effective, and no further issues exist.

Figure 6.12: Resolving the Problem Ticket in ServiceNow

Closed State

The Closed State in a Problem ticket in ServiceNow signifies that the problem has been fully resolved, verified, and documented. Once a problem ticket is moved to the Closed State, it is considered complete, and no further action is required unless the problem reoccurs.

Figure 6.13: Closing the Problem Ticket in ServiceNow

A set period can also be observed before setting the problem to the Closed state to confirm that the known error has been solved. If evidence suggests that the issue persists, the state can be set back to Root Cause Analysis , using the Re-analyse button. The process can then be worked through again to continue to find the solution.

Different Problem-Solving Techniques in Problem Management

Effective Problem Management relies on structured techniques to identify the root causes, and implement solutions. The following are the most common Problem–solving Techniques.

5 Whys: A simple but powerful iterative questioning technique to drill down to the root cause (example, application on Azure being inaccessible).

Figure 6.14: Five Whys Technique with Example

Ishikawa (Fishbone) Diagram: This visualizes the potential causes across categories such as People, Process, Technology, and Environment.

Figure 6.15: Ishikawa (Fishbone)Technique Template

Figure 6.16: Ishikawa (Fishbone)Technique Example

Fault Tree Analysis (FTA): This uses logic diagrams to trace system failures, ideal for complex technical issues (for example, network outages).

Figure 6.17: Fault Tree Analysis (FTA) Technique Template

Figure 6.18: Fault Tree Analysis (FTA) Technique Example

Conclusion

In this chapter, we explored the complete journey of Problem Management, starting from its core concepts and importance within IT Service Management, to understanding the roles and responsibilities that drive it.

We highlighted how effective Problem Management delivers real value to organizations by reducing incident volumes, improving service stability, and supporting proactive IT operations.

Through the detailed breakdown of key stages such as detection, logging, investigation, and resolution, we gained insight into the structured lifecycle that ensures problems are not just treated, but permanently resolved.

We also examined how ServiceNow provides a powerful platform for implementing Problem Management. The problem ticket lifecycle in ServiceNow mirrors ITIL best practices, and enhances efficiency through intelligent handling and visibility.

Finally, we discussed various problem-solving techniques that aid Root Cause Analysis, enabling teams to move beyond temporary fixes, and deliver long-term improvements.

In summary, mastering Problem Management is essential for creating a stable, reliable, and customer-focused IT environment. When implemented with the right tools such as ServiceNow, and supported by strong processes and skilled teams, Problem Management becomes a critical pillar for achieving continual service improvement and operational excellence.

In the next chapter, we will delve into the critical IT Service Management (ITSM) practice of Change Management. We’ll explore its purpose, which is to control and govern the lifecycle of all changes to IT services, from initial request to successful implementation. Our discussion will cover key concepts like the different types of changes, the role of the Change Advisory Board (CAB), and the processes that ensure changes are planned, approved, and executed with minimal risk to the business

Multiple Choice Questions

What is the main goal of Problem Management in ITIL?

To fix incidents as quickly as possible

To identify the root cause of incidents

To install new hardware

To monitor network activity

Which role is primarily responsible for overseeing the Problem Management process?

Change Manager

Service Desk Agent

Problem Manager

Incident Analyst

What is a Known Error in ITIL terminology?

A new type of incident.

An issue that cannot be resolved.

A problem with a documented root cause, and a workaround.

A mistake made by the Service Desk.

What module in ServiceNow helps technicians document temporary solutions, while a permanent fix is pending?

Incident Record

Known Error Article

Change Request

Alert Management

What is the purpose of Root Cause Analysis (RCA) in Problem Management?

To quickly close incidents

To find out who made a mistake

To identify the underlying reason an incident happened

To assign incidents to the Service Desk

Answers

b

c

c

b

c

C HAPTER 7

Change Management

Introduction

In today’s rapidly evolving digital landscape, organizations must constantly adapt to meeting changing business needs, embrace modern technologies, and exceed customer expectations. However, introducing changes to IT services, without a structured process can lead to service disruptions, security vulnerabilities, and operational inefficiencies. This is where Change Management, a core process within IT Service Management, plays a vital role.

Change Management provides a standardized approach for planning, approving, and implementing changes to IT services and infrastructure—minimizing risk, while ensuring system stability and service continuity. In this chapter, we will explore the fundamental components of Change Management, including change identification, assessment, planning, implementation, and post-change review.

We will examine the importance of key elements such as Change Requests (CRs), Change Models (CMs), Change Advisory Boards (CABs), and risk and impact assessments, which help to ensure that changes are evaluated and implemented efficiently. Special attention will be given to categorizing changes—Standard, Normal, and Emergency—based on urgency, complexity, and risk.

The chapter also addresses the common challenges organizations face, when implementing change management practices, such as resistance to change, communication gaps, and risk mismanagement. Practical strategies for change planning, scheduling, communication, and post-implementation analysis will be shared to overcome these challenges.

Additionally, we will provide a practical overview of how Change Management processes are effectively executed using ServiceNow, a leading ITSM platform. With features such as automated workflows, risk calculation engines, CAB Workbench, Change Calendar, and conflict detection, ServiceNow empowers IT teams to streamline change handling, while maintaining governance and compliance.

By the end of this chapter, readers will gain a clear understanding of how a robust and well-implemented Change Management process—supported by tools such as ServiceNow—can reduce service disruptions, accelerate innovation, and ensure reliable, secure, and compliant IT operations.

Structure

In this chapter, we will cover the following topics:

Overview of Change Management in ITSM

Key Concepts and Terminology

Goals, Benefits and Objectives of Change Management

Types of Changes

The Change Management Process

Introduction to ServiceNow Change Management

Change Management Lifecycle in ServiceNow

Metrics and Reporting in ServiceNow for Change Management

Overview of Change Management in ITSM

Change : As per ITIL 4, a Change in IT refers to any modification, addition, or removal that could directly or indirectly impact IT services. This definition encompasses any alteration to IT infrastructure, software, processes, or other components that could impact the delivery of IT services.

Change Management : The Change Management team in IT is a group of individuals responsible for overseeing and managing the process of implementing changes in a controlled and structured manner, ensuring that standardized methods and procedures are used for efficient and prompt handling of changes. This team ensures that changes are properly evaluated, approved, tested, and implemented to minimize risks, avoid disruptions, and maintain the stability, security, and reliability of IT services. The goal is not to avoid change, but to manage it in a structured, controlled way that limits the risks to business operations, with minimum disruptions.

Consider this scenario:

You have been using the same office chair for five years, and it is now worn out.

You have a spare chair at home, and consider replacing it after getting your manager’s approval.

However, you cannot proceed independently because the organization has a dedicated team responsible for managing infrastructure assets. Any addition, modification, or removal of office equipment must be coordinated through this team.

Applying this to IT:

As a server administrator, you identify that an old server needs replacement.

Even though you manage the server, you must follow the Change Management process before making any changes.

This includes:

Submitting a ticket (Change Request) for approval.

Coordinating with the dedicated team (Change Advisory Board) to assess and authorize risks.

Ensuring proper testing, scheduling, and backout plans are in place.

The same applies to modifications like CPU upgrades, memory expansion, or disk resizing—all require formal approval.

Why is Change Management Necessary?

Approval from Change Management is required to ensure that changes are controlled, risks are minimized, and the stability, security, and reliability of IT services are maintained. The Change Management approval process is a critical control mechanism that ensures changes are implemented in a structured, controlled, and safe manner, protecting the organization from unnecessary risks and disruptions.

Here are the key reasons, why this approval process is essential:

Risk Mitigation: Risk management is essential during the Assess to Authorize phase of Change Management, as it ensures that all proposed changes are evaluated for potential impact, vulnerabilities, and alignment with business goals. This proactive assessment helps prevent disruptions, security risks, and data loss, enabling informed approval decisions and safer change implementation.

Assess Phase: Risk Identification

During this stage, the Change Manager performs a risk and impact analysis. ServiceNow’s Risk Calculator are often used to evaluate:

Technical risk (compatibility, system performance)

Business risk (downtime, customer impact)

Security and compliance risks

Example: If the change affects a customer-facing service, it is flagged as high-risk, and may require more testing or contingency planning.

Authorize Phase: Risk Informed Decision Making

The CAB reviews the risk assessments to decide:

Should the change proceed?

Should it be deferred, reworked, or rejected?

Are mitigation controls (backout plans, testing) in place?

Result : Changes are authorized only when the risks are manageable, and a solid mitigation plan is present.

Minimizing Disruptions: Unplanned or poorly executed changes can disrupt IT services, leading to downtime or degraded performance. Change Management ensures that changes are scheduled and implemented in a way that minimizes impact on users and business operations, and there is less or no conflict between two changes.

Resource Optimization: Change Management ensures that resources (time, budget, and personnel) are used efficiently. It prevents redundant or unnecessary changes, and ensures that changes are prioritized based on their impact and urgency as well as business needs.

Compliance and Governance: Industries are subject to regulatory requirements (GDPR, HIPAA, SOX) that mandate strict control over IT changes. The approval process ensures that changes comply with legal, regulatory, and organizational policies.

Coordination and Communication: Changes often involve multiple teams or stakeholders. The approval process ensures proper coordination and communication, reducing the likelihood of conflicts or misunderstandings.

Testing and Validation: Change Management ensures that changes are tested and validated before deployment. This reduces the likelihood of introducing errors or defects into the production environment.

Preventing Unauthorized Changes: Without an approval process, unauthorized or rogue changes could be made, leading to security breaches, compliance violations, or system failures. Change Management ensures that only authorized changes are implemented.

Alignment with Business Objectives: Changes must align with the organization’s goals and priorities. The approval process ensures that changes are justified, necessary, and support business needs.

Example of the Change Management Process in Action

Scenario : A server administrator wants to upgrade memory on a production server.

Process:

The administrator submits a Change Request to the Change Management team.

The Change Manager evaluates the request, assesses risks, and consults the CAB, if necessary.

The Change Team approves the change, and schedules it during the maintenance window.

The implementation changes, assesses the server, and confirms it is functioning correctly.

The Change Management team documents the change, and communicates its success to stakeholders.

Key Concepts and Terminology

If you are new to IT Change Management, understanding the key terms is essential. The following are important concepts related to Change Management:

Change Management: The process of controlling and managing changes to IT systems to minimize risks and disruptions.

Example : Before upgrading a server, IT teams follow a structured process to ensure that it does not cause downtime.

Change Request (CR): A formal proposal to make a change (any addition/modification) in the IT environment.

Example : A request to install a new software update on company laptops.

Change Advisory Board (CAB): A group of IT and business stakeholders who review and approve as well as authorize major changes.

Example : Before replacing a critical database server, the CAB checks if the change is safe.

Emergency Change Advisory Board (ECAB): A smaller, faster version of CAB that approves emergency changes.

Example : If a security patch must be applied immediately, ECAB reviews it quickly.

Standard Change : A low-risk, pre-approved change that follows a set implementation and backout plan.

Example : Resetting an employee’s forgotten password.

Normal Change : A change that may or may not require CAB approval, depending on the risk involved.

Example : Upgrading the company’s email server software.

Emergency Change : A critical change that must be done quickly to fix a major incident.

Example : Patching a server to stop a cyber-attack.

Request for Change (RFC): Another term for Change Request (CR), a documented proposal for a change.

Example : A form submitted to increase cloud storage for a department.

Impact Assessment: Evaluating how a change might affect IT services and users.

Example : Before updating a network switch, IT checks if it will cause Internet downtime.

Risk Assessment: Identify the risk level by using risk questions.

Example : If a new firewall rule blocks important traffic, it could disrupt work.

Backout Plan: A step-by-step guide to undo a failed change, or revert the environment in stable and usable conditions.

Example: If a software update crashes a system, IT rolls back to the old version.

Post-Implementation Review (PIR): A review after a change to check if it worked as expected.

Example: After a server upgrade, IT verifies, if performance improved.

Configuration Item (CI): Any IT component (hardware, software, or document) tracked in a CMDB (Configuration Management Database) which has impacted, or change will be deployed on the same.

Example : A company laptop, licensed software, or a network router.

CMDB : A database that stores details of all the CI’s and their relationships.

Example : A list of all company servers, their locations, and software versions.

Types of Changes

In IT Service Management, changes to IT infrastructure, applications, or processes must be carefully controlled to minimize risks and disruptions. ITIL and other ITSM frameworks classify changes into three main categories:

Normal Changes (Require risk assessment and CAB approval)

Emergency Changes (Urgent, ECAB approval)

Standard Changes (Low-risk, pre-approved)

This chapter explores each type in detail, including their characteristics, approval processes, and real-world examples.

Standard Changes (Low-Risk, Pre-Approved)

Standard Changes are frequent, low-risk changes that follow a pre-defined and pre-approved process. Since they are routine and well-understood, they do not require additional approval for each instance.

Key Characteristics

Low risk : Minimal impact on services.

Repetitive : Follow a documented procedure.

Pre-authorized : Approved via template.

No CAB Involvement : Executed as per the agreed process.

Examples of Standard Changes

Routine server patching (non-critical updates).

Adding a new user to an existing system.

Scheduled hardware replacements (swapping a failed hard drive in a RAID array).

Process Flow

Request logged (via template in ServiceNow).

Pre-approved procedure followed (no additional approval needed).

Change implemented (Implementation team).

Documentation updated (for audit and tracking).

Normal Changes (Require Risk Assessment and CAB Approval)

Normal Changes are non-standard changes that require impact and risk assessment, and approval from the Change Advisory Board before implementation.

Key Characteristics

Moderate to high risk : Potential impact on services.

Requires documentation : Detailed change plan, backout strategy, and testing.

CAB approval needed : Evaluated by stakeholders before execution.

Examples of Normal Changes

Upgrading a production database.

Deploying a new software version in a live environment.

Changing network firewall rules.

Increasing server CPU/memory capacity.

Process Flow

Change Request (CR) submitted (with impact analysis).

CAB Review (assesses risks, approves/rejects).

Scheduled and Tested (in a controlled environment).

Implemented (during the approved maintenance window).

Post-Implementation Review (PIR) (verifies success).

Emergency Changes

Emergency Changes are planned as per the business needs, high-priority changes required to fix P1 incidents, or security vulnerabilities that cannot wait for normal CAB approval.

Key Characteristics

High urgency : Must be implemented immediately.

Expedited approval : Fast-tracked by an Emergency CAB (ECAB).

Medium to high risk : May bypass some controls due to urgency.

Examples of Emergency Changes

Patching a zero-day security vulnerability.

Fixing a crucial application bug, causing business disruption.

Process Flow

Emergency CR raised (with justification).

ECAB Review (quick risk assessment).

Immediate implementation (once approved).

Post-Implementation Review (PIR) (to check if Change was successful).

Best Practices for Emergency Changes

Minimize use: Only for truly critical situations.

Document thoroughly: Ensure audit compliance.

Conduct PIR, where required to learn from the change to prevent future emergencies.

Comparison of Change Types

Aspect

Standard Change

Normal Change

Emergency Change

Risk Level

Low

Moderate/High

High

Approval Needed

Pre-approved

CAB Approval

ECAB (Fast Approval)

Frequency

High (Routine)

Medium

Low (Ad-hoc)

Example

Password reset

Server upgrade

Zero-day patch

Table 7.1: Comparison of Change Types

Goals, Benefits, and Objectives of Change Management

Change Management in IT is a structured approach to managing changes to systems, services, and infrastructure to ensure minimal disruption, maintain stability, and align with the business goals.

Goals

Benefits

Objectives

1. Minimize Risks

1. Reduced Downtime

1. Standardize the Change Process

2. Maintain Service Stability

2. Improved Service Quality

2. Assess and Prioritize Changes

3. Ensure Compliance

3. Risk Mitigation

3. Ensure Proper Approval

4. Improve Efficiency

4. Better Resource Utilization

4. Plan and Schedule Changes

5. Enhance Communication

5. Enhanced Security

5. Test Changes Before Deployment

6. Increased Accountability

6. Communicate with Stakeholders

7. Faster Incident Resolution

7. Document Changes

8. Improved Stakeholder Confidence

8. Monitor and Review Changes

9. Support Continuous Improvement

Table 7.2: Goals, Benefits, and Objectives of Change Management

Real-World Example of Change Management Goals and Benefits

Scenario: An organization plans to upgrade its Customer Relationship Management (CRM) system.

Goals:

Ensure that the upgrade does not disrupt customer service.

Align the upgrade with business objectives such as improving customer satisfaction.

Risks :

If not carefully planned or tested, the upgrade could introduce bugs or compatibility issues, potentially disrupting access to customer data, and impacting live customer interactions.

Issues (Without Change Management):

In a previous instance, a similar upgrade was deployed directly into production, without staging environment testing, resulting in system downtime and a backlog of unresolved customer queries.

Objectives (With Change Management):

Test the CRM upgrade in a staging environment to validate functionality and integration.

Schedule the upgrade during off-peak hours to minimize business impact.

Communicate the upgrade timeline, potential impacts, and support contacts to all stakeholders, including the customer support team.

Document the rollback plan in case the upgrade needs to be reverted.

Benefits of Applying Change Management:

Reduced risk of downtime through testing and structured planning.

Improved system performance and user experience due to pre-implementation validation.

Better stakeholder confidence through timely communication and transparency.

Increased change success rate by following a structured approval and review process.

The Change Management Process

The Change Management Lifecycle is the structured process of managing a change from its initial request to closure, ensuring that it is done in a controlled, risk-aware, and efficient way. Effective change management demands clear processes for submitting, assessing, approving, and implementing changes. As such, most organizations follow a sequence of prescribed steps:

Figure 7.1: Change Management Process

Request for Change (RFC) Submission

The process begins when a stakeholder, such as an IT team member, business unit, or end user identifies the need for a change, and submits a formal Request for Change. The RFC includes essential details such as the purpose of the change, its expected benefits, potential risks, impact on services, and urgency level. This documentation ensures that the Change Management team has all the necessary information to evaluate the request effectively.

The RFC must include all the essential details aligned with the 7R’s of Change Management to enable a thorough evaluation:

Who raised the change?

What is the reason for the change?

What is the return required from the change?

What are the risks involved in the change?

What resources are required to deliver the change?

Who is responsible for building, testing, and implementing the change?

What is the relationship between this change and other changes?

Capturing this information ensures that the Change Management team has all the necessary context to assess feasibility, risks, and potential impact, and to make informed decisions regarding approval and implementation.

Initial Review to Assess and Categorization

Once the RFC is submitted, the Change Manager conducts an initial review to assess its validity, and classify it into one of the three categories:

Assessment : The Change Assessment is a critical phase where proposed changes are evaluated for risk, impact, feasibility, and alignment with business goals.

Initial Triage and Filtering: Quickly determine if the RFC is valid and complete.

Actions:

Verify if the RFC contains all the required details (description, justification, and urgency).

Reject incomplete/invalid requests for resubmission.

Risk and Impact Analysis: Identify the potential disruptions and dependencies.

Actions:

Technical Impact : Will the change affect system performance, security, or compatibility?

Business Impact : Could it disrupt operations, revenue, or user experience?

Resource Assessment : Are budget, time, and skills available?

Dependencies : Does the change rely on other systems/teams?

Feasibility Evaluation : Determine if the change is practical, and worth implementing.

Actions:

Cost-Benefit Analysis (CBA) : Do benefits outweigh the costs?

Technical Feasibility : Can the current infrastructure support the change?

Regulatory Compliance : Does it meet the legal/security policies?

Categorization: Here, the change is categorized, according to the Impact.

Standard Change : Pre-approved, low-risk modifications (password resets, and routine updates) that follow an established procedure, and do not require additional approval.

Normal Change : Non-routine changes (server upgrades, and software deployments) that require a thorough risk assessment, and approval from the CAB.

Emergency Change : Urgent modifications (security patches, and critical bug fixes) that need immediate implementation to resolve a high-priority incident. These are fast-tracked through an Emergency CAB.

Proper categorization ensures that each change follows the appropriate approval and implementation pathway.

Planning and Scheduling

With the request finalized, the change must now be fully planned out. The planning stage should incorporate and document details such as impact, rollout plans, backout plans, change roles, and any associated downtime the change might necessitate. Scheduling the change during a maintenance window to minimize disruption.

Preparing test environments to validate the change before production deployment.

Defining rollback procedures to revert the system, if the change fails.

Communicating the change to the affected teams and end-users.

This step ensures that the change is executed smoothly, with contingencies in place for unforeseen issues.

Change Approval

The RFC is sent to the CAB, as well as any other authorities or internal groups that might have a stake in the change. The CAB reviews the available information, makes an educated assessment of the risks and rewards, and provides a recommendation to the change manager responsible for giving the final approval. The CAB then accepts or rejects the change. The following are the potential impacts on IT services and business operations:

Resource requirements (time, cost, personnel).

Back out plan feasibility in case of failure.

Compliance and security implications.

Based on this assessment, the CAB may approve, reject, or request modifications to the change. Emergency Changes, due to their critical nature, undergo an expedited review by the ECAB, which focuses on immediate risk mitigation.

Change Implementation

The change is deployed by the Implementation Team, according to the approved plan. Depending on the complexity, this may involve:

Phased rollouts (Approved and decided during CAB meeting).

Real-time monitoring to detect and address issues promptly.

Collaboration with support teams (Service Desk) to manage user inquiries.

Documentation is updated throughout the process to maintain an audit trail.

Post-Implementation Review (PIR)

After deployment, a Post-Implementation Review (PIR) is conducted to:

Verify whether the change met its objectives.

Identify any unexpected issues or gaps.

Capture lessons learned to improve the future changes.

Introduction to ServiceNow Change Management

ServiceNow Change Management offers a powerful suite of tools designed to simplify, automate, and enhance IT change processes. Built on the innovative Now Platform, it leverages advanced automation and AI-driven insights to deliver efficient and reliable change management solutions.

ServiceNow equips organizations with a range of features to optimize and streamline the change process, enhancing both visibility and governance. The following are some of the key capabilities:

Multi-Path Change Handling: ServiceNow supports flexible change models, allowing you to tailor workflows, and flow activities based on the nature of the change, whether it is standard, normal, or emergency. This ensures that each type of change is processed appropriately.

Dynamic Approval Workflows: Approval mechanisms are flexible and rule-based, enabling organizations to generate approvals dynamically, based on specific business needs or change parameters. This reduces bottlenecks, and ensures that relevant stakeholders are always involved.

Built-In Risk Evaluation: ServiceNow integrates AI-driven risk assessment tools to evaluate each change for potential disruption. These assessments are embedded into the process, helping to make more informed decisions, and avoid unanticipated service impacts.

Conflict Identification: Using built-in conflict detection tools, ServiceNow flags any scheduling overlaps or Configuration Item (CI) conflicts, based on change timelines. This helps to avoid service clashes, and minimizes downtime.

Interactive Change Calendar: The platform offers a visual calendar interface to track planned changes, scheduled outages, and blackout windows. This supports better planning and resource allocation.

CAB Workbench: ServiceNow provides a dedicated workspace for Change Advisory Board (CAB) meetings, enabling strategic decision-making, reviewing failed changes, and overseeing crucial transitions with clear context and documentation.

Unified Platform Integration: By consolidating ITSM, IT Operations Management (ITOM), DevOps, and Change Management into a single platform, ServiceNow allows seamless collaboration across teams. It acts as a sole source of truth, enabling a comprehensive understanding of change impacts on configuration items and associated services.

Comprehensive Support Features: From automated scheduling and approval routing to change tracking and analytics, ServiceNow offers an end-to-end framework for managing changes effectively and consistently. It empowers teams to implement changes more frequently, without compromising on reliability.

Change Management Lifecycle in ServiceNow

ServiceNow’s Change Management module follows a structured lifecycle to ensure that IT changes are properly controlled from initiation to closure. The following is a comprehensive explanation of each stage in the change management lifecycle within ServiceNow:

Figure 7.2: Change Request Lifecycle in ServiceNow

New

A Change Request (CR) is created in ServiceNow. This can be submitted manually by a user or automatically triggered by other ITSM processes (for example, Incident or Problem). The requester fills out the necessary details such as:

Change type (Standard, Normal, and Emergency)

Description

Business justification

Affected services or Configuration Items (CIs)

Proposed schedule

Example : A network team initiates a change request to upgrade firmware on routers across data centers.

Steps for Creating a New Change Request in ServiceNow:

Log into ServiceNow .

In the left-hand navigation pane ( Application Navigator ), type " Change " in the search bar.

Click Change > Create New

Figure 7.3: Creating a New Change Request

You may see options like Preapproved Change (Standard), Normal Change , or Emergency Change, depending on your organization’s setup.

Figure 7.4: Selecting which Type of Change needs to be Created

Choose the Type of Change , fill out the Change Request Form , and Submit.

Figure 7.5: Filling all the Relevant Details in a New Change Record

Figure 7.6: Justification, Implementation, Back out Plans, and Test Results Addition

Assess

The change is reviewed by a change manager or assigned analyst to assess its validity, scope, and potential impact. Risk and impact assessments are performed using built-in tools or questionnaires. Change success score may be calculated (if enabled) to gauge the likelihood of a successful implementation.

Figure 7.7: Change Request Sent for Approval

Figure 7.8: Change Request Approved by the Change Manager

Authorize

After assessment, the change requires approval .

Depending on the risk and type, this could involve:

Change Advisory Board (CAB) review and sign-off.

Automated approvals for low risk/standard changes.

If rejected, the change may be sent back for rework, or cancelled.

Figure 7.9: Awaiting Approval from the CAB

Figure 7.10: Change Approval from the CAB

Schedule

Once authorized, the change is scheduled for implementation. It is entered into the Change Calendar which highlights:

Conflicting changes

Maintenance windows

Blackout periods

This step ensures no overlap with other major activities that could affect business continuity, and click " IMPLEMENT ."

Figure 7.11: Change Request Moved to Scheduled State

Figure 7.12: Change Request Scheduled Timing for Implementation

Implement

The change is executed according to the approved plan.

Tasks are assigned to relevant teams, and tracked in real time.

ServiceNow allows implementers to update status, attach evidence (such as logs or screenshots), and communicate progress.

If an issue occurs, a back out plan can be triggered, or the change can be marked as failed.

Figure 7.13: Assigned Change Tasks to Different Teams for Implementation

Figure 7.14: Moving to Review State Post Change Successfully Implemented

Review

After implementation, the change enters the review phase. This involves:

Validating that the change achieved its objectives.

Ensuring that no incidents occurred as a result.

Documenting any lessons learned.

Identifying opportunities for improvement.

Figure 7.15: Review State

Close

Once reviewed and verified, the change is formally closed.

All associated tasks and documentation must be completed.

The final status (successful, failed, backed out) is recorded.

The record is locked for auditing and compliance purposes.

Figure 7.16: Change Request Closed as Successful

Metrics and Reporting in for Change Management

ServiceNow provides robust metrics, KPIs, and reporting capabilities to measure the effectiveness, efficiency, and reliability of Change Management processes. These insights help organizations track performance, identify bottlenecks, and improve change success rates. These insights help stakeholders make data-driven decisions, and ensure continuous improvement.

Metrics

Metrics in Change Management are quantifiable measurements used to track and evaluate the efficiency, effectiveness, and performance of IT changes. They provide data-driven insights into how well-planned changes are planned, approved, implemented, and reviewed within an organization.

Example: A company notices a high rate of failed changes (30%) in its reports. By analyzing metrics, it discovers:

Most failures occur due to inadequate testing.

Emergency changes have a 50% higher failure rate than planned ones.

Solution :

Introduce mandatory testing checkpoints before implementation.

Reduce emergency changes by improving proactive maintenance.

Result :

Failure rate drops to 10% within six months.

Business confidence in IT changes improves.

Examples of Key Change Management Metrics

A. Change Volume and Categorization Metrics

Metric

Description

Why It Matters

Total Changes Requested

Count of all change requests submitted

Measures change workload

Change Type Distribution

% of Standard/Normal/Emergency changes

Shows process maturity

Change Category Trends

Changes by category (Hardware/Software/Network)

Identifies focus areas

Table 7.3: Change Metric - Change Volume and Categorization Metrics

B. Change Success Metrics

Metric

Description

Why It Matters

Change Success Rate

% of changes completed without incidents

Indicates process effectiveness

Failed Changes

Changes that required rollback or caused incidents

Highlights risk areas

Emergency Change Ratio

% of changes classified as Emergency

Measures stability (lower = better)

Table 7.4: Change Metric - Change Success Metrics

C. Efficiency and Timelines Metrics

Metric

Description

Why It Matters

Average Approval Time

Time from submission to approval

Identifies approval bottlenecks

Average Implementation Time

Time from approval to completion

Measures execution speed

Change Lead Time

End-to-end time (request to closure)

Tracks overall process efficiency

Table 7.5: Change Metric - Efficiency and Timelines Metrics

D. Risk and Compliance Metrics

Metric

Description

Why It Matters

Risk Score Distribution

% of High/Medium/Low-risk changes

Assesses risk exposure

Unauthorized Changes

Changes implemented without approval

Measures policy compliance

CAB Approval Rate

% of Normal changes approved by CAB

Shows governance effectiveness

Table 7.6: Change Metric - Risk and Compliance Metrics

E. Reporting Capabilities: Reporting capabilities for Change Management refer to the tools, features, and functionalities that allow IT teams and leadership to track, analyze, and communicate the performance and impact of changes made to IT systems and services. These capabilities are usually built into ITSM platforms such as ServiceNow, and they help ensure that the change process is transparent, measurable, and continuously improving.

What Reporting Capabilities Include:

Dashboards: Visual overviews of current and historical change activities (for example, number of changes, pending approvals, and failed changes).

KPI Tracking: Metrics like Change Success Rate, Mean Time to Implement, or % Emergency Changes.

Trend Reports : How change performance evolves over time (monthly change volumes, and rising failure trends).

Drill-down Reports: Insights into specific teams, services, or change types ( example, top five services with failed changes).

CAB Reports: Reports that assist the Change Advisory Board in decision-making before approval.

Why Reporting is Important in Change Management:

Reason

Explanation

Performance Monitoring

See how well your change process is working. Are changes successful? Fast?

Compliance and Audit

Reports provide an audit trail of who did what, when, and why essential for governance.

Decision Making

Data helps Change Managers and CABs decide which changes to approve or reject.

Risk Identification

Spot patterns such as repeated failures, frequent emergency changes, or risky systems.

Transparency & Accountability

Tracks individual/team performance, promoting accountability.

Continuous Improvement

Identify process bottlenecks and improve future change execution

Table 7.7: Reporting in Change Management

Conclusion

Change Management plays a vital role in ensuring stability, reliability, and continuity in IT services while enabling organizations to evolve and innovate. Throughout this chapter, we have explored the foundational principles of Change Management within the ITSM framework, including its key terminologies, types of changes, and its overarching goals of minimizing risk and ensuring controlled transformation.

We examined the complete lifecycle of a change—from identification and assessment to implementation and review—emphasizing how each phase contributes to a structured and consistent approach. By categorizing changes such as Standard, Normal, or Emergency, and involving key roles such as Change Advisory Boards (CAB), organizations can better prioritize and manage the impact of IT changes on service delivery.

We then turned our focus to ServiceNow, a powerful ITSM platform that streamlines Change Management through intelligent automation, real-time risk analysis, and collaborative tools such as the CAB Workbench and Change Calendar. ServiceNow not only simplifies complex workflows but also enhances decision-making through robust reporting and metrics—such as change success rate, mean time to implement, and emergency change trends.

In summary, implementing a structured Change Management process using ServiceNow empowers IT teams to balance innovation with operational stability. By following best practices, leveraging automation, and continuously monitoring performance, organizations can achieve greater agility, reduce service disruptions, and drive continuous improvement in their IT landscape.

In this next chapter, we will delve into the interconnected practices that support a stable and efficient IT environment. We will start by exploring Event Management, which allows for the proactive detection and response to issues. Following this, we will examine Knowledge Management, a key to improving operational efficiency and user satisfaction by sharing collective expertise. We will also cover the Configuration Management Database which provides a single source of truth for all IT assets. Finally, we will discuss Release and Deployment Management, DevOps, and Continuous Service Improvement, all of which are crucial for ensuring the smooth delivery, evolution, and ongoing enhancement of IT services

Key Takeaways

Change Management ensures structured control over IT modifications, balancing innovation with stability.

Standard, Normal, and Emergency changes each follow distinct workflows, ensuring appropriate oversight.

ServiceNow’s Change Management module enhances ITIL processes with automation, AI-driven risk assessment, and real-time visibility.

The Change Management lifecycle—from request to closure—is streamlined in ServiceNow with guided workflows, dynamic approvals, and post-implementation reviews.

Metrics and reporting provide actionable insights, helping organizations measure success, optimize processes, and demonstrate compliance.

Multiple Choice Questions

What is the primary goal of Change Management in ITSM?

To eliminate all IT changes

To implement changes with minimal disruption, while maintaining stability

To reduce IT staff workload

To avoid documentation

Which of these is NOT a standard type of change in ITSM?

Standard Change

Normal Change

Emergency Change

Random Change

What does CAB stand for in Change Management?

Change Advisory Board

Change Authorization Board

Central Approval Bureau

Configuration Advisory Body

Which type of change is pre-approved , and follows a documented procedure?

Emergency Change

Normal Change

Standard Change

Major Change

What is the key benefit of ServiceNow Change Management?

Enforcing rigid processes that slow down all development cycles.

Streamlining the change process to minimize IT service disruption, and reduce risks.

Eliminating the need for a Change Advisory Board (CAB) by automating all approvals.

Exclusively focusing on tracking emergency changes over normal changes.

Which phase in the ServiceNow Change Lifecycle involves Post-Implementation Review (PIR)?

Authorize

Implement

Review

Close

Which metric helps to measure the percentage of changes completed without incidents?

Change Volume

Emergency Change Ratio

Average Approval Time

Change Success Rate

What does ServiceNow’s " Conflict Detection " feature help identify?

Employee disagreements

Scheduling overlaps between changes

Software bugs

Cybersecurity threats

Which group approves of Emergency Changes in ServiceNow?

ECAB (Emergency CAB)

Standard CAB

IT Manager only

No approval needed

What is the purpose of a Back out Plan in Change Management?

To cancel all changes permanently

To avoid documentation

To speed up approvals

To revert a failed change to its original state

Answers

b

d

a

c

b

c

d

b

a

d

C HAPTER 8

Other Supporting Modules

Introduction

In the ever-evolving landscape of modern IT environments, delivering consistent, high performing services requires more than just incident handling, it demands proactive monitoring, structured knowledge sharing, seamless deployments, and a commitment to continuous improvement. This chapter explores the interconnected disciplines that collectively support the stability, efficiency, and growth of IT service delivery: Event Management, Knowledge Management, Configuration Management Database (CMDB), Release and Deployment Management, DevOps, and Continuous Service Improvement (CSI).

We begin by examining Event Management, a process that detects, interprets, and responds to significant occurrences (or “ events ”) in the IT environment. Event Management enables early detection of issues, prevents potential service disruptions, and plays a crucial role in proactive operations.

Next, we delve into Knowledge Management, a critical component for improving operational efficiency and user satisfaction. By capturing, organizing, and sharing organizational knowledge, this process empowers IT teams to resolve issues faster, and make informed decisions based on collective experience and documented best practices.

We then explore the role of the CMDB, which acts as a central repository of IT assets, and their relationships. A well-maintained CMDB enables better impact analysis, root cause identification, and change planning, ultimately reducing risks, and enhancing service reliability.

Following this, Release and Deployment Management is introduced as a structured approach to planning, scheduling, and controlling the movement of releases to test and live environments. This ensures that new or changed services are delivered smoothly with minimal disruption.

We also discuss the importance of DevOps, a cultural and technical shift that bridges the gap between development and operations. DevOps promotes automation, collaboration, and continuous integration/delivery (CI/CD), allowing organizations to innovate rapidly, while maintaining stability.

Finally, we cover Continuous Service Improvement, a core ITIL principle that ensures services remain aligned with evolving business needs, and are enhanced over time. CSI provides the framework to analyse performance data, identify opportunities for optimization, and embed a culture of iterative improvement across IT operations.

Together, these components form a cohesive strategy for managing, evolving, and enhancing IT services in a modern enterprise.

Structure

In the chapter, the following topics will be covered:

Event Management

Knowledge Management

Configuration Management Database (CMDB)

Release and Deployment Management

DevOps

Continuous Service Improvement (CSI)

Event Management

Event Management is a critical process in ITIL that focuses on monitoring and managing events throughout the IT infrastructure to ensure optimal service performance and availability. It helps organizations detect, analyse, and respond to events, before they escalate into incidents or outages.

Key Concepts in Event Management

Event: An event is any observable change in the state of an IT service, system, or component. Events can be normal (a user logging in) or exceptional (a server going offline). An event does not necessarily have to be a bad event impacting our infrastructure.

Examples:

A server CPU usage exceeds 90%.

A backup job completes successfully.

Purpose: Events provide visibility into the health and performance of IT systems, enabling proactive management.

Real-time Scenario:

The mobile banking application’s response time increases from 2 seconds to 10 seconds due to a sudden surge in user traffic.

The monitoring tool detects the slowdown, and generates an event.

The event includes details such as timestamp, affected service, and performance metrics.

Alert: An alert is a notification triggered by an event that requires attention. Alerts are generated, when an event meets predefined thresholds or conditions.

Examples:

An alert is generated, when disk space usage exceeds 80%.

An alert is triggered, when a critical application stops responding.

Purpose: Alerts help IT teams identify and address potential issues, before they impact services.

Real-time Scenario:

An alert is triggered because the response time exceeds the predefined threshold of 5 seconds.

The alert is sent to the IT operations team, indicating a potential performance issue.

The alert includes information about the severity level (critical, warning) and the impacted service.

Notification

Definition : A notification is a message sent to inform the relevant stakeholders (IT staff, managers) about an event or alert. Notifications can be delivered via email, SMS, or other communication channels.

Examples:

An email notification is sent to the IT team, when a server goes down.

A text message is sent to the on-call engineer, when a critical alert is triggered.

Purpose: Notifications ensure that the right people are aware of events or alerts, and can take appropriate action.

Incident

Definition: An incident is an unplanned interruption or degradation of an IT service that affects users or business operations. Incidents are often caused by events that are not resolved in time.

Examples:

A server outage causes the company website to go down.

A network failure prevents employees from accessing email.

Purpose: Incident management focuses on restoring normal service operations as quickly as possible to minimize the business impact.

Types of Events:

Information

Type of event that requires no action. Typically used to confirm the status of an equipment or a service, the success of a transaction or activity, or to generate statistical analysis. Examples:

A batch job was completed successfully

Transaction logging or automated reports

Warning

Type of event signalling the approach of a threshold. Indicate that the situation should be checked and the appropriate actions taken to avoid an exception (failure).

Example :

Disk space on a server is used at 65% and increases; if it reaches 75%, the response time becomes unacceptable.

The completion time of a transaction is 10% longer than normal.

The transmission rate of a packet increased by 15% the last hour.

The warning means an unusual activity. It is an indication that the situation calls for increased surveillance. In some cases, it might resolve itself, for example, when an unusual increase workload occurs, once completed, the situation returns to a normal state.

Exception

Type of event indicating that an equipment functions abnormally which causes or may cause a negative impact on business activities.

Examples :

A server is down

More than 150 users have logged simultaneously on an application

A network segment is not responding to routine requests

Table 8.1: Categorization of Events

How Event Management Works

In essence, event monitoring and management in ITIL is about:

Detecting changes : Monitoring the IT infrastructure for any deviations from the expected state.

Categorizing events : Identifying which of these changes are significant enough to require attention.

Responding appropriately : Taking the necessary actions to address the identified events, ensuring service quality and availability.

Figure 8.1: Event Monitoring Flowchart

Occurrence : Among all the events that occur, which ones should be detected must be determined.

Notification : Issued by a CI, or by a monitoring tool.

These are of two types:

Active tools, that query CIs on their status and availability.

Passive tools, that detect CI alerts and communications as well as make correlations to identify exceptions.

Detection : Once the notification is received, it is interpreted by the monitoring system, or another management tool (such as Octopus).

Event Logging : Creation of the event request type in the request management tool.

First-level of Correlation and Filtering : According to the rules established in the correlation engine, the event is communicated to the management request system, or it is ignored (filtering), and is identified as an event type:

Information : No action

Warning : An equipment reaches a threshold that requires a verification, and potentially an automatic or manual action to prevent an exception (failure).

Exception : A service or an equipment function abnormally; business is impacted. The exception event will be transmitted as an incident, a problem or a change.

Second-level of Correlation: If the event is a " Warning " type, a decision must be made about its significance, and the appropriate actions to be taken. Correlation is ensured by a “ correlation engine ” (which is usually a part of a management tool) which compares the event with a set of criteria in a prescribed order. These criteria are called “ business rules ”. The idea is to design a system that identifies events that impact the business, and use the rules to determine the level and type of impact.

By example:

Number of similar events.

Number of CI generating similar events.

Specific action associated to a code or data.

Comparison of data usage, according to a maximum or a minimum.

Others

If no action is required, the event will be logged for future reference.

Alert/Human Intervention : If the " Warning " event requires immediate attention, a notification is sent to the group responsible of the affected configuration item.

Auto-Response : Just as an " Exception " event, correlation rules of the management system can automatically create an incident, problem or change, and the new request will be managed through the corresponding processes.

Closure : Closing of " Information " or " Warning " event. The " Exception " event will be closed through the incident, problem or change processes.

Importance of Event Management

Proactive Monitoring: Enables early detection of potential issues before they escalate into incidents.

Improved Service Availability: Reduces downtime by addressing issues promptly.

Efficient Resource Utilization: Automates event monitoring and filtering, reducing manual effort.

Enhanced Decision Making: Provides insights into IT system performance and trends.

Example:

Event: A database server’s CPU usage spikes to 95%.

Alert: An alert is generated because the CPU usage exceeds the predefined threshold of 90%.

Notification: An email notification is sent to the database administrator, and the IT operations team.

Incident: If the issue is not resolved promptly, the database becomes unresponsive, causing an application outage. An incident is logged to restore the service.

Integration of Monitoring Tool with ServiceNow

Integrating monitoring tools such as LogicMonitor with ServiceNow can significantly enhance IT operations by enabling real-time incident detection, automated ticket creation, and streamlined incident management. This integration bridges the gap between monitoring and ITSM, ensuring that issues are identified and resolved quickly, minimizing downtime, and improving service delivery.

How LogicMonitor Integrates with ServiceNow

Real-Time Alerting and Incident Creation

LogicMonitor continuously monitors IT infrastructure (servers, networks, applications, and so on) and generates alerts, when predefined thresholds are breached or anomalies are detected.

Through integration, these alerts can be automatically forwarded to ServiceNow as incidents or events.

ServiceNow’s Event Management module can process these alerts, correlate them, and create incidents in the Incident Management module.

Automated Ticket Creation

When LogicMonitor detects an issue, it sends an alert to ServiceNow via APIs.

ServiceNow receives the alert, and automatically creates an incident ticket with details such as:

Alert description

Severity level

Affected device or service

Monitoring data (for example, metrics, logs, and so on)

This eliminates the need for manual ticket creation, reducing response times, and ensuring that no critical issues are missed.

Enriching Incidents with Monitoring Data

LogicMonitor provides detailed monitoring data (for example, performance metrics, logs, and diagnostics) that can be attached to the ServiceNow incident.

This data helps IT teams quickly diagnose and resolve issues, without switching between tools.

ServiceNow’s Incident Management module can display this information directly in the incident record, providing context for faster resolution.

Two-Way Synchronization

The integration can be configured to allow two-way communication between LogicMonitor and ServiceNow.

For example:

When an incident is resolved in ServiceNow, the status can be updated in LogicMonitor, closing the alert.

If an alert is acknowledged or suppressed in LogicMonitor, the corresponding incident in ServiceNow can be updated accordingly.

Proactive Problem Management

LogicMonitor’s predictive analytics and anomaly detection can identify potential issues, before they impact services.

These insights can be used to create proactive problem records in ServiceNow’s Problem Management module, allowing teams to address the root causes, before they escalate.

Example Use Case

Scenario : A server’s CPU usage exceeds 90% for an extended period.

LogicMonitor : Detects the anomaly, and sends an alert to ServiceNow.

ServiceNow : Creates an incident, assigns it to the infrastructure team, and attaches performance metrics from LogicMonitor.

Resolution : The team investigates the issue using the attached data, resolves the incident, and updates the status in ServiceNow, which automatically closes the alert in LogicMonitor.

Knowledge Management

Knowledge Management is a critical component of IT Service Management that focuses on capturing, organizing, and sharing knowledge to improve efficiency, reduce redundancy, and enhance decision-making. It ensures that valuable information is accessible to the right people at the right time, enabling faster issue resolution, better service delivery, and continuous improvement. The following is a detailed description of the key aspects of Knowledge Management:

What is Knowledge Management in ServiceNow?

Knowledge Management in ServiceNow refers to the process of creating, managing, and sharing knowledge articles within the platform to support IT and business operations. It is designed to:

Provide a centralized knowledge base for storing and accessing information.

Enable self-service for end-users, reducing the workload on support teams.

Improve incident resolution times by providing quick access to solutions.

Promote continuous improvement by capturing and reusing knowledge.

Key Components of Knowledge Management in ServiceNow

Knowledge Base

The Knowledge Base is the central repository, where all knowledge articles are stored.

It is accessible to users, agents, and other stakeholders, based on their roles and permissions.

Articles can be categorized, tagged, and organized for easy navigation and search.

Knowledge Articles

Knowledge Articles are the core elements of the Knowledge Base. They provide solutions, SOPs, and lessons learnt. Release plans, updates, instructions, best practices, and troubleshooting steps for common issues.

Articles can include texts, images, videos, and attachments to make them more informative and user-friendly.

They follow a standardized format to ensure consistency and clarity.

Knowledge Search

ServiceNow offers powerful search capabilities to help users find relevant knowledge articles quickly.

Features such as Natural Language Processing (NLP) , auto-suggestions , and filters enhance the search experience.

Search results are ranked by relevance, ensuring that the most useful articles appear at the top.

Knowledge Management Roles

Knowledge Authors : Create and update knowledge articles.

Knowledge Managers : Review, approve, and manage the Knowledge Base.

End-Users : Access and use knowledge articles for self-service or troubleshooting.

Integration with Other Modules: Knowledge Management integrates seamlessly with other ServiceNow modules, such as:

Incident Management : Suggesting relevant articles during ticket creation or resolution.

Problem Management : Linking knowledge articles to problem records for root cause analysis.

Service Catalog : Providing self-service solutions for common requests.

Knowledge Article Lifecycle

The Knowledge Article Lifecycle refers to the process of creating, reviewing, publishing, updating, and retiring knowledge articles. Managing this lifecycle ensures that knowledge remains relevant, accurate, and useful over time.

Figure 8.2: Accessing Knowledge Management in ServiceNow

Stages of the Knowledge Article Lifecycle:

Figure 8.3: Knowledge Management Lifecycle in ServiceNow

Draft: A Draft state refers to the initial version of a KB article that is still under development or revision. At this stage, the article has not been finalized, and is not yet ready for review or publication. It serves as a working document where authors can refine content, gather inputs, and ensure accuracy, before moving it to the next stage.

Review: The Review state in Knowledge Management represents that the phase KB article is evaluated for accuracy, completeness, and relevance, before it is published. During this stage, designated reviewers assess the content to ensure that it meets organizational standards, and provides value to end users. Feedback may be provided for revisions, and only after approval in this phase does the article progress toward publication. This step ensures that only validated and high-quality information is made available in the knowledge base.

Scheduled for Publishing: When a KB article is marked as Scheduled for Publishing , it indicates that the article has successfully completed the drafting, review, and approval processes. It is now queued to be made available to the intended audience within the organization or community. This state ensures that the article is ready for release at a specified time, or as part of a planned update.

Published: A Published state signifies that the KB article is live and accessible to users. At this stage, the article is available in the Knowledge Base, and can be searched, viewed, and utilized by end-users, support teams, or other stakeholders. Published articles are considered the official source of information for the topics they cover.

Pending Retirement: When an article is in the Pending Retirement state, it means that the article has been identified for removal or archiving due to reasons such as obsolescence, irrelevance, or updates in processes or technology. This state allows for a final review or transition period, before the article is officially retired.

Retired: A Retired state indicates that the KB article has been removed or archived from the active Knowledge Base. Articles are retired, when they are no longer relevant, accurate, or useful. ServiceNow also allows for automatic retirement of articles by specifying a «valid to» date during submission, after which the article is automatically retired.

Outdated: An Outdated state refers to a KB article that contains information that is no longer accurate, relevant, or up to date. Outdated articles may still be accessible in the Knowledge Base, but are flagged to inform users that the content may not be reliable. These articles are typically reviewed, and either updated or retired.

Review and Publish Articles in ServiceNow

The process of reviewing and publishing a Knowledge Base (KB) article involves several structured steps to ensure that the content is accurate, clear, and aligned with organizational standards. The following is a professional explanation of this process:

Feedback: During the Review stage of a KB article, reviewers play a crucial role by providing a detailed feedback. They evaluate the content for accuracy, clarity, completeness, and relevance, highlighting any issues, concerns, or areas that require improvement. This feedback is typically shared, either directly within the KB platform, or through email communication. In addition to reviewer input, end users can also provide feedback once the article is published, this may include ratings, comments, or suggestions based on the article’s usefulness. This continuous loop of feedback helps maintain the quality and relevance of the knowledge base, ensuring articles stay accurate and valuable over time.

Approval: After the necessary revisions are made based on the feedback, the KB article is submitted for final approval. Designated approvers such as managers or subject matter experts review the revised article to confirm that all feedback has been addressed, and that the content meets organizational standards. Once approved, the article is cleared for publishing.

Publishing: Upon receiving final approval, the KB article is published or updated in the Knowledge Base platform. At this stage, the article becomes accessible to the intended audience, within the organization or community. Users can now search for, reference, and utilize the article to resolve issues, complete tasks, or gain insights.

Introduction to CMDB

The Configuration Management Database (CMDB) is like a central record-keeping system for all the important parts of your IT environment. These parts, called Configuration Items (CIs), include things such as laptops, servers, software, applications, databases, and the services that help run the business.

Think of the CMDB as a giant map that helps organizations understand what IT assets they have, how they are connected, and how they support the day-to-day operations.

Why is CMDB Important?

A CMDB plays a crucial role in helping IT teams manage and support their technology infrastructure effectively. While it primarily helps track IT assets—such as servers, software, applications, and databases, its real value lies in how it connects the dots between these components. When an issue arises, the CMDB provides a clear picture of how different items are related. For example, if a server goes down, the CMDB can show which applications or business services depend on it, helping IT teams respond faster, and more accurately.

With better visibility into what assets exist, and how they are used, organizations can reduce the time spent searching for information and troubleshooting problems. This leads to faster resolution of issues, less downtime, and improved user satisfaction. Additionally, having a well-maintained CMDB supports smarter planning by allowing IT teams to assess the impact of proposed changes, before they are implemented, minimizing risks, and avoiding unexpected disruptions.

The CMDB also plays a key role in risk reduction by helping teams understand dependencies across systems. This is especially important during change implementations, upgrades, or audits. From a compliance perspective, the CMDB ensures accurate and traceable records of assets, changes, and relationships, making audit processes more efficient and reliable.

In short, a CMDB provides the foundation for efficient IT service management by offering visibility, control, and insight into the organization’s technology landscape.

What is in a CMDB?

A CMDB stores data about Configuration Items (CIs). These are anything that supports IT services, such as:

Physical items : Computers, routers, servers.

Software items : Applications, databases.

Service items : Email services, payroll systems.

Each CI includes information such as its name, type, owner, and whether it is active or retired.

It also tracks relationships, and how items depend on each other. For example:

A server hosts an application.

A network switch connects to a router.

A business app depends on a database.

Understanding these relationships is very helpful, when diagnosing problems, or planning upgrades.

How Does CMDB Help Other Processes?

A CMDB is not just a place to store technical asset details; it plays an important role in enabling and enhancing many IT processes. For example, in Incident and Problem Management, when something breaks, the CMDB helps the support team quickly identify which components or systems are involved. This leads to faster diagnosis, and resolution of the issue.

In Change Management, the CMDB provides a clear view of system dependencies. This helps IT teams assess the potential impact of a proposed change, before it is implemented, reducing the risk of accidental outages. Similarly, in Release Management, the CMDB ensures that teams know exactly where updates need to be deployed, and which systems or services are affected.

For the Service Catalog, the CMDB helps map out the services provided to end users, and connects them to the underlying infrastructure. This not only supports better service delivery but also helps users understand what services are available, and how they function behind the scenes.

Keeping the CMDB Clean and Useful

For a CMDB to truly support IT operations, the data inside it must be accurate and reliable. An outdated or inconsistent CMDB can do more harm than good. That is why organizations follow the best practices to keep it clean and useful. This includes conducting regular audits and clean-ups to ensure that the CMDB reflects the real IT environment.

Using standard naming conventions is also important so that every Configuration Item is easy to identify and locate. Access controls should be in place to make sure only authorized personnel can make updates; this helps prevent accidental or unauthorized changes. Additionally, automation tools can be used to continuously scan the network and update the CMDB automatically, reducing human errors, and saving time.

Common Challenges with CMDB

Despite its benefits, maintaining a CMDB comes with its own set of challenges. One of the most common issues is bad or outdated data. If the information is not current, it can lead to confusion during troubleshooting or planning. Another challenge is information overload. Trying to track every small detail can make the CMDB hard to manage and overwhelming for users.

There is also the problem of unclear ownership. If it is not clear who is responsible for maintaining certain parts of the data, things can quickly fall out of sync. Lastly, integrating the CMDB with other IT systems—like monitoring tools and asset management, can be complex, and requires careful planning.

To overcome these issues, it is recommended to start small. Most organizations begin by tracking only the most critical systems and services, and then expand the CMDB gradually as governance and processes mature.

CMDB in ServiceNow

In ServiceNow, the CMDB is a core application that is deeply integrated with other IT Service Management modules. It comes with predefined categories (called “ CI classes ”) such as servers, applications, and network gear which help in organizing assets more efficiently.

One of the standout features of ServiceNow’s CMDB is its visual relationship mapping. This lets users see how different components are connected which is especially helpful during incident diagnosis, or change planning. ServiceNow also supports automated discovery tools that scan the network to detect assets, and automatically populate the CMDB, keeping the data accurate with minimal manual effort.

The CMDB integrates seamlessly with modules such as Incident Management, Change Management, Problem Management, and Asset Management, offering a unified view across processes. Another valuable feature is Business Service Mapping, which visually connects technical components (like servers and databases) to the business services they support crucial during major incidents or outages to prioritize fixes, based on business impact.

A Real-Life Example

Imagine your company’s online banking portal is performing slowly. Without a CMDB, the support team might spend hours figuring out where the problem lies. But with a well-maintained CMDB, they can quickly look up the " Online Banking " service, and see all the related infrastructure, such as application servers, databases, and network components.

Suppose a recent change was made to one of the servers. With this insight from the CMDB, the team can trace the issue, identify that change, and roll it back, or apply a fix promptly restoring service performance quickly. This kind of impact analysis and root-cause tracing becomes significantly faster, and more efficient with a CMDB in place.

Summary

The CMDB is far more than just a data repository, it is a foundational part of effective IT service management. By giving IT teams clear visibility into the relationships between systems, applications, and services, a CMDB empowers them to resolve incidents faster, plan smarter changes, and reduce risks.

A clean, well governed CMDB ensures that your organization is ready for audits, compliant with policies, and responsive to business needs. Ultimately, it enhances operational efficiency, improves service reliability, and helps IT deliver real business value in a structured and proactive way.

Release and Deployment Management

Imagine you have a smartphone. One day, you receive a notification that a new version of your phone’s operating system is available, maybe it is Android 14 or iOS 17. That notification is the result of a release that your phone manufacturer (Apple/Samsung) has carefully prepared over weeks or months.

Before this new OS version reached your phone, the release team at the company worked behind the scenes to plan what features and fixes would be included such as improved battery life, new camera features, or better security. Once the plan was ready, developers built and tested the software on many different phone models to make sure it works correctly. They tested how it behaves, when you open apps, receive calls, or use Bluetooth. After everything passed the quality checks, they scheduled a rollout, deciding when and how the new OS would be delivered to users like you.

Now comes the deployment part. You get the update delivered to your phone over the Internet. When you click " Install ," your phone reboots and the new OS is installed. This entire process of installing the update on your device is known as the deployment. Sometimes, companies roll it out to users in phases (10% of users today, then gradually to others) to make sure no big issues appear.

Also, if something goes wrong after the update, like a bug causes apps to crash, the company may roll back the update, or send a quick patch to fix it. It is a safety net in Release and Deployment Management.

Release and Deployment Management is a process used by IT teams to safely deliver new or changed services such as software updates, bug fixes, or new features, into the live environment used by end users or customers.

Using the mobile phone scenario:

The Release part is everything done before the update reaches your phone. It includes planning, building, testing, and scheduling the update. Just like Apple or Google prepares a new iOS or Android version and checks it thoroughly before making it available.

The Deployment part is when the update is actually installed on your device. This is done either all at once (a big bang deployment) or gradually (phased or canary deployments) to monitor for issues. When you press " Install update " and your phone restarts, that’s deployment happening.

Key Terms

Release : A release is a collection of new features, updates, bug fixes, or configuration changes that are bundled together and delivered as one package. A release can be:

Major : A large update with new functionality (Android 14).

Minor : A small update or fix (bug fix for an app crash).

Emergency : A quick release to fix a critical issue (security patch).

Release Unit: A release unit is the smallest part of a release that can be deployed independently. Each unit is tested and managed as part of the overall release package.

For example:

A new login page for a website.

An updated version of an app module.

Release Package: A release package is a group of one or more release units that are tested together, and prepared for deployment. Think of it like the final software, " bundle " that is ready to go live. It contains:

Code

Configuration changes

Documentation

User instructions

Back-out Plan/Rollback Plan: A back-out or rollback plan is a safety mechanism. If something goes wrong during deployment, the system can be returned to its previous stable state. This reduces business risk and downtime.

Release Calendar: This is a schedule or timeline showing when releases are planned. It helps teams coordinate, avoid conflicts, and communicate with stakeholders.

Stages of the Release Lifecycle

The Release Lifecycle consists of several structured stages that ensure updates or changes to IT systems are delivered efficiently, and with minimal disruption to end users. Let us walk through each stage, using the example of a mobile banking app update.

Planning: The release lifecycle begins with the planning stage. Here, the team defines what is going to be released, why it is needed, and when it should go live. This includes deciding on the scope of the release (new features, bug fixes, and performance improvements) including identifying risks, dependencies, and timelines. For instance, the product team may decide to release a new fingerprint login feature in the banking app to improve security and user experience. This stage also involves coordinating with other departments such as customer support and change management.

Build and Test: Once the plan is finalized, the next step is to build and test the release. The development team codes the new feature, and then the teams run various tests to ensure that it works as expected. In our banking app example, internal teams would test the fingerprint login on different devices and operating systems to make sure it is secure, and functions properly under various conditions. This stage ensures that the release is reliable, before it reaches the end users.

Deployment Preparation: With a tested release package in hand, the team moves to the deployment preparation stage. This includes finalizing documentation, creating user guides, scheduling any necessary downtime, and notifying stakeholders. If changes require a maintenance window, it is communicated to the users in advance. In our example, the IT team might schedule the deployment during late-night hours, when fewer customers are using the app, and prepare helpdesk instructions in case users face login issues.

Deployment: The deployment stage is when the release is installed or pushed into the live production environment. Depending on the strategy, this might be done all at once (a " big bang " deployment) or in phases. For the banking app, the update might first be released to a small group of users (a canary deployment) to monitor performance before being rolled out to everyone. Support teams monitor the system closely during this time to address any issues quickly.

Post-Deployment Review: After the deployment is complete, the team conducts a post-deployment review. This involves verifying whether the release was successful, checking for any issues reported by users, and collecting feedback. Lessons learned during this release are documented, and used to improve future releases. In the banking app example, the team might find that users appreciated the new login method, but a few experienced compatibility issues on older phones—this feedback would be noted for future enhancements.

Benefits of Effective Release Management

When Release and Deployment Management is done well, it brings several valuable benefits to both IT teams, and the organization as a whole. One of the most important benefits is the reduction in outages and disruptions. Well planned and tested releases ensure that new updates do not accidentally break the existing systems or cause service downtime, which can be costly and frustrating for users.

Secondly, user satisfaction improves because releases happen smoothly and deliver value such as new features or bug fixes, without causing confusion or system errors. When users experience seamless improvements in the systems they rely on, trust in IT services grows.

Another major advantage is better coordination and communication. Release and Deployment Management promotes structured planning and clear communication among developers, testers, support teams, and business stakeholders. Everyone knows what is changing, when it is happening, and how to respond, if something goes wrong.

In addition, Release and Deployment Management enables predictable and safe deployments. Instead of last-minute rushes or reactive fixes, releases are scheduled, monitored, and rolled out using proven methods such as phased or canary deployments. This reduces risks, and improves stability.

Finally, RDM supports stronger compliance and traceability. Every step of the release process, what was released, who approved it, what testing was done, and when it went live is documented. This audit trail is essential for meeting regulatory requirements, and demonstrating accountability during reviews or audits.

How Release and Deployment Management Differs from Change Management

Though Release and Deployment Management and Change Management are closely related, they serve different purposes, and involve different activities.

Change Management is primarily about deciding what changes should happen, and ensuring that they are reviewed, approved, and aligned with business goals. This includes assessing potential risks, impacts, and the business justification behind the change. For example, if a team wants to upgrade a core database system, Change Management ensures that the upgrade is necessary, does not pose excessive risks, and is approved by the appropriate stakeholders.

Release and Deployment Management, on the other hand, focuses on how and when those approved changes are delivered. Once a change is authorized, Release and Deployment Management takes over to manage the testing, packaging, scheduling, and deployment into production. Continuing the same example, while Change Management approves the database upgrade, RDM plans how the upgrade will be installed, performs test deployments, and oversees the rollout.

Change Management typically involves business stakeholders, governance teams, and risk management functions because the focus is on decision making and oversight. In contrast, Release and Deployment Management is more technical in nature, involving IT operations, development, QA, and support teams to execute the change effectively.

Moreover, Change Management applies to all types of changes including infrastructure updates, policy changes, or configuration modifications. Release Management is usually specific to changes related to software or system updates that require bundling, testing, and deployment.

Summary

Release and Deployment Management ensures that updates go live safely and reliably, without disturbing business operations. While Change Management controls what should happen, Release Management handles how and when it happens. Together, Change Management and Release and Deployment Management form a powerful combination: One ensures changes are the right ones, and the other ensures that they are delivered the right way. Understanding their differences helps organizations avoid confusion, and ensures that IT services remain stable, reliable, and aligned with business needs.

By using the right deployment strategy, such as phased or pilot releases, organizations can reduce risks and gain confidence in their changes. Together, these processes help IT teams support business goals with stability, speed, and accountability.

DevOps

In many traditional IT organizations, the people who write codes (developers) and the people who run and maintain systems (operations teams) work in isolation. Developers focus on building new features or fixing bugs, while operation teams are responsible for deploying those updates, and ensuring systems run smoothly without disruption. While this separation might seem logical, it often leads to communication gaps, delays, and finger-pointing, when something breaks. For example, developers may push out an update that works perfectly in their environment, but when the operations team installs it, it might crash the system due to configuration mismatches, or unforeseen dependencies.

This is where DevOps comes in, a term that blends " Development " and " Operations ". DevOps is not just a technical method or a job title; it is a collaborative culture and set of practices that encourages both development and operations teams to work together throughout the entire software lifecycle. This means from the moment a feature is planned, to the point it is developed, tested, deployed, and maintained, everyone involved works in sync. The result is not just faster delivery of software, but better quality, fewer errors, and more stable services.

DevOps in Everyday Life

Let us now bring this closer to something relatable: your mobile phone. Think about how your phone’s operating system (like Android or iOS) and your apps (like WhatsApp or your banking app) get regular updates. You get new features, security patches, or visual improvements almost every few weeks, often without even noticing any downtime. That smooth experience is very much the result of DevOps principles.

Now, imagine your banking app is planning a new feature that lets you apply for a loan instantly and see approval in real time. Without DevOps, the development team might build this feature and then hand it off to the operations team, who would test it, schedule deployment, and notify users. This process could take weeks or even months, and any mistake discovered late in the cycle could mean starting over or delaying release. If something went wrong during the update, the blame game might start developers saying, " it worked on my machine " and operations saying, " it broke in production ."

But with DevOps, both teams collaborate from the beginning. Developers write small chunks of code, and test them frequently using automated tools. These pieces are integrated regularly, a process called Continuous Integration. Once tested and approved, they move to the next stage, Continuous Delivery, meaning the code is always in a deployable state. The actual deployment to your phone happens through automated pipelines that ensure the update is smooth, reliable, and easily rolled back if something goes wrong. Operations teams monitor the app’s behaviour after the release, ensuring there are no performance issues, and if there are, they work together with developers to fix them immediately.

How DevOps Works

Behind the scenes, DevOps relies heavily on automation. Instead of manually testing code, clicking buttons to release updates, or setting up servers one at a time, DevOps teams use tools to do these tasks automatically. This includes testing software the moment a developer makes a change, packaging the code for release, deploying it to different environments (test, staging, production), and monitoring how it behaves. This automation significantly reduces human error, saves time, and makes the process consistent and repeatable.

Another powerful DevOps concept is Infrastructure as Code (IaC), where servers, databases, and other resources are managed using code. Just like an architect creates blueprints for a building, DevOps engineers write configuration scripts that tell systems exactly how to set up infrastructure. This makes it easy to reproduce environments across testing and production, ensuring what worked in testing will work in live systems.

DevOps and Traditional IT Processes

DevOps doesn’t replace traditional IT practices like Change Management or Release Management, it complements them. For instance, Change Management focuses on ensuring that updates are reviewed and approved before going live. In DevOps, these approvals can be automated or built into the development pipeline, reducing bottlenecks while still maintaining control. Similarly, Release Management is about planning and scheduling updates, and DevOps helps by enabling smaller, more frequent releases instead of large, risky deployments.

Why DevOps Matters

The benefits of DevOps are enormous. It enables shorter development cycles, meaning businesses can respond to user feedback more quickly and stay ahead of competitors. It improves team collaboration because developers and operations staff are working toward shared goals. It also leads to fewer failures, because changes are smaller and tested frequently, and when something does go wrong, the system can recover faster thanks to built-in rollback mechanisms. Ultimately, DevOps helps IT teams become more agile, efficient, and aligned with business needs, creating better outcomes for both users and the organization.

Summary

To put it simply, DevOps is about teamwork, speed, and quality. It breaks down traditional barriers, encourages continuous improvement, and helps organizations deliver better software faster and more reliably. Whether it’s updating a phone app, deploying a new website, or maintaining large-scale enterprise systems, DevOps ensures that the process is smooth, automated, and collaborative from start to finish. For any organization aiming to thrive in the digital era, embracing DevOps is not just a technical shift it’s a cultural one.

Continuous Improvement

Continuous Improvement is a core principle of the ITIL framework. It focuses on regularly evaluating and improving IT services, processes, and practices to align with business goals, enhance efficiency, and deliver greater value to customers. Continuous Improvement ensures that IT services evolve in response to changing business needs, technological advancements, and feedback from stakeholders.

In the context of ServiceNow, Continuous Improvement is supported through various modules and functionalities that enable organizations to capture, manage, and implement improvement initiatives systematically. Following is an explanation of the key components of Continuous Improvement in ServiceNow:

Idea Management

Idea Management is the process of capturing, evaluating, and implementing improvement ideas from stakeholders, including employees, customers, and partners. It fosters innovation and ensures that valuable suggestions are not overlooked.

How ServiceNow Supports Idea Management:

Idea Submission : Users can submit improvement ideas through a user-friendly portal or form in ServiceNow.

Idea Evaluation : Submitted ideas are reviewed, categorized, and prioritized based on their potential impact, feasibility, and alignment with business goals.

Collaboration : Stakeholders can comment, vote, and provide feedback on ideas to refine and improve them.

Workflow Automation : ServiceNow automates the routing of ideas to the appropriate teams for review and approval.

Tracking and Reporting : Ideas are tracked throughout their lifecycle, from submission to implementation, with detailed reporting to measure their impact.

Benefits of Idea Management in ServiceNow :

Encourages innovation and collaboration across the organization.

Ensures that valuable ideas are captured and acted upon.

Provides transparency into the status and progress of ideas.

Feedback Management

Feedback Management involves collecting, analysing, and acting on feedback from users and stakeholders to identify areas for improvement. It helps organizations understand user satisfaction, pain points, and expectations.

How ServiceNow Supports Feedback Management:

Feedback Collection : ServiceNow enables the creation of surveys and feedback forms that can be distributed to users after interactions, such as incident resolution or service delivery.

Sentiment Analysis : Advanced analytics and AI capabilities in ServiceNow can analyse feedback to identify trends, sentiment, and areas of concern.

Actionable Insights : Feedback is linked to relevant records (for example, incidents, services) to provide context and drive actionable improvements.

Reporting and Dashboards : ServiceNow provides dashboards and reports to visualize feedback data, helping organizations prioritize improvement efforts.

Benefits of Feedback Management in ServiceNow:

Improves user satisfaction by addressing the pain points, and enhancing services.

Provides data-driven insights to guide decision-making.

Enables continuous monitoring of service quality and performance.

Improvement Projects

Improvement Projects are structured initiatives aimed at enhancing IT services, processes, or tools. They are typically driven by identified gaps, feedback, or strategic goals.

How ServiceNow Supports Improvement Projects:

Project Creation : Improvement projects can be created directly in ServiceNow, with details such as objectives, scope, timelines, and resources.

Task Management : ServiceNow’s project management capabilities allow teams to break down projects into tasks, assign responsibilities, and track progress.

Integration with ITSM : Improvement projects are linked to relevant ITSM processes (for example, incident management, problem management) to ensure alignment with operational goals.

Resource Allocation : ServiceNow helps allocate resources efficiently, ensuring that improvement projects are adequately staffed and funded.

Progress Tracking : Dashboards and reports provide real-time visibility into the status of improvement projects, including milestones, risks, and outcomes.

Benefits of Improvement Projects in ServiceNow

Ensures that improvement initiatives are systematically planned and executed.

Provides visibility into project progress and outcomes.

Aligns improvement efforts with organizational goals and priorities.

How These Components Work Together in ServiceNow

Idea Submission : A user submits an idea for improving a service through the ServiceNow portal.

Feedback Collection : Feedback from users highlight recurring issues or areas for improvement.

Idea Evaluation : The idea is reviewed, prioritized, and approved based on feedback and business impact.

Improvement Project Creation : An improvement project is initiated to implement the idea, with tasks, timelines, and resources defined in ServiceNow.

Execution and Tracking : The project team executes the improvement initiative, with progress tracked and reported in ServiceNow.

Feedback Loop : After implementation, feedback is collected to assess the impact of the improvement, and identify further opportunities for enhancement.

Benefits of Continuous Improvement in ServiceNow

Enhanced Service Quality : Regular improvements lead to better service delivery and user satisfaction.

Increased Efficiency : Streamlined processes and reduced inefficiencies save time and resources.

Data-Driven Decisions : Insights from feedback and analytics guide strategic improvements.

Alignment with Business Goals : Continuous Improvement ensures that IT services evolve to meet the changing business needs.

Outcome : The upgrade is completed, and feedback shows improved user satisfaction.

Scenario: Improving Incident Resolution Times

Idea Management : The idea to improve incident resolution times originated from a data driven observation by the IT support leadership team during quarterly service performance reviews. Analysis of service metrics extracted from ServiceNow highlighted a significant increase in the Meantime to Resolve (MTTR) for high-priority incidents, specifically, P1 incidents. Over the last quarter, the MTTR for P1 incidents had doubled, increasing from an average of 2 hours to 4 hours.

This deviation from standard expectations triggered a concern, especially given the critical business impact associated with delayed P1 resolutions. The prolonged resolution time was also flagged during a review of major incident records and stakeholder feedback, which indicated slower coordination, delayed escalations, and inefficient communication during bridge calls. Recognizing the operational risk and potential business disruption, the team proposed an initiative to analyse and streamline the incident handling process. The primary idea was to reduce the MTTR for P1s back to the targeted threshold of 2 hours over the next six months. This became a strategic goal under the Continuous Service Improvement (CSI) program, with a dedicated task force assigned to investigate root causes, and implement corrective actions.

Goal : Reduce the MTTR for Priority 1 incidents from 4 hours to 2 hours within the next 6 months.

Feedback Management :

Root Cause Analysis (RCA) : The IT team conducts an RCA and identifies the following issues:

Lack of clear escalation paths for high-priority incidents.

Insufficient training for Level 1 support staff on handling complex issues.

Delays in obtaining necessary information from end-users.

Improvement Project

Action Items:

Redesign the incident escalation process to ensure faster routing to Level 2 and Level 3 support teams.

Provide targeted training for Level 1 staff on troubleshooting common high-priority issues.

Implement a self-service portal for end-users to submit detailed incident information upfront.

Update the incident management workflow in the ITSM tool to automate escalations for Priority 1 incidents.

Introduce a mandatory field in the incident form for end-users to provide detailed descriptions and attachments.

Tracking the Improvement

We will track the success of the project using the following steps:

Monitor MTTR for P1 incidents monthly to check if it is reducing from 4 hours to our target of 2 hours.

Check escalation times to ensure that incidents are quickly routed to the right support teams.

Review incident data weekly to see if users are filling in detailed information using the new form, and self-service portal.

Collect feedback from support teams and end-users to understand what is working, and what needs adjustment.

Assess training impact through quick evaluations and performance tracking of Level 1 agents.

Monthly review meetings will help track progress, and make any necessary changes.

Outcome :

After 6 months, the MTTR for Priority 1 incidents has decreased to 2 hours.

User satisfaction scores have improved by 20%.

Lessons Learned :

The redesigned escalation process and training programs were highly effective.

The self-service portal reduced delays in obtaining information, but requires further promotion to increase adoption.

Standardization :

Document the updated incident management process and training materials in the Knowledge Base.

Incorporate the new escalation workflow into the organization’s ITIL process guidelines.

Optimization :

Continue to monitor MTTR and user satisfaction to ensure sustained improvement.

Explore additional automation opportunities to further reduce resolution times.

Conclusion

In an era where digital transformation drives every aspect of business, the reliability, agility, and maturity of IT services are central to organizational success. This chapter brought together key ITSM and modern delivery disciplines: Event Management, Knowledge Management, CMDB, Release & Deployment Management, DevOps, and Continuous Service Improvement (CSI), each playing a unique but interconnected role in shaping a resilient and future-ready IT environment.

We began with Event Management which enables real-time visibility into system activities and anomalies. By detecting and responding to critical events proactively, organizations can significantly reduce unplanned outages and business impact, while shifting from reactive firefighting to predictive IT operations.

Knowledge Management emerged as the foundation for a self-sustaining IT support ecosystem. By capturing and sharing organizational knowledge in structured ways, IT teams reduce resolution time, enhance decision-making, and ensure consistent service delivery regardless of staff changes or knowledge silos.

The CMDB was presented as the central nervous system of ITSM, providing an accurate and up-to-date view of all configuration items CIs and their interdependencies. This visibility empowers better risk assessments, change impact analyses, and efficient root cause investigation, allowing for more informed and confident operational decisions.

We then explored Release and Deployment Management, a process driven discipline that governs the safe and efficient rollout of new or changed services into production. When releases are planned, tested, and executed in a controlled manner, organizations can deliver innovation while safeguarding service continuity.

Building upon that, DevOps introduced a modern, agile, and collaborative approach to software delivery. Through automation, continuous integration/deployment, and breaking down traditional silos, DevOps enables faster delivery of high-quality services—aligning IT outputs more closely with business demands.

Finally, CSI served as the guiding philosophy that ties all the above disciplines together. By embedding a culture of reflection, measurement, and incremental enhancement, CSI ensures that IT services not only meet current expectations, but continuously evolve to exceed them in the future.

Bringing It All Together

Individually, each of these areas brings value. Collectively, they create a comprehensive and scalable approach to delivering high-performing IT services. Together, they enable organizations to:

Detect and respond to issues faster.

Make decisions based on real-time insight and historical knowledge.

Manage change and deployments with precision and reduced risks.

Foster cross-functional collaboration between development and operations.

Commit to ongoing improvement aligned with business goals.

By adopting these integrated practices, IT becomes more than just a support function—it becomes a strategic partner in driving business growth, innovation, and customer satisfaction.

As you implement or mature these capabilities within your organization, remember that success is not achieved through tools alone, but through people, processes, and a shared commitment to excellence.

Multiple Choice Questions

What is the primary goal of Event Management in ITSM?

To manage software licenses

To respond to user service requests

To detect and respond to significant changes in the IT environment

To conduct regular audits

Which of the following best defines a CI in CMDB?

Only hardware assets

Any component that needs to be managed to deliver IT services

Service Desk tickets

Only cloud infrastructure components

What is the key benefit of Knowledge Management?

Tracking network usage

Reducing the need for backup systems

Enabling faster resolution through shared knowledge

Preventing unauthorized software installation

What does DevOps primarily aim to improve?

Collaboration and automation between development and operations

Manual testing efforts

Number of ITIL certifications

Data center size

In Release and Deployment Management, a " back-out plan " refers to:

A plan for onboarding new employees.

A plan to delay future releases.

A strategy for removing old assets from CMDB.

A contingency plan to revert changes, if deployment fails.

Which of the following is a core principle of DevOps?

Segregation of duties

Waterfall development

Monthly manual deployments

Continuous Integration and Continuous Delivery (CI/CD)

Which of the following statements is true about the CMDB?

It maintains information about CIs and their relationships.

It is used for storing incident resolutions.

It only stores information about physical hardware.

It is a part of the Service Catalog.

What is the objective of Continuous Service Improvement (CSI)?

To maintain network bandwidth.

To create a backup for all Cis.

To ensure IT services align with changing business needs through ongoing improvements.

To deploy code automatically.

In Knowledge Management, what is typically the best source for creating knowledge articles?

Executive meeting notes

Frequently resolved incidents and requests

Daily timesheets

VPN logs

What is a common trigger for Event Management?

A new hire onboarding request.

A password reset.

An alert from monitoring tools like Solar Winds or Zabbix.

A scheduled project meeting.

Answers

c

b

c

a

d

d

a

c

b

c

Index

A

Accurate Categorization 114

C

Call Center 56

Call Center, features 56 , 57

Change Management 162

Change Management, architecture 163

Change Management, categories

Emergency Changes 168

Normal Changes 167

Standard Changes 167

Change Management, concepts 165 , 166

Change Management, ensuring 162

Change Management, metrics 184 , 185

Change Management, objectives 169

Change Management, process 171

Change Management, reasons 163 , 164

Change Management, scenarios 170

CMDB, challenges 204

CMDB, configuring 204

CMDB, ensuring 202 , 203

CMDB, initializing 205

Configuration Management Database (CMDB) 202

Continuous Improvement 212

Continuous Improvement, benefits 214

Continuous Improvement, components

Feedback Management 213

Idea Management 212

Improvement Projects 213

Continuous Improvement, points

Execution/Tracking 214

Feedback Collection 214

Idea Evaluation 214

Idea Submission 214

Project Creation 214

D

DevOps 210

DevOps, configuring 210

DevOps, illustrating 211

DevOps, implementing 211

E

Emergency Changes 168

Emergency Changes, characteristics 168

Emergency Changes, flows 168

Emergency Changes, practices 169

Event Management 191

Event Management, concepts

Alert 192

Event 191

Incident 193

Notification 192

Event Management, importance 196

Event Monitoring, terms

Categorizing Events 194

Detect Changes 193

Responding Appropriately 194

F

Feedback Management 213

Feedback Management, benefits 213

Feedback Management, terms 213

H

Help Desk 57

Help Desk, features 57

HR Service Delivery, sources

Customer Service Management (CSM) 35

Integrated Risk Management (IRM) 36

HR Service Delivery, terms

Employee Decument Management 35

Employee Service Center 35

Knowledge Management 35

Onboarding/Transition 35

I

Idea Management 212

Idea Management, benefits 213

Idea Management, terms 212

Improvement Projects 213

Improvement Projects, benefits 214

Improvement Projects, terms 213

Incident 104

Incident, characteristics

Affected Services 106

Category/Subcategory 105

Impact 105

Priority 105

Urgency 105

Incident, configuring 104 , 105

Incident, impact

Compliance/Legal 106

Customer 106

Financial 106

Operational 106

Reputational 106

Incident Management 103

Incident Management, architecture 113

Incident Management, benefits 114

Incident Management, configuring 116

Incident Management, goals 114

Incident Management, lifecycles

Categorization 118

Diagnosis/Investigation 120

Escalation 120

Identification 118

Logging 118

Prioritization 119

Resolution 121

Response 119

Incident Management, objectives 115

Incident Management, responsibilities 115

Incident Management, roles

Delegation 113

Documentation 114

Escalation 113

Incident Resolution, scenarios 215

Incident, scope 106

Incident States 123

Incident States, preventing 125 , 126

Information Technology Infrastructure Library (ITIL) 4

ITIL, architecture 23

ITIL, aspects 6

ITIL, illustrating 5 - 7

ITIL, scenarios 23

ITIL, service 24

ITOM, terms

Discovery 33

Event Management 33

Operational Intelligence 33

Service Mapping 33

IT Service Management (ITSM) 9

IT Services 7

IT Services, domains

Cloud Computing 8

Collaboration/Communication Services 9

Data Backup/Recovery Services 9

Email Services 8

Enterprise Resource Planning (ERP) 9

Mobile Device Management (MDM) 9

Network Services 8

Security Services 8

Software Development 9

Technical Support Services 9

ITSM, benefits

Alignment/Business Objectives 14

Continous Improvement 14

Cost Optimization 14

Customer Satisfaction 14

Incident Resolution/Root Cause 14

Productivity Efficiency 14

Risk Management 14

Service Quality 14

ITSM, components 32 , 33

ITSM, evolution 11

ITSM, frameworks

Agile 13

COBIT 13

DevOps 13

ISO/IEC 20000 13

IT4IT 13

ITIL 12

Lean 13

ITSM, operations

Adoption 11

Agile/DevOps 12

Digital Transformation 12

Expansion/Standardization 11

Frameworks 12

ITIL 11

IT Management 11

Service-Oriented Approach 12

ITSM, reasons

Alignment/Business Goals 10

Continuous Improvement 10

Resource Utilization 10

Risk Mitigation 10

Service Quality 10

K

KB Article, process

Approval 202

Feedback 201

Publishing 202

Knowledge Article Lifecycle 199

Knowledge Article Lifecycle, stages

Draft 200

Outdated 201

Published 201

Retired 201

Retirement Pending 201

Review 200

Scheduled Publishing 201

Knowledge Base (KB) Article 201

Knowledge Management 198

Knowledge Management, architecture 198

Knowledge Management, components

Knowledge Articles 199

Knowledge Base 198

Knowledge Search 199

Modules Integration 199

Roles 199

L

LogicMonitor 196

LogicMonitor, process

Data Monitoring 197

Incident Creation 196

Proactive Problem Management 197

Ticket Creation 197

Two-Way Synchronization 197

M

Major Incident 107

Major Incident, characteristics

Escalation 107

High Impact 107

Priority 107

Reputational Risks 107

Special Handling 107

Urgency 107

Widespread Scope 107

Major Incident, impacts

Business Operations Disruption 108

Customer Experience 108

Financial Loss 108

Legal/Compliance Risks 108

Reputational Damage 108

Major Incident, terms

Collaboration, enhancing 109

Post-Incident Reviews 109

Predefined Playbooks 109

Rapid Decision-Making 109

Metrics 183

N

Normal Changes 167

Normal Changes, characteristics 168

Normal Changes, flows 168

Now Community 48

Now Community, benefits 48 , 49

Now Community, resources 48

P

Priority 110

Priority, levels 110

Priority Matrix 111

Priority Matrix, benefits 113

Priority Matrix, levels 112

Proactive Problem Management

about 137

Advantages 138

Characteristics 137

Flow 137

Limitations 138

Scenario 138

Problem Management 55 , 132

Problem Management, benefits 140 , 141

Problem Management, characteristics 55

Problem Management, concepts 133 , 134

Problem Management, configuring 132 , 133

Problem Management, lifecycle

Categorization 145

Identification/Detection 143

Investigation 145

Logging 144

Prioritization 145

Resolution 145

Problem Management, metrics 142

Problem Management, roles

Continuous Improvement 135

Operational Efficiency 135

Proactive Incident Management 135

Risk Mitigation 136

Service Disruption 135

User Experience 135

Problem Management, types

Proactive Problem 137

Reactive Problem 136

Problem-Solving, techniques

5 Whys 156

Fault Tree Analysis (FTA) 157

Ishikawa 156

Problem Ticket 147

Problem Ticket, ensuring 147

Problem Ticket, lifecycle

Assess 149

Closed State 155

Fix in Progress 153

New 149

Resolved State 154

Root Cause Analysis (RCA) 151

Problem Ticket, logging 148

R

RCA, architecture 151

RCA, ensuring 151

RCA, implementing 152 , 153

Reactive Problem Management

about 136

Advantages 137

Characteristics 136

Flow 137

Limitations 137

Scenario 137

Release Deployment 205

Release Deployment, benefits 208

Release Deployment, stages

Build Test 207

Deployment 208

Deployment Preparation 207

Planning 207

Post-Deployment 208

Release Deployment, terms

Back-Out Plan/Rollback 207

Release 206

Release Calendar 207

Release Package 207

Release Unit 206

Request for Change (RFC) 172

Request Fulfilment 91

Request Fulfilment, architecture 95

Request Fulfilment, benefits 93 , 94

Request Fulfilment, characteristics

Automation 96

Focus 96

Process 96

Purpose 95

Request Fulfilment, lifecycle

Closure 92

Fulfillment 92

Request Intake/Submissions 91

Validation/Approval 92

Request Fulfilment, workflow 96

RFC, concepts

Change Approval 173

Change Implementation 174

Initial Review 172

Planning/Scheduling 173

Post-Implementation Review (PIR) 174

Root Cause Analysis (RCA) 151

S

Service 80

Service Catalog 84

Service Catalog, architecture 84

Service Catalog, characteristics

Content 94

Focus 94

Purpose 94

User Interaction 94

Service Catalog, features

Modules Integration 85

Request Workflow 85

Self-Service Capabilities 85

Service Categories 84

Service Items 85

User-Friendly Interface 84

Service Catalog, implementing 86 , 88

Service Catalog, roles

Approver 88

Business Stakeholders 90

Catalog Manager 89

Fulfiller 88

Fulfillment Team 90

Process Onwers 90

Requestor 88

Service Manager 89

ServiceNow Administrators 90

Service Owner 89

Service Catalog, types 85

Service Desk 53 , 58

Service Desk, architecture 54

Service Desk, benefits 60

Service Desk, features 58

Service Desk, forms

Call Center 56

Help Desk 56

Service Desk 56

Service Desk, goals 59

Service Desk, implementing 70 , 71

Service Desk, objectives 60

Service Desk, streamlining 72 - 75

Service Desk, terminologies

Problem Management 55

Service Request 55

Service Desk, types

Centralized 61

Follow-the-Sun 62

Local 61

Multi-Level 64

Outsourced 64

Self-Service 63

Spacialized 63

Virtual 62

Service Level Agreement (SLA) 65

Service Management 4 , 15

Service Management, characteristics 16

Service Management, configuring 16

Service Management, trends

AI/ML 21

Enterprise Service Management (ESM) 22

Shift-Left/Self-Service 20

ServiceNow 27 , 146

ServiceNow, benefits

Automation/AI Capabilities 37

Collaboration/Communication 38

Community/Ecosystem 38

Compliance/Security 38

Comprehensive/Integrated Platform 36

Comprehensive Reporting 38

Robust Integration 37

Scalability/Flexibility 37

Superior User Experience 37

ServiceNow Change Management 174

ServiceNow Change Management, capabilities 174 , 175

ServiceNow Change Management, lifecycle

Assess 179

Authorize 180

Close 182

Implement 181

New 176

Review 182

Schedule 180

ServiceNow, disadvantages

Complexity 39

Customization Challenges 39

High Costs, implementing 39

Performance Concerns 40

Resource Intensive 39

ServiceNow, evolutions 31 , 32

ServiceNow, history 31

ServiceNow, implementing 40 - 44

ServiceNow, inputs

Change Process 146

Incidents 146

ServiceNow, interfaces 44 - 47

ServiceNow, outputs

Accept Risk/Input 147

Known Errors 147

Permanent Fix 147

Request For Change (RFC) 146

ServiceNow, platform

Cloud-Hosted 30

Multi-Instance 30

ServiceNow, products

ITOM 33

ITSM 32

Strategic Portfolio Management (SPM) 33

ServiceNow Security, operations

Security Incident Response 34

Security Operations Center (SOC) 34

Threat Intelligence 34

Vulnerability Response 34

ServiceNow, terms

Automation Flow/Business Processes 28

Centralize Service Management 29

Service Request 55 , 82

Service Request, architecture 82

Service Request, characteristics 55

Service Request, configuring 83

Service Request Management 81

SLA 122

SLA, architecture 66

SLA, implementing 67 , 68

SLA, metrics 69 , 70

SLA, practices 70

SLA, process 65

SLA, scenario 66 , 67

SPM, terms

Agile Development 34

Application Portfolio Management (APM) 34

Financial Management 34

Project Portfolio Management (PPM) 33

Stakeholder 17

Stakeholder, ensuring 19

Stakeholder, types

Service Manager 18

Service Owner 18

Support Teams 19

Users 19

Standard Changes 167

Standard Changes, characteristics 167

Standard Changes, flows 167

T

Traditional Management 15

Traditional Management, architecture 15

Traditional Management, characteristics 15

V

Value 80

Value, architecture 80

Value, concepts 80

Value, process 81

Value Streams 81

Value Streams, architecture 81