IT Service Manager
IT
SmartSuite for the IT Service Manager
The IT Service Manager owns the service management practices: the service catalog, SLAs, process ownership for incident, problem, change and request, continual improvement and business relationship management. They make sure services are defined, measured, improving and understood by their business customers.
Reports to:
What you own
The IT Service Manager owns the service management practices: the service catalog, SLAs, process ownership for incident, problem, change and request, continual improvement and business relationship management.
- Own the service catalog and service level agreements
- Own ITSM process design, metrics and continual improvement
- Oversee incident, problem, change and request practices
- Manage business relationships and service reviews
- Govern the ITSM toolset and its configuration
- Report service performance against SLAs
Reporting lines
Who this role reports to, who reports to them, and the peers they work with most.
Reports to
Chief Information Officer
See the roleDirect reports
Service Desk Manager
See the roleChange and Release Manager
See the roleIncident and Problem Manager
See the roleIT Asset Manager
See the roleConfiguration Manager
See the roleWorks closely with
IT Operations Director
See the roleGRC Platform Administrator
See the roleIT Compliance Manager
See the roleHow SmartSuite supports the IT Service Manager
The IT Service Manager owns the service catalog, SLAs and the practices behind them, and the CIO and business customers judge the function on whether services are defined, measured and improving. SmartSuite gives every practice one structure, one set of rules and one history, so service reviews draw on live performance, not last month's extract.
Own the catalog, the SLAs and the practices
Consistent categories, priorities, ownership and queues apply across incident, problem, change and request, so the Service Desk Manager's analysts and the Change and Release Manager classify work the same way and your metrics compare like with like.
ITSM suiteResponse and resolution times, breaches and escalations are tracked consistently against each service level, so the OLA you agreed with the IT Operations Director is measured the same way as the SLA you promised the business.
ITSM suiteNo-code adaptability lets you evolve workflows, SLAs, forms and views as the practice matures, so governing the ITSM toolset means changing a rule, not raising a development ticket.
ITSM suiteStay connected to operations, assets and compliance
Automated routing and triage assign tickets on category, urgency and your rules, so a request reaches the right queue without a dispatcher and the Service Desk Manager's team starts on the work, not the sorting.
ITSM suiteChange governance manages approvals, scheduling and CAB-style controls in the same workspace as incidents, so the Change and Release Manager and the IT Operations Director see what a change touched when an incident follows it.
ITSM suiteReal-time status communication keeps requesters informed with clear, consistent updates, so business relationship reviews are about improvement rather than about the time nobody told a department why their request was waiting.
ITSM suiteShow the business a service that improves
Continuous improvement insights analyze backlog volume, trends and service performance over time, so the continual improvement register you own is fed by evidence and each action can be tied to the metric it moved.
ITSM suiteProblem Management links recurring incidents to root causes and long-term fixes, so the Incident and Problem Manager can show a business customer that the fault they keep raising has a permanent fix in progress.
ITSM suiteAudit-ready activity history keeps traceable records of actions, decisions and approvals across every practice, so the process ownership ISO/IEC 20000-1 and DORA expect is evidenced from the system rather than described in a document.
ITSM suiteService level. Defines services and SLAs in a catalog and measures performance against them with live dashboards.
Request. Runs request fulfillment through a service portal with routing, approvals and SLAs.
Incident. Owns the incident and problem process configuration, priorities and escalation rules.
Change. Owns change enablement with CAB workflows and risk-based approvals.
Reporting. Reports service performance and improvement actions to IT leadership and business customers.
Products this role uses most
Industry reference
ITIL 4 defines the practices the role owns, from service level management and relationship management to continual improvement, and ISO/IEC 20000-1:2018 is the certifiable service management standard built on them. COBIT 2019's DSS02 (managed service requests and incidents) supplies the control framing. Regulated sectors expect documented service levels and process ownership: FFIEC guidance for banks, DORA for EU financial entities, HIPAA for healthcare systems and FedRAMP for providers to US government. ITIL 4's service level management practice is where the three artifacts this role owns meet: the catalog that defines each service, the SLA that sets its targets and the service review that reports against them, with continual improvement fed by the same measures.
Related roles
Chief Information Officer
See the roleExplore Further
Guides and definitions from the GRC Knowledge Center and the What-is glossary, chosen for this role.
Frequently asked questions
The IT Service Manager owns the service management practices: the service catalog and service level agreements, the design, metrics and continual improvement of the ITSM processes, oversight of the incident, problem, change and request practices, business relationship management and service reviews, and governance of the ITSM toolset and its configuration. They report service performance against SLAs, so the services the business consumes are defined, measured, improving and understood by the people who depend on them.
Service Catalog defines the services and Service Level Management (SLAs) measures performance against the SLAs attached to them with live dashboards, so each service has a definition, an owner, a target and a current performance figure in one place. A service review with a business customer starts from the dashboard, not from a report assembled the day before, and a missed target shows which requests or incidents caused it.
Service Desk & Request Portal runs request fulfillment through a service portal with routing, approvals and SLAs, so a user raises a request in one place, it is routed to the right team, approvals happen in sequence and the response time is measured. The Service Desk Manager runs the queue while the IT Service Manager owns the catalog the requests are drawn from, and Knowledge Management holds the articles the service desk uses to resolve the common ones.
The IT Service Manager owns the incident and problem process configuration, priorities and escalation rules in IT Incident Management, and owns change enablement in Change Management with CAB workflows and risk-based approvals. The Incident and Problem Manager and Change and Release Manager run the practices day to day, while the IT Service Manager sets the priority matrix, the escalation path and the approval thresholds they operate within, and changes them as continual improvement finds a better design.
SmartSuite reports service performance and improvement actions to IT leadership and business customers from the catalog, SLA measurements and request and incident records as they stand. The IT Service Manager can show the Chief Information Officer how each service performed against its targets and what improvement actions are open, and take the same view into a service review with a business customer. The IT Operations Director and IT Compliance Manager see the same services.
New customers can start with SmartSuite Onboarding, a guided four-week program around one or two priority workflows. For an ITSM practice the first workflow is the service catalog: load the catalog with owners and SLA targets, configure the priority matrix and escalation rules, and open the request portal to users. Incident, problem and change practices follow as each is reviewed, and the GRC Platform Administrator and IT Asset Manager work in the same workspace, so service, asset and control records refer to the same services.