Experience, Strategy and Transformation

A question in this part of the exam often shows you a single word, such as experience, vision, or transformation, and asks which one a short scenario is describing. The words come from three different areas of ITIL Version 5, and knowing which area a word belongs to is usually enough to answer.

ITIL Version 5 keeps ITIL Foundation as the entry point and adds advanced areas that build role-relevant capability on top of it (ITIL Version 5 explained^[1]). Three of those areas supply the vocabulary this objective tests. ITIL Experience is about how people think and feel about the products and services they use, treating that felt quality as something to design rather than leave to chance (ITIL Experience (Version 5)^[2]). ITIL Strategy is about setting direction and connecting it to measurable outcomes (ITIL Strategy (Version 5)^[3]). ITIL Transformation is about changing how an organization operates (ITIL Transformation (Version 5)^[4]).

Each area answers a different question. Experience asks how people think and feel about their interactions; Strategy asks where the organization is going, and why; Transformation asks how the organization changes to get there. The figure below lays the three areas out with the question each one answers and the terms it supplies. At Foundation level the task is only to recall each term's basic definition and to separate the ones that sound alike, not to carry out the work of these advanced areas. The sections below take the three areas in turn and then gather the pairs the exam most often tries to blur.

ITIL Experience deals with the human side of a service: not whether the system worked, but how the interaction felt. In ITIL Experience, experience is the sum of how a person thinks and feels about their interactions with a product, service, or organization. When those interactions happen through digital technology and channels, the same thing is called digital experience. ITIL treats this as a design goal in its own right, summed up in the idea that digital technology should feel as good as it functions (ITIL Experience (Version 5)^[2]).

User experience and customer experience

Two of the terms name whose experience you mean and how wide a slice of it. User experience (UX) is the experience one person has when interacting with a specific product or service and its provider, for example how usable and satisfying a single application is. Customer experience (CX) is wider: the sum of the functional and emotional interactions a customer has with a provider across the entire relationship and all of its touchpoints. Because CX spans the whole relationship while UX is a single product interaction, CX is the broader of the two, and a service can deliver good UX on one screen yet still add up to a poor CX overall (experience through human eyes^[5]). The figure below sets UX and CX on one breadth axis, from the single interaction to the whole relationship.

Trust, human-centred design, and the XLA

Three more terms complete the area. Trust is the confidence one party has in the reliability, integrity, and ability of another, such as a consumer's confidence in a provider; it is not granted once but built up over time through consistent, positive experiences. Human-centred design puts the needs, contexts, and behaviours of the people who will use a product at the centre of the design process, so the result is usable, useful, and desirable. An experience level agreement (XLA) sets targets for the experience users and customers actually have, focused on outcomes and how people feel.

The XLA is where a careful reader has to reconcile two true statements. A Service Level Agreement (SLA), covered under service relationships, documents technical service-level targets such as availability or resolution time, and every one of them can be met while users are still frustrated. An XLA does not replace the SLA; it adds targets for the experience the SLA cannot see. So the same service can pass its SLA and fail its XLA, which is exactly the contrast the exam likes to draw.

ITIL Strategy is about direction: deciding where the organization is going and how it will get there. A strategy is a plan that describes how an organization will achieve its objectives. Two narrower kinds sit under it. A business strategy defines the organization's overall goals and how to reach them, while a digital strategy defines how the organization will use digital technology to achieve those business objectives. The digital strategy serves the business strategy; it is a means to the same goals, not a separate destination (ITIL Strategy (Version 5)^[3]).

Mission, vision, and purpose

Three short statements are the ones candidates most often swap by mistake, because each describes the organization at a high level but from a different angle.

Statement	What it answers	Time frame
Mission	What the organization does and why it exists	Today
Vision	What it aspires to become	The future
Purpose	What it does for its consumers and stakeholders, and why	Its reason to serve

A quick test: if a sentence is aspirational and future-tense (we want to become...), it is a vision, even when a mission option is on offer.

VUCA and leadership

Two final terms describe the conditions strategy has to work in and the capability that drives it. VUCA stands for volatility, uncertainty, complexity, and ambiguity, the characteristics of the turbulent modern environment organizations operate in (ITIL Strategy (Version 5)^[3]). Leadership is the ability to guide, influence, and inspire people toward achieving the organization's objectives. Strategy sets the direction; leadership moves people along it.

The three transformation terms line up on a single scale of how much is changing, and how deeply. At one end is business as usual (BAU): the normal, day-to-day running of an organization's established, ongoing operations and services, the steady state that the other two act upon. A change is a discrete alteration to that steady state, an addition, modification, or removal that makes a product, service, process, or way of working different, and it is usually incremental. Transformation is at the far end: a profound and often radical change in how an organization operates, delivers value, or is structured, such as a digital transformation, going well beyond any single change (ITIL Transformation (Version 5)^[4]). The figure below lays the three terms along that scale of depth, from the steady state to a profound reshaping.

The distinction the exam tests is depth, not size. Rolling out a new laptop model to every employee touches a lot of people, but it is still a change: the way the organization operates is the same the next morning. Moving from selling boxed software to running a subscription service rewrites how the organization delivers value and earns revenue, so it is a transformation. And when neither is under way, the established services simply keep running as business as usual. Read the scenario for how deeply the operating model shifts, not for how large or expensive the effort sounds.

Most questions on this objective are recognition questions: a one-line scenario or definition, with four terms to match it to. The tempting wrong answer is almost always a neighbour from the same area, so the fastest approach is to place the scenario in Experience, Strategy, or Transformation first, then choose within it. These are the pairs and triples that come up most.

Experience versus digital experience

If the scenario stresses digital technology or channels specifically, the answer is digital experience; if it is about interactions in general, it is plain experience. The word digital in the stem is the tell.

UX versus CX

A single product or app, or one user's satisfaction, points to user experience. The whole relationship across many touchpoints points to customer experience, the broader term. Picking UX for a whole-relationship scenario is the classic mistake.

XLA versus SLA

If the target is about how users feel or the outcomes they get, it is an experience level agreement. If it is a technical service level such as uptime or resolution time, it is a Service Level Agreement. A stem that dwells on satisfaction or perception while offering an SLA option is baiting the SLA answer.

Mission, vision, and purpose

Mission is what the organization does now; vision is the future it wants to reach; purpose is what it does for stakeholders and why. A future-tense, aspirational sentence is a vision even when a mission option is present.

Change, transformation, and BAU

An incremental alteration is a change; a profound reshaping of how the organization operates is a transformation; the steady-state running of established services is business as usual. Judge by depth, not by how big or costly the effort sounds.