Short answer
Service management is the capability to operate services against defined expectations and improve them using incidents, requests, and performance data. It makes service outcomes, ownership, and improvement work visible enough to assess.
About Service management
Operates services against defined expectations and improves them using incidents, requests, and performance data. The competency covers service control and improvement, not the technical repair work itself.
Use this competency for
- Functions accountable for service requests, incidents, service levels, or operational improvement.
- Roles that coordinate service performance across users, support teams, and technical owners.
Do not use this competency for
- Roles that only deliver project work and have no responsibility for an operating service.
Important distinctions
Incident response
Incident response restores service during a disruption. Service management also governs requests, expectations, performance, and improvement across normal operation.
Customer support
Customer support handles user conversations and cases. Service management defines and improves the operating system behind those interactions.
Expectations by level
IC1
Applies service procedures
Handles well-defined requests and service tasks with guidance, follows current priorities and escalation paths, and records work so the service record is complete.
Observable behaviors
- Classifies requests using the current service categories.
- Updates status, owner, and resolution notes before closing work.
- Escalates exceptions with the impact and actions already tried.
Examples
- Closed an access request with the approval and completion evidence attached.
- Escalated a repeated queue failure after linking the affected requests and timestamps.
IC2
Runs a service area
Independently manages an operating service area, resolves ambiguous priority conflicts, and uses request, incident, and performance evidence to improve team workflows.
Observable behaviors
- Reviews service measures and investigates material misses.
- Coordinates owners through a request or incident that crosses teams.
- Changes a workflow after documenting the recurring cause and expected result.
Examples
- Reduced reassignment loops by changing intake fields after reviewing one quarter of tickets.
- Coordinated a service-level miss across support and engineering and recorded the recovery actions.
IC3
Sets service standards
Defines service management standards across teams, frames systemic service problems, and establishes measures and ownership that others use without central direction.
Observable behaviors
- Defines shared service measures, ownership, and exception paths.
- Uses trend evidence to prioritize improvements across service boundaries.
- Reviews whether operating practices produce comparable and useful service data.
Examples
- Introduced one service taxonomy across three teams after mapping conflicting queue definitions.
- Set a cross-team improvement plan after incident and request data showed the same handoff failure.