ITIL 4 Foundation — Intermediate

The four dimensions model

Applying Fundamentals' SVS structure to organizational factors: ITIL 4's four dimensions model ensures a holistic approach (directly connecting to Fundamentals' "think and work holistically" guiding principle) to service management, covering: organizations and people (organizational structure, culture, roles, and required competencies), information and technology (the information and knowledge needed to manage services, plus the technologies supporting service management), partners and suppliers (relationships with other organizations involved in designing, developing, deploying, delivering, supporting, and improving services), and value streams and processes (how the organization's various parts work together in an integrated way to enable value creation, connecting directly to Fundamentals' service value chain). Each dimension is influenced by external factors (political, economic, social, technological, legal, environmental — a PESTLE-style consideration), and ITIL 4 explicitly requires balancing attention across all four dimensions, since neglecting any one (say, focusing purely on technology while ignoring organizational culture and people factors) undermines effective service management even if the other dimensions are well-addressed.

Value co-creation — the SVS's underlying purpose

Central to ITIL 4's departure from ITIL v3 (Overview): the SVS exists to enable value co-creation — the recognition that value isn't simply delivered by IT to a passive business/customer, but co-created through collaboration between service provider and service consumer, both contributing to and benefiting from the outcome. This reframing matters practically: it shifts ITSM's implicit goal from "IT executes requests efficiently" toward "IT and business stakeholders jointly ensure services actually produce the intended outcomes" — a genuinely different orientation that shows up throughout ITIL 4's guiding principles (particularly "focus on value" and "collaborate and promote visibility," Fundamentals) and the four dimensions' emphasis on partners/suppliers and organizational culture, not just technical execution.

Applying the service value chain to a concrete scenario

Connecting Fundamentals' six value-chain activities to a realistic example: a new service request begins with engage (understanding what the requesting stakeholder actually needs), flows through plan and design and transition (determining how to deliver it and ensuring it meets quality/cost/timing expectations), draws on obtain/build (acquiring or building the necessary service components), and results in deliver and support (the ongoing operational service, plus support when issues arise) — with improve operating continuously across all of this, not as a separate final stage. This flow illustrates why the six activities aren't a fixed lifecycle sequence: a mature service might skip design-and-transition largely and move quickly from engage to deliver-and-support for a routine, well-understood request, while a genuinely novel service would engage all six activities more deliberately.

Practices, applied within the four dimensions

Intermediate-level synthesis: any given ITIL practice (Fundamentals) is itself shaped by all four dimensions — incident management (a commonly tested practice) requires appropriate organizational roles and escalation culture (organizations and people), appropriate tooling and knowledge bases (information and technology), potentially coordination with external support vendors (partners and suppliers), and a defined process flow integrated with other practices (value streams and processes). Recognizing that practices don't exist independently of the four dimensions — they're implemented through all four simultaneously — is what distinguishes genuine ITIL 4 conceptual understanding from simply memorizing practice names and definitions.

Continual improvement — embedded, not a separate phase

Building on Fundamentals' point about the service value chain's "improve" activity operating continuously: ITIL 4 explicitly treats continual improvement as embedded throughout the SVS (appearing in guiding principles, the value chain, and as its own formal practice) rather than a distinct end-of-lifecycle phase the way ITIL v3's "Continual Service Improvement" lifecycle stage might have implied. This is a subtle but frequently tested distinction — ITIL 4 exam questions testing "when does improvement happen" expect "continuously, throughout" rather than "as a final stage after operation."