What is service management?

Service management is a set of specialised organisational capabilities for enabling value for customers in the form of services. ITIL defines a 'capability' as the ability to perform an activity, built from resources (people, information, technology, partners, processes) organised in a way that adds value.

Key definitions you must know

• Service: a means of enabling value co-creation by facilitating outcomes customers want to achieve, without the customer having to manage specific costs and risks.
• Value: the perceived benefits, usefulness and importance of something. Value is co-created by the provider and consumer together, not delivered one-way.
• Utility: what the service does — fitness for purpose. Removes constraints from the consumer.
• Warranty: how well it does it — fitness for use. Covers availability, capacity, security and continuity. A service needs BOTH utility and warranty to create value; one without the other fails.
• Cost: the amount of money spent on a specific activity or resource. Costs removed from the consumer by the service are part of the value proposition; costs imposed on the consumer reduce value.
• Risk: possible event that could cause harm or loss, or make it harder to achieve objectives. Risk removed = value; risk introduced = reduces value.

Service relationships

• Service provider: the organisation providing services.
• Service consumer: an umbrella role covering customer, user and sponsor — these can be the same person or different people.
• Customer: defines requirements and is accountable for outcomes.
• User: uses the service day to day.
• Sponsor: authorises budget for the service.
• Service relationship: a cooperation between provider and consumer, comprising service provision, service consumption and service relationship management.

Outputs and outcomes

• Output: a tangible or intangible deliverable of an activity.
• Outcome: a result for a stakeholder enabled by one or more outputs. Outcomes are what customers actually pay for — not outputs.

Common mistakes to avoid

• Don't confuse output (a deliverable) with outcome (the result that matters to the stakeholder).
• Don't think value is delivered by the provider alone — it is CO-created.
• Don't forget warranty covers availability, capacity, security and continuity — all four, not just uptime.
• Remember 'service consumer' is a role that can be split across customer/user/sponsor or held by one person.

What are the four dimensions?

ITIL 4 says a service can never be reliable if you only think about process. You have to view service management from four angles at once, or you get blind spots. The four dimensions are:

• Organizations and people
• Information and technology
• Partners and suppliers
• Value streams and processes

All four are constantly influenced by external PESTLE factors: Political, Economic, Social, Technological, Legal, Environmental. That acronym is a favourite exam target.

Organizations and people

This covers the structure, culture, roles, and required competencies of an organisation. It is not just about headcount. A rigid, siloed structure or a culture that resists change will sabotage even well-designed processes. Look for exam scenarios where a good process fails because of poor communication or the wrong skills.

Information and technology

Covers the information and knowledge needed to manage services, plus the technologies supporting them (workflow systems, knowledge bases, AI tools). It also includes the relationships between components, such as dependencies and integrations. Watch for questions about information governance, data quality, and how technology choices constrain or enable value.

Partners and suppliers

Covers relationships with other organisations involved in designing, developing, deploying, delivering, supporting, or improving services. This ranges from formal outsourcing contracts to loose collaborative partnerships. Strategies range from insourcing everything to full outsourcing, with most organisations sitting somewhere in between.

Value streams and processes

Covers how the various parts of an organisation work together in an integrated way, through value streams (the steps to create and deliver a product or service) and processes (which transform inputs into outputs). This dimension asks 'what activities does the organisation perform, and how?'

Common mistakes to avoid

• Do not confuse the four dimensions with the seven guiding principles or the 34 practices — they are separate ITIL 4 concepts.
• Do not forget PESTLE sits AROUND the four dimensions, influencing all of them, not inside any single one.
• Remember the Service Value System (SVS) is the bigger picture that the four dimensions support — they ensure the SVS remains holistic.
• The four dimensions must be considered for EVERY service, not just complex or high-risk ones.

Exam tip

If a question describes a service failure caused by something other than the actual technical fault (culture, contract terms, missing information, poor handoffs), it is almost certainly testing whether you can name the relevant dimension.

What the guiding principles are

ITIL 4 has seven guiding principles. They are recommendations that guide an organisation in all circumstances, no matter what changes to strategy, goals or management happen. They are NOT rules to follow blindly - they are things to think about and adapt to the situation.

The seven principles

