Skip to content

ITIL and IT Service Management

This perspective states Alescent's posture toward ITIL and IT Service Management as common service-management disciplines.

Domain Classification

ITIL and IT Service Management are primarily Practices-domain constructs when they refer to repeatable service-management practices, operating processes, governance cadences, service controls, and management disciplines.

They also touch Platforms when the subject is the technology environment, Products when services are treated as managed offerings, and Players when roles, accountabilities, and competencies are involved.

Alescent Position

Alescent recognizes ITIL and IT Service Management as useful disciplines for improving service quality, reliability, change control, incident response, service accountability, and operational consistency.

Alescent's position is a "yes, and" position:

  • yes, ITIL and IT Service Management provide useful operating discipline, common language, and service-governance structures;
  • and, Alescent extends service management by asking whether service practices create, protect, assure, or realize value rather than merely institutionalizing process compliance.

Value Realization Extension

A Value Realization-based extension of IT Service Management emphasizes:

  • service performance as a value condition;
  • continuity, reliability, recovery, and support as value-protection mechanisms;
  • change control as a control and value-realization discipline, not only a risk gate;
  • incident and problem management as sources of value evidence, value leakage, and value erosion signals;
  • service catalogs and service levels as investment and value-governance artifacts;
  • service metrics as indicators that require value interpretation.

Preferred Use

Use ITIL or ITSM language where derived content must connect to service-management, operations, infrastructure, support, reliability, or CIO operating audiences.

Use Value Realization language where the discussion is about economic outcome, value protection, evidence, valuation, investment, or realized value.

Prohibited Use

Do not treat process compliance as value realization.

Do not treat service maturity as value realization without evidence.

Do not treat service levels as sufficient value evidence unless they connect to a governed value case.

Do not allow ITSM terminology to obscure the distinction between operational performance and realized value.

  • Practices
  • Platforms
  • Products
  • Players
  • IT Investment Management
  • Capability Optimization
  • Continuity Optimization
  • Control Optimization
  • Compliance Optimization
  • Capacity Optimization
  • Performance Measures
  • Value Statement