ISO 20000 Lead Auditor study materials
ISO 20000 Lead Auditor study resources

ISO 20000 Lead Auditor: Fundamental principles and concepts of a service management system

ISO 20000 Lead Auditor · Work through your exam, one topic at a time.

All guide sections

Fundamental principles and concepts of a service management system

Domain 1 - Fundamental principles and concepts of a service management system

This domain tests whether you can explain what a service management system (SMS) is, how ISO/IEC 20000-1:2018 treats it, and why it is a management system standard rather than a process cookbook. Expect definitions, the process approach, risk-based thinking and top management's role.

Core concepts

  • Service: a means of delivering value by facilitating outcomes customers want, without the customer owning specific costs and risks.
  • Service management: the capabilities and processes used to direct and control a service provider's activities and resources.
  • SMS: the policies, objectives, processes and resources that direct and control service management, including governance of processes operated by other parties.
  • ISO/IEC 20000-1 uses the harmonized structure: context, leadership, planning, support, operation, performance evaluation and improvement. It requires a documented scope, policy, objectives, monitoring, internal audit, management review and improvement.
  • The standard is technology- and methodology-neutral. ITIL or DevOps can inform practice but are not audit criteria.

Worked example

An organization claims compliance because it has an incident process and a service desk. The auditor asks for the SMS scope, policy, measurable objectives, risk treatment, internal audit results and management review minutes. The incident process is only one operational control. Conformity is judged against the whole SMS, not the existence of a single process. A useful test is whether the process has defined inputs, outputs, owners, interfaces, performance measures and improvement actions linked to service outcomes.

Traps

  • Treating certification as a badge for an IT department rather than for the defined scope.
  • Confusing a tool implementation with an SMS.
  • Forgetting that supplier-operated services remain in scope.
  • Quoting ITIL as if it were an auditable requirement.