ITIL 4 SL common mistakes
ITIL 4 SL · Understand the traps and how to avoid them.
DITS: When a scenario asks who should own, fund, or govern a digital initiative, the candidate selects the option that assigns accountability to the IT function alone, or treats the digital strategy as a technology roadmap with milestones for systems.
Most candidates come from an IT operations or service management background and have internalised the older 'IT strategy = align technology with the business' model. DITS separates an organisation-wide digital strategy (business model, customer experience, culture, revenue) from an IT strategy (technology direction and how IT enables it), and questions are written to punish the collapse of the two.
What to do instead
Before reading the options, ask one question: 'Is this about how the whole organisation creates and captures value, or about how technology is run and delivered?' If it is the former, eliminate every option that makes it a technology-only decision or a CIO-only accountability. Keep a two-column comparison sheet (digital strategy vs IT strategy) and re-read it immediately before each mock paper.
DITS: In scenarios describing rapid market or technology change, the candidate chooses the option that restores predictability - a fixed multi-year plan, a detailed upfront requirements phase, tighter central control - rather than the option that increases sensing and adaptability.
Risk aversion plus prior training in plan-driven delivery. Words like 'plan', 'standardise' and 'control' feel like the safe, mature answer, and 'experiment' and 'iterate' feel unbusinesslike to candidates who have been rewarded for certainty.
What to do instead
Build two paired lists and rehearse the mapping. Cue words: volatile, uncertain, ambiguous, rapid, emerging, disruptive, unknown. Response family: shorter planning cycles, options and experiments, decentralised decision rights, sensing mechanisms, willingness to stop things. In the exam, underline the cue words in the stem before looking at the options - the cue should trigger the response family, not a preference.
DITS: On innovation items, the candidate labels an incremental improvement to an existing product for existing customers as 'disruptive innovation', or rejects a genuinely disruptive option because it is described as initially cheaper or lower-performing.
Everyday usage of 'disruptive' means 'big' or 'radical'. The exam uses the stricter economic meaning, where disruption begins at the low end or in an underserved segment with an offer that is simpler and initially inferior on the attributes mainstream customers value, then improves until it threatens incumbents. A candidate using the colloquial meaning will invert the correct answer.
What to do instead
Memorise a three-part test and apply it to every innovation option: (1) does it serve a new or overserved/underserved segment? (2) is it initially weaker on mainstream performance attributes? (3) does its improvement trajectory eventually threaten the incumbent? Classify ten familiar real-world examples against the test until the pattern is automatic.
DITS: On digital risk questions, the candidate picks the most conservative option - avoid the initiative, delay it, add more controls, require full certainty - instead of an option that keeps the initiative inside a stated risk appetite.
Risk management is usually taught defensively, so 'good practice' is equated with minimising exposure. DITS treats risk-taking as the mechanism through which digital strategy delivers value, and the examined skill is balancing opportunity against risk rather than removing risk.
What to do instead
Learn the distinctions between risk appetite, risk tolerance and risk profile. On every risk item, first check whether the stem supplies an appetite or tolerance statement. If it does, prefer the option that keeps activity inside that boundary (proportionate controls, staged commitment, exit criteria) over any option that eliminates the exposure entirely.
DITS: The candidate can recite the digital leadership concepts but, given a scenario, selects the directive or purely technical response rather than matching the capability to the symptom described - for example answering a stem about low psychological safety and poor idea-sharing with tighter governance and clearer reporting lines.
Revision by flashcard definition produces recall without discrimination. Leadership concepts are learned as a list of nouns (emotional intelligence, digital mindset, coaching, collaboration) with no attached 'when you would use this' trigger, so the exam's symptom-to-response matching cannot be performed.
What to do instead
For each leadership concept write a single line in the form 'symptom in the stem -> leadership response'. Examples: low trust or fear of speaking up -> empathy, psychological safety, coaching; leaders out of touch with customers -> customer immersion, value stream involvement; decisions bottlenecked at the top -> delegated decision rights. Then practise scenario-only questions, underlining the symptom before choosing.
DPI: On questions about a manager acting or deciding, the candidate selects an option that assumes authority over teams, suppliers or customers the person only influences - or, conversely, declines to act on something the person clearly can influence.
'Control' and 'influence' are used interchangeably in ordinary speech, but the exam treats them as a precise boundary. Candidates who have not internalised the boundary default to the answer that sounds most decisive, which is usually the one that exceeds the role's authority.
What to do instead
Before answering, sketch two circles. Into 'control' put only what the role owns: its own resources, its own processes, its own decisions. Anything else is influence-only. Any option that requires a decision over an influence-only item is wrong; the correct answer will be framed as persuade, negotiate, build a business case, or escalate. Practise by classifying five options per question as control or influence before selecting.
DPI: When a stem describes resistance to a new way of working, the candidate answers with change enablement machinery - raise a change request, route it through the change authority, schedule a CAB review - instead of addressing adoption.
Change enablement is the better-known ITIL practice and the word 'change' triggers it reflexively. Candidates do not pause to distinguish a change to a service or configuration item from a change in what people do, believe or are capable of.
What to do instead
Sort the stem in one step: is it about technology, configuration or a live service, or is it about people's behaviour, willingness and capability? Technology -> change enablement. People -> organisational change management, addressed through sponsorship, stakeholder engagement, communication, capability building and reinforcement. Choose the toolkit first, then the option.
DPI: On measurement questions, the candidate picks activity or output indicators - number of changes deployed, tickets closed, training sessions delivered, dashboards published - where the stem asks how to know whether the plan or improvement is achieving its objective.
These are the numbers teams already report, so they feel measurable, available and therefore 'correct'. Candidates also blur critical success factors, KPIs and metrics into a single idea of 'things we count'.
What to do instead
Learn the hierarchy explicitly: vision or objective -> critical success factors -> KPIs -> metrics. For each candidate indicator apply one test: 'If this number improves, does it prove the objective was achieved, or only that we were busy?' If it only proves busyness, reject it. Also tag each candidate as leading or lagging and check which type the stem is asking for.
DPI: On 'what should be done first / next' improvement questions, the candidate jumps to implementation - pilot it, buy the tool, roll it out - rather than answering with an earlier step such as understanding the current state, agreeing the target, or planning the approach.
Action bias, combined with memorising the continual improvement model as a list of seven labels rather than as a set of gates. Without knowing what each step rules out, every option containing a verb like 'implement' looks like progress.
What to do instead
Memorise the seven questions in order and write beside each one what it forbids. Vision forbids solutioneering. Where are we now forbids proposing remedies. Where do we want to be forbids acting before a measurable target exists. How do we get there forbids starting work. Use the forbidden-actions column to eliminate options rather than picking the most energetic one.
DPI: On governance items, the candidate assigns accountability to the service provider or IT director, or swaps the three governing activities - choosing 'monitor' when the stem describes setting direction and objectives, or 'evaluate' when the stem describes a performance review.
Governance is often experienced second-hand as reporting, and the three verbs sound interchangeable at a glance. Candidates also import the assumption that the team doing the work is accountable for governing it.
What to do instead
Anchor governance to the governing body and drill the three verbs until they separate cleanly: evaluate (assess needs, options, performance), direct (set direction, policy, plans, roles, constraints), monitor (check performance and compliance against direction). For each stem ask one question - is the body assessing, deciding, or checking? - and eliminate options that place accountability below the governing body.