ITIL 4 MP common mistakes
ITIL 4 MP · Understand the traps and how to avoid them.
Drawing the service value chain as something the organisation designs per service, and then choosing an answer that describes a bespoke six-step flow as 'the value chain'.
The value chain diagram and value stream diagrams look almost identical in the syllabus material, and both are described as 'flows' of activity. Candidates memorise the shape without the distinction, so under time pressure they grab whichever term appears first in the option.
What to do instead
Hold one sentence in memory: the value chain is generic and universal (the six activities: plan, improve, engage, design and transition, obtain/build, deliver and support, in a fixed set of possible sequences); a value stream is what a specific organisation actually designs for a specific scenario, with named steps and hand-offs. Whenever a question mentions a particular product, team or customer journey, the answer is almost always about the value stream.
Using 'shift left' and 'swarming' interchangeably, e.g. selecting 'move resolution to first line' as an example of swarming, or 'bring together a multi-skilled group' as an example of shift left.
Both are presented in the same part of the guidance as working practices that improve flow, both sound like 'get things fixed sooner', and neither has a memorable one-line definition in the exam preparation material.
What to do instead
Anchor each to where the work goes. Shift left = move work, knowledge or decision authority closer to the point of origin or the user (self-service, automation, first-contact resolution capability, moving testing earlier). Swarming = a group with varied competences works collaboratively on one item at one time instead of handing it along a tiered escalation path. If the option describes a team forming around an item, it is swarming.
Treating the ITIL practices as fixed processes and picking answers that describe a mandatory sequence (for example, 'the problem management process must always follow the incident management process').
Prior ITIL certification or work experience with process models creates a strong expectation of defined inputs, activities and outputs; the practices-as-organisational-capabilities idea feels abstract, so the familiar process framing wins.
What to do instead
Before answering, classify the question: purpose/definition questions are answered from the practice purpose statement, and value stream questions are answered from the flow of the scenario. Also rehearse the purpose statements that are most often swapped: incident management restores service quickly; problem management reduces the likelihood and impact of incidents by identifying causes and workarounds; service request management handles predefined, user-initiated requests as part of normal service delivery.
Reconstructing the customer journey stages out of order, typically dropping 'offer' or 'agree', or collapsing 'explore' and 'engage'.
Seven stages is above the usual working-memory chunk of four or five, the stage names are abstract, and exam options often list five of the seven in a plausible-looking order.
What to do instead
Memorise the sequence as three pairs plus an outcome: Explore, Engage | Offer, Agree | Onboard, Co-create | Realize. Then attach one job to each: explore = understand the market and the customer's needs; engage = reach agreement on interaction and communication; offer = shape and present the value proposition; agree = formalise the service agreement; onboard = get the customer into a position to consume; co-create = joint production of value; realize = the customer achieves outcomes.
Treating 'the customer' as one undifferentiated party and choosing an answer aimed at the wrong role - for example, recommending outcome-based reporting for the user, or recommending usability improvements for the sponsor.
Everyday business language uses customer, consumer, user and client loosely; the exam uses them as distinct stakeholder roles and deliberately puts several of them in the same scenario stem.
What to do instead
Before reading the options, label every party named in the stem: the sponsor/funder (cares about cost, risk, outcomes and value), the customer (defines requirements and owns the service relationship), the user (cares about usability and their own task), and suppliers/partners (bound by agreements). Then eliminate any option whose benefit lands on the wrong party.
Reading high-velocity IT as 'go faster' and choosing whichever option maximises deployment frequency or automation, even when the stem is about stability, experimentation or trust.
The phrase 'high velocity' strongly primes speed, and the technology examples in the material (automation, CI/CD, cloud) reinforce a purely throughput reading of the topic.
What to do instead
Test each option twice: does it increase the rate of value delivery, and does it protect quality, resilience and the ability to recover? High-velocity IT is about rapid, iterative delivery of digital products alongside robustness and a tolerance for safe failure. Options that buy speed by removing control usually lose to options that buy speed by removing waste while keeping feedback and recovery in place.
Assuming ITIL 4 requires or replaces a particular way of working - for example, 'the organisation must adopt DevOps', 'Agile should be replaced by ITIL practices', or 'Lean is mandatory for high-velocity organisations'.
The high-velocity material discusses Lean, Agile, DevOps, design thinking and resilience thinking side by side with ITIL concepts, so candidates read co-existence as prescription.
What to do instead
Default to the integration answer. ITIL 4 is deliberately method-agnostic; it defines what good looks like (practices, value streams, the four dimensions, the guiding principles) and leaves the method to the organisation. An option saying the organisation should adopt, align, integrate or tailor will beat one saying it must replace, mandate or discard something.
Confusing governance with management, e.g. selecting 'the service manager approves the policy' or 'the CIO reviews the improvement plan' as an example of governance.
In most organisations the same senior people both govern and manage, so the distinction feels artificial; and the word 'governance' is used loosely in everyday business speech to mean 'oversight by senior people'.
What to do instead
Use the three verbs: governance is evaluate, direct and monitor, performed by a governing body, and concerns direction, accountability and control across the whole organisation. Management is planning, organising, resourcing and delivering within that direction. If the option describes executing, resourcing or operating, it is management; if it describes setting direction, delegating accountability or monitoring performance against it, it is governance.
Misusing measurement vocabulary - calling a metric a critical success factor, or choosing a lagging indicator (customer satisfaction last quarter, incidents last month) where the stem asks for something predictive.
The terms are defined in the material but not contrasted with worked examples, and in practice organisations label almost any number a KPI, so candidates' work experience actively misleads them.
What to do instead
Build the hierarchy top-down: a CSF is a qualitative statement of what must go right for the objective to be met; a KPI is the measure that tells you whether the CSF is being met; a metric is any other measurement collected for context. Then apply the time test: leading indicators predict a future outcome (test coverage, change lead time, backlog trend), lagging indicators report an outcome already realised. Questions asking what to watch or what to change next want a leading indicator.
Applying the guiding principles as a checklist or fixed sequence - for example, deciding that 'keep it simple and practical' must be completed before 'optimize and automate', or rejecting an option because it 'skips' a principle.
Candidates trained on frameworks with ordered phases expect ordered steps, and the numbered list in the material invites a sequence reading.
What to do instead
State the rule to yourself before answering: the seven principles are recommendations applied together and simultaneously, they are not mandatory and they are not sequential. In option analysis, an answer that contradicts 'focus on value' or 'start where you are' is wrong regardless of how efficient it sounds; an answer that merely applies the principles in a different order is not wrong.