• Focus on value - everything the organisation does should map back to value for stakeholders, directly or indirectly. Value must always be defined from the customer or stakeholder viewpoint, not the provider's.
• Start where you are - do not start from scratch or discard what already works. Assess the current state, use existing services, processes and tools where they add value, and measure before deciding what to change.
• Progress iteratively with feedback - do not attempt one big-bang improvement. Break work into smaller, manageable pieces that can be completed in a timely manner, gather feedback at each step, and adjust.
• Collaborate and promote visibility - work across boundaries, involve the right stakeholders at the right time, and make work, progress and decisions visible so trust and buy-in improve. Silent working alone reduces the chance of getting things right first time.
• Think and work holistically - no service or practice stands alone. Recognise that outcomes depend on the coordinated management of all the activities of an organisation (the Four Dimensions), and results depend on the end-to-end effort.
• Keep it simple and practical - use the minimum number of steps to accomplish an objective. If a process, service or metric doesn't add value or produce a useful outcome, get rid of it. Judge in terms of outcomes, not adherence to process.
• Optimize and automate - use human effort only where it truly adds value; simplify and optimize before automating. Automating a bad process just makes a bad process happen faster.

How to remember them

A popular mnemonic is FSPCTOK or simply memorise by the first letter run: Focus, Start, Progress, Collaborate, Think, Keep, Optimize.

Common mistakes

• Thinking there are more or fewer than seven - there are exactly seven, no more, no less.
• Assuming the principles apply only during Improvement - they apply to ANY initiative and interaction, across the whole Service Value System.
• Confusing 'Progress iteratively with feedback' with Agile methodology - the principle is broader than any one framework; it is a mindset, not a specific method.
• Forgetting that ALL seven principles should normally be considered together for any given situation, though some will be more relevant than others depending on context.
• Mixing up 'Keep it simple and practical' with 'Optimize and automate' - simplicity comes first, automation comes after optimizing, never before.

What the SVS actually is

The Service Value System (SVS) is the big-picture model showing how ALL the components and activities of an organisation work together to create value. It is not the same as the value chain (that is just one part of it).

The SVS has FIVE components:

• Guiding principles
• Governance
• Service value chain
• Practices (34 of them)
• Continual improvement

Inputs and outputs

Opportunity and demand go IN to the SVS. Value comes OUT. That is the whole point of the system - everything inside it exists to turn opportunity and demand into value for stakeholders.

The service value chain - the operating model

The value chain sits INSIDE the SVS and is the operating model. It has SIX activities, and you must know all six:

• Plan
• Improve
• Engage
• Design and transition
• Obtain/build
• Deliver and support

Common mistake: candidates think these six run in a strict left-to-right sequence. They do not. Any activity can call on any other activity in any order, as many times as needed - this is why it is drawn as a hexagon with arrows crossing every which way, not a straight line.

How practices fit in

The 34 practices are resources (people, process, tech, partners) that get pulled into value chain activities as needed. A single practice, like change enablement, can support several different value chain activities. Practices are not tied one-to-one with activities - do not try to memorise a fixed pairing, because it does not exist.

Value chain activities in plain English

• Plan: ensures a shared understanding of vision, status and improvement direction across the org.
• Improve: ensures continual improvement of products, services and practices across all value chain activities.
• Engage: provides understanding of stakeholder needs, transparency, and good relationships.
• Design and transition: ensures products/services meet stakeholder expectations for quality, cost and time to market.
• Obtain/build: ensures service components are available when and where needed, meeting specifications.
• Deliver and support: ensures services are delivered and supported to agreed specs and stakeholder expectations.

Common mistakes to avoid

• Muddling the SVS (five components, the whole system) with the value chain (six activities, one component of the SVS).
• Assuming the value chain is sequential - it is not, it is flexible and iterative.
• Forgetting that governance is a distinct SVS component, separate from the value chain and separate from practices.
• Thinking practices only feed one activity each - most feed several.

What counts as a general management practice?

ITIL 4 has 34 practices split into three groups: 14 General Management, 17 Service Management, and 3 Technical Management. General management practices are adapted from general business management into service management - they are not unique to ITIL.

