ITIL 4: What is it?

ITIL 4 introduces a comprehensive framework that includes 34 management practices, each helping organisations deliver IT services aligned with business goals. These practices are grouped into three categories:

• General management practices (14)
• Service management practices (17)
• Technical management practices (3)

Alongside these, ITIL 4 provides seven Guiding Principles that serve as universal recommendations to guide behaviours and decisions across all areas of service management.

1. General Management Practices

These practices are borrowed or adapted from general business management disciplines.

• Architecture management. Ensures the logical design and evolution of systems and services. For example, designing cloud architecture to support a new digital platform.
• Continual improvement. Aligns improvements with business goals. For example, running monthly retrospectives to identify service improvements.
• Information security management. Protects data confidentiality, integrity and availability. For example, implementing ISO 27001 controls for access management.
• Knowledge management. Ensures valuable information is available and accessible. For example, creating a searchable knowledge base for service desk agents.
• Measurement and reporting. Supports decision-making with meaningful data. For example, publishing monthly KPIs on incident response times.
• Organisational change management. Prepares and supports individuals for change. For example, communicating and training users before rolling out new tools.
• Portfolio management. Ensures investments align with business strategy. For example, prioritising service upgrades that support key business goals.
• Project management. Plans and controls project delivery. For example, delivering a CRM implementation using agile methodology.
• Relationship management. Builds positive relationships with stakeholders. For example, account managers conducting quarterly business reviews.
• Risk management. Identifies and manages risk. For example, using a risk register during a data centre migration.
• Service financial management. Manages budgeting, accounting and charging. For example, forecasting IT budget requirements for cloud subscriptions.
• Strategy management. Formulates and maintains strategy across services. For example, defining a three year digital transformation strategy.
• Supplier management. Ensures value from third party vendors. For example, conducting performance reviews with hosting providers.
• Workforce and talent management. Develops and retains IT talent. For example, building skills matrices and succession planning.

2. Service Management Practices

These practices are core to the planning, delivery and support of IT services.

• Availability management. Ensures services meet availability needs. For example, designing systems with failover to achieve 99.9% uptime.
• Business analysis. Analyses business needs and defines solutions. For example, gathering user stories to build a self-service portal.
• Capacity and performance management. Balances resources with demand. For example, monitoring CPU usage to plan server upgrades.
• Change enablement. Minimises risk when implementing changes. For example, using a change advisory board for approving major IT changes.
• Incident management. Restores normal service quickly. For example, resolving printer issues via the service desk.
• IT asset management. Manages the lifecycle of hardware and software assets. For example, tracking laptops through procurement, use and disposal.
• Monitoring and event management. Detects and responds to system events. For example, using dashboards to track server outages.
• Problem management. Prevents recurring incidents. For example, root cause analysis of repeated email outages.
• Release management. Controls the release of new features or fixes. For example, coordinating app updates with internal stakeholders.
• Service catalogue management. Maintains a single source of service information. For example, publishing a catalogue of available IT services.
• Service configuration management. Maintains configuration item information. For example, using a CMDB to manage server dependencies.
• Service continuity management. Ensures services can recover from disruption. For example, developing a disaster recovery plan.
• Service design. Designs new or changed services. For example, designing a new IT onboarding process.
• Service desk. Provides a point of contact for users. For example, logging and resolving tickets via phone or portal.
• Service level management. Sets and monitors service targets. For example, defining response times in an SLA.
• Service request management. Handles routine service requests. For example, processing user requests for software installation.
• Service validation and testing. Ensures services meet requirements before release. For example, QA testing a new mobile app before go-live.

3. Technical Management Practices

These practices provide the technical foundations that support service management.

• Deployment management. Moves changes into live environments. For example, deploying new software via CI/CD pipelines.
• Infrastructure and platform management. Oversees physical and virtual infrastructure. For example, managing a hybrid data centre and cloud setup.
• Software development and management. Manages the software development lifecycle. For example, agile sprint planning and feature releases.

The Seven Guiding Principles

• Focus on value. Everything should create or support value for stakeholders. For example, prioritising features based on customer feedback.
• Start where you are. Assess the current state and build upon it. For example, reusing existing monitoring tools instead of buying new ones.
• Progress iteratively with feedback. Break work into manageable chunks and learn from each. For example, using short sprint cycles with user demos.
• Collaborate and promote visibility. Work together and share knowledge across teams. For example, holding cross-team workshops to plan service changes.
• Think and work holistically. Consider all parts of the organisation as an interconnected whole. For example, aligning IT change with HR onboarding processes.
• Keep it simple and practical. Use only what is necessary and eliminate waste. For example, avoiding overcomplicated workflows in the ticketing system.
• Optimise and automate. Streamline before introducing automation. For example, simplifying approval steps before automating request fulfilment.

Final Thoughts

ITIL 4 gives organisations a modern, adaptable approach to managing IT services by combining practical, categorised practices with universal guiding principles. When used together, these elements ensure services are not only efficient and reliable, but also continuously improving and aligned to business value.