English:IT Service Management
IT Service Management
Introduction
IT Service Management (ITSM) is the coordinated management of people, practices, information, technology, partners, and workflows used to design, deliver, support, and continually improve digital services. Its central question is not simply whether a server, application, or network is functioning. The stronger question is: Does the service enable useful outcomes for users and the organization at an acceptable level of cost and risk?
For university students, ITSM offers a bridge between technical computing and organizational management. You learn to connect systems engineering, user experience, governance, risk, operations, data, and business strategy. ITSM is therefore relevant to Information technology, Information systems, Computer science, Business administration, Cybersecurity, and Digital transformation.
A network operations center illustrates one operational setting in which teams monitor services and coordinate responses. ITSM is broader than operations alone: it also includes planning, relationship management, service design, change, knowledge, measurement, and improvement.
The video introduces the current ITIL Foundation (Version 5) perspective. Use it as a starting point, but remember that ITSM is the discipline while ITIL is one influential body of guidance for practicing that discipline.
Learning Objectives
After working through this aiMOOC, you should be able to:
- Explain services and value: Distinguish services, products, outputs, outcomes, costs, risks, utility, warranty, and experience.
- Analyze ITSM systems: Explain how people, information, technology, suppliers, practices, and value streams interact.
- Manage operational scenarios: Differentiate incidents, service requests, problems, changes, events, and known errors.
- Evaluate service levels: Select indicators that connect technical performance with user and business outcomes.
- Improve services: Use evidence, feedback, and iterative improvement to identify and test changes.
- Compare frameworks: Relate ITIL, ISO/IEC 20000, COBIT, DevOps, Agile, and SRE without treating them as interchangeable.
- Assess automation and AI: Evaluate opportunities, limitations, governance needs, and human accountability in AI-enabled service management.
What Is a Service?
A service enables value co-creation by helping consumers achieve desired outcomes without requiring them to manage every specific cost and risk themselves. A university learning platform, for example, is not merely a web application. The service includes identity access, hosting, support, integrations, data protection, availability, documentation, change communication, and the experience of students and staff.
A useful service-management analysis separates several ideas:
- Output: A produced deliverable, such as a restored database or deployed software release.
- Outcome: A result enabled for a stakeholder, such as students being able to submit assignments before a deadline.
- Utility: What the service does and whether it is fit for purpose.
- Warranty: How reliably the service performs and whether it is fit for use under agreed conditions.
- Risk: Uncertainty that may affect objectives, including service interruptions, security failures, supplier failures, or poor adoption.
- Experience: How stakeholders perceive and interact with the service across its lifecycle.
A technically successful output can still fail to create value. For example, an IT team may close a ticket within its target time while the user still cannot complete the task that motivated the request. Strong ITSM therefore combines operational measures with outcome and experience measures.
Value Co-Creation and Stakeholders
Value is not created by the provider alone. Providers, customers, users, sponsors, suppliers, and other stakeholders contribute needs, resources, decisions, feedback, and capabilities. This is why service management depends on relationship quality, transparent expectations, and shared information.
For a campus Wi-Fi service, the network team may provide infrastructure and monitoring, a cloud supplier may provide identity services, students and staff provide demand and feedback, cybersecurity staff define controls, and university leaders fund the service. No single participant creates the whole result.
ITIL and the Current Framework Landscape
ITIL (Version 5) is the current evolution of ITIL. It extends digital product and service management for complex, AI-enabled environments while retaining central ideas such as value co-creation, the ITIL Value System, guiding principles, four dimensions, management practices, value streams, and continual improvement. It also introduces a more explicit product-and-service lifecycle perspective and gives greater attention to experience, responsible AI, resilience, and sustainability.
ITIL 4 remains important because many organizations, courses, certifications, and implementations still use it. The transition should therefore be understood as an evolution rather than a complete reset.
The ITIL Value System
The ITIL Value System connects demand and opportunity with activities and capabilities that create value. Its major elements include:
- Guiding principles: Recommendations used to support decisions in varied situations.
- Governance: Direction and control so that priorities, risk, accountability, and performance are managed coherently.
- Value chain activities: Interconnected activities used to create and deliver value.
- Management: Organizational practices that provide resources and capabilities for accomplishing objectives.
- Continual improvement: Ongoing improvement at strategic, tactical, and operational levels.
The familiar ITIL guiding principles include focus on value, start where you are, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, and optimize and automate. They are useful because they guide judgment rather than prescribing a single workflow.
Four Dimensions of Product and Service Management
A service should be analyzed through four connected dimensions:
- Organizations and people: Roles, skills, culture, communication, leadership, and capacity for change.
- Information and technology: Data, applications, infrastructure, automation, security, architecture, and knowledge.
- Partners and suppliers: External providers, contracts, dependencies, sourcing strategies, and shared responsibilities.
- Value streams and processes: End-to-end flows that transform demand and opportunities into outcomes.
The dimensions prevent a common failure mode: trying to solve a service problem using technology alone when the root cause is actually unclear ownership, poor data, a supplier dependency, or a broken workflow.
DevOps illustrates why ITSM increasingly emphasizes cross-functional work. Development, quality, operations, security, support, and product roles need shared feedback loops and common outcomes rather than isolated optimization.
Product and Service Lifecycle Thinking
ITIL (Version 5) strengthens lifecycle thinking for digital products and services. A useful lifecycle view includes discover, design, acquire, build, transition, operate, deliver, and support. These activities should not be treated as a rigid waterfall sequence. Real value streams may revisit activities repeatedly as teams learn from telemetry, incidents, users, changing risks, and new opportunities.
Lifecycle thinking helps you ask questions such as: What user need are we discovering? What must be designed for reliability and accessibility? Which capabilities should be acquired rather than built? How will the change enter production? How will the service be operated, delivered, supported, measured, and improved?
Core ITSM Practices
Service Desk and Service Request Management
The service desk provides a communication interface between users and the service provider. A mature service desk does more than log tickets. It captures demand, provides context, resolves common issues, coordinates escalation, communicates status, improves knowledge, and learns from repeated interactions.
A service request is usually a predefined, user-initiated request such as access to software, a password reset, equipment provisioning, or information. Good request management standardizes routine work where appropriate, exposes clear request options, automates predictable steps, and preserves human support for exceptions or sensitive cases.
Incident Management
An incident is an unplanned interruption to a service or a reduction in service quality. The main purpose of incident management is to restore normal service operation quickly enough to limit negative impact. Effective incident response depends on prioritization by impact and urgency, ownership, diagnosis, escalation, communication, recovery, and learning.
Major incidents require especially clear coordination. Technical recovery is only one workstream; stakeholder communication, decision authority, evidence preservation, and post-incident learning are also essential.
This Atlassian session provides a practical view of incident response and blameless post-incident learning. While tools and terminology vary, the transferable lesson is that organizations need explicit roles, communication routines, and learning loops.
A public status page is one mechanism for communicating service condition, incidents, and planned maintenance. Communication quality affects trust even when the technical repair takes time.
Problem Management
A problem is a cause, or potential cause, of one or more incidents. Incident management restores service; problem management reduces the likelihood or impact of recurrence. A workaround can reduce impact without removing the underlying cause, while a known error records a problem that has been analyzed but not necessarily eliminated.
Useful problem-analysis methods include timeline reconstruction, causal analysis, fault-tree thinking, trend analysis, and the Five Whys. Avoid reducing complex socio-technical failures to a single person's action. Systems, incentives, interfaces, workload, procedures, and safeguards can all shape outcomes.
Change Enablement
A change adds, modifies, or removes something that may directly or indirectly affect services. Change enablement aims to increase the number of successful changes by assessing risk, authorizing changes appropriately, and managing schedules and dependencies without turning every change into a slow approval ritual.
Many organizations distinguish low-risk pre-authorized standard changes, assessed normal changes, and urgent emergency changes. The appropriate control should be proportional to risk. Automated testing, peer review, progressive delivery, observability, and rollback capability can reduce change risk while preserving speed.
The video demonstrates a change-management workflow. Use it to examine how risk, approvals, collaboration, and deployment information can be connected rather than handled in isolated systems.
Continuous delivery shows how technical feedback, automated checks, and deployment controls can become part of a managed flow. ITSM and continuous delivery are compatible when governance is built into the value stream rather than added only at the end.
Service Configuration and IT Asset Management
Service configuration management maintains information about configuration items and their relationships where that information is useful for service management. A configuration item might be an application, database, virtual machine, network component, document, service, or supplier dependency.
IT asset management focuses on the lifecycle, value, cost, risk, contractual status, and accountability of technology assets. Configuration and asset data overlap, but they answer different questions. A configuration model is useful only if its data is sufficiently accurate, timely, and connected to decisions. Collecting every possible attribute can create cost without value.
Knowledge Management
Knowledge management makes useful information available to the right people at the right time. Good knowledge is findable, current, understandable, evidence-based, and connected to real tasks. Incident records, problem analyses, workarounds, architecture decisions, service instructions, and user guidance can all contribute to organizational learning.
Generative AI can help search, summarize, classify, or draft knowledge, but it also creates risks: hallucinated procedures, stale answers, privacy leakage, biased recommendations, and unclear accountability. Human review, source traceability, access controls, feedback, and retirement of obsolete content remain important.
Service Levels, Measurement, and Experience
A service-level agreement (SLA) documents agreed service expectations between provider and customer. Useful service measures might include availability, response time, recovery time, request fulfillment time, change failure rate, security performance, customer effort, task completion, and stakeholder satisfaction.
No single metric is sufficient. Metrics can be gamed when people optimize the number rather than the intended outcome. For example, a target for fast ticket closure can encourage premature closure. You should therefore connect operational metrics to outcomes and experience, examine trends rather than isolated numbers, and discuss trade-offs explicitly.
Reliability Concepts
Reliability engineering complements ITSM. Common terms include:
- SLI: A measured characteristic of service behavior, such as successful-request ratio.
- SLO: A target range for an SLI.
- SLA: A documented agreement that may include service targets, responsibilities, and consequences.
- MTTR: A time-based measure used in different ways across organizations, so its definition must be made explicit.
- Error budget: The amount of unreliability tolerated relative to a reliability objective, often used to balance change velocity and stability.
This Google Cloud session on Site Reliability Engineering shows how monitoring, error budgets, emergency response, toil reduction, and blameless learning can complement service-management practices.
Continual Improvement
Continual improvement is not a final phase that begins after service delivery. It is a recurring activity throughout strategy, design, operation, support, and transformation. A sound improvement cycle asks what the current situation is, what target condition is desired, which changes are feasible, how effects will be measured, and what has been learned.
The Plan-Do-Check-Act cycle is a classic model for iterative improvement. In ITSM, the same mindset can be applied to a service, a workflow, a knowledge base, a supplier relationship, or the measurement system itself.
A practical improvement register can record the problem or opportunity, evidence, expected value, owner, priority, risk, action, experiment, measure, and result. Small improvements often outperform large redesigns when teams can learn quickly and adjust.
Visualizing Flow
A value stream shows how work and information move from demand or opportunity toward value. Mapping helps reveal queues, delays, handoffs, rework, unnecessary approvals, missing feedback, and automation opportunities.
A Kanban board can make work visible and help teams reason about flow, work in progress, bottlenecks, and blocked items. Visualization is useful only when it supports decisions and collaboration; it should not become reporting theater.
Standards, Governance, and Complementary Approaches
ISO/IEC 20000
ISO/IEC 20000-1:2018 specifies requirements for establishing, implementing, maintaining, and continually improving a service management system. It addresses the planning, design, transition, delivery, and improvement of services. Unlike ITIL guidance, an organization's service management system can be assessed against the requirements of the ISO standard for a defined scope. The 2018 edition remains current and has a 2024 amendment concerning climate-action changes in management-system standards.
COBIT
COBIT is a framework for governance and management of enterprise information and technology. It complements ITSM by emphasizing governance objectives, accountability, stakeholder needs, risk, performance, and alignment between enterprise goals and information-and-technology decisions. ITIL is commonly used to guide product and service management practices, while COBIT can help frame governance and control at a broader enterprise level.
Agile, DevOps, and SRE
Agile emphasizes iterative learning and adaptive delivery. DevOps emphasizes collaboration and fast, reliable flow across development and operations. SRE applies software-engineering approaches to operational reliability. ITSM can coordinate these approaches by clarifying services, stakeholders, risk, support, governance, and continual improvement.
The productive question is not "Which framework wins?" but "Which concepts help this organization create and protect value in this context?" Rigid process bureaucracy can damage flow, while uncontrolled speed can damage reliability, security, compliance, and trust.
AI, Automation, and Modern ITSM
Automation is valuable when it removes avoidable effort, reduces delay, improves consistency, or increases observability. Examples include automated request fulfillment, event correlation, dependency discovery, test execution, change-risk signals, knowledge retrieval, and routing.
AI expands these possibilities through language interfaces, pattern detection, summarization, recommendation, and agentic workflows. However, service-management decisions can affect access rights, customer communications, security, finances, and business continuity. AI-enabled ITSM therefore needs governance proportional to impact.
You should ask:
- Purpose and accountability: What decision is automated, who remains responsible, and when must a person intervene?
- Data quality and provenance: Which data trains or informs the system, and is it current, authorized, and representative?
- Security and privacy: Could prompts, logs, model outputs, or integrations expose confidential information?
- Fairness and accessibility: Could prioritization or self-service work worse for some users?
- Explainability and auditability: Can important recommendations be traced and reviewed?
- Resilience: What happens when the AI service is unavailable, wrong, or manipulated?
The current ITIL (Version 5) places stronger emphasis on digital product and service management in AI-enabled environments and includes responsible AI as a visible area of professional practice.
Designing an ITSM Operating Model
An operating model translates principles into responsibilities, information flows, tools, and decision rights. A university IT department could organize around services such as identity, learning platforms, research computing, networks, collaboration tools, and student systems rather than around technical components alone.
A useful design process can begin with a service and stakeholder map, then identify value streams and failure modes, define roles, decide what evidence is needed, establish interfaces with suppliers and security teams, and choose tools only after the workflow and information needs are understood.
Operational centers and service desks can act as coordination hubs, but effective service management is distributed across the organization. Product owners, developers, architects, security specialists, suppliers, managers, users, and support staff all contribute to service outcomes.
Example: University Learning Platform
Imagine that the learning platform becomes unavailable during a final examination. Monitoring detects failed requests, students report inability to submit answers, and the service desk declares a major incident. Incident management coordinates restoration and communication. A status page keeps stakeholders informed. Service configuration data helps identify dependencies. Supplier management engages the cloud provider. Security staff verify that the outage is not an attack.
After recovery, problem management investigates contributing conditions. Change enablement evaluates a proposed fix. Continual improvement turns lessons into actions such as capacity testing, clearer escalation thresholds, improved observability, and an updated communication plan. Service-level management reviews whether the targets reflected the real academic impact. The result is not merely a closed ticket; it is a more resilient service and a better future user experience.
Interactive Tasks
Quiz: Test Your Knowledge
Which statement best describes IT Service Management? (Managing services to enable stakeholder outcomes and value) (!Managing only servers and networks) (!Purchasing technology at the lowest cost) (!Writing software without operational responsibility)
What is the main purpose of incident management? (Restore normal service operation as quickly as appropriate) (!Identify every root cause before restoring service) (!Approve every software deployment) (!Negotiate all supplier contracts)
What distinguishes problem management from incident management? (It addresses causes or potential causes of incidents) (!It is used only for password reset requests) (!It replaces service-level management) (!It measures only customer satisfaction)
Which ITIL dimension focuses on external providers and dependencies? (Partners and suppliers) (!Organizations and people) (!Information and technology) (!Value streams and processes)
What is a service-level objective? (A target value or range for a service-level indicator) (!A complete inventory of configuration items) (!A mandatory software development method) (!A list of unresolved incidents)
Which change is most suitable for a predefined low-risk procedure? (A standard change) (!An unknown major incident) (!A new strategic objective) (!An unassessed emergency)
Why can a ticket-closure metric be misleading? (It can reward closing work before the user outcome is achieved) (!It always measures customer value perfectly) (!It cannot be recorded automatically) (!It makes incident communication impossible)
What is the purpose of a configuration model? (Provide useful information about configuration items and relationships) (!Store every possible technical attribute forever) (!Replace all monitoring tools) (!Eliminate the need for service owners)
How does ISO/IEC 20000-1 differ from ITIL guidance? (It specifies auditable service management system requirements) (!It is only a software product) (!It forbids continual improvement) (!It applies only to network hardware)
Which principle best supports gradual improvement based on learning? (Progress iteratively with feedback) (!Avoid all measurement) (!Centralize every decision) (!Automate before understanding the work)
Memory Game
| Incident | Unplanned interruption or reduction in service quality |
| Problem | Cause or potential cause of one or more incidents |
| Workaround | Temporary approach that reduces or eliminates impact |
| Service desk | Communication interface between users and service provider |
| SLO | Target value or range for a measured service indicator |
| Value stream | Connected activities that move demand toward an outcome |
| Known error | Analyzed problem that has not necessarily been permanently removed |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Restore service quickly | Incident management |
| Reduce recurrence by analyzing causes | Problem management |
| Assess and authorize service-affecting modifications | Change enablement |
| Agree and review service expectations | Service level management |
| Capture and share useful operational knowledge | Knowledge management |
...
Crossword Puzzle
| Incident | What term describes an unplanned interruption to a service? |
| Problem | What term describes a cause or potential cause of incidents? |
| Service | What enables value by helping consumers achieve desired outcomes? |
| Warranty | What term describes whether a service is fit for use under agreed conditions? |
| Supplier | What type of external party may provide technology or capabilities to a service? |
| Improvement | What recurring activity seeks better performance and outcomes over time? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- Service Mapping: Choose a digital service you use at university and create a one-page map showing users, provider teams, suppliers, technologies, and the main outcome the service enables.
- Ticket Classification: Write ten realistic support examples and classify each as an incident, service request, problem signal, or change request; justify every classification in one sentence.
- Service Metrics: Design a small dashboard with three technical measures and three user-outcome or experience measures for a campus Wi-Fi service, then explain why each measure matters.
- Incident Communication: Produce a short status-page update for a fictional learning-platform outage, including impact, current action, workaround if available, and the time of the next update.
Standard
- Value Stream Mapping: Interview two people who participate in an IT support workflow, map the steps from demand to outcome, identify delays or rework, and propose two measurable improvements.
- Service Desk Observation: With appropriate permission, visit or interview a university or organizational service desk and document roles, escalation paths, knowledge use, recurring request types, and privacy safeguards.
- Change Risk Analysis: Create a risk assessment for upgrading an authentication service, including dependencies, testing, authorization, communication, rollback, monitoring, and post-implementation review.
- Problem Analysis: Build a causal diagram for a recurring fictional outage and show how technical, organizational, supplier, and process factors could interact; avoid blaming a single individual.
Advanced
- ITSM Operating Model: Design an operating model for a medium-sized university IT organization, showing service ownership, governance, support tiers, value streams, supplier interfaces, metrics, and continual-improvement responsibilities.
- Service Management Experiment: Run a small controlled experiment on a real or simulated workflow, such as knowledge search or request intake, define a baseline and success measure, collect data, and evaluate whether the change improved the outcome.
- AI Governance for ITSM: Prototype an AI-assisted service-desk use case and write a governance brief covering purpose, data access, human oversight, failure modes, security, bias, auditability, and fallback procedures.
- Framework Comparison: Produce a research poster or short video comparing ITIL, ISO/IEC 20000, COBIT, DevOps, and SRE using one case study; explain where the approaches complement each other and where their purposes differ.
Learning Assessment
- Major Incident Case Analysis: Analyze a scenario in which a cloud-based examination system fails during peak use; create an incident command structure, communication plan, recovery priorities, evidence needs, and a post-incident learning agenda.
- Service Level Design: Given a student information service with different user groups, propose SLIs, SLOs, and experience measures; justify how your design balances reliability, cost, risk, accessibility, and academic impact.
- Change Governance Decision: Compare two possible deployment strategies for a high-risk identity-service change and defend one using risk, rollback capability, testing evidence, user impact, and governance requirements.
- Value Stream Improvement: Evaluate a request-fulfillment process with long queues and repeated approvals; redesign the flow, identify automation opportunities, and explain how you would test whether the redesign actually improves value.
- Framework Integration: Recommend how an organization could combine ITIL guidance, ISO/IEC 20000 requirements, COBIT governance, and DevOps or SRE practices without duplicating controls or creating contradictory accountabilities.
- AI Service Management Review: Assess an AI agent that can resolve support requests autonomously; define which request types it may handle, which must be escalated, what evidence must be logged, and what conditions should trigger suspension of automation.
Evidence of Learning
Strong evidence of learning goes beyond recalling definitions. You should be able to demonstrate:
- Knowledge: Accurate use of service-management concepts, including value, service, outcome, incident, problem, change, service level, configuration, governance, and continual improvement.
- Systems thinking: Ability to connect people, technology, suppliers, information, processes, risks, and stakeholder experience in one service model.
- Analytical skill: Ability to interpret incidents, metrics, dependencies, value streams, and failure patterns using evidence rather than assumption.
- Design skill: Ability to create workable service models, communication plans, measures, controls, and improvement experiments.
- Professional communication: Clear writing, visual explanation, stakeholder interviewing, incident communication, and reasoned presentation of trade-offs.
- Responsible automation: Ability to distinguish suitable automation from decisions that require stronger oversight, contextual judgment, or human accountability.
- Transfer: Ability to apply ITSM ideas to unfamiliar contexts such as higher education, healthcare, public services, cloud platforms, research computing, or AI-enabled services.
- Products: A portfolio containing service maps, value-stream diagrams, incident analyses, metric designs, risk assessments, governance briefs, or improvement reports.
OERs on the Topic
The English Wikipedia article on IT service management provides an openly accessible overview of the discipline and related frameworks.
For current professional reference, compare the open information pages from the official organizations responsible for major frameworks and standards:
- PeopleCert ITIL Foundation Version 5: Current overview of ITIL Foundation learning themes.
- ISO/IEC 20000-1:2018: Official ISO overview of service management system requirements.
- ISACA COBIT: Official overview of COBIT for governance and management of enterprise information and technology.
- IBM IT Service Management: Freely accessible introduction to ITSM concepts and business context.
- Wikimedia Commons Network Operations Center media: Open media that can support discussion of operational monitoring environments.
Linked Learning Areas
The following navigation table connects IT Service Management with its essential concepts and neighboring fields.
Key Takeaways
ITSM treats technology as part of a service system whose purpose is to enable outcomes and value. Effective practice combines user needs, operational reliability, governance, risk, data, suppliers, knowledge, and continual improvement. ITIL provides adaptable guidance, ISO/IEC 20000 provides auditable service-management-system requirements, and COBIT addresses broader governance and management of enterprise information and technology.
Modern ITSM should not become ticket bureaucracy. It should make work visible, improve flow, restore services effectively, reduce recurring failure, support responsible change, learn from evidence, and connect technical performance with human and organizational outcomes. As automation and AI become more capable, this systems perspective becomes more important because speed without trustworthy governance can scale errors just as quickly as it scales useful work.