For Foundation you need to recognise all 14 by name and know the detail of five in particular: continual improvement, information security management, relationship management, supplier management, and (to a lesser depth) risk management.

The 14 general management practices

• Strategy management
• Portfolio management
• Architecture management
• Service financial management
• Workforce and talent management
• Continual improvement
• Measurement and reporting
• Risk management
• Information security management
• Knowledge management
• Organizational change management
• Project management
• Relationship management
• Supplier management

Continual improvement (the one exam favourite)

This practice provides a structured approach for improving products, services, and the practices themselves, at every level. Its core tool is the continual improvement model, a seven-step loop: vision, where are we now, where do we want to be, how do we get there, take action, did we get there, how do we keep the momentum going. It links tightly to the guiding principle 'progress iteratively with feedback'. Every single person in the organisation is expected to contribute to continual improvement - it is not owned by one team.

Information security management

Ensures information is protected against unauthorised access, disruption, or loss. Built on the CIA triad: confidentiality (only authorised access), integrity (accurate and complete, unaltered), and availability (accessible when needed). A common trap is confusing this with basic IT security - it is a management practice covering policy, risk, and controls, not just technical tooling.

Relationship management vs supplier management

Relationship management establishes and nurtures links between the organisation and its stakeholders at strategic and tactical levels. Supplier management ensures suppliers and their performance are managed appropriately to support the seamless provision of quality products and services - this includes creating a single point of visibility for supplier and contract information.

Common exam mistakes

• Muddling general management practices with service management practices (for example, service desk and incident management are service management practices, NOT general management).
• Thinking continual improvement only happens during a formal 'CSI register' review - it is continuous and everyone's job.
• Assuming information security management is purely technical rather than a governance-and-risk practice.
• Forgetting there are exactly 34 practices in total, not 26 (the old ITIL v3 processes) or some other number.

What is an ITIL practice?

A practice is a set of organisational resources designed for performing work or accomplishing an objective. ITIL 4 replaces the old ITIL v3 'processes' with 34 practices, grouped into three categories: General Management (14), Service Management (17), and Technical Management (3). This topic focuses on the Service Management and Technical Management practices.

The 3 Technical Management practices

• Deployment management: moves new or changed hardware, software, documentation or processes to live environments; can also install within test or staging environments.
• Infrastructure and platform management: oversees the infrastructure and platforms used by an organisation, monitoring technology solutions available including from third parties.
• Software development and management: ensures applications meet stakeholder needs in terms of functionality, reliability, maintainability, compliance and auditability.

Key Service Management practices to know cold

• Incident management: minimises the negative impact of unplanned interruptions by restoring normal service operation as quickly as possible.
• Problem management: reduces the likelihood and impact of incidents by identifying actual and potential causes, and managing workarounds and known errors.
• Change enablement: maximises the number of successful service changes by ensuring risks are properly assessed. Three change types: standard (pre-authorised, low-risk, well understood), normal (assessed and authorised via a change authority), and emergency (must be implemented ASAP, e.g. to resolve a major incident).
• Service desk: the single point of contact between the service provider and users, capturing demand for incident resolution and service requests.
• Service level management: sets clear business-based targets for service performance, so delivery can be assessed, monitored and managed against these targets (SLAs).
• Service request management: supports the agreed quality of a service by handling all pre-defined, user-initiated requests in an effective, user-friendly manner.
• Release management: makes new and changed services and features available for use.
• Service configuration management: ensures accurate information about configuration items (CIs) and their relationships is available when needed (via a CMDB/CMS).
• Monitoring and event management: systematically observes services and CIs, detects state changes classed as events, and determines the appropriate response.
• Continual improvement: aligns practices and services with changing business needs through ongoing improvement (uses the continual improvement model).

Common exam mistakes

• Don't confuse incident management (restore service fast) with problem management (find root cause, prevent recurrence).
• A workaround reduces or eliminates incident impact but does NOT resolve the underlying problem.
• Change enablement covers ALL IT changes, not just standard IT infrastructure — but standard changes do NOT need individual authorisation each time, they follow a pre-agreed procedure.
• Service desk is a practice AND may be delivered via various channels (phone, chat, portal) — the exam expects you to know it is about communication and coordination, not just ticket logging.</br>