IT Management Activities Glossary and Definitions
IT Service and Operations Management Glossary
Return to the main IT Leadership Knowledge Base page
Table of Contents
- • IT Service Management
• IT Change Management
• IT Asset Management
• Incident Management
• Problem Management
• Configuration Management (CMDB)
• IT Service Desk / Help Desk Management
• IT Operations Management (ITOM)
• Release and Deployment Management
IT Service Management
IT Service Management (ITSM) is the set of policies, processes, and practices used to design, deliver, manage, and improve the way IT services are provided to an organization’s employees and customers. Rather than focusing purely on technology systems, ITSM treats IT as a service provider, emphasizing the end-to-end experience of consuming IT capabilities and ensuring that services meet defined quality, availability, and performance standards.
The most widely adopted ITSM framework is ITIL (Information Technology Infrastructure Library), which organizes IT service management around a service value chain encompassing planning, engagement, design and transition, obtain and build, deliver and support, and continual improvement. Other frameworks and standards, such as ISO/IEC 20000 and frameworks based on Lean and Agile principles, offer complementary or alternative approaches, particularly for organizations seeking greater speed and flexibility than traditional ITIL implementations.
Core ITSM processes include incident management (restoring service quickly after disruptions), problem management (identifying and eliminating root causes of recurring incidents), change management (controlling the introduction of changes to minimize risk), configuration management (maintaining accurate records of IT assets and their relationships), and service level management (defining and monitoring service quality commitments through SLAs).
A foundational element of ITSM is the service catalog, which provides a structured, user-facing inventory of available IT services, along with clear descriptions, request procedures, and expected fulfillment times. This is typically supported by a service desk or help desk function that serves as the primary point of contact for users seeking support or requesting services.
Modern ITSM has evolved to emphasize business value and user experience over rigid process adherence, incorporating Agile and DevOps principles to increase delivery speed while maintaining appropriate control. Many organizations now measure ITSM effectiveness not just through traditional metrics like mean time to resolution, but through user satisfaction scores and business outcome metrics. Effective ITSM implementation requires appropriate tooling, typically an ITSM platform that automates workflow, tracks service requests and incidents, and provides reporting on service performance, alongside a cultural shift toward treating IT delivery as a customer-centric service rather than a purely technical function.
IT Change Management
IT Change Management is the structured process for controlling the lifecycle of changes to IT systems, infrastructure, and applications, ensuring that modifications are implemented with minimal disruption to business operations and appropriate risk mitigation. Change management is one of the core ITSM disciplines and exists to balance the organization’s need for agility and continuous improvement against the risk that poorly managed changes can cause outages, security vulnerabilities, or service degradation.
The change management process typically categorizes changes by risk and complexity: standard changes (pre-approved, low-risk, routine changes following established procedures), normal changes (requiring assessment and approval through a defined workflow), and emergency changes (urgent changes needed to resolve critical incidents, requiring expedited but still controlled approval). Each category follows an appropriately calibrated level of scrutiny, avoiding the common failure mode of applying heavyweight approval processes to every change regardless of actual risk.
A central governance mechanism in traditional change management is the Change Advisory Board (CAB), a cross-functional group that reviews and approves higher-risk changes, assessing potential impact, required testing, rollback plans, and scheduling conflicts with other planned changes. This process aims to identify conflicts or risks before changes are implemented, rather than discovering problems after deployment.
Effective change management requires thorough documentation of proposed changes, including business justification, technical implementation details, testing evidence, rollback procedures, and communication plans for affected stakeholders. Post-implementation review processes assess whether changes achieved their intended outcomes and whether any unexpected issues arose, feeding lessons learned back into the process.
Modern IT change management has evolved significantly with the adoption of DevOps and continuous delivery practices, which emphasize automated testing, progressive deployment strategies (such as canary releases and feature flags), and a shift toward smaller, more frequent changes rather than large, infrequent releases. This approach, often called “shifting change management left,” embeds risk mitigation into the development pipeline itself rather than relying solely on manual approval gates. Organizations with mature change management practices experience significantly fewer change-related incidents while maintaining the delivery speed necessary to remain competitive.
IT Asset Management
IT Asset Management (ITAM) is the practice of tracking, managing, and optimizing an organization’s IT assets throughout their lifecycle, from procurement through deployment, maintenance, and eventual retirement or disposal. Assets under management typically include hardware (servers, laptops, networking equipment), software licenses, and increasingly, cloud resources and digital assets.
ITAM is often divided into two closely related disciplines: Hardware Asset Management (HAM), which tracks physical devices and infrastructure, and Software Asset Management (SAM), which focuses specifically on software licensing compliance, utilization, and optimization. Both disciplines share the common goal of maintaining an accurate, real-time inventory that supports informed decision-making about technology investments and risk.
A core function of ITAM is maintaining a Configuration Management Database (CMDB) or asset repository that records detailed information about each asset, including ownership, location, configuration, warranty status, and relationships to other assets and services. This data underpins numerous other IT management functions, including change management (understanding what will be affected by a proposed change), incident management (identifying which assets are involved in a service disruption), and security management (ensuring all assets receive appropriate patches and security controls).
Software Asset Management carries particular importance given the financial and legal risk associated with license compliance. Organizations must track license entitlements against actual usage to avoid both under-licensing (which creates compliance and audit risk) and over-licensing (which wastes budget on unused capacity). Regular software audits, whether self-initiated or vendor-driven, require accurate ITAM data to defend against compliance claims and potential penalties.
As organizations increasingly adopt cloud and SaaS models, ITAM practices have expanded to include cloud asset management, tracking virtual resources, subscription-based licensing, and usage-based billing models that behave very differently from traditional perpetual license and on-premises hardware models. Effective ITAM requires ongoing discovery and reconciliation processes, since assets are added, moved, and retired continuously, and manual tracking quickly becomes unreliable at scale. Organizations with mature ITAM practices realize significant cost savings through license optimization and asset lifecycle planning, while also reducing security and compliance risk from unknown or unmanaged assets.
Incident Management
Incident Management is the process responsible for restoring normal service operation as quickly as possible following an unplanned interruption or reduction in service quality, minimizing adverse impact on business operations. It is one of the most visible and operationally critical ITSM disciplines, as incidents directly affect end users and can have significant business and financial consequences if not resolved promptly.
The incident management process typically begins with detection and logging, whether through automated monitoring alerts, user-reported tickets, or proactive identification by IT staff. Each incident is then categorized and prioritized based on factors such as business impact and urgency, often using a standardized priority matrix that determines response time expectations and escalation procedures.
A critical element of effective incident management is clear escalation pathways, ensuring that incidents beyond the initial responder’s expertise or authority are quickly routed to appropriate specialist teams or more senior staff. For major incidents with significant business impact, organizations typically activate a formal major incident process, which may include establishing a dedicated incident commander, setting up a war room or virtual bridge for real-time coordination, and providing regular stakeholder communications until resolution.
Modern incident management increasingly incorporates practices from Site Reliability Engineering (SRE), including blameless post-incident reviews that focus on systemic improvement rather than individual fault-finding, and the use of service level objectives (SLOs) and error budgets to balance reliability investment against feature development velocity. Automation plays an increasingly important role, with AIOps (AI for IT Operations) platforms helping to detect anomalies, correlate related alerts, and in some cases automatically remediate common issues without human intervention.
Effective incident management requires robust monitoring and observability tooling to detect issues quickly, clear runbooks and documentation to guide response, and well-defined communication protocols to keep stakeholders informed throughout the incident lifecycle. Post-incident reviews are essential for continuous improvement, capturing root causes, contributing factors, and actionable follow-up items that feed into problem management processes. Organizations that measure and continuously improve metrics like mean time to detect (MTTD) and mean time to resolve (MTTR) demonstrate stronger operational resilience and reduced business disruption from IT service failures.
Problem Management
Problem Management is the ITSM discipline focused on identifying, analyzing, and eliminating the root causes of incidents to prevent their recurrence, distinguishing it from incident management’s focus on rapid restoration of service. Where incident management asks “how do we get service back up quickly,” problem management asks “why did this happen, and how do we ensure it never happens again.”
The discipline distinguishes between known errors (problems with documented root causes and workarounds, even if a permanent fix hasn’t yet been implemented) and unresolved problems still under investigation. A Known Error Database (KEDB) serves as a critical knowledge asset, allowing support teams to quickly identify workarounds for recurring issues even before permanent fixes are deployed, significantly reducing resolution time for repeat incidents.
Problem management operates in two modes: reactive problem management, which investigates root causes after incidents have occurred, particularly recurring or high-impact incidents, and proactive problem management, which analyzes trends and patterns across the incident history to identify potential problems before they cause significant business impact. Techniques such as root cause analysis (RCA), the “five whys” method, and fishbone diagrams are commonly used to systematically identify underlying causes rather than settling for superficial explanations.
Effective problem management requires strong collaboration between problem managers and technical subject matter experts, as well as clear linkage to change management, since implementing permanent fixes for identified problems typically requires formal changes to be planned, tested, and deployed. Organizations must also balance the resource investment in problem management against other operational priorities, as thorough root cause analysis can be time-intensive and may compete with other pressing work.
A mature problem management practice tracks metrics such as the number of known errors with pending fixes, the reduction in repeat incidents over time, and the percentage of major incidents that undergo formal post-incident review. Organizations with strong problem management capabilities experience declining incident volumes over time as underlying issues are systematically eliminated, rather than the same incidents recurring indefinitely because only symptoms, not root causes, are addressed. This proactive orientation ultimately reduces long-term operational costs and improves overall service reliability.
Configuration Management (CMDB)
Configuration Management is the ITSM discipline responsible for maintaining accurate, up-to-date information about IT assets, known as Configuration Items (CIs), and the relationships between them. This information is typically stored in a Configuration Management Database (CMDB), which serves as a foundational data source supporting numerous other IT management processes.
Configuration Items can include hardware components, software applications, network devices, documentation, and even services themselves, along with their attributes (such as version, location, and owner) and their relationships to other CIs (such as which applications run on which servers, or which services depend on which infrastructure components). This relationship mapping is often visualized as a service map or dependency map, providing critical visibility into how changes or failures in one component might cascade to affect other systems and services.
The value of configuration management becomes particularly apparent during incident response, where understanding CI relationships allows technical teams to quickly identify what might be causing a service disruption or what else might be affected by a failing component. Similarly, change management relies heavily on CMDB data to assess the potential impact and risk of proposed changes before they are approved and implemented.
Maintaining CMDB accuracy is one of the most persistent challenges in configuration management, as the underlying IT environment changes constantly through new deployments, decommissions, and reconfigurations. Manual CMDB maintenance quickly becomes unreliable at any meaningful scale, leading most mature organizations to invest in automated discovery tools that continuously scan the environment and reconcile findings against the CMDB, flagging discrepancies for review.
Modern configuration management practices have evolved alongside infrastructure-as-code and cloud-native architectures, where configuration is increasingly defined and version-controlled in code rather than manually documented after the fact. This shift enables more accurate, real-time configuration tracking but also requires new tooling and practices to maintain visibility across increasingly dynamic, ephemeral cloud infrastructure. Effective configuration management provides the factual foundation that underpins reliable incident management, informed change decisions, accurate asset management, and overall IT operational visibility.
IT Service Desk / Help Desk Management
IT Service Desk (or Help Desk) Management is the discipline of operating the primary point of contact between IT and the end users it serves, handling incidents, service requests, and general technology inquiries. While often used interchangeably, “help desk” traditionally refers to a more narrowly focused, reactive support function, while “service desk” reflects a broader, more strategic role encompassing request fulfillment, service catalog management, and alignment with overall ITSM processes.
Service desk management encompasses several key operational considerations: staffing models (whether support is provided through tiered levels, with Tier 1 handling common issues and escalating complex problems to Tier 2 and Tier 3 specialists), channel strategy (supporting users through phone, email, chat, self-service portals, and increasingly AI-powered virtual agents), and coverage models (determining hours of operation, including whether follow-the-sun support is needed for global organizations).
A critical success factor for service desk operations is the first-call resolution rate, measuring the percentage of issues resolved during the initial contact without requiring escalation or follow-up, as higher first-call resolution directly correlates with both user satisfaction and operational efficiency. Service level agreements (SLAs) typically define expected response and resolution times based on incident priority, providing accountability and clear expectations for both IT and the business.
Modern service desk management increasingly emphasizes self-service capabilities, including knowledge base articles, automated password resets, and AI-powered chatbots that can resolve common issues without human intervention, reducing overall ticket volume and freeing human agents to focus on more complex issues. Shift-left strategies aim to resolve issues at the earliest, lowest-cost point of contact, whether through self-service or improved Tier 1 capabilities, rather than routinely escalating to more expensive specialist resources.
Effective service desk management also requires robust ticketing and workflow tools to track requests from intake through resolution, comprehensive knowledge management to capture and reuse solutions, and regular analysis of ticket trends to identify opportunities for automation or proactive problem resolution. Organizations increasingly measure service desk success not just through traditional operational metrics like resolution time, but through user satisfaction scores and the strategic value the service desk provides as the human face of IT to the broader organization.
IT Operations Management (ITOM)
IT Operations Management (ITOM) encompasses the processes, tools, and practices used to monitor, manage, and maintain the ongoing health, performance, and availability of an organization’s IT infrastructure and services. While ITSM focuses on the processes governing how IT services are delivered and supported, ITOM focuses more specifically on the technical management of the underlying infrastructure that makes those services possible.
Core ITOM functions include infrastructure monitoring (tracking the health and performance of servers, networks, storage, and cloud resources), event management (correlating and prioritizing alerts generated across the technology environment to identify meaningful issues amid the noise), capacity management (ensuring sufficient infrastructure resources are available to meet current and projected demand), and availability management (ensuring systems and services meet defined uptime and performance targets).
Modern ITOM has been significantly reshaped by the shift to cloud and hybrid infrastructure, requiring tools capable of providing unified visibility across on-premises data centers, multiple public cloud providers, and edge computing environments. This complexity has driven adoption of AIOps (Artificial Intelligence for IT Operations) platforms, which apply machine learning to infrastructure and application telemetry data to detect anomalies, predict potential failures before they occur, and in some cases automatically trigger remediation actions.
Observability has become a central concept in modern ITOM practice, extending beyond traditional monitoring to provide deeper insight into system behavior through the combination of metrics, logs, and distributed tracing data. This is particularly critical in modern microservices and cloud-native architectures, where traditional monitoring approaches struggle to provide meaningful visibility into complex, distributed system interactions.
Effective ITOM requires careful balance between comprehensive monitoring coverage and alert fatigue, as overly sensitive or poorly tuned monitoring generates excessive noise that causes operations teams to miss genuinely critical issues among a flood of low-value alerts. Automation plays an increasingly central role, not just in detection but in remediation, with self-healing infrastructure capabilities reducing the need for manual intervention for well-understood, recurring issues. Organizations with mature ITOM capabilities achieve higher system availability, faster mean time to detection and resolution for infrastructure issues, and more efficient use of operations staff, who can focus on strategic improvements rather than constant reactive firefighting.
Release and Deployment Management
Release and Deployment Management is the ITSM discipline responsible for planning, scheduling, and controlling the movement of new or changed software and infrastructure into production environments. It bridges the gap between development activities and operational service delivery, ensuring that releases are deployed in a controlled, predictable manner that minimizes risk to business operations.
The discipline encompasses release planning (determining what changes will be bundled into a given release and when it will occur), build and test coordination (ensuring releases are properly validated before deployment), deployment execution (the actual technical process of moving code and configuration into production), and post-deployment verification (confirming the release achieved its intended outcome without introducing new issues).
Traditional release management often followed a “big bang” model, bundling numerous changes into large, infrequent releases that required extensive coordination and carried significant risk if problems emerged, since diagnosing which of many simultaneous changes caused an issue could be time-consuming. Modern DevOps and continuous delivery practices have shifted many organizations toward smaller, more frequent releases, reducing the blast radius of any individual deployment and making problems easier to diagnose and roll back.
Contemporary release management increasingly employs progressive deployment strategies such as blue-green deployments (maintaining two identical production environments and switching traffic between them), canary releases (gradually rolling out changes to a small subset of users before full deployment), and feature flags (deploying code but controlling feature activation independently of deployment, allowing gradual rollout or instant rollback without redeployment).
Effective release management requires close coordination with change management to ensure appropriate risk assessment and approval, particularly for high-impact releases, as well as robust automated testing and deployment pipelines that reduce manual error and increase deployment velocity. Rollback planning is a critical component, ensuring that if a release causes unexpected issues, the organization can quickly and safely revert to the previous stable state. Organizations with mature release management practices, particularly those embracing continuous delivery principles, are able to deploy changes far more frequently while simultaneously experiencing fewer deployment-related incidents, demonstrating that speed and stability are not inherently in tension when proper practices are in